Most freelance proposals don’t lose work because the price was too high or the portfolio wasn’t strong enough. They lose work because the proposal itself was weak — generic, vague, or written entirely from the freelancer’s perspective instead of the client’s.
A proposal isn’t a formality you fill out after a good discovery call. It’s a sales document. It’s often the last thing standing between you and a signed contract. Treat it accordingly.
What a proposal is actually doing
Before getting into structure and tactics, understand what a proposal is trying to accomplish.
It’s not a quote. A quote gives a number. A proposal builds the case for why that number makes sense — and why you are the right person to deliver it.
By the time someone reads your proposal, they’ve already spoken to you. They’re interested. The proposal’s job is to confirm that interest, remove doubt, and make saying yes feel like the obvious next step.
Every section of a good proposal is doing one of three things: demonstrating understanding, building confidence, or reducing friction.
The mistake almost everyone makes
Most freelance proposals are written about the freelancer.
“I am a designer with 5 years of experience. I specialise in branding and web design. Here are my services and my rates.”
That’s a CV, not a proposal. The client already knows roughly what you do — they got on a call with you. What they need to see in the proposal is that you understand them — their problem, their context, what success looks like, what’s at stake.
Flip the focus. Make the proposal 80% about them and 20% about you. The moment a client reads a proposal and thinks “they actually get what we’re trying to do” — you’ve won more than half the battle.
The structure that works
There’s no single correct format. But there is a logical sequence that moves a client from “interested” to “ready to sign.” Here’s what that looks like in practice.
1. The opening — show you were listening
Start with your understanding of their situation. Not a generic intro. Not “thank you for the opportunity.” A sharp, specific summary of what they told you on the call — the problem they’re trying to solve, the context around it, and what they’re hoping to achieve.
This does something important: it proves you were paying attention. It also gives the client a chance to correct you if you’ve misunderstood something — which is far better than discovering that misalignment three weeks into the project.
Keep it to two or three short paragraphs. Specific and confident, not exhaustive.
Example framing: “You’re launching a new service line in Q3 and need the website to reflect that shift before the campaign goes live. The current site is functional but doesn’t communicate the positioning clearly enough for enterprise buyers — which is the audience this launch is targeting.”
That’s a real understanding of a real problem. It reads completely differently from “we understand you need a website redesign.”
2. The proposed approach — what you’re going to do and why
This is where you walk through your solution. Not a bullet list of deliverables yet — that comes later. This section is about thinking.
What’s your approach to solving their problem? Why are you recommending what you’re recommending? What have you seen work in similar contexts?
This is the section that builds the most confidence. Anyone can list deliverables. Not everyone can explain the strategic reasoning behind them in a way that makes a client feel like they’re in good hands.
Keep it readable. Short paragraphs, plain language. You’re not writing a technical document — you’re having a written conversation with someone who needs to trust you.
3. Scope of work — what’s included, exactly
Now get specific. List every deliverable clearly. Not vague categories — actual outputs.
Not: “Website design” But: “Design of up to 8 page templates — Homepage, About, Services overview, Individual service page, Case study, Blog index, Blog post, Contact — delivered as high-fidelity Figma files ready for development handoff.”
The more specific your scope, the less room there is for “I thought that was included” conversations later. Specificity protects both sides.
Also state clearly what is not included. This feels counterintuitive — why draw attention to what you’re not doing? Because it prevents the single biggest source of freelance conflict: scope creep born from assumptions.
“This proposal does not include copywriting, SEO setup, or third-party plugin costs. These can be scoped separately if needed.”
One sentence. Saves weeks of friction.
4. Timeline — phases, not just a final date
Give the client a phased timeline, not just an end date. Break the project into logical stages with approximate durations and milestones.
This does two things. It shows the client you’ve thought through how the work actually happens — which builds confidence. And it sets the expectation that their responsiveness affects the timeline, which you can then reinforce in your kickoff call.
Something like:
- Week 1–2: Discovery and strategy
- Week 3–4: Initial concepts and direction
- Week 5: Refinement based on feedback
- Week 6: Final delivery and handoff
Adjust for your project type. The point is that a timeline with phases feels considered. A single delivery date feels like a guess.
5. What you need from them
This section gets left out of most proposals. Don’t leave it out.
Clients often don’t realise how much a project depends on them. Content, brand assets, access to platforms, internal approvals, timely feedback — all of these affect whether you can deliver on time.
Listing what you need from them upfront does two things: it sets professional expectations, and it surfaces potential blockers before the project starts rather than in the middle of it.
“To begin, I’ll need: existing brand assets and guidelines, access to the current website backend, confirmed sitemap or content structure, and a designated point of contact for approvals.”
Simple. Clear. Prevents the most common mid-project slowdown.
6. Investment — present the price with confidence
Don’t bury the price. Don’t apologise for it. Present it clearly, broken down in a way that makes sense given the scope you’ve just described.
If you’ve done the proposal right up to this point — shown understanding, outlined the approach, detailed the scope, broken down the timeline — the price should feel like a natural conclusion, not a shock.
A few things that help the investment section land well:
Break it down by phase or deliverable — not because you’re justifying every line item, but because it helps the client understand what they’re getting for what they’re paying. A single lump sum can feel opaque. A structured breakdown feels transparent.
State payment terms clearly — 50% upfront, 50% on delivery. Or thirds: kickoff, midpoint, final. Whatever your structure, spell it out. Don’t leave it for the invoice.
Include what happens outside scope — “Additional work or rounds of revision beyond those included will be quoted separately and agreed before proceeding.” One sentence that prevents a lot of awkward conversations.
On the number itself — charge what the work is worth, not what you think they can handle or what you think sounds reasonable. If the project will take 40 hours and your rate is X, the price is X times 40 — not X times 40 minus a discount to seem more competitive. Discounting before you’ve even been asked is leaving money on the table and signalling that the price was soft to begin with.
7. Why you — briefly
This is not the place for a long biography. A short paragraph — three to five sentences — that speaks directly to why you’re the right person for this project specifically.
Reference relevant experience. Name a similar type of problem you’ve solved. If you have a testimonial that’s directly relevant, one short line from it here is worth more than three paragraphs of self-description.
Keep it grounded. Confidence without arrogance. You’re not trying to impress them — you’ve already done that on the call. You’re just reinforcing the decision they’re already leaning toward.
8. The close — make the next step obvious
End with a clear call to action. Not “let me know if you have any questions.” That leaves the ball in the air.
Tell them exactly what happens next:
“If this looks right, the next step is to sign the agreement and send through the first payment. I’ll then send across the project contract and we can schedule the kickoff call. Happy to jump on a quick call if you’d like to talk through anything first.”
Clear. Specific. No ambiguity about what “yes” looks like.
The design of the proposal matters too
Content comes first. But presentation isn’t irrelevant.
A proposal that’s well laid out — clean typography, clear sections, consistent formatting, your branding — communicates professionalism before the client reads a word. It signals that you operate at a certain standard.
You don’t need a complex template. You need something that’s easy to read on a screen, clearly structured, and looks like it was made with care. Notion, Google Docs with clean formatting, a simple PDF — all fine. What’s not fine is a wall of unsectioned text sent as a plain email.
Tools worth knowing: Notion, Better Proposals, Prospero, or even a well-designed Google Docs template you’ve built once and reuse. The goal is something that looks intentional and is easy to navigate.
Timing and follow-up
Send the proposal within 24–48 hours of the discovery call. Not a week later. The momentum from a good conversation cools fast — a prompt proposal keeps it warm.
If you haven’t heard back in three to four days, follow up. Not a “just checking in” message — something with a bit more substance.
“Wanted to make sure the proposal landed okay and see if anything came up that you’d like to talk through. Happy to jump on a quick call if that’s easier.”
One follow-up is professional. Two is the limit. If there’s still no response after two, move on — and leave the door open politely.
“Completely understand if the timing isn’t right. Feel free to reach out whenever it makes sense — happy to revisit.”
That message has won back projects months later. People remember how you handled the silence.
When they push back on price
It will happen. How you handle it matters.
First, don’t immediately offer a discount. Ask a question instead: “Is it the total investment, or is it more about the payment timing?” Often it’s the latter — they can do the project, they just can’t front the full amount. A payment structure adjustment solves that without touching your rate.
If they genuinely can’t meet the budget, the right move is to reduce scope — not price. “We could bring this within that budget by starting with phases one and two and building out the rest later. Would that work?”
This protects your rate, gives them a path forward, and positions the reduced version as a strategic choice rather than a compromise.
If the budget is just incompatible with what needs to be done — be honest about it. “To deliver this properly, I can’t get below X. If the budget is fixed at Y, I want to be upfront that I don’t think I could do the work justice at that level.” Then let them decide. Sometimes they find more budget. Sometimes they don’t. Either way, you’ve maintained your integrity and your rate.
A few things that kill proposals quietly
- Sending it too long after the call
- Writing in generic language that could apply to any client
- Listing deliverables without any context or reasoning
- Including a long agency-style credentials section nobody reads
- Vague scope that leaves room for interpretation
- Not stating what you need from the client
- Ending without a clear next step
- Typos — especially in the client’s name or company name
That last one sounds obvious. Check anyway.
The compounding effect of a good proposal
Here’s the thing about building a solid proposal process: it gets faster every time. The first few take effort. By the tenth, you have a template that’s battle-tested, language you trust, and a structure you can adapt in under an hour.
And the better your proposals get, the less you need to compete on price. Clients who receive a proposal that clearly understands their problem and maps a credible path to solving it — they’re not shopping around the same way. You’ve already differentiated yourself from most of the competition by doing the thinking properly upfront.
That’s the compounding return on getting this right.
Leave a Reply
You must be logged in to post a comment.