How to Write a Sales Proposal That Closes

How to write a sales proposal (with a template outline)

A proposal is not a summary of your discovery calls. It's a purchase justification document, written for someone who probably wasn't on those calls. That distinction changes almost every decision you make: what goes on page one, how much time you spend on your company overview (very little), and whether the pricing sits at the front or the back.

Most proposals that stall in procurement fail for the same reason. They read like a vendor talking about itself, when they need to read like a buyer's internal business case with your logo on it. Fix that, and the document starts doing work while you sleep.

Start with the buyer's decision, not your solution

The person opening your proposal is often a step removed from the champion you've been working with. They have thirty minutes, a shortlist, and a nagging suspicion that the numbers won't survive scrutiny. If your first page is a company boilerplate paragraph and a table of contents, you've already lost a portion of their attention.

The opening section should do three things in under a page:

1. State the business problem in the buyer's language, using specific figures they gave you in discovery.
2. Name the desired outcome and the timeframe attached to it.
3. Summarise what you're proposing and the total investment, in one paragraph.

Say your champion is a VP of RevOps at a mid-market SaaS company with roughly 80 reps, and her stated pain is that forecast accuracy has drifted badly enough that the CFO no longer trusts pipeline reviews. Your opening paragraph writes itself: "This proposal outlines a forecasting workflow for [Company]'s 80-rep sales org, targeting forecast variance under 10% within two quarters, at an annual investment of $148,000."

That single sentence gives a CFO everything she needs to keep reading, or to stop. Both outcomes are useful to you.

The template outline

Here is a structure that holds up across most B2B deals from $30K to seven figures. Adjust section depth to deal size, not deal complexity.

1. Executive summary (½ to 1 page). The three points above. No logos, no mission statements, no "thank you for the opportunity." One paragraph on the problem, one on the proposed solution, one on the investment and expected return.

2. Current state (1 page). Mirror back what you learned in discovery, using the buyer's own numbers and phrases wherever possible. This section exists to prove you listened and to give internal stakeholders who weren't on the calls a shared understanding of the baseline. If the champion forwards the proposal to a skeptical peer, this page does the selling for her.

3. Proposed solution (1 to 3 pages). Organised by outcome, not by product feature. If you sell a platform with six modules, do not list six modules. Instead, list the two or three outcomes tied to the buyer's stated goals, and describe which capabilities support each. A common mistake is to write this section as if the buyer will read every word. They won't. Use subheadings that stand alone.

4. Implementation and timeline (½ to 1 page). A dated table with milestones, owners on both sides, and a go-live date. Vagueness here is where deals die in legal review. If the buyer's team doesn't know when they need to allocate hours, they'll assume the worst.

5. Commercial terms (½ page). Pricing, term length, payment schedule, and what's included. If you offer options, offer no more than three, and recommend one. A three-tier layout with a "recommended" marker consistently outperforms an open-ended pricing menu, because it converts a choice into a preference.

6. Success metrics (½ page). The specific KPIs you'll both measure, the baseline, the target, and the review cadence. This is the section that separates proposals that close from proposals that get "parked." A buyer who can see how success will be measured can defend the purchase later.

7. Next steps (¼ page). Named signatories, required internal approvals on the buyer's side, and the date by which countersignature is needed to hit the go-live milestone. Attach the order form as an appendix, not as a separate email.

That's it. Seven sections, rarely more than eight pages including whitespace.

Where most proposals leak value

A few patterns show up repeatedly in win-loss reviews of lost deals:

The proposal was written for the champion, not the committee. The champion loved it. The CFO opened page one, saw a feature list, and closed the tab. Every proposal should pass what you might call the "CFO skim test": if a finance leader read only the executive summary, the pricing table, and the success metrics, would they have enough to approve it?

Pricing appears without context. A $148,000 number sitting alone triggers sticker shock. The same number sitting next to "current cost of the problem: $2.1M in missed forecast, per your Q1 board deck" triggers arithmetic. Anchor pricing against the cost of inaction the buyer has already acknowledged.

Scope creep dressed as generosity. Adding "and we'll also throw in X, Y, and Z" makes the proposal look padded and raises questions about what you're actually selling. Give one meaningful concession, tied to a specific ask (accelerated signature, multi-year term), and stop.

No expiry. A proposal without a valid-until date is a proposal that sits in a shared drive for six months. Attach expiry to something real, such as pricing tied to the current quarter or an implementation slot that gets reassigned.

A note on customisation versus templating

Experienced AEs sometimes over-customise, spending four hours rewriting boilerplate for a $45K deal. Others under-customise, sending a find-and-replace document that the buyer sniffs out on page two. The right cut is this: templated structure, custom content in three sections only. Current state, success metrics, and the executive summary must be written from scratch every time. Everything else can be assembled from a library of pre-approved blocks.

That discipline saves hours per proposal and produces documents that actually feel written for the buyer, because the sections the buyer notices most are the ones that were.

The takeaway

• Rewrite your next proposal's first page so a CFO who reads only that page has enough to make a decision. If they don't, the rest of the document won't save you.
• Build a proposal library with locked template sections and three "custom every time" sections: executive summary, current state, success metrics.
• Anchor every pricing number to a cost-of-inaction figure the buyer has already stated on a call. Never let a price sit alone on the page.
• Add an expiry date tied to something concrete, such as an implementation slot or quarter-end pricing, and reference it in the next-steps section.