The prompt
Score 10 of 10, Excellent
Use it when Your contact supports the purchase but must convince a boss or committee, and you want a short, forwardable case written in their terms, not your pitch.
- {{champion}}
- {{decision_maker}}
- {{offer}}
- {{discovery_notes}}
- {{proposal}}
- {{evidence}}
Full prompt and why it works
Prompt
Write a short business case that {{champion}} can forward to {{decision_maker}} to get approval for buying {{offer}}. My contact supports the purchase, but the decision maker was not in our conversations and will read this cold, so it has to stand on its own and read as the buyer's own case, not our sales pitch. What the buyer told us (the problem, what it costs them, what they have tried, their goals), in their words where possible: """ {{discovery_notes}} """ The proposal (price, terms, timeline, what is included): """ {{proposal}} """ Evidence we may share (results from named customers, references, published figures): {{evidence}} Use these headings, and keep it under 450 words: 1. The decision needed: one sentence, with the cost and the date it is needed by. 2. The problem today: what is happening and what it costs or risks, in the buyer's own figures. 3. The proposed solution: what changes, in plain terms, without product jargon. 4. Cost and return: the full cost from the proposal; savings or gains only where the buyer's figures support them, with the arithmetic on one line, for example "3 people x 5 hours a week x 48 weeks = 720 hours a year". 5. Options considered, including doing nothing, one line each. 6. Risks, and how each is handled. 7. Next steps if approved. Write in the buyer's voice ("we" meaning their company), in a plain, factual tone a finance reader would trust. Do not invent savings, hours, percentages or results, and do not use evidence from other customers unless it is listed above. If a section has nothing to support it, write "[needs input: ...]" saying what is missing, and list those gaps after the case so I can raise them with my contact.
Variables
- {{champion}}
- Your contact who supports the purchase, with their role.
- {{decision_maker}}
- Who approves it, for example "their CFO" or "the operations committee".
- {{offer}}
- What they would be buying, in a few words.
- {{discovery_notes}}
- What the buyer told you about the problem, its cost, what they tried and their goals.
- {{proposal}}
- Your proposal's price, terms, timeline and scope.
- {{evidence}}
- Results, references or published figures you are allowed to share, or "none".
Why it works
- Who it's for. It is written for a decision maker who was not on any call, in the buyer's own voice and figures, because a forwarded sales pitch rarely survives an approval meeting.
- What good looks like. Every saving shows its arithmetic on one line from the buyer's own numbers, so a finance reader can check it rather than distrust it.
- If unsure. Sections without support get "[needs input: ...]" and a list of gaps to raise with your contact, instead of invented figures that would sink the case.