Sales
Sales Proposal: How to Write One That Moves Deals Forward Instead of Stalling Them
A sales proposal is the document a prospect uses to justify buying from you. It is not a brochure, a capabilities deck, or a price list. It is a decision document. The best sales proposals are built on what you learned during discovery, not on a template you filled in with the company name. They restate the prospect's problem in their own language, quantify what that problem is costing them, present your solution as the specific answer to that specific problem, and make the purchase feel inevitable rather than risky. Most sales proposals lose because they describe the product instead of describing the outcome. If your proposal reads the same whether you are sending it to a 50-person startup or a 5,000-person enterprise, it is a brochure, not a proposal.
From discovery call to proposal: what to carry forward
The proposal should feel like a continuation of the sales conversation, not a generic document that could have been sent before the call happened. Pull specific details from discovery: the prospect's current process, the pain points they described, the metrics they care about, and the timeline they mentioned. Use their language, not yours. If they called it a "pipeline visibility problem," do not relabel it as a "revenue intelligence opportunity" in the proposal. Mirror their words back to them. This signals that you listened, and it makes the proposal easier for an internal champion to circulate because it already uses the vocabulary their team recognizes.
- Restate the prospect's problem using their exact language
- Reference specific pain points and metrics from discovery
- Include the timeline and constraints they mentioned
- Write for the internal champion who will circulate it
Framing ROI without fabricating numbers
Prospects expect an ROI case, but they are skeptical of inflated projections. Ground your ROI analysis in numbers the prospect provided or can verify. If they told you their sales team spends 12 hours per week on manual reporting, calculate the cost of those hours at their average compensation. If they shared their close rate, model what a 10% improvement would mean in revenue. Avoid presenting ROI as a guarantee. Instead, frame it as a scenario: "Based on the numbers you shared, if this solution saves your team 8 hours per week, the annual value is roughly $X." Scenario-based ROI is credible because it is grounded in the prospect's own data and it invites them to adjust the assumptions rather than dismiss the conclusion.
- Use numbers the prospect provided or can verify
- Model scenarios rather than guaranteeing outcomes
- Tie savings or gains to metrics the prospect already tracks
- Invite the prospect to adjust assumptions
Writing for the buying committee, not just your contact
Most B2B purchases involve three to seven decision-makers. Your contact is rarely the only person who needs to approve the deal. The proposal must work for people who were not in the discovery call and who have different priorities. The CFO wants to see cost justification. The end user wants to see ease of adoption. The IT lead wants to see security and integration details. Structure the proposal so each stakeholder can find what they need quickly. The executive summary should satisfy a time-constrained executive. The detailed sections should satisfy the evaluators. If your proposal only makes sense to someone who was in the room during discovery, it will stall when it reaches the rest of the committee.
Competitive positioning without naming competitors
Sales proposals rarely name competitors directly, and they should not. Instead, position against the alternatives implicitly. If the main competitor is cheaper but less reliable, emphasize your uptime guarantees and support responsiveness without saying "unlike Competitor X." If the prospect is considering building in-house, address the total cost of ownership, maintenance burden, and opportunity cost of engineering time. Include a section called "Why this approach" or "What sets this apart" that focuses on the capabilities and commitments that matter most to this specific prospect. The framing should make the prospect's other options feel riskier by comparison, not by accusation.
Closing terms and next steps
The end of the proposal should make it easy to say yes. Include a clear summary of the investment, the start date, and what happens immediately after signing. Spell out the onboarding process in two or three sentences so the prospect can visualize the transition. Include a signature block or an approval mechanism. If the proposal requires legal review, note the expected turnaround and offer to provide a redline-ready version of the terms. Set a validity period for the pricing, typically 30 days, to create urgency without pressure. The last impression the proposal leaves should be confidence and momentum, not ambiguity about what happens next.
Generate a sales proposal from your next call
Paste your call notes and get a structured proposal with scope, pricing, timeline, and terms.
Try the free generatorFAQ
How quickly should I send a sales proposal after the discovery call?
Within 48 hours. Speed signals competence and keeps momentum from the conversation. If the proposal requires internal approvals on your side, tell the prospect during the call when to expect it and hit that deadline. A proposal that arrives a week late competes with whatever else landed on the prospect's desk since then.
Should a sales proposal include case studies?
Yes, if they are relevant to the prospect's industry or problem. One strong case study that mirrors the prospect's situation is more persuasive than five generic ones. Include the starting condition, what you did, and the measurable outcome. Keep it to half a page or less.
How many pricing options should a sales proposal include?
Two or three. One option feels like a take-it-or-leave-it ultimatum. Four or more creates decision fatigue. Three options work well: a baseline that solves the core problem, a recommended option with additional value, and a premium option for prospects who want everything. Label the recommended option clearly.
What is the difference between a sales proposal and a quote?
A quote lists prices for specific products or services. A sales proposal builds a case for why the prospect should buy, then includes pricing as part of that case. Quotes work for commodity purchases where the buyer already knows what they want. Proposals work for considered purchases where the buyer needs to be convinced of the approach, not just the price.