Write a Business Case Your Champion Can Take Internally

    You are building the document a champion uses to win an internal argument. You will not be in the room; this has to work without you.

The customer and what they'd be buying: {{deal}}
The problem, and everything I know about what it costs them: {{problem_and_cost}}
What they've told me about their goals and metrics: {{their_metrics}}
Price and structure: {{pricing}}
Who has to approve, and what they care about: {{approvers}}
What else they might spend this money on: {{competing_priorities}}
Evidence I have — comparable customers, results, benchmarks: {{proof}}

Produce:

**The problem in their numbers.** Quantify {{problem_and_cost}} using {{their_metrics}}. Show every assumption and its source, and prefer their figures to mine — a number the customer supplied is one they'll defend. Where I've had to estimate, mark it clearly and keep it conservative. An overstated business case dies in the first finance review.

**Cost of doing nothing.** What this costs over the next year if they don't act. This is the most important section, because the real competitor is inaction, not another vendor.

**Expected return.** What changes, by how much, and by when. Include the ramp — nothing delivers full value on day one, and claiming it does destroys credibility. Give a conservative case and a likely case; skip the best case entirely.

**The investment.** {{pricing}} plus honest total cost: implementation, training, internal time, anything they'd have to stop doing. Listing hidden costs myself is what makes the rest believable.

**Payback and comparison.** When it breaks even, and how that compares against {{competing_priorities}}.

**Risks, and how they're handled.** The three things an approver will worry about — adoption, implementation effort, vendor risk, switching cost — each answered plainly. Address them before finance raises them.

**Evidence.** From {{proof}}, the most relevant comparable, described in a way that survives scrutiny. Name the ways their situation differs.

**The one-page version** for the approver who won't read the rest, tuned to what {{approvers}} care about.

Write in their language, not mine — no product names as headings, no marketing adjectives. If {{problem_and_cost}} lacks real numbers, tell me exactly which figures I need to go get from my champion, because without them there's no business case here.