A sales proposal is the discovery call, written down, with a price at the end. That's the whole job. Most proposals fail because they forget the first half: they open with the vendor's history, tour the product, and get to the buyer's problem somewhere on page four, if at all. The buyer reads the summary and the price, notices neither one mentions anything they said on the call, and files it with the other two.
This is how to write one that reads like you listened: what you need before you start, the seven sections in order, how long each should be, and the checks to run before you hit send.
Before you write: what discovery has to give you
You can't write a specific proposal from a vague call. Before opening a document, check that you actually have these five things. If two or more are missing, the next step is another conversation, not a proposal.
- The priority, in their words. What they said when you asked why now. Not your paraphrase, theirs.
- Two or three named pains. With a cost attached, even a rough one: hours a week, deals lost, a deadline at risk.
- Who decides, and how. The people who'll read this who weren't on the call, and what they care about.
- The timeline. When they need to be live, and what's driving that date.
- The shape of the budget. Not a number necessarily, but whether this is a line item that exists or one that has to be created.
If your notetaker captured the call, most of this is already sitting in the summary. We wrote a separate piece on getting from call notes to a proposal.
The seven sections, in order
This is the structure behind our sales proposal template. The order matters: every section earns the next one, and pricing comes last because by then the reader knows what it buys.
1. Cover
Their name is the headline, not your logo. “A faster claims process for Fieldstone” beats “Proposal from Beacon Analytics.” The cover sets up “this was made for us” before anyone reads a sentence. Include the date, the contact it's addressed to, and who to reach on your side.
2. Executive summary
The one section every stakeholder reads, including the ones who read nothing else. About 150 words. Three moves: where they are today, where they want to be, and the shape of your plan to get there. Open with their most urgent priority, in their phrasing. Three headline numbers if you have them (the outcome, the timeline, the investment). No adjectives about your company.
3. Where you are today
The challenges, in the buyer's own terms. This is the section that proves you listened, and it's the one most proposals skip or replace with “industry trends.” Two or three challenges, each with a plain title and two sentences on what the status quo costs. Don't invent problems they didn't mention. Don't soften the ones they did.
4. How we'll help
Your approach, mapped to their challenges one for one. Challenge A gets answer A. Capabilities appear only as the answer to a stated problem; anything that doesn't map to a challenge gets cut, however proud of it you are. For each: what you'll do, and the outcome it buys them. This is where the feature tour usually sneaks in. Don't let it.
5. Proof it works
One relevant case study with real numbers. A customer like them, a result they want. Relevant beats impressive: a mid-size logistics firm that cut dispatch time 41% means more to a mid-size logistics firm than a Fortune 500 logo does. If you don't have a case study in their segment, use the closest one and say why it applies. Never let an AI, or a colleague in a hurry, write a case study from memory.
6. Pricing
After the value story, never before it. Real line items from a real catalog, so the buyer and procurement see the same thing. Two or three options if the deal allows it: a recommended package in the middle, a lighter one below, an expanded one above. One short paragraph above the table frames the investment against the cost of the problem. No “affordable,” no apologizing.
7. Timeline and next steps
A concrete rollout with dates, and the specific next step you agreed on the call. “Let us know your thoughts” is not a next step. “Technical review with your IT lead on the 22nd, then a signed order form by the 30th to hold the November kickoff” is. The proposal should end with momentum, not a question.
How long should it be?
Six to ten pages, or the web equivalent, for a considered B2B deal. Shorter for transactional deals, where a quote may be all that's needed. The executive summary and pricing get read by everyone; the middle sections get read by the people who'll live with the decision. Write for both: a skimmable summary and a substantive middle, not a long summary and a thin middle.
Writing rules that hold up
- Their words over yours. If the buyer said “the Friday fire drill,” the proposal says “the Friday fire drill.”
- Numbers over adjectives. “Reduces handoffs from five to two” beats “streamlines your workflow.”
- Cut 30%. First drafts carry everything you know. Remove what the buyer already knows, generic observations, and any sentence that would be true of any vendor.
- Read it aloud. If a line would sound absurd said across a table, it goes. “We are pleased to present this comprehensive solution” has never been said aloud by anyone.
- One design system. Consistent type, one accent colour, your brand but quiet. A proposal that looks assembled from three decks reads as three people who didn't talk.
Before you send: the six-point check
- Does the executive summary open with their priority, not your company?
- Is every challenge one they actually raised?
- Does every capability answer a named challenge?
- Is every number sourced, and every case study real?
- Is pricing after the value story, with line items procurement can read?
- Is the next step specific, dated, and the one you agreed?
After you send
The proposal's job isn't done at send. Send it as a link so you can see what happens next, and attach the PDF for procurement. Then follow up on what the buyer did, not on a calendar. We cover both in how to track proposal engagement and proposal follow-up emails by signal.
Doing it with AI
Everything above can be drafted by AI, and increasingly is. The difference between useful and useless output is entirely what the AI is working from. Prompted with “write a sales proposal for a software company,” it produces the average of every proposal on the internet. Fed the discovery notes and the deal record, it produces a first draft with the buyer's priority in the summary and their pains in section three. Our ChatGPT prompts for sales proposals show the manual version of that.
We built Veew so the manual version isn't necessary: it reads the deal and the call notes, writes the seven sections above from them, cites only case studies from your approved library, and delivers a designed, trackable proposal with a matching PDF. It's the same structure as this post, with the typing done. The AI proposal generator page covers what it needs and what it produces.
However you write it, the standard is the same: a proposal the buyer could not mistake for one sent to someone else.