Two freelancers with near-identical skills bid on the same project. One wins it; the other never hears back. Nine times out of ten, the difference wasn't talent, price, or even the work itself — it was the proposal. A proposal isn't paperwork you send after the real selling is done. For most client relationships, it is the selling: the single document a prospect reads, alone, when deciding whether to trust you with their money — the closing move at the end of your lead-generation funnel. Treat it as an afterthought and you'll lose work you were the best choice for.
The good news is that winning proposals aren't a dark art, and they're not about being the cheapest or the flashiest. They come down to structure, specificity, and a few principles most people get backwards. Here's how to write one that reads like a solution instead of a sales pitch.
The one mistake that sinks most proposals
Before the structure, the single most important idea, because it explains most losing proposals in one line: they describe the freelancer instead of solving the client's problem. They read like a resume when they should read like a solution.
Watch the difference. "I've been designing websites for over ten years and specialise in modern, responsive design" is about you — it's background, and the client has to do the work of translating it into what they'll get. "Your current site takes six seconds to load, and most mobile visitors leave before they ever see your portfolio" is about them — it's their problem, named specifically, and it signals you already understand their situation. The second sentence makes a prospect keep reading; the first makes them skim to the price and compare you on cost alone. Every section of a great proposal passes the same test: is this about me, or about them? Lead with them, always.
The core principle A client doesn't care what you do. They care what changes for them. A proposal that reflects their problem back to them, more clearly than they could state it themselves, has half-won the job before it ever mentions price.
The seven sections that win work
Winning proposals are remarkably consistent in structure. You don't need to reinvent it each time — a reliable skeleton, customised to each client, does the job. Here's the sequence, and crucially, why it's in this order.
| Section | Its job |
|---|---|
| 1. Summary | Restate the client's problem in their words — prove you get it |
| 2. Scope of work | Exactly what you'll do — and what you won't |
| 3. Deliverables | The concrete things they'll receive |
| 4. Timeline | Phased stages — makes the work feel structured, lowers risk |
| 5. Pricing | The investment — framed after the value is clear |
| 6. Terms | Payment schedule, revisions, boundaries |
| 7. Signature | The clear next step to say yes |
Notice what's not at the top: your company background. The instinct to open with "about us" or "who we are" is almost universal and almost always wrong. A prospect doesn't care about your history until they're convinced you understand their problem — so any bio, credentials, or firm information belongs near the end, as reassurance for a client who's already interested, not as an introduction to one who isn't yet.
WebCatalog
Desktop tool that turns websites into standalone apps with multi-account profiles and workspaces.
Best for: Power users juggling many web apps & accounts
The summary is the whole proposal in miniature
If a client only reads one section, it's the first one — so the summary does the heaviest lifting. Its entire job is to reflect the client's own situation and problem back to them so accurately that they feel understood. A client who sees their exact problem described in your opening lines will read every page that follows. A client who sees a generic "thank you for the opportunity to submit this proposal" will skim and price-shop. It's the same understand-them-first instinct that makes lead nurturing work in the run-up to this moment.
The move is to open with their world — the specific problem, the stakes, what's not working — and then bridge into your approach as the resolution. Done well, the summary flows straight into the scope: here's your problem, and here, immediately, is how the work below solves it. That single section, more than any other, is what separates a proposal that gets read from one that gets filed.
Pricing: frame value first, then name the number
Pricing is where most proposals stall, and the fix is usually about placement and framing rather than the number itself. The rule: price comes after value, never before. Show a client the price before they understand what they're buying and it lands as a raw cost. Show them the same figure after you've framed the problem, the solution, and the deliverables, and it reads as an investment against a clear return.
→ Place it after the value. Never let the number be the first substantive thing they see.
→ Offer a small range of options. A core package beside a more comprehensive one shifts the client from "yes or no?" to "which one?" — and a reasonable middle looks more reasonable next to a premium.
→ Break it down. An itemised price shows exactly what they're paying for; a single lump sum invites the question "why so much?"
The goal isn't to be cheap. It's to make the value obvious enough that the price feels fair — even when you're not the lowest bid.
This is also where being not the cheapest becomes survivable. When a proposal has already established that you understand the problem and can prove you'll solve it, price becomes one factor among several rather than the only one. Compete on value framing and you stop competing on being the lowest number, which is a race you don't want to win anyway.
Scope and terms: the cheapest place to set boundaries
Here's the section freelancers most often rush, and later regret. A vague scope doesn't just risk scope creep — it makes the client less confident, because uncertainty about what's included reads as uncertainty about whether you've done this before. Precision here does double duty: it protects you and it reassures them.
Spell out exactly what's included, and — just as importantly — add an exclusions section stating what isn't. Cap revisions to a specific number. Define how change requests are handled and priced. Setting these boundaries in the proposal prevents the large majority of disputes that otherwise erupt mid-project, when renegotiating is expensive and sours the relationship. The proposal is the cheapest, calmest place you will ever have to set these terms; every boundary you leave unstated now is one you'll have to defend later, under pressure, for free. Far from scaring clients off, clear terms signal that you've run projects before and think ahead — which builds trust rather than eroding it.
Prove, don't promise — and make saying yes easy
Two finishing touches separate a good proposal from a winning one. The first: prove, don't promise. Anyone can claim they deliver results; a proposal that shows them is far more persuasive. Fold in a relevant case study, a short client testimonial, a concrete before-and-after from similar work. Proof does what adjectives can't — it lets the client believe the outcome because they've seen you produce it before. This is the same logic behind building visibility that wins clients in the first place: demonstrated credibility beats claimed credibility every time — much of which, for agencies, now gets built on LinkedIn before a proposal is ever sent.
The second: make the next step obvious. A surprising number of proposals simply stop, leaving the client to figure out what happens next — and a proposal without a clear call to action is a missed opportunity. End with an unmistakable next step: sign here, book the kickoff call, reply to confirm. You've spent the whole document earning a yes; don't make the client hunt for where to give it. A great proposal makes saying yes feel easy and obvious.
If polishing the presentation of all this — the design and layout that make a proposal look as credible as its content — is where you'd like a hand, that's what branding and graphic design support is for.
The short version
A winning client proposal isn't the cheapest one or the prettiest one — it's the one that reads like a solution to the client's problem rather than a description of your skills. Open with their situation, not your resume; reflect their problem back so clearly in the summary that they feel understood; then walk them through scope, deliverables, and timeline before you ever name a price, so the number lands as an investment rather than a cost. Set your boundaries in writing while it's cheap and calm to do so, prove your ability with real results instead of claiming it with adjectives, and finish with a next step so obvious that saying yes takes no effort. Build a reliable template around those principles — the same systematise-what-works thinking behind picking the right agency tools — and customise it to each client, and you stop sending resumes and start sending solutions — which is the whole difference between the freelancer who wins the project and the one who never hears back.
Want proposals that look as credible as they read?
We help agencies and freelancers design client-ready proposals that win the work.
Explore Branding & Graphic Design →Frequently asked questions
What should a client proposal include?
A strong client proposal typically has seven sections: a summary that restates the client's problem, the scope of work, the deliverables, a timeline, pricing, terms, and a signature block. The order matters as much as the contents — the proposal should open with the client's situation and the value you'll create, and only present pricing after the client understands what they're buying. Supporting proof like case studies or testimonials strengthens it, and a clear next step at the end tells the client exactly how to say yes. Any "about us" background belongs near the end, not the beginning.
Why do most proposals lose?
Most proposals lose on structure, not price. The common failure is describing the freelancer or agency's skills and history instead of the client's problem and desired outcome — a proposal that reads like a resume rather than a solution. When a client can't quickly see their own situation reflected and understand the value on offer, they default to comparing on price alone, where you rarely win. Other frequent killers are burying or under-framing the price, vague scope that invites doubt, no proof of past results, and no clear next step. Almost all of these are fixable with a solid template and a checklist.
Where should pricing go in a proposal?
Pricing should come after the scope and value, never before. If a client sees the price before they understand what they're getting and why it matters, the number lands as a raw cost with no context. Presented after you've framed the problem, the solution, and the deliverables, the same number reads as an investment against a clear return. Many proposals also benefit from offering a small range of pricing options — for example a core package and a more comprehensive one — because a reasonable middle option looks more reasonable sitting next to a premium one, and giving the client a choice shifts them from "yes or no" to "which one."
How do you protect yourself from scope creep in a proposal?
The proposal is the cheapest and easiest place to set boundaries, long before any dispute can arise. Spell out the scope precisely, state what's explicitly not included in an exclusions section, cap the number of revisions, and define how change requests will be handled and priced. Setting these terms up front prevents the large majority of the disagreements that otherwise surface mid-project, when renegotiating is expensive and strains the relationship. Clear boundaries also signal professionalism — they show the client you've run projects before and think ahead, which builds rather than erodes trust.
