Build the ROI business case the CFO will actually read, not the deck your champion saw

I need a business-case document aimed at the CFO, Grace Halvorsen at Windmere Manufacturing, who has not been on a single call with us and will read this cold, applying a level of financial scrutiny that {{champion_name_if_any}} never did.

What we sell: a predictive-maintenance platform for factory equipment. The quantified cost of the problem today, as specifically as it's known: unplanned downtime cost roughly $340,000 last year across two plants, per their own maintenance logs. The expected ROI or payback timeline: projected 9-month payback assuming a 30% reduction in unplanned downtime, based on comparable deployments. Other budget priorities this is competing against for approval: a planned ERP upgrade and a warehouse automation project both up for approval this quarter.

WRITE FOR A SKEPTICAL FINANCIAL READER
A CFO reading this is not evaluating whether the product is good; they're evaluating whether the number being asked for is the best use of that specific amount of money against every other use of it this quarter. Write accordingly: lead with the cost of the current problem in unplanned downtime cost roughly $340,000 last year across two plants, per their own maintenance logs, stated as a number, not a narrative — a CFO who reads "significant inefficiencies" has learned nothing, while one who reads a specific dollar or hour figure has something to actually evaluate. Follow immediately with projected 9-month payback assuming a 30% reduction in unplanned downtime, based on comparable deployments, stated with its actual assumptions visible, not hidden behind a headline multiple — if the ROI figure assumes a specific adoption rate, time savings per employee, or volume figure, name that assumption explicitly rather than presenting the output number alone, since a CFO who can't see the assumption behind a number will either distrust the number or, worse, quietly discount it without saying so.

ADDRESS THE COMPETING-PRIORITIES REALITY
Acknowledge directly, in one section, that this spend is competing against a planned ERP upgrade and a warehouse automation project both up for approval this quarter for the same limited budget — do not write as if this is the only decision on the CFO's desk this quarter. Make the case for why this specific spend clears the bar relative to typical hurdle rates for a purchase like this, not by claiming it's more important than everything else in the abstract, but by being explicit about the payback timeline and the downside of not acting, so the CFO has an actual comparison point rather than a vague appeal to priority.

RISK AND DOWNSIDE SECTION
Include one honest section on what happens if the projected ROI doesn't fully materialize — the realistic downside case, not just the best case. A business case with only an upside scenario reads as sales material to a financial reader trained to look for exactly what's missing; naming the downside case, even briefly, is what signals this was written with their scrutiny in mind rather than around it.

FORMAT
One page, numbers-first, no product screenshots or feature descriptions — a CFO business case is not a product pitch, and any section that reads like one should be cut. Use a simple cost-versus-benefit structure a finance reader could summarize in one sentence to their own boss.

HONESTY CHECK
If unplanned downtime cost roughly $340,000 last year across two plants, per their own maintenance logs or projected 9-month payback assuming a 30% reduction in unplanned downtime, based on comparable deployments is genuinely soft — an estimate with no real supporting data behind it — say so plainly rather than presenting it with false precision; a CFO who catches one unsupported number in a business case will discount every other number in it too, even the solid ones.