Client Proposal Writer

Turn discovery notes into a proposal that restates the client problem in their words, scopes the work, and prices it with clear boundaries.

Act as a consultant who writes proposals that get signed. Turn my notes into a proposal.

My discovery notes (verbatim, messy is fine):
"""
[PASTE NOTES, QUOTES, EMAILS]
"""

Details:
- Client and contact: [COMPANY, NAME, ROLE]
- What I propose to do: [SCOPE IN ONE OR TWO SENTENCES]
- Price and structure: [AMOUNT — FIXED FEE / RETAINER / HOURLY]
- Timeline: [START, MILESTONES, END]
- What I need from them: [ACCESS, APPROVALS, CONTENT, SIGN-OFFS]

Write the proposal with these sections:
1. The situation — their problem restated in their own words, quoting my notes where possible
2. The outcome — what is measurably different when this is done, with the metric they named
3. Approach — the phases, what happens in each, and what they receive at the end of each
4. What is not included — the explicit out-of-scope list that prevents a scope fight later
5. Investment — the price, what it covers, payment schedule, and what a change request costs
6. Timeline — dates and the dependencies that would move them
7. Why me — three sentences maximum, tied to this specific problem
8. Next step — one action with a date

Rules:
- Use their vocabulary, not mine
- No adjectives that cannot be verified ("world-class", "cutting-edge")
- Flag any place where my notes are too thin to write a real section, as [MISSING: what to ask]
- Keep the whole thing under two pages

How to use this prompt

• Paste raw notes rather than a tidy summary — the client's exact phrasing is what makes the proposal feel written for them.
• Do not remove the "what is not included" section, even if it feels negative. It is the section that protects you.
• Resolve every [MISSING] flag before sending; each one is a question you still owe the client.

Why this prompt works

Proposals lose when they describe the seller instead of the buyer. Making the model quote your discovery notes back forces the document to prove you listened, and separating scope from out-of-scope converts the most common post-signature argument into a pre-signature agreement.

Variations to try

• Ask for a one-page version for a smaller engagement, keeping only sections 1, 2, 5, and 8.
• Add "include three pricing tiers with a clear reason to pick each" for optionality.
• Ask the model to review a proposal you already sent and list every unverifiable claim.

Common mistakes to avoid

• Letting the model invent a metric the client never mentioned — always check section 2 against your notes.
• Deleting the change-request line to seem flexible, then absorbing three weeks of unpaid work.
• Sending a proposal longer than the discovery call that produced it.

Works well with