How long should a sales proposal be?

Long enough to answer the buyer's questions and no longer. Most winning B2B proposals land between 4 and 10 pages. If it takes more than that, you probably haven't clarified scope yet.

Should the executive summary come first or last?

Write it last, place it first. Buyers skim it before deciding whether to read the rest — it has to compress the entire deal into one page.

Do I need to include a case study?

One relevant proof point beats three generic ones. A single named customer in the buyer's industry with a measurable result is enough.

How fast should I send a proposal after a sales call?

Within 24–48 hours while the buyer's memory of the pain is fresh. Speed itself signals competence.

How to Write a Sales Proposal That Wins (Step by Step)

A sales proposal isn't a document — it's a decision aid. Its job is to make it easy for a buyer (usually a buyer plus two or three people they need to convince internally) to say yes without having to reconstruct the whole conversation. Most proposals fail because they read like a company brochure with a price at the end. Winning proposals read like a private memo written for one specific buyer's situation.

This is the exact structure we've seen work across thousands of B2B proposals: consulting, SaaS, agency, professional services. The section order matters, and so does what each section is allowed to do. Skip a step and the proposal starts to feel generic; add a step and it starts to feel bloated.

Lead with the customer's problem, not your company

Almost every rejected proposal opens the same way: a paragraph about the seller — how long they've been in business, awards, logos. The buyer already agreed to read the proposal; they don't need to be re-sold on the fact that you exist. The first page needs to prove one thing: you understood what they said on the call.

Open with a two-to-four sentence restatement of their situation. Use their words, not your category jargon. If they said "our AEs are ghosting leads after demo," don't translate that into "lead-nurturing optimisation" — leave it exactly as they said it. That single move signals listening better than any case study.

Write the executive summary last, place it first

The executive summary is the only section that will always be read. It gets forwarded, screenshotted, pasted into Slack. If it doesn't stand alone, the deal stalls. Keep it to one page. It should answer four questions in this order:

What is the buyer trying to achieve, in one sentence?
What are you proposing, in one sentence?
What is the expected outcome, ideally quantified?
What is the price and the next step?

Write it after you've written the rest — it's a compression, not an introduction. If you can't compress the proposal into one page, the proposal isn't clear enough yet.

Make scope specific enough that a stranger could deliver it

Scope is where most proposals hedge, and hedging is what makes buyers hesitate. Vague scope creates two problems at once: the buyer can't picture what they're buying, and they suspect you'll change your mind about what's included once the contract is signed.

Write scope as if you were handing this project to someone who has never met the buyer. Include deliverables (things they can see), activities (things you'll do), owners (who does what), and explicit exclusions (what is not included). Exclusions are the most under-used tool in proposal writing — they eliminate scope creep before it starts and they build trust because they show you've thought carefully about boundaries.

Present pricing with context, never bare

A price on its own is a number. A price next to what it replaces is an argument. Every pricing section should contain three things: the number, what the buyer gets for it, and a reference point. The reference point can be the cost of the current situation ("last year, that gap cost an estimated $X in missed renewals"), a comparable investment they've already made ("less than one AE's monthly OTE"), or a range of options that make the middle one look reasonable.

If you're offering more than one price point, structure them as three tiers — never two. Two options force a binary choice; three options invite the buyer to compare. The middle tier should be the one you actually want to sell.

Include social proof, but only relevant social proof

A logo wall of Fortune 500 clients does very little for a mid-market buyer. One named customer in their industry with a specific measurable result does a great deal. If you can, include a two-sentence quote from someone in a similar role — not the CEO, the person who used the product day-to-day. Buyers trust peers more than executives.

Close with a specific, low-friction next step

Every proposal ends with some version of "let us know if you have any questions." That sentence is where deals go to die. Replace it with a specific next step, ideally with a proposed time. "If this looks right, reply and we'll set up a 20-minute kickoff on Thursday at 10 or 2." A yes should require one click, not one meeting to schedule another meeting.

What to check before you send

Before you send, read the proposal out loud. Every sentence a buyer would circle or ask you to rephrase is a sentence to rewrite. Look for hedging language ("we could potentially", "may be able to"), acronyms you didn't define, and any paragraph that could apply to any of your other customers — that's a paragraph pulled from a template that needs to be rebuilt for this deal.

Then run it through a persuasion check. Most proposals aren't rejected for a single flaw; they're rejected because the buyer can't tell whether the seller understood them, whether the scope is real, and whether the price maps to a real outcome. Those are three separate questions with three separate answers — and you can tell within thirty seconds whether a proposal answers them.

Frequently asked questions

How long should a sales proposal be?: Long enough to answer the buyer's questions and no longer. Most winning B2B proposals land between 4 and 10 pages. If it takes more than that, you probably haven't clarified scope yet.
Should the executive summary come first or last?: Write it last, place it first. Buyers skim it before deciding whether to read the rest — it has to compress the entire deal into one page.
Do I need to include a case study?: One relevant proof point beats three generic ones. A single named customer in the buyer's industry with a measurable result is enough.
How fast should I send a proposal after a sales call?: Within 24–48 hours while the buyer's memory of the pain is fresh. Speed itself signals competence.