Building a value case for a CFO

What the CFO is actually measured on

Before you write a word, be clear on what sits on their scorecard: margin and cost base, cash conversion and working capital, capital efficiency and return on invested capital, forecast accuracy, and the risk register. Everything you present competes for the same finite capital as every other proposal in the business.

That competition is the thing most sellers miss. Your case is not being judged against doing nothing. It is being judged against the next best use of the same money.

Lead with payback, not features

A CFO reads a business case in a predictable order: what does it cost, what comes back, when, and how confident are we. Structure the case in that order and you are already speaking their language.

• Total investment, including implementation, internal effort and ongoing run cost — not just licence.
• Annual value, broken into named drivers.
• Payback period, in months.
• Return over three years, with the assumptions that produce it.

If a number cannot be traced to a driver, take it out. One unexplained figure undermines the rest of the document.

Make every driver defensible

"£2.1m of annual value" is a claim. "Churn reduction of two points on a £40m renewable base" is an argument. The second survives scrutiny because the CFO can test it: is our churn really that high, is the base really that size, is two points realistic.

Give every driver a basis, a source for the baseline and a stated assumption. Then say plainly that the figures are directional estimates. Sellers fear this weakens the case. It does the opposite — a CFO trusts a range with visible assumptions far more than a confident single number.

Cost avoidance is not cash

Be careful how you classify value. A CFO will separate hard savings that reduce the cost base, cost avoidance that prevents future spend, and productivity gains that free up time without removing cost. Time saved is only value if the business does something with the capacity, and a CFO will ask what.

Claiming soft benefits as hard savings is the fastest way to lose a finance review. Label them honestly and you keep credibility for the drivers that are real.

Risk is part of the return

CFOs are as motivated by downside protection as upside. Regulatory exposure, audit findings, key-person dependency, single points of failure in critical processes, forecast volatility — quantify what the current state risks and what the proposed state reduces. For regulated industries this is often the stronger half of the argument.

What to have ready before the meeting

• The sensitivity: what happens to payback if the benefit is half what you projected.
• The phasing: when the cost lands versus when the value arrives, quarter by quarter.
• The comparable: an organisation of similar size and profile that achieved a similar outcome.
• The do-nothing case: the cost of the status quo over the same period.
• Who owns the benefit internally once you have gone.

Common mistakes with CFOs

• Presenting a headline ROI with no visible arithmetic.
• Ignoring implementation cost and internal effort in the investment figure.
• Overstating soft productivity gains as cash savings.
• Using vendor benchmarks instead of the customer's own numbers.
• Bringing the business case to the end of the deal rather than building it during discovery.

How Verity helps

Select the CFO persona and Verity frames the whole dossier through that lens: priorities and challenges in financial terms, an ROI model where annual value equals the sum of its drivers and payback follows arithmetically, each driver carrying its assumption, and the sources kept so you can show where a baseline came from. You still bring the customer's real numbers — but you do not start from a blank page.