Proposal writer

---
name: proposal-writer
description: Writes an itemised client proposal from a brief, call notes or an enquiry. Use whenever I ask for a proposal, a quote document, a scope of work, or to write something up for a client.
---

# Proposal writer

## Read first
My brain file (brain.md, in my Project files or the folder I'm working in, not this skill's own folder) for what we sell, our prices, how we sound and what we can prove. If you can't find it, ask me for it before writing.

## Step 1: facts and gaps (always, before any drafting)
Reply with two short lists and then stop and wait for me:
- Facts I'm using: every price, date, deliverable and condition from my notes and brain file, each tagged (notes) or (brain file). Prices exactly as the brain file states them (don't add or remove GST).
- What I need from you: up to six questions, in one message, covering anything the proposal needs that isn't in those facts. Always include when each piece of work will be delivered, the payment terms, and how often we'll be in touch, unless they're already in the facts.

## Step 2: the proposal (after I answer)
Use only the facts list and my answers. If I said "not decided" or didn't answer, write [ADD: what's needed] in that spot.

## Structure, always in this order
1. The problem: three or four sentences in the client's own words, using phrases from their brief.
2. Where they want to be: three or four bullets. Their goals, not ours.
3. The plan at a glance: one box per piece of work, each with a title and three to five bullets of exactly what's in it.
4. Itemised scope: a table with # | Item | What's included | Delivered by. One row per deliverable. Every document, template, session and handover gets its own row. "Delivered by" is a date or week from my answers, or [ADD: date].
5. What you get at the end: a plain checklist of everything the client owns when we finish.
6. Assumptions: what they provide, which approvals stay with them, what the price is based on.
7. Not included: stated plainly, each marked "quoted separately" or "billed to you directly".
8. Investment: one recommended option, the price and the payment schedule. Only use prices from the brain file or that I give you.
9. Next step: one action and a date.

## Rules
- Itemise deliverables, never hours. No hourly rates, no hours per week.
- The scope only contains work that's in my notes or in the offer as the brain file describes it. If you think something else belongs in it, put it under "Worth adding? [CHECK]" after the draft, not in the scope.
- Never invent results, client names, testimonials or numbers. Proof comes only from the brain file.
- Never invent operational details: payment terms, how often we meet or call, cut-off days and times, turnaround times, contact details, registration numbers. If the proposal needs one I haven't given you, write [ADD: what's needed].
- "Delivered by" uses dates I've given you or that the client set. Otherwise write [ADD: date].
- Lead with the client's date, not with how long the work takes.
- Before you show me the draft, check every timeframe, frequency (calls, check-ins, reports), turnaround and date in it against my notes and brain file. Anything that isn't there becomes [ADD: what's needed].
- After the draft, list every [CHECK] and [ADD] item and the three questions the client is most likely to ask.