The Business Case That Actually Gets Funded: A CFO's Guide

I've reviewed hundreds of transformation business cases, and most of them fail for the same reason: they're written by technologists for technologists. They describe features, architectures, and capabilities — things that excite engineers but leave finance teams cold. If you want your business case to get funded, you need to speak the language of the people who control the budget.

The Language of Finance

CFOs and boards evaluate investments using a specific vocabulary: IRR (internal rate of return), NPV (net present value), payback period, and risk-adjusted returns. If your business case doesn't include these metrics, it's not speaking their language. It doesn't matter how compelling your technology narrative is — if you can't answer 'what's the IRR?' you're not ready for the boardroom.

Building the Financial Model

Start with the cost of the current state — not the cost of the proposed solution. Quantify the inefficiencies, lost revenue, risk exposure, and opportunity costs of doing nothing. This establishes the baseline that your investment is measured against. Then model the expected improvements: how much efficiency gain, revenue uplift, risk reduction, and opportunity capture does the transformation deliver?

Be conservative. Finance teams are allergic to hockey stick projections. Use Monte Carlo simulation if you can — it shows a range of outcomes with probabilities, which is far more credible than a single-point estimate. Vision™'s ROI calculator produces exactly this kind of probabilistic output.

Addressing Risk

Every business case should include a risk section that's honest about what could go wrong. Paradoxically, acknowledging risks increases credibility. A business case that claims 'no significant risks' tells the CFO that you haven't done your homework. A business case that identifies specific risks and proposes specific mitigations tells the CFO that you're thinking like a business leader, not a technology enthusiast.

The One-Page Summary

Regardless of how detailed your analysis is, you need a one-page executive summary. It should answer four questions: What's the problem? What's the proposed solution? What does it cost? What's the return? If you can't fit those answers on one page, your business case isn't clear enough yet.