Create a winning proposal

Step 1 — Load the call, not your memory of it

Paste the whole transcript as text — signal, not summary. The winning proposal is already in there: what they want, what they’re afraid of, what "good" looks like to them, and the exact words they use for all three. Your memory compresses that into "they need a website." The transcript kept the gold.

Below is the transcript of a discovery conversation with [client] about [project]. Extract, with quotes: (1) what they SAY they want; (2) what they seem to actually need, where that differs; (3) every fear, objection, or bad past experience they mentioned; (4) how they describe success, in their own words; (5) constraints — budget signals, timeline, who decides; (6) the vocabulary they use for their business. Nothing that isn’t grounded in the transcript — mark gaps as UNKNOWN.

UNKNOWN is load-bearing, again. A proposal that guesses at budgets or invents needs reads like every other proposal — the model fluently completing the average one instead of yours.

Step 2 — Add your half of the truth

The transcript is their half. Now load yours: what you actually offer, real prices, honest dates, and two or three past projects that matter here. Short bullets, real numbers.

Here is my side: [services · real pricing · availability · 2–3 relevant past projects]. Rules for everything that follows: nothing outside this list may be offered, and no price, date, or capability may be invented.

Every commitment in the final document must trace to a window you loaded. The model may arrange your facts; it may never mint new ones.

Step 3 — Draft it in their language

Draft the proposal: (1) THE SITUATION — their goal and its stakes, in their vocabulary, so they recognize themselves in the first paragraph; (2) WHAT WE’LL DO — concrete scope, each deliverable traceable to a want or fear from the extraction; (3) HOW IT WORKS — steps, timeline, what I need from them; (4) INVESTMENT — from my numbers only; (5) WHAT SUCCESS LOOKS LIKE — their definition, made measurable; (6) NEXT STEP — one clear action. Address their fears without labeling them as fears. Two pages. Where anything is UNKNOWN, leave me a bracketed question, never a guess.

The steering that matters most is the opening: the average proposal talks about the vendor; this one opens with the client recognizing their own situation. That single move is most of why a proposal "feels like you listened" — because, mechanically, it did.

Step 4 — Red-team it from the buyer’s chair

Fresh window — the shape from Red-team critical work, pointed at your own pitch. Paste the transcript, then the draft:

You are the person who received this proposal, and you’ve been burned by vendors before. Above is the call we had; below is the proposal. As this buyer, tell me bluntly: (1) what reads generic or copy-pasted? (2) what did I say on the call that the proposal ignored? (3) which commitments are vague enough to worry me? (4) what would make me say yes faster?

Fold in what stings. Run it once more if the first round drew blood.

Step 5 — Verify every commitment, then send it warm

You’re signing this. Go line by line: every price, date, deliverable, and promise — true, yours, and something you’d happily be held to? Resolve every remaining UNKNOWN by asking the client or cutting the line. The model arranged the words; the commitments are yours.

Then send it while the conversation is still warm. A grounded proposal the next morning beats a polished one next week — speed is itself evidence that working with you feels like this.

---

Check your understanding: why does the proposal open with their situation instead of your services — and where is the model never allowed to be creative?

Use this process for other persuasive documents. Their words + your facts + a buyer’s-chair red-team: that’s the pitch deck, the grant application, the internal business case, the job application. Anything you win by making the reader feel understood.