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.
Pricing it: anchor the number to value
By the time you write the price into a proposal, you should already know the number and why it's right — and that comes from value, not from fear. If the business case says the fix is worth far more than the price over the payback window, the price isn't a risk to defend; it's a bargain you can prove.
Before you name a number, be able to answer: what is this worth to them over the payback window, and where does my price sit inside that? Lead with the value, then state the price as the cost of capturing it. "The case we built shows this pays for itself in X months" is a price a champion can defend; "our price is…" with no anchor is a number they'll pick apart.
Scope is the price's best friend. Be explicit about what's included, what's not, and what anything extra costs. When scope is clear, the price means what it says and you're not negotiating against your own ambiguity later.
Never discount before the buyer asks. The most expensive AE mistake is lowering the price to preempt an objection or to "make it easy." If you discount, make it a trade — price down, term or scope concession in return, and only within what you're approved to give. Every concession should cost the other side something real, or you've given away margin for the life of the deal.
The negotiation itself is its own skill, covered in the negotiation module. Get the number right here, keep the scope honest, and you walk into that conversation holding value instead of hoping.
Start here
You have a proposal the buyer can defend, at a price built on value. Sending it is not the end — the next lesson is the discipline that decides whether it comes back signed: what to do after you send the proposal.