A proposal is the document your champion uses to win the deal you can no longer win in person. Its job is not to impress you — it's to let the buyer say yes and then defend that yes to everyone who wasn't in the room. Write it so it reads like a plan the buyer already agreed to: it restates their problem, proves the value, and makes approval easy.
The proposal's structure (what belongs in it)
A defensible proposal follows one shape:
- The problem and the outcomes. Open by restating what you found in discovery: the problem, its cost, and the outcomes you both agreed matter. If they recognize themselves on page one, they'll trust the rest.
- The solution. Describe how what you're proposing delivers each agreed outcome — in their language, not your spec sheet.
- The value and business case. Put the case you built with their numbers front and center. This is what the economic buyer defends.
- The terms, price, and scope. Be explicit about what's included, what's not, and the price. Ambiguity here is what dies in procurement.
- The ask. Close with the next step and a validity date, so the deal has a pulse and a clock.
Write it for the room that approves it
Every section should survive being read by a committee member who never met you. That means: their problem, their numbers, no jargon, honest scope, and a clear price tied to value. If your champion could forward the proposal to their boss with one line and have it make sense, you've done it right.
What kills a proposal
Don't make it a feature dump or a generic template — it has to reflect this buyer's discovery. Don't bury the price or hide scope exclusions; surprises get deals killed late. And don't send it and disappear — a proposal needs a next step and a follow-through, not a wish and a wait.
Start here
You have a proposal the buyer can defend. The trickiest part is getting the number right — the next lesson covers putting a value-anchored price on it before the negotiation begins.