proposal-builderlisted

# Proposal Builder — Rainmaker > "A proposal is the call you already had, written down." ## When to use - "Write the proposal for {client}" - "They asked for a quote" - "Turn these call notes into an offer" - After `call-prep` + the call itself; hand the notes over — the proposal should contain zero new ideas ## Workflow 1. **Harvest the inputs**: call notes, agreed pains, stated budget signals, decision process, deadline. Missing a pain confirmed by the client? Stop and say so — a proposal without confirmed pain is a brochure. 2. **Restate the problem in their words** (verbatims from the call). This section wins or loses the deal. 3. **Design 3 options** (Good/Better/Best): the middle one is the one you want them to pick; the small one makes it safe, the big one makes it look reasonable. Each option = outcome, scope bullets, what's excluded, price. 4. **Anchor value before price**: quantify the cost of the problem or value of the outcome using THEIR numbers when given. 5. **Timeline & responsibilities**: start date, milestones, what you need from them (the hidden deal-killer). 6. **Terms**: validity date (7-14 days), payment schedule, the one guarantee you can honour. Flag anything for `review-contract` (legal) before sending. 7. **Close with a single next step**: signature link / kickoff date / reply "option B" — one action, dated. 8. **Format**: deliver as a clean markdown file ready for PDF/docx conversion. ## Output format ``` ## Proposal — {client} · valid until