What a sales proposal is
A sales proposal is the document that turns a discovery process into a recommendation. It restates the buyer's problem, says what success would look like, recommends a solution, shows how it will be delivered and what it costs, and ends with the steps that lead to a decision. In a B2B deal it is usually read by people who were never on a call, so it has to make sense on its own.
That is the main difference between a good proposal and a brochure. A brochure describes the seller. A proposal describes the buyer's situation, uses their numbers and their language, and only then explains why this solution fits. If a finance or IT reviewer can read the first page and understand why the project matters, the proposal is doing its job.
A proposal is not the same as a quote or a contract. The proposal makes the case and presents pricing options; the quote is the priced offer for the option the buyer picks; the order form is what they sign. Keeping the three separate lets the proposal stay readable while the commercial detail lives in the documents built for it.
Most proposals are sent too early. The best time is after discovery has confirmed the problem, the people involved and how they decide, and ideally after the main contact has reviewed a draft. A proposal the champion has already shaped is far more likely to be forwarded internally than one that arrives cold.
When to send a sales proposal
- Discovery is done: you know the problem, the cost of leaving it alone, who decides and how.
- Your champion needs a document to circulate to people who were not in the meetings.
- The buyer has asked you to set out options and pricing in writing before a decision meeting.
- Several vendors are being compared and you need your recommendation in one place, in the buyer's terms.
- An existing customer is considering an expansion that needs its own business case and approval.
Proposal vs quote vs RFP response vs business case
Four documents are often confused in B2B deals. The practical differences are who writes each one, what it is for and what it contains.
| Document | Written by | What it is for | What it contains |
|---|---|---|---|
| Sales proposal | Seller, ideally shaped with the champion | Recommends a solution and asks for a decision | Problem, outcomes, solution, plan, pricing options, proof, next steps |
| Quote | Seller, approved by the deal desk | Prices the option the buyer chose | Line items, quantities, discounts, terms and a validity date |
| RFP response | Seller, in the buyer's format | Answers a buyer's formal questionnaire | The buyer's questions, answered in order, with requested attachments |
| Business case | Buyer's champion, often with seller help | Justifies the purchase internally | Cost of the problem, options including doing nothing, ROI, risks and the decision ask |
The sales proposal template
Write it in this order and keep the first page short enough that an executive who reads nothing else still understands the recommendation. Square brackets mark what you replace. Use the buyer's own words from discovery wherever you can.
Cover and summary
| Section | What to write |
|---|---|
| Title | [Proposal for (buyer company): (the outcome, in their words)] |
| Prepared for and by | [Buyer names and roles] / [your name, role and contact] |
| Date and version | [Date] / [version number] |
| Executive summary | [Three or four sentences: the problem, the outcome, what you recommend, what it costs and what you ask them to decide by when] |
The buyer's situation and goals
| Section | What to write |
|---|---|
| Current situation | [What happens today, as the buyer described it in discovery] |
| Cost of the problem | [The impact they quantified: time, revenue, risk or cost; cite who said it or where the number came from] |
| Why now | [The event or deadline that makes this a priority this quarter] |
| Outcomes and success measures | [Two or three measurable outcomes, each with how and when it will be measured] |
| Requirements and constraints | [Must-haves, technical or security requirements, budget range, timing] |
Recommended solution
| Section | What to write |
|---|---|
| What we recommend | [The products, modules or services, in plain language] |
| How it meets each requirement | [One line per requirement from the section above] |
| What is not included | [Anything they might assume is included but is not] |
| Alternatives considered | [Other approaches, including doing nothing, and why you do not recommend them] |
Implementation plan and timeline
| Phase | Dates | What happens | Buyer responsibilities | Seller responsibilities |
|---|---|---|---|---|
| [Kick-off and set-up] | [Dates] | [Configuration, integrations, access] | [Admin, IT contact, data] | [Implementation lead] |
| [Pilot or first team] | [Dates] | [First users live] | [Pilot group and feedback] | [Training and support] |
| [Full rollout] | [Dates] | [All users live] | [Internal communication] | [Training and success reviews] |
| [First review] | [Date] | [Measure against the success measures] | [Data and attendance] | [Report and recommendations] |
Investment and pricing options
| Option | What is included | Term | Price | Best for |
|---|---|---|---|---|
| [Option A: recommended] | [What it includes] | [Term] | [Price per year, plus one-time fees] | [Who it suits] |
| [Option B: smaller scope] | [What it includes] | [Term] | [Price] | [Who it suits] |
| [Option C: broader scope] | [What it includes] | [Term] | [Price] | [Who it suits] |
| Pricing notes | [Validity date, what is excluded, taxes, and that a formal quote follows the chosen option] |
Proof, risks and next steps
| Section | What to write |
|---|---|
| Relevant proof | [A case study, reference or result from a company like theirs, with permission to cite it] |
| Risks and how they are handled | [Adoption, integration, timing or data risks, each with a mitigation and an owner] |
| Assumptions | [What the plan and price assume, such as user numbers or start date] |
| Next steps to a decision | [Dated steps: review meeting, security review, legal review, signature, kick-off] |
| Acceptance | [How the buyer confirms the chosen option, and who on your side to contact] |
Proposal checklist before you send it
| Check | Why it matters |
|---|---|
| The first page states the problem, the recommendation, the price and the decision date | Many readers only read the first page |
| The problem and outcomes use the buyer's own words and numbers | They trust their figures more than yours |
| Every requirement has a line saying how it is met | Reviewers check requirements one by one |
| Pricing options are clear and a formal quote is promised for the chosen one | Commercial detail belongs in the quote, not the proposal |
| Next steps have dates and owners on both sides | A proposal without next steps stalls in an inbox |
| Your champion has reviewed a draft | They know what their colleagues will object to |
Prefer a file? We email the Word, Excel and PDF versions to your work address, free.
Email me the filesSales proposal example
Example: fictional company
Here is the template filled in for the same invented deal as the sales quote and order form examples, at the proposal stage. Prices are fictional and shown in US dollars, before tax.
Ferncastle Analytics sells a forecasting platform. After three discovery calls with Marlow & Finch Logistics, its account executive sends a proposal that Dana Okafor, Director of Revenue Operations, will take to the CFO.
Summary and goals
| Section | Example entry |
|---|---|
| Executive summary | Marlow & Finch's regional forecasts are built in spreadsheets and reconciled by hand each week. We recommend the Ferncastle forecasting platform with the advanced analytics module, live by 1 December 2026, for $35,000 a year. We ask for a decision by 20 November 2026. |
| Cost of the problem | Dana estimates that her team spends a day a week reconciling regional forecasts, and the CFO has missed two quarterly forecasts this year. |
| Why now | The new financial year starts on 1 January and the board has asked for a reliable quarterly forecast from Q1. |
| Outcomes and success measures | One forecast view for all regions by the January board meeting; weekly reconciliation time cut, measured by the RevOps team in February. |
Investment and pricing options
| Option | What is included | Term | Price | Best for |
|---|---|---|---|---|
| A: Platform and analytics (recommended) | Forecasting platform, advanced analytics module, implementation and training | 24 months | $35,000 a year plus $5,000 one-time | Teams that want trend reporting from day one |
| B: Platform only | Forecasting platform, implementation and training | 24 months | $27,000 a year plus $5,000 one-time | Teams that want to start with forecast views only |
Next steps to a decision
| Step | Example entry |
|---|---|
| Proposal review with the CFO | 13 November 2026, Dana Okafor and Helen Avery |
| Security review | 16 November 2026, Marlow & Finch IT |
| Decision and quote | 20 November 2026; formal quote for the chosen option the same day |
| Signature and kick-off | Order form signed by 26 November 2026; kick-off 1 December 2026 |
Example: fictional company. Ferncastle Analytics, Harborview Metrics, Marlow & Finch Logistics and every person named in this example are invented for illustration. Any resemblance to real companies or people is coincidental.
How to write a sales proposal
Finish discovery first
Confirm the problem, its cost, the people who decide and the decision process before you write. A proposal cannot fix a deal where those are still unknown.
Write the buyer's section before yours
Describe their situation, the cost of the problem and the outcomes in their words and numbers. Only then describe your solution and how it meets each requirement.
Offer two or three options
Present a recommended option and one or two alternatives with different scope. Options let the buyer choose between your offers rather than between you and a competitor.
Make the plan concrete
Show phases with dates and responsibilities on both sides, and how success will be measured at the first review.
Review it with your champion
Share a draft with your main contact and ask what their colleagues will object to. Fix it before the proposal circulates.
Send it with dated next steps
End with the steps to a decision, each with a date and an owner, and share the proposal where you can see who has read it.
Common sales proposal mistakes
Leading with the company story
Pages about your history and awards push the buyer's problem off the first page. Start with their situation and your recommendation.
Generic copy
A proposal that could be sent to any customer reads like one. Use the buyer's numbers, names and deadlines.
One take-it-or-leave-it price
A single price invites a yes-or-no comparison with competitors. Offer options with different scope.
No next steps
Proposals without dated next steps sit in inboxes. Say what happens next, when and who does it.
Sending it before discovery is done
If you cannot write the cost of the problem in the buyer's words, it is too early to propose.
Attaching it to an email and hoping
Once it is forwarded you lose sight of it. Share it somewhere you can see who opened it and follow up with the right people.
How Revspire runs this template
Revspire Digital Sales Rooms give each deal a branded room the buyer and seller share, so the proposal sits next to the mutual action plan, buying-committee stakeholder mapping and the rest of the deal content, with secure content sharing and real-time buyer engagement analytics that show who has read it.
When the buyer picks an option, Revspire CPQ builds the quote from guided configuration and global price books, with discounts routed for approval, so the price in the proposal and the price on the quote stay the same.
Sales proposal template FAQs
What should a sales proposal include?
An executive summary, the buyer's situation and goals in their words, the recommended solution and how it meets each requirement, an implementation plan, pricing options, relevant proof, risks and assumptions, and dated next steps to a decision.
How long should a sales proposal be?
Long enough to cover the sections above and no longer. The first page matters most: it should state the problem, the recommendation, the price and the decision date, because many readers will not go further.
What is the difference between a proposal and a quote?
A proposal makes the case for a solution and usually presents options. A quote prices the option the buyer chooses, line by line, with terms and a validity date. Most B2B deals send the proposal first and the quote once an option is chosen.
When should you send a sales proposal?
After discovery has confirmed the problem, its cost, who decides and how, and ideally after your main contact has reviewed a draft. Sending one earlier usually produces a document nobody can act on.
Related templates and reading
- Free templateMutual action plan templateA shared, dated plan from discovery to go-live, with a buyer owner and a seller owner on every milestone.
- Free templateStakeholder map templateEvery person in the buying group on one page, with buying role, influence, stance, priorities and a next action.
- Free templateSales enablement business case templateA one-page sales enablement business case: the problem, what ramp, rep time and turnover cost today, the options, the numbers and a dated decision ask.
- Free templateSales close plan templateEvery remaining step between verbal intent and signature, with owners on both sides, the approval chain and the risks the buyer never sees.
- Template: the priced offer for the option the buyer choosesSales quote template
- Template: the document the buyer signsSaaS order form template
- Listicle: tools for building and tracking proposalsBest sales proposal software
- Platform: share the proposal next to the mutual action planRevspire Digital Sales Rooms