Winning work
How to write a freelance proposal that wins the work
8 min read
A proposal is not a description of your services. It is an argument that you understand the client's problem well enough to be trusted with it, followed by the easiest possible yes.
Start from their words, not yours
Open with the problem as the client described it on your call, using their language and their numbers. If they said "we lose half a day a week to quoting", write that, not "operational inefficiency".
This single move separates proposals that get read from proposals that get filed. It also protects you: if you cannot state the problem crisply, you do not yet know enough to price the work.
The structure that carries the argument
- 1.Situation: two or three sentences on where the client is now, in their words.
- 2.Outcome: what will be true when the work is done, stated as a result rather than an activity.
- 3.Approach: the phases, with what happens in each and roughly how long it takes.
- 4.Deliverables: a specific, countable list. Anything not listed is out of scope.
- 5.Investment: the price, ideally as two or three options rather than one figure.
- 6.Practicalities: timeline, what you need from them, revision rounds, and payment terms.
- 7.Next step: one action, with a date.
Price with options
A single price invites a yes/no decision. Two or three scoped options change the question to "which one", and they let a client who wants you but has less budget still say yes.
Anchor with the fullest option first, then a core option, then a minimal entry point. Keep the difference in scope obvious — fewer deliverables, not vaguer ones.
- Quote a project fee rather than an hourly rate wherever the outcome is definable.
- State the deposit and the payment schedule in the proposal, not after acceptance.
- Give the price a validity date so it does not get reused six months later.
Scope defences that avoid arguments later
- Name the number of revision rounds and what counts as a round.
- List explicit exclusions for the things clients most often assume are included.
- State your dependency on their inputs — feedback windows, content, access — and what happens to the timeline if they slip.
- Add a short change-request clause: new scope is quoted separately before it starts.
Length, format and follow-up
Two to four pages beats twenty for most freelance work. Lead with the situation and outcome so a skim of the first page is enough to decide to read on.
Send it when you said you would, then follow up once after three working days and once more a week later. Ask a question in the follow-up — "is the phased option closer to what you had in mind?" — rather than only checking in.
Common questions
- How long should a freelance proposal be?
- Two to four pages for most projects. The decision-maker should be able to understand the problem, outcome and price from the first page alone.
- Should I include the price in the proposal?
- Yes, and ideally as two or three scoped options. Withholding price forces an extra round of emails and loses momentum.
- How many times should I follow up on a proposal?
- Twice is normal: once around three working days after sending, once a week later. Each follow-up should ask a question that is easy to answer.