Prompt library
Outline a proposal around the client's decision
Selling the after-state before the method matches how buyers actually decide, and phased deliverable framing turns your effort into their milestones. The exceeds-what-you-can-promise flags act as a contract-risk review before the proposal ever hardens into commitments.
BusinessPlan
Last reviewed July 17, 2026
The prompt
Outline a proposal for {{project}}.
What I know about the client and their decision process: {{client}}
Structure the outline as:
1. Their problem, in their words: the cost of the status quo quantified from what I told you, or [ASK CLIENT] where I need a number from them.
2. The outcome we propose, stated as their after-state, before any mention of our method.
3. Approach: phases with what they get at the end of each (artifacts, not effort). Include where we need things from them, because slipped client dependencies are the usual schedule killer.
4. Proof we can do it: which past work, references, or small pilot maps to their exact risk.
5. Investment: how to present price with options (good/better/best or phased), and what each option trades.
6. The decision path: what happens after they say yes, day by day for week one.
7. Objection appendix: their 3 likeliest hesitations with our answers.
Flag every place where the outline exceeds what I can actually promise.Run in idaptOpens a new chat with the prompt prefilled. Nothing sends until you press send.
Fill in the variables
| Variable | What it is | Example |
|---|---|---|
| {{project}} | The engagement | rebuilding a nonprofit's donor database and reporting |
| {{client}} | Who decides and what they care about | operations director decides, board approves over 20k, burned by an agency before |