Build a simple ROI business case for your champion to defend
Champions often want to buy but struggle to justify cost internally. This prompt builds a concise, number-backed business case in email form that your champion can paste into an internal message or present to finance without help.
You are a sales strategist helping a B2B rep support their champion at a prospect company. Write a business case summary the champion can share internally to justify the purchase.
1. Open with the business problem being solved — one sentence, written from the perspective of the prospect company, not the vendor.
2. Quantify the current cost of the problem using the inputs I provide. Show the math explicitly — don't just state a number.
3. Show the expected value of solving it with our product: use conservative, base-case, and optimistic scenarios. Label them clearly. Do not round aggressively or inflate.
4. Calculate a simple payback period: how many months before the investment breaks even under the base case?
5. List two or three non-financial benefits (time savings, risk reduction, etc.) — keep these brief and tied to outcomes the finance team cares about.
6. Write a one-paragraph summary the champion can use as the opening of an internal email or a slide title, written in their voice, not a vendor's.
7. Flag any assumptions I should validate before the champion shares this — weak assumptions undermine credibility.
Prospect company name and industry: {{COMPANY_NAME_INDUSTRY}}
Our product and annual cost: {{PRODUCT_AND_PRICE}}
Known problem metrics (time lost, error rates, headcount, etc.): {{PROBLEM_METRICS}}
Expected outcomes / results data we have: {{EXPECTED_OUTCOMES}}
If the problem metrics are thin or estimated, flag the business case as directional only and recommend getting finance-validated numbers before sharing. {{COMPANY_NAME_INDUSTRY}}{{PRODUCT_AND_PRICE}}{{PROBLEM_METRICS}}{{EXPECTED_OUTCOMES}}
How to use this prompt
- Copy the prompt above (Copy button on the top-right).
- Replace each
{{VAR}}with your own value. Variables:{{COMPANY_NAME_INDUSTRY}}{{PRODUCT_AND_PRICE}}{{PROBLEM_METRICS}}{{EXPECTED_OUTCOMES}}. - Paste it into one of the recommended tools below.
- Iterate: tighten constraints in the prompt if the output is generic.
Why this prompt is structured this way
The prompt is split into explicit steps because LLMs do better when the path is named, not implied. Each variable forces specificity at the input layer — vague inputs get vague outputs.
Pair this prompt with a tool
Grammarly
$12/moGrammar, tone, and clarity across every app.
Grammarly remains the default for grammar + tone checking. The 'Grammarly Go' generative features are catching up but are not the main reason to subscribe.
Notion AI
$8/user/mo add-onAI baked into the docs/wiki/projects tool you already use.
Notion AI is unremarkable as a standalone writer but indispensable if Notion is your team's source of truth — it works on the docs and databases you already have.
Claude (Anthropic)
$0/mo (Pro at $20)Frontier model with long context and strong reasoning.
Claude (Opus / Sonnet / Haiku tiers) is the assistant favored by writers and engineers who care about reasoning quality and tone. 1M token context on Opus.
ChatGPT (OpenAI)
$0/mo (Plus at $20)The category-defining general-purpose AI assistant.
ChatGPT has the broadest feature surface: image gen, voice, custom GPTs, web browsing, code execution. Often the right default; sometimes beaten on specific tasks by Claude or Perplexity.
The PlaybookPrompts weekly
One short email per week. The five sharpest prompts we found, one tool worth your attention, one anti-pattern to avoid. Unsubscribe in one click.
Newsletter signup is not configured. Set PUBLIC_NEWSLETTER_USERNAME in the build env.