← Index6 entries · By Task
Section IV · For the Task

Prompts for writing proposals

Prompts that turn project briefs into clear, scoped client proposals.

§ Overview

A proposal is where a conversation becomes a commitment, and most of them lose the deal in the gap between what the client said they wanted and what the document actually promises. AI is good at closing that gap because it can take messy discovery notes and reorganize them into the structure a buyer needs to say yes: clear scope, explicit boundaries, pricing, and acceptance terms.

The prompts here cover the full arc of winning and documenting work. "Turn Discovery Notes Into a Tailored Sales Proposal" and "Write a Tight Client Proposal With Scope and Pricing" handle the core document. Around them sit the pieces that move a deal forward: a "Post-Call Deal Recap" that locks in next steps, a "One-Page Decision Memo" for internal buy-in, and a "Business Case With ROI and Payback" for when the buyer needs to justify the spend upstairs.

The common failure is scope creep written right into the proposal. Vague deliverables invite endless revisions. Use the model to draft an explicit out-of-scope section, because what you exclude protects your margin as much as what you include.

§ Field Notes

What makes a good prompt for writing proposals

A strong proposal prompt feeds the model the buyer's own words. The single biggest lever is pasting your real discovery notes so the proposal mirrors the client's stated goals and pain points rather than generic benefit-speak. A proposal that quotes the buyer back to themselves feels tailored because it is.

Good prompts also force structure and boundaries. Ask explicitly for an out-of-scope section, milestone-based pricing, and acceptance criteria. These are the clauses that prevent disputes later, and they're easy for a human to forget under deadline. A prompt that demands them every time turns your proposals into a repeatable, defensible system.

§ Pro Tips

Get sharper results

  • 01Paste raw discovery notes verbatim. The model will map your scope and pricing to the exact goals the client named, which is far more persuasive than generic value claims.
  • 02Always generate an explicit out-of-scope list. Naming what you won't do is the cheapest protection against revision creep and margin erosion.
  • 03Tie pricing to milestones, not one lump sum. It makes the number feel earned and gives the buyer natural checkpoints to approve.
  • 04Pair the proposal with the post-call recap email so the client gets a forward-ready summary of next steps while the conversation is still warm.
§ FAQ

Common questions

How detailed should the discovery notes I paste in be?

More detail is better, even if it's messy. Include the client's goals in their own phrasing, their constraints, budget signals, and anything they flagged as a worry. The model turns that raw material into a structured proposal that feels custom, and it can't reflect a concern you never recorded.

Can AI handle the pricing section, or should I do that myself?

Let the model structure the pricing, scope, and milestones, but set the actual numbers yourself. It's good at organizing a tiered or milestone-based layout, not at knowing your costs or market rate. Treat any figure it suggests as a placeholder to replace.

What's the fastest way to turn a sales call into a proposal?

Run the post-call recap prompt immediately after the call to capture next steps and confirmed understanding, then feed those same notes into the proposal prompt. The recap doubles as both a relationship touchpoint and the clean input your proposal draft needs.

§ The Prompts · 6