Skip to content
Playbook ·

The anatomy of a sales proposal that closes

Nine sections, in a specific order, each with a job. What to include, what to cut, and why the executive summary should be written last but read first.

YZ 7 min read

In short: A sales proposal that closes is a decision document for someone who was not on the call. Nine sections, in this order: executive summary, where you are today, what success looks like, what we propose, scope and deliverables, timeline, investment, why us, next steps. Restate the prospect's situation in their own words, keep scope as bullet lists, write the executive summary last, and cut anything that would read the same in a proposal for a different prospect.

A proposal is a decision document, not a brochure

The best proposals are read by someone who was not on the call: a CFO, a VP, a procurement lead. They need to understand the problem, the plan and the price without a demo. That constraint decides the structure.

Below is the default section set proposal.here generates. Every section can be renamed, re-ordered, disabled or replaced, but the logic behind the order is worth keeping.

1. Executive summary

Three to five sentences: who you are talking to, the problem they named, what you propose, the outcome. No bullets. Written last, read first.

2. Where you are today

Restate the prospect's situation in their own words. If they said "we lose a day a week to manual reporting", write that, not "inefficient reporting workflows". This section proves you listened and lets the champion check your understanding before anyone sees pricing.

3. What success looks like

The goals the prospect named, each measurable where possible. These become the criteria the deal is judged against later, so be precise and be conservative.

4. What we propose

Map your offering to the pains and goals above. Resist listing everything you do. If the prospect raised three problems, this section has three parts.

5. Scope and deliverables

Included, excluded, assumed. Most post-signature friction comes from this section being vague. Bullet lists, not prose.

6. Timeline

Kickoff, onboarding, go-live, first review. Reflect dates the prospect mentioned ("before the Q1 planning cycle"). A small table works well here.

7. Investment

Prose that explains the pricing table: what is included, how billing works, what assumptions the number rests on. The table itself is rendered separately so it stays accurate when pricing changes.

8. Why us

Two to four proof points that answer objections raised on the call. Specific customers, specific results. If a claim is not in your FAQ or asset library, it should not be here.

9. Next steps

A numbered list with owners and dates, ending with how to accept. Proposals without a clear next step die politely.

What to cut

  • Company history longer than two sentences.
  • Feature lists that were not discussed on the call.
  • Stock photography and decorative pages.
  • Any paragraph that would read the same in a proposal for a different prospect.

Why generation helps here

The structure above is easy to agree on and hard to execute at 6 p.m. after four calls. Generating the first draft from the transcript removes the blank page; keeping the structure in a shared template removes the drift. Reps edit; they do not reinvent.

Keep reading