Three words come up in every freelance article: brief, scope of work, proposal. Articles use them interchangeably. They're not interchangeable.
Confusing them is the reason freelancers send the wrong document at the wrong moment — pitching pricing too early, defining scope too late, or signing nothing because the contract template "felt enterprisey."
Here's the quick guide. What each is, when to send it, who signs, and what happens when you skip the wrong one.
The 30-second version
| Document | Job | Sent | Signed by | |---|---|---|---| | Proposal | Sell the work | After discovery call | Optional (sales tool) | | Brief / SOW | Define the work | After client says yes | Always | | Contract / MSA | Define the relationship | Once per client | Always |
If you only do one: brief, signed. The other two are recoverable. A scope dispute without a signed brief is not.
Proposal: the sales document
A proposal is a pitch in document form. Its job is to win the deal, not to lock down the work.
What's in it:
- Cover with brand and project name
- Outcome paragraph (what success looks like for the client, in their terms)
- Approach section (your method — phases, methodology)
- 2-3 pricing tiers (the middle one usually wins)
- Timeline overview
- Why-me section (relevant past work, expertise)
- A clear next step (pick a tier, sign here, schedule the kickoff)
- Validity date (proposals expire, otherwise they sit open for months)
What's NOT in it:
- Detailed deliverables (those go in the brief)
- Out-of-scope list (also in the brief)
- Acceptance criteria
- Payment terms in legal detail
- Liability or IP clauses
When to send: after the discovery call, before any work begins. The client should be in "deciding" mode, not "researching freelancers" mode.
When you skip it: you go from "yeah maybe" to "what's it cost?" with no narrative. Clients pick on price alone. Or worse, you skip straight to a brief and the client treats it as a giveaway estimate they're not committed to.
Length: 2-4 pages. Short enough to read in one sitting. Long enough to differentiate.
Brief / Scope of Work: the definitional document
The brief (often called scope of work, or SOW) is what you actually build to. Its job is to lock down what's being delivered.
In freelance, "brief" and "SOW" are usually the same document. The terms diverge in larger engagements:
- Brief = standalone document used by smaller projects + agencies
- SOW = formal scope inside a Master Service Agreement, typically for retainers with multiple sub-projects
For a typical freelance engagement, pick one term and stick with it. Don't send both.
What's in it:
- Project overview (2-3 sentences anyone can understand)
- Scope of work — every deliverable, painfully specific
- Out of scope — every related thing you are NOT doing (this section is what saves you)
- Timeline with milestones and dates
- Budget and payment terms (specific dollars, specific dates)
- Technical requirements (stack, hosting, integrations)
- Acceptance criteria (how "done" is measured)
- Revision policy (X rounds included, $Y per additional round)
- Signatures from both parties
What's NOT in it:
- Sales pitch language (the proposal already did that)
- Multiple pricing tiers (one tier — the one they picked)
- Marketing copy or differentiation pitch
- Legal boilerplate (that's in the contract)
When to send: after the proposal is accepted. Client signs this BEFORE you start work.
When you skip it: every "while you're in there" becomes a free addition. Every "small revision" becomes the third revision. You have no document to point at when scope expands. ~80% of freelance disputes trace back to a missing or vague brief.
Length: 2-4 pages. Same as the proposal but for a different reason: long enough to be specific, short enough that the client actually reads what they're signing.
Contract / MSA: the relationship document
The contract (Master Service Agreement) defines the legal frame around the work, not the work itself.
What's in it:
- Parties (legal entities, addresses)
- Payment terms (currency, late fees, dispute process)
- IP ownership (who owns the deliverables, when ownership transfers)
- Confidentiality / NDA clauses
- Liability caps (typically capped at fees paid)
- Termination rights (kill fee, notice period)
- Governing law and jurisdiction
- Indemnification
What's NOT in it:
- The actual deliverables (those are in the brief, attached as an exhibit)
- Pricing for THIS specific project (that's in the brief or proposal)
- Sales-y language
When to send: once per client, for the relationship — not per project. If the client signs a long-form MSA, every subsequent project just needs an SOW exhibit referencing it.
When you skip it: you're operating without legal protection on IP, liability, payment recovery. Most freelancers get away with no MSA for years. Then one project goes sideways and they realize the cost of that gap.
Length: 4-12 pages depending on how aggressive the lawyer was. Tools like LegalZoom and Bonsai have decent templates.
How they fit together
DISCOVERY CALL
↓
[ PROPOSAL ] ← sells the work, pricing tiers
↓
client picks a tier
↓
[ BRIEF / SOW ] ← defines exactly what gets built
↓
both sign
↓
work begins, governed by the brief
↓
ALL backed by [ MSA / CONTRACT ] ← signed once per client
For a small project (under ~$5K) you can collapse:
- Proposal + brief into ONE document (a "brief proposal")
- Skip the MSA and use a one-page service agreement instead
For a larger project (over ~$10K) you should keep them separate:
- Proposal sells. Brief locks. MSA protects.
The one mistake to never make
Sending pricing in a brief that hasn't been preceded by a proposal.
When the brief is the first place the client sees a number, they treat it as an opening offer to negotiate. When the brief LOCKS IN a number that the proposal already set, they treat it as a commitment they made.
The order is:
- Discovery (figure out what they need)
- Proposal (pitch + price)
- Client says yes to a tier
- Brief (lock the scope at that price)
- Sign + start
Skipping straight to brief = price negotiation in the wrong document, every time.
Side-by-side: same project, three documents
For a hypothetical $6,800 dental practice website (the example from our brief examples post):
Proposal (3 pages):
- "We help service businesses like yours turn website traffic into booked appointments"
- 3 tiers: Starter $4.5K, Standard $6.8K, Premium $9.5K
- Approach: 6-week sprint, 2 design rounds, launch + 30-day warranty
- Why-us: 12 dental + medical sites built, average 40% increase in inbound calls
Brief (4 pages):
- 5 specific pages, listed
- Out of scope: appointment booking, patient portal, blog
- Specific Stripe-equivalent payments milestones at 50/25/25
- Acceptance: site loads under 2s, all pages mobile responsive on tested devices
- Revision policy: 2 rounds included, $95/hr for additional
Contract / MSA (6 pages):
- IP transfers on final payment
- Liability capped at total fees paid
- 30-day cure period before termination
- Net-30 payment terms with 1.5%/month late fee
- Governing law: state of [freelancer's state]
Three documents, three different jobs. Each does its job well only because it's not trying to do another's.
When you can simplify
Solo freelancer doing $1-5K projects? You can:
- Use a "brief proposal" combining the sales pitch + scope
- Use a one-page service agreement instead of a full MSA
- Get email confirmation instead of a legal signature for low-risk work
Just don't skip the scope-defining part. Whatever you call it, whatever format it takes — there must be a written, agreed list of:
- Deliverables (what's in)
- Exclusions (what's out)
- Acceptance criteria (when "done")
- Payment schedule (when money moves)
Without those four, you're operating on faith. Faith doesn't hold up when the deal goes sideways.