회수 기간과 세 가지 시나리오를 담은 CFO용 비즈니스 케이스

Role: You are a value-engineering lead who has built more than 150 business cases for B2B software and services deals between 50,000 and 5 million dollars, and who has sat across from CFOs who cut every number in half before believing it.
Context: [prospectCompany] is evaluating [productService]. The champion supports us, but the deal of about [dealSize] over a [contractTerm]-month term needs finance sign-off, and the CFO has not met us. The document will be forwarded without us in the room, so every number must trace back to something the buyer told us or to an assumption they can edit.
Task: Write a business case the champion can hand to finance as-is: baseline cost of the current state, three value drivers, payback and return over the term, three scenarios, an editable assumptions table, and the challenges finance will raise with our answers.
Inputs:
- [prospectCompany]: the buyer; use their name throughout, never "the client".
- [productService]: what we sell and the price basis (per seat, per site, flat).
- [buyerMetrics]: numbers the buyer shared (headcount, hours, volumes, error rates, current spend, targets). Build the baseline only from these. If a needed number is missing, insert a clearly labeled assumption with a plausible range and continue; do not invent a precise figure.
- [dealSize]: total contract value; treat it as the investment line.
- [contractTerm]: term in months; compute every return over exactly this term.
Constraints:
- Use the buyer's units and currency; state the currency once and keep it.
- Separate hard savings (cash leaving the company), soft savings (time freed) and revenue upside; finance weights them differently, so never add them into one headline number without showing the split.
- The conservative scenario must still work with the smallest driver removed; if it does not, say so plainly.
- No vendor claims without a source: mark each figure as "customer-reported", "buyer-provided" or "assumption".
- Include implementation cost, internal time and change effort on the cost side.
- Plain English, no superlatives, under 900 words for the full document.
- Before answering, check that every number appears in the assumptions table and that payback is recomputed per scenario.
Output format:
Markdown with these numbered sections and headings:
1. One-paragraph summary with the payback month, net return over the term and the single assumption that matters most.
2. Baseline: a table with columns Cost item, Annual amount, Source, Confidence.
3. Value drivers: exactly three, each with mechanism, formula, annual value and type (hard, soft, revenue).
4. Scenarios: a table with columns Scenario (conservative, expected, upside), Key assumption changes, Annual value, Payback month, Net return over term.
5. Assumptions table with columns Assumption, Value used, Range, Who can confirm.
6. What finance will challenge: five objections, each with a two-sentence answer and the data that would settle it.
7. Three questions for the champion to confirm before this goes to the CFO.