What goes in a B2B sales proposal
Guide · Sales · 5 min read · last verified 2026-07-27
A B2B sales proposal is the commit-stage document that asks a buying organization to approve a specific purchase. It restates the buyer's problem in the buyer's own words, assembles the evidence the evaluation has already produced, states a price with its basis visible, and closes with the path from this document to a signed agreement. It is not an introduction and it is not a brochure. By the time a proposal is warranted, most of the selling has happened — this is a different animal from the early follow-up covered in what to send a prospect after the first call, and its job is to let a decision hold up in rooms the seller never enters.
That framing decides what belongs inside. A proposal read only by your champion could be informal, because they sat through every call. But proposals tend to travel: to a finance approver, a procurement reviewer, a department head who heard about the project last week. The useful test for every section is the absent reader — someone who missed every conversation, holds part of the decision, and will give the document minutes rather than hours. Write for that reader and the proposal becomes what it actually is at commit stage: the champion's forwarding artifact, the document half of helping your champion sell internally.
Their problem, in their words
Open with the problem as the buyer described it, quoted or closely paraphrased from your notes, in their vocabulary rather than your category's. A buyer who recognizes their own words tends to keep reading; a buyer who meets generic language about efficiency and transformation tends to discount everything that follows it. Include what they said about the current state, what they said would happen if nothing changed, and who inside their organization said it. Resist the urge to sharpen the problem with consequences the buyer never stated. If the stakes were never made explicit, ask before you draft — invented urgency reads as invented, and the absent reader has no call history against which to give you the benefit of the doubt.
The evidence already shown
A commit-stage document is a record, not a reveal. Pull forward the strongest artifacts the evaluation produced: what the pilot showed in the buyer's own environment, the answers to the questions this committee actually asked, the reference story that matches their situation rather than the most impressive one you have. Nothing in the proposal should be new. A new claim at this stage invites new scrutiny, and new scrutiny tends to reopen an evaluation you already passed. Attribute every piece of evidence — where it came from, who on the buyer's side saw it, where the fuller version lives — because approvers tend to spot-check what they can, and a claim that survives a spot-check strengthens the whole document while an orphaned assertion weakens it.
Price, with its basis
State the price plainly and show how it was built: what is included, what drives the amount, and what the buyer chose along the way — the tier they selected, the scope they set, the options they declined. A price with a visible basis turns pushback into a conversation about scope; a bare figure turns it into a discount request. The same dynamics run through handling price objections with evidence, and the proposal is where they are settled in writing. If the price moved during the evaluation, say why it moved. Approvers who can see the reasoning tend to defend the amount inside their own hierarchy; approvers handed an unexplained figure tend to negotiate it down on principle.
The decision path
End with what happens next, specifically: who signs, which review steps remain, and the dates both sides already agreed to. If the deal runs on a mutual action plan, this closing section is a snapshot of its remaining rows — do not build a second, competing schedule. A proposal that ends with an open invitation to get in touch hands the schedule to chance. One that ends with the path both sides already walked through preserves the commitment that produced it.
What to cut
Cut the feature inventory. Cut the company history, the mission statement, the generic case studies, and every claim about your category that a competitor could copy word for word. The test for each remaining paragraph is whether it answers a question this committee asked or helps the absent reader approve. Feature dumps are the most common failure because they feel like added value — but at commit stage they tend to work against you, inviting the committee to re-scope the purchase around capabilities nobody requested. Anything a skeptical reader could brush aside without you there to defend it is weight your champion has to carry alone.
How long — and when a quote is enough
A proposal should be as long as its argument requires and no longer, which is usually shorter than the template suggests. Busy approvers tend to read the summary, the price, and the next steps first — sometimes only those — so write those pages as if they were the whole document and let everything else exist to back them up. The proposal-versus-quote question resolves the same way. A quote serves a buyer who has already decided and needs the amount and the terms on paper; a proposal argues a case for a committee that still holds a live decision. Send a quote into an undecided committee and the case goes unmade. Send a full proposal to a buyer who only asked for the number and you bury the single page they wanted.
None of this is writing in the usual sense — it is assembly. If the evaluation was run against the questions the buyer genuinely needed answered, the proposal already exists in pieces: the stated problem, the checked evidence, the priced scope, the agreed path. Teams that work evidence-first, including those using Magrios to keep buyer questions and their sourced answers in one place, tend to find the proposal is the shortest document of the deal, because everything in it has been seen, checked, and agreed once already. That is exactly what makes it safe to forward.