Writing a Proposal That Actually Wins Work
Most proposals lose before the price is even mentioned. Here is how to fix the parts that matter.
There is a particular kind of silence that follows a proposal you were sure would land. No reply for a week, then a polite note saying the client has "decided to go in another direction." Most freelancers and small agencies treat this as a pricing problem. It rarely is. In the majority of cases the proposal lost before the numbers were ever read, because the first page failed to convince the reader that you understood their situation.
A proposal is not a product description. It is an argument, built in a specific order, aimed at a specific person who is usually nervous about making the wrong call. Understanding that changes almost everything about how you write one.
Start with their problem, not your process
The most common mistake in a proposal is opening with a description of the sender: who they are, how many years they have been doing this, what makes their approach unique. None of that means anything to a client until they believe you have grasped what is actually wrong.
Open instead with a short, accurate restatement of the problem, in the client's own language wherever possible. If they told you during a call that their checkout process was "leaking customers at the last step," use that phrase. It signals that you were listening rather than pattern-matching their brief to a template you already had.
This section should be two or three sentences, not a page. Its only job is to make the client nod before they have read anything about what you plan to do.
Show the shape of the solution, not every detail
There is a temptation to prove competence by listing every step of the work in granular detail. This backfires in two ways. First, it gives a client with limited time enough information to attempt the project themselves or hand it to someone cheaper who follows your outline. Second, it buries the decision-maker in detail they are not equipped to evaluate, which slows the decision rather than speeding it up.
A better approach describes the shape of the solution: the phases, the reasoning behind them, and what changes for the client at each stage. Save granular detail for the working relationship itself, once you have been engaged.
A simple three-part structure
- What we understand about the problem, in plain terms
- How we would approach it, broken into two or three phases
- What you will have at the end of each phase
This structure works whether you are proposing a week-long project or a six-month retainer. It scales by adding detail within each phase, not by adding new sections.
Price with confidence, not apology
Pricing language gives away more than the number itself. Phrases like "I hope this works for your budget" or "happy to discuss if this is too much" signal that you expect to be negotiated down before anyone has objected. Clients notice this, consciously or not, and many will push simply because the invitation was there.
State the price plainly, attach it to the value described above it, and stop. If you offer options, offer them as genuinely different scopes of work rather than the same work at three price points designed to nudge the client toward the middle one. A menu of near-identical options with arbitrary price gaps reads as a pricing trick, and experienced buyers recognise it instantly.
| Weak pricing language | Stronger alternative |
|---|---|
| "I hope this fits your budget" | "The investment for this scope is £X" |
| "Let me know if this is too much" | "This price reflects [specific reason]" |
| Three options, same scope | Three options, three different scopes |
Address the objection before it is raised
Every industry has a handful of predictable hesitations. In a service business it might be timeline risk, or whether the client will need to manage the project closely, or what happens if the scope changes midway. Rather than hoping these do not come up, name them directly in a short section near the end of the proposal.
This does two things. It shows the client you have done this enough times to anticipate the questions, and it removes the awkwardness of them having to ask something that might sound like doubt. A single paragraph addressing "what happens if priorities change partway through" often does more to build trust than any amount of praise for your own work.
Keep the proposal short enough to be read once, properly
Length is not a proxy for thoroughness. A proposal that runs to twelve pages is not more persuasive than one that runs to three; it is simply more likely to be skimmed, forwarded without being read in full, or set aside for "later," which is where good proposals go to die.
A useful test: could the client read this in the time it takes to drink a cup of coffee, and come away able to explain the offer to a colleague in two sentences? If not, cut it down. Appendices are for detail; the proposal body is for decisions.
Make the next step obvious and small
Many proposals end with something vague, such as "let me know if you have any questions" or "looking forward to hearing your thoughts." This puts the entire burden of moving the process forward on the client, at exactly the point where momentum matters most.
Replace it with a specific, low-effort next action: a date by which you will follow up if you have not heard back, a short call to confirm scope, or a simple reply confirming which option they would like to proceed with. The easier the next step, the less time there is for the decision to be deprioritised behind something more urgent.
Questions worth asking yourself before sending
- Does the opening prove I listened, or does it describe me?
- Is the pricing stated plainly, without hedging language?
- Have I named the obvious objection rather than hoping it does not surface?
- Could someone forward this and have it make sense without extra explanation?
- Is there a specific, small next step at the end?
Following up without sounding desperate
Silence after sending a proposal is normal and rarely personal. Clients get busy, proposals sit in inboxes, and internal approvals take longer than anyone expects. A short, warm follow-up a few business days after sending, referencing something specific from the original conversation, tends to work far better than a generic "just checking in."
If there has still been no response after a second follow-up, it is reasonable to close the loop yourself: a brief note saying you will consider the opportunity closed unless you hear otherwise by a certain date. This is not pressure tactics; it is simply respecting your own time and often prompts a reply from clients who had genuinely intended to respond but had not gotten around to it.
The proposal is a preview of working with you
Clients read a proposal not only for its content but as a sample of what it will be like to be your client: how clearly you communicate, how well you listen, how easy you are to say yes or no to. A proposal that is clear, well organised and free of unnecessary padding tells the client something true about how the actual work will go.
Treat every proposal you send as a small piece of the product itself, not paperwork that precedes it. For more on structuring client relationships once the work begins, see our related coverage in business.
About the author
Idris Oyelaran covers consumer technology, privacy and applied science. He is happiest explaining a complicated system in ordinary language, and he tests every recommendation on his own devices before it appears in a story.
