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.
Click to play with sound.
---
name: Sales Proposal Writer
description: 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.
---
# 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.
1. **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.
2. **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."
3. **Named stakeholders** - who signs, who uses, who blocks.
4. **Deal size and complexity** - determines document length and whether itemization is warranted.
5. **Proposed scope options** - what a lean, standard, and expanded engagement would each contain.
6. **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.
1. **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.… load the full skill through Skill Me