Most freelance proposals lose for the same reason: they are about the freelancer. Three paragraphs of background, a portfolio link, a list of services, and a price at the bottom. The client has to do the work of figuring out whether any of it solves their problem.
A proposal that wins does the opposite. It starts with the client's situation, shows a specific plan, gives a clear choice, and makes the next step obvious. It is usually shorter, not longer.
TL;DR
A winning proposal opens by restating the client's problem in their own words, then lays out a specific scope with deliverables, timeline and exclusions. It offers two or three priced options rather than a single take-it-or-leave-it number, and it ends with one clear action for the client to take. Send it quickly after the discovery call, and follow up on a schedule you decide in advance.
Before you write: earn the right to propose
The strongest proposals are written after a real conversation. A 20–30 minute discovery call gives you three things you cannot get from a brief:
- The actual problem, which is often different from the request ("we need a new website" may really mean "our current site does not generate leads").
- The constraints, including budget range, deadline and who else is involved in the decision.
- The language the client uses, which you will mirror in the proposal.
If a client refuses any conversation and just wants a price, you can still send one, but expect a lower win rate and price accordingly.
The structure that works
Keep it to what the client needs to make a decision. A reliable structure:
1. The situation (one short paragraph)
Restate what you heard. "You are launching a new service line in Q4 and your current site has no way to explain it or capture inquiries. The team wants something live before your October campaign." If the client reads this and nods, you have already done more than most competitors.
2. The outcome
What will be different when the work is done? Keep it concrete: "a site that explains the new service and routes inquiries to your sales inbox", not "an elevated digital presence".
3. The scope
This is the heart of the proposal. List:
- Deliverables, counted and specific (five page templates, two revision rounds each)
- Exclusions, the things a reasonable client might assume are included but are not
- Assumptions, such as the client supplying copy by a certain date
- Timeline, with key milestones rather than a single end date
If you are pricing this as a fixed fee, the post on how to scope a fixed-fee project covers how to write each of these so they hold up.
4. Options and pricing
5. Next step
One sentence. "To go ahead, accept the option that suits you and we will send the contract and deposit invoice." Not three possible next steps. One.
Offer options, not a single price
A single price invites a yes-or-no decision, and "no" is easy. Two or three options change the question to "which one?"
An illustrative example for a website project:
| Included | Essentials | Recommended | Extended |
|---|---|---|---|
| Page templates | 3 | 5 | 5 |
| Revision rounds | 1 | 2 | 3 |
| Copywriting | Client supplies | Client supplies | Included |
| Post-launch support | — | 2 weeks | 30 days |
| Price | 3,500 | 5,500 | 8,000 |
A few rules make options work:
- Each option should be a real, deliverable project, not a decoy you hope nobody picks.
- Vary scope, not just price. If the client wants the lower price, they take less scope. That protects your rate.
- Mark one as recommended and say why in a sentence.
- Three is usually the ceiling. More options make the decision harder, not easier.
The pricing model behind each option matters too. If parts of the work are genuinely unpredictable, consider a hybrid. The post on hourly vs fixed fee vs retainer pricing covers when each one fits.
What to leave out
- Long company histories. One line of credibility, plus a link to relevant work, is enough.
- Every service you offer. Only what applies to this project.
- Legal terms in full. The proposal sets out what and how much; the contract handles the legal detail. Mention that a contract follows acceptance.
- Vague value claims. "We deliver results" says nothing. A relevant case example, described honestly, says a lot.
Make accepting easy
A proposal that has to be printed, signed, scanned and emailed back loses momentum. The easier it is to say yes, the more often clients do.
With COLO, the client reviews and approves your proposal through the client portal, and the contract that follows is signed in the same place, so there is less of a gap between "yes" and "start". If you prefer to work from a document, the freelance proposal template follows the structure above.
Follow up on a schedule
Most freelancers send a proposal and then wait, hoping. Decide your follow-up schedule before you hit send. A simple one:
- Day 0: Send the proposal with a short note restating the recommended option.
- Day 3: Check whether they have any questions about scope or options.
- Day 7: Offer a short call to walk through it, or ask whether the timing has changed.
- Day 14: A final, friendly close-out: "I will assume this is on hold for now. Happy to pick it up whenever suits."
Keep each follow-up short and useful. A question about their timeline or a small clarification is better than "just checking in". And the day-14 message often gets a reply, because it gives the client permission to be honest.
FAQ
How long should a freelance proposal be?
As short as it can be while still defining the scope clearly. For most small to mid-sized projects, two to four pages is plenty. Length is not a signal of quality.
Should I include a proposal fee for large projects?
For complex projects where the proposal itself requires significant analysis, a paid discovery or scoping phase is reasonable. It also filters out clients who are only collecting quotes.
What if the client asks for a discount?
Offer to reduce scope rather than price. Moving them to a smaller option keeps your rate intact and keeps the conversation about value.
How quickly should I send the proposal after the call?
While the conversation is still fresh for the client. Within a day or two is a good target for most projects.
The proposal is the first deliverable
Clients judge how you will run their project by how you run the proposal. A clear, specific, well-structured document sent promptly tells them the project will be clear, specific and well-run too. That is often what wins the work. For the next step after a yes, the freelance contracts guide and the post on the client onboarding process pick up from there.