← All articles
Sell & Grow
How to Write a Proposal That Wins the Client
By the FabricLoop Team · May 2026 · 4 min read
Most proposals are written from the wrong starting point. The writer begins with what they want to say — their credentials, their process, their pricing — and the client's problem becomes a brief formality in section one before the real pitch begins.
The buyer experiences this as exactly what it is: a generic document with their name in the header. They read it, nod vaguely, and often choose the competitor whose proposal made them feel understood.
A proposal that wins is not a brochure. It's a demonstration that you've listened — that you understand the problem better than anyone else who's pitched, and that your approach is specifically designed for this situation, not copy-pasted from a template.
"The proposal you send after a great discovery call is just a written version of the conversation you've already had. If it says something new, you haven't listened carefully enough."
The six-section structure
This structure is designed for service businesses and B2B engagements. It follows the logical sequence of a buyer's decision-making process — from "do they understand my problem?" to "can I trust them?" to "is this worth the money?"
1
Problem restatement
In your own words, describe the client's situation and the specific problem this engagement will solve. Include the cost or consequence of not solving it. Do not mention your solution yet.
e.g. "Your team is spending 12 hours per week on manual reporting that could be automated — time that's currently coming from your senior developers."
2
Proposed approach
Describe how you will solve the problem — your methodology, the key decisions you'll make together, and why this approach is the right one for their situation. Avoid generic "our proven process" language; make it specific to them.
e.g. "We'll start with a two-week audit of your existing data flows before building anything — this avoids the common mistake of automating a broken process."
3
Deliverables
List specifically what they will receive — not activities you'll perform, but outputs they'll have. Be concrete. Vague deliverables create scope disputes later; specific ones build confidence now.
e.g. "Automated weekly P&L report emailed to three stakeholders every Monday by 9am; dashboard accessible to finance team; documentation for your in-house team to maintain."
4
Timeline
A clear schedule with milestone dates, key decision points, and what you need from them at each stage. Show that you've thought about sequencing, not just totals. Flag any dependencies on their team's input.
e.g. "Week 1–2: audit and access setup (requires read access to your data warehouse). Week 3–4: build and test. Week 5: review and revisions. Week 6: handover and training."
5
Investment
State the price clearly with what it includes and what's out of scope. If you have options, keep it to two — not five. Name your payment terms. If there's a deposit, state the amount and when it's due.
e.g. "Total investment: £8,400. 50% due at project start, 50% on completion. Includes up to two rounds of revisions. Additional work billed at £120/hr with written approval."
6
Next step
One single, specific action for them to take. Not "let us know if you have any questions" — a concrete next step with a suggested date. Make it as easy as possible to say yes.
e.g. "If you'd like to move forward, reply to this email and I'll send a contract and invoice for the deposit. I have availability to start the week of 19 May."
The problem restatement is the most important section
Most proposal writers treat the opening as a formality — a brief acknowledgment of the client's situation before getting to the real content. This is exactly backwards. The problem restatement is where you either win or lose the reader's attention.
When a buyer reads an accurate, specific description of their own problem — written in language that reflects how they think about it, not how you sell — something shifts. They feel understood. And feeling understood is the foundation of trust, which is the foundation of the sale.
Write this section last. After you've written the rest of the proposal, come back to the opening and refine it to reflect everything you've learned about their situation. It should feel like you've been thinking about their problem all week — because you have.
Walk through it live
Send the proposal, then schedule a 20-minute call to walk through it together. Don't wait passively for their verdict. Walking through it live lets you clarify, address objections in real time, and reinforce the most persuasive parts. Proposals reviewed on a call close at significantly higher rates than those sent and left to be read in silence.
What to leave out
A shorter, sharper proposal almost always outperforms a comprehensive one. Remove:
- Your company history and background — save it for an appendix if they want it; buyers at proposal stage already know who you are
- Generic "why us" sections — if you have specific evidence (relevant case study, named result), include it; otherwise, cut it
- Methodology jargon — your "proprietary framework" impresses nobody unless you can explain why it produces better results for this client
- Multiple pricing options presented as equal — if you offer options, guide them toward the right one rather than presenting a menu
The length trap
There's a temptation to write long proposals to appear thorough. Buyers read the problem restatement, skim the deliverables, jump to the price, and then decide whether to read the rest. A 4-page proposal that nails those three sections beats a 15-page one that buries them in methodology every time.
How FabricLoop helps you write better proposals
The quality of a proposal depends on the quality of your discovery notes. FabricLoop keeps everything from your initial conversation — the client's exact words, their concerns, their timeline — in one thread, so when you sit down to write the proposal, the raw material is all there and nothing's been lost to a fading memory or a deleted Slack message.
10 things to take away from this article
- Most proposals are written from the sender's perspective — winning proposals are written from the buyer's perspective.
- A proposal is a written version of your discovery conversation — if it contains something new, you didn't listen carefully enough.
- The six sections in order: Problem restatement, Proposed approach, Deliverables, Timeline, Investment, Next step.
- The problem restatement is the most important section — it's where buyers decide whether you understand them.
- Write the problem restatement last, after you've thought through the whole engagement.
- Deliverables should describe outputs the client receives, not activities you'll perform — specificity prevents scope disputes.
- Always include a single, concrete next step — not "let us know if you have questions."
- Walk through proposals live on a call rather than sending and waiting — close rates are significantly higher.
- A 4-page proposal that nails the key sections outperforms a 15-page one that buries them in methodology.
- Remove your company history, generic "why us" sections, and methodology jargon unless you have specific evidence to back them up.
