Guide · updated 6 November 2026
Proposal vs statement of work vs contract
A proposal wins the work. A statement of work defines it. A contract governs the relationship around it. Here's what goes in each, when a freelance developer needs which, and when one document can do the job of all three.
Side by side
| Compare | Proposal | Statement of work | Contract |
|---|---|---|---|
| Its job | Win the work: the problem, your approach, the price | Define the work: exactly what's delivered and how it's accepted | Govern the relationship: liability, ownership, payment, ending it |
| When it's sent | First, before the client has decided | After a yes, before work starts (bigger projects) | Before work starts; often once per client, reused |
| Who reads it closely | The person deciding to hire you | The people checking the work: product owner, project manager | Legal, finance, the founder |
| What's in it | Overview, approach, scope, estimate, timeline, payments, a next step | Deliverables, acceptance criteria per milestone, dependencies, change control | Ownership of work, confidentiality, liability limits, payment terms, termination |
| Tone | Persuasive and plain | Precise and testable | Formal |
| Changes later | Send a new version | A change order, approved in writing | An amendment, signed by both |
How they fit together
On a bigger project, in order: the proposal makes the case and gets a yes; the statement of work turns that yes into milestones with acceptance criteria; the contract (often a master agreement you reuse with the same client) carries the legal terms; and anything that changes later goes through a written change order that points back to the approved version.
On a small project, one document is often enough: a proposal that includes the scope, the price, payment terms, what's excluded, who owns the work and how changes are handled, approved by the client in writing. Many freelancers work this way for jobs of a few weeks. For larger or riskier work, keep the contract separate, and have a lawyer read your terms once.
What not to do: put the legal terms only in an email thread, or start work on a verbal yes. If it isn't in a document the client approved, it's your memory against theirs.
See each one written out
Questions people ask
Is a statement of work a contract?
It can be. A signed statement of work that sets out the work, the price and the terms can be binding on its own; more often it sits under a master agreement that holds the legal terms, and each SOW covers one project. Whether a document is binding depends on where you are and what it says, so for large contracts have a lawyer read your terms once.
Can a proposal be a contract?
For small jobs it often works as one: if the proposal states the scope, price, payment terms and ownership, and the client approves it in writing, many freelancers treat that as the agreement. It isn't legal advice, and for bigger or riskier work a separate contract is safer.
Which comes first, the proposal or the SOW?
The proposal. It wins the work; the statement of work then pins down what “done” means for each milestone before work starts. On small projects the two are often the same document.
Do I need a master services agreement?
If you'll do several projects for the same client, one agreement with the legal terms plus a short SOW per project saves renegotiating liability and ownership every time. For a one-off job, a proposal with clear terms or a single contract is usually enough.
What's the difference between a scope of work and a statement of work?
A scope of work is the list of what's included (and, ideally, excluded). A statement of work contains the scope plus how it's delivered and accepted: milestones, acceptance criteria, dependencies, change control and the price.
This guide explains common practice; it isn't legal advice.