Process
Sell, define, govern: the three documents
The contract sinks more than bad design.
Nobody hires a studio because the paperwork is good. But we've watched more client relationships go sideways over a fuzzy contract than over a weak layout. Three documents do three different jobs here, and the whole mess starts with confusing them for each other.
Get the three straight and the relationship stays calm. Blur them and every disagreement in month three has nowhere to land.
Here's your problem, here's how we'd solve it, here's what it costs, here's why us — a proposal is allowed to be a little aspirational. The mistake people make is treating it as the agreement. It isn't. It's the pitch, and a pitch is where the work starts, not where it's pinned down.
Where the proposal says redesign your site for this price, the statement of work says exactly which pages, exactly how many revision rounds, exactly what the client owes us to keep moving, exactly when each milestone is due. It is the document you hold each other to when memories start to differ.
The master agreement is the legal floor under the whole relationship, signed once. Who owns the work when it's done, what's confidential, what happens if someone walks. The most-argued clause is always ownership: who owns the design and the code at the end. Settle that in writing before there's anything to fight about.
Sign the pitch as the contract and you've agreed to a mood, not a scope.
Fold all three into one.
You don't need three separate fat documents flying around. Fold all three into one well-designed agreement: pricing up front, then the approach and the problem, then the phases and the deliverables, then the legal terms at the back.
One object, signed once. It reads like a considered thing instead of a stack of contracts, and it gets signed faster because the client isn't waiting on their lawyer to reconcile documents that half-contradict each other.
A SOW earns its keep in month three, when memories start to differ and someone reaches for the document. Exact is what protects both sides. The boring version is the one that ends the argument before it starts.
Ownership is the clause always argued last, which is exactly why it should be named first. Named early, it's a sentence. Named late, it's a dispute.
A good statement of work is boring on purpose.
Boring is what protects both of you. Exact pages, exact rounds, exact milestones, written down before there's a disagreement to have.
The paperwork is part of the craft. It's the same reason the site brief exists before a proposal ever gets written, and why our process starts with getting the scope exact instead of exciting.