Sales Proposal Writer
A proposal should make the buyer feel understood before it sells anything. If the first page is about the vendor, the buyer stops reading; if the price appears as one take-it-or-leave-it number, the negotiation becomes about discounting instead of scope. This skill produces a proposal that mirrors the buyer's own words back to them, anchors the price with options, and expires - so the deal has a reason to move.
Inputs to collect
Gather these before drafting. Where an input is missing, use the default and label the guess as a guess.
- Discovery notes or call transcript - the buyer's own phrasing of the problem is the raw material for the opening. Without at least one direct quote or near-quote, the proposal will read as a template.
- The quantified pain - numbers the buyer gave (hours lost, revenue at risk, headcount cost). If none surfaced, compute a reasonable range and flag it: "estimated, based on your stated team size of 12."
- Named stakeholders - who signs, who uses, who blocks.
- Deal size and complexity - determines document length and whether itemization is warranted.
- Proposed scope options - what a lean, standard, and expanded engagement would each contain.
- Desired start date - anchors the validity window and the next step.
Operating procedure
Order matters: the buyer's problem must be established before any solution appears, and price must never appear before value.
- Restate their problem in their words, first. Open with a two-to-three-sentence situation summary that mirrors discovery. Quote the buyer directly where possible. This section mentions the vendor zero times.
- Make the cost of inaction concrete. Use the buyer's numbers. "Your team currently spends ~40 hours/month reconciling exports, roughly $48K/year at your stated loaded cost" beats any adjective. Label estimates as estimates.
- Present the approach as outcomes, not activities. "Your team will be able to close the books in 3 days instead of 9" beats "We will deliver a data pipeline." One paragraph per outcome.
- Define scope and deliverables per phase or workstream. Specific enough to be credible, loose enough to avoid scope arguments before the contract is signed. Push technical detail to an appendix.
- Present the investment as options with an anchor. Offer two or three tiers, listed highest first - the anchor. The middle option is the one most buyers should choose; design it that way. Do not itemize line-by-line unless the buyer asked or the deal is complex enough to require it: itemized pricing invites nickel-and-diming. A single number is acceptable only for transactional deals under roughly $10K.
- Add a validity window. Every proposal expires - 30 days is standard; 14 days for a deal with a stated urgent start date. An open-ended proposal gives the buyer permission to stall indefinitely.
- Close with one dated next step. One action, one suggested date within 5 business days: "If this looks right, the simplest path forward is a 30-minute call Tuesday to align on the start date."
- Run the customization check. Confirm at least three details that could only apply to this buyer: their team size, a specific pain they named, a named stakeholder. Fewer than three and the proposal reads as a mail merge - and will be treated like one.
Thresholds
- Body length: under 3 pages for a typical mid-market deal; readable in under 5 minutes. Appendices carry technical specs and legal terms.
- Situation summary: 2-3 sentences, at least one buyer quote or near-quote.
- Pricing: 2-3 options, anchor listed first; middle option designed as the intended choice.
- Validity: 30 days standard, 14 days when urgency is real.
- Next step: dated within 5 business days of sending.
- Customization: minimum 3 buyer-specific details.
Proposal skeleton (copy and fill)
[BUYER COMPANY] - Proposal: [OUTCOME, NOT PRODUCT NAME]
Prepared for [STAKEHOLDER NAME], [DATE] · Valid through [DATE + 30 DAYS]
1. YOUR SITUATION
[2-3 sentences mirroring discovery. Include: "[DIRECT BUYER QUOTE]"]
2. WHAT THIS IS COSTING YOU
[FILL: buyer's numbers → annualized cost. Label estimates: "estimated, based on [STATED FACT]"]
3. PROPOSED APPROACH
[FILL: 2-3 outcome statements - "Your team will be able to X"]
4. SCOPE & DELIVERABLES
Phase 1 - [NAME]: [deliverables, duration]
Phase 2 - [NAME]: [deliverables, duration]
5. INVESTMENT
Option A - [EXPANDED SCOPE]: $[ANCHOR PRICE]
Option B - [STANDARD SCOPE]: $[INTENDED PRICE] ← most clients choose this
Option C - [LEAN SCOPE]: $[FLOOR PRICE]
Pricing valid through [DATE].
6. NEXT STEP
[ONE action, ONE date]: "If this looks right, a 30-minute call on [DAY] to align on start date."
Appendix: [technical specs / legal terms / assumptions]
Deliverable
Produce a proposal document containing: the buyer-worded situation summary, the quantified cost of inaction, outcome-framed approach, phased scope, a 2-3 option anchored investment section with a validity date, one dated next step, and an appendix for anything technical or legal.
Do NOT
- Do NOT lead with a company bio or awards page - it signals a template and the buyer stops reading.
- Do NOT list features the buyer never asked about - every unrequested feature dilutes the ones they did.
- Do NOT include a generic ROI calculator not built from the buyer's actual data - it undermines credibility more than it helps.
- Do NOT present price before value - investment is section 5, never section 1.
- Do NOT skip the expiry date - an undated proposal has no forcing function.
- Do NOT write a formal document for a small transactional deal. Use the same structure - situation, value, scope, price, next step - as three short paragraphs in an email instead.
Quality bar
Before sending, verify: the first section contains zero vendor mentions and at least one buyer quote; the cost of inaction has a number; pricing shows options with the anchor first and a validity date; the next step names a date; at least three buyer-specific details appear; the body reads in under five minutes with no jargon, buzzwords, or passive voice. Any sentence that does not add information the buyer needs to decide gets cut.
1---2name: sales-proposal-writer3description: Writes a B2B sales proposal or SOW that restates the buyer's problem in their own words, quantifies the cost of inaction, presents price as anchored options, and drives one dated next step. Use when someone asks "write a proposal for this client", "turn my discovery notes into a proposal", "how should I present pricing in this proposal", or when a deal needs a document to move from discovery to close. Do NOT use for a one-page internal decision brief - use one-pager-designer instead; for investor decks use pitch-deck-builder; for setting the underlying price model use pricing-strategy.4---56# Sales Proposal Writer78A proposal should make the buyer feel understood before it sells anything. If the first page is about the vendor, the buyer stops reading; if the price appears as one take-it-or-leave-it number, the negotiation becomes about discounting instead of scope. This skill produces a proposal that mirrors the buyer's own words back to them, anchors the price with options, and expires - so the deal has a reason to move.910## Inputs to collect1112Gather these before drafting. Where an input is missing, use the default and label the guess as a guess.13141. **Discovery notes or call transcript** - the buyer's own phrasing of the problem is the raw material for the opening. Without at least one direct quote or near-quote, the proposal will read as a template.152. **The quantified pain** - numbers the buyer gave (hours lost, revenue at risk, headcount cost). If none surfaced, compute a reasonable range and flag it: "estimated, based on your stated team size of 12."163. **Named stakeholders** - who signs, who uses, who blocks.174. **Deal size and complexity** - determines document length and whether itemization is warranted.185. **Proposed scope options** - what a lean, standard, and expanded engagement would each contain.196. **Desired start date** - anchors the validity window and the next step.2021## Operating procedure2223Order matters: the buyer's problem must be established before any solution appears, and price must never appear before value.24251. **Restate their problem in their words, first.** Open with a two-to-three-sentence situation summary that mirrors discovery. Quote the buyer directly where possible. This section mentions the vendor zero times.262. **Make the cost of inaction concrete.** Use the buyer's numbers. "Your team currently spends ~40 hours/month reconciling exports, roughly $48K/year at your stated loaded cost" beats any adjective. Label estimates as estimates.273. **Present the approach as outcomes, not activities.** "Your team will be able to close the books in 3 days instead of 9" beats "We will deliver a data pipeline." One paragraph per outcome.284. **Define scope and deliverables per phase or workstream.** Specific enough to be credible, loose enough to avoid scope arguments before the contract is signed. Push technical detail to an appendix.295. **Present the investment as options with an anchor.** Offer two or three tiers, listed highest first - the anchor. The middle option is the one most buyers should choose; design it that way. Do not itemize line-by-line unless the buyer asked or the deal is complex enough to require it: itemized pricing invites nickel-and-diming. A single number is acceptable only for transactional deals under roughly $10K.306. **Add a validity window.** Every proposal expires - 30 days is standard; 14 days for a deal with a stated urgent start date. An open-ended proposal gives the buyer permission to stall indefinitely.317. **Close with one dated next step.** One action, one suggested date within 5 business days: "If this looks right, the simplest path forward is a 30-minute call Tuesday to align on the start date."328. **Run the customization check.** Confirm at least three details that could only apply to this buyer: their team size, a specific pain they named, a named stakeholder. Fewer than three and the proposal reads as a mail merge - and will be treated like one.3334## Thresholds3536- Body length: under **3 pages** for a typical mid-market deal; readable in under **5 minutes**. Appendices carry technical specs and legal terms.37- Situation summary: 2-3 sentences, at least one buyer quote or near-quote.38- Pricing: 2-3 options, anchor listed first; middle option designed as the intended choice.39- Validity: 30 days standard, 14 days when urgency is real.40- Next step: dated within 5 business days of sending.41- Customization: minimum 3 buyer-specific details.4243## Proposal skeleton (copy and fill)4445```46[BUYER COMPANY] - Proposal: [OUTCOME, NOT PRODUCT NAME]47Prepared for [STAKEHOLDER NAME], [DATE] · Valid through [DATE + 30 DAYS]48491. YOUR SITUATION50[2-3 sentences mirroring discovery. Include: "[DIRECT BUYER QUOTE]"]51522. WHAT THIS IS COSTING YOU53[FILL: buyer's numbers → annualized cost. Label estimates: "estimated, based on [STATED FACT]"]54553. PROPOSED APPROACH56[FILL: 2-3 outcome statements - "Your team will be able to X"]57584. SCOPE & DELIVERABLES59Phase 1 - [NAME]: [deliverables, duration]60Phase 2 - [NAME]: [deliverables, duration]61625. INVESTMENT63Option A - [EXPANDED SCOPE]: $[ANCHOR PRICE]64Option B - [STANDARD SCOPE]: $[INTENDED PRICE] ← most clients choose this65Option C - [LEAN SCOPE]: $[FLOOR PRICE]66Pricing valid through [DATE].67686. NEXT STEP69[ONE action, ONE date]: "If this looks right, a 30-minute call on [DAY] to align on start date."7071Appendix: [technical specs / legal terms / assumptions]72```7374## Deliverable7576Produce a proposal document containing: the buyer-worded situation summary, the quantified cost of inaction, outcome-framed approach, phased scope, a 2-3 option anchored investment section with a validity date, one dated next step, and an appendix for anything technical or legal.7778## Do NOT7980- **Do NOT lead with a company bio or awards page** - it signals a template and the buyer stops reading.81- **Do NOT list features the buyer never asked about** - every unrequested feature dilutes the ones they did.82- **Do NOT include a generic ROI calculator** not built from the buyer's actual data - it undermines credibility more than it helps.83- **Do NOT present price before value** - investment is section 5, never section 1.84- **Do NOT skip the expiry date** - an undated proposal has no forcing function.85- **Do NOT write a formal document for a small transactional deal.** Use the same structure - situation, value, scope, price, next step - as three short paragraphs in an email instead.8687## Quality bar8889Before sending, verify: the first section contains zero vendor mentions and at least one buyer quote; the cost of inaction has a number; pricing shows options with the anchor first and a validity date; the next step names a date; at least three buyer-specific details appear; the body reads in under five minutes with no jargon, buzzwords, or passive voice. Any sentence that does not add information the buyer needs to decide gets cut.
SkillMedev