A contract that arrives with the yes

The contract on most small projects was never refused. It was never sent. Sending it would have meant a second document, a second email a few days after the friendly one, and being the person who made a warm arrangement formal. So the project ran on the proposal, or on a thread, and the terms got worked out in week six when it was too late for them to be terms.

North removes the second document. The agreement is drafted alongside the proposal, from the same scope and the same terms, and the client sees it the moment they accept. The terms arrive attached to the decision rather than as a hurdle a week later.

What the agreement is

It is not a paragraph of legalese the software wrote on the spot. It is a standard body of ten plain-language clauses, written to protect the freelancer, with the deal's own terms filled in from the option the client accepts: what is being delivered, for how much, on what schedule.

The ten, by heading: the engagement; fees and payment; scope and revisions; timeline and the client's responsibilities; ownership and intellectual property; cancellation and payment for completed work; confidentiality; independent contractor status; limitation of liability; and general terms. That is the set a working freelancer needs and roughly the set a client's finance department will accept without a call. The elaborate dispute-resolution ladders and mutual-indemnity boilerplate that get copied from software agreements are not in it, on purpose.

You read the clause body while you are reviewing the proposal, in the same sitting. You can edit any clause. What you cannot do is send a contract that disagrees with the offer it travels with, because the price and scope are the proposal's, filled in at acceptance.

How the client signs

They accept the proposal in their deal room, and the agreement appears. To sign it, they verify their email address once, by a link sent to them, so the signature is bound to a real person and not to whoever had the browser open. The signature is recorded with that address and the time. From that moment the signed document is the record: the proposal, the option chosen, the terms, and the signature, in one place both of you can open.

You are told the moment it is signed, by email, on every plan. If the terms need to change later, you amend and reissue; the previous version stays on file, and the client sees which one is current.

The two lines that matter

The contract is yours. North drafts it, you edit it, you send it, and from the moment it goes it is an agreement between you and your client, in your name.

North is not a lawyer. It drafts and it explains, and it can be wrong. The clause body is written for the ordinary small creative project, and that is most projects, but it is not written for your jurisdiction specifically, for a client with unusual requirements, or for a job where real money or safety is on the line. At those moments the right move is twenty minutes with someone qualified before you send. North will say so when a question crosses that line, rather than hedging everything else it has told you.

The thing a contract cannot do

It cannot make you paid. A contract wins you a strong position in a dispute, and a dispute is a project with its own costs and a modest chance of ending in money. What makes you paid is the deposit, banked before work starts, and the final files, held until the balance clears. The agreement's payment clause writes both of those in. The rest is up to the order you do things in: deposit first, scope in writing second, signature third, on every job, including the friendly one.