How to Build an AI Business Case That Survives a CFO

Most AI business cases fail the CFO review because they were not built for CFO review. They were built to get approval, not to survive scrutiny. The difference is significant.

An AI business case built to win approval is optimistic about benefits, quiet about costs, vague about measurement, and silent about who owns the accountability for whether the projected return materializes. A CFO who has seen several of these documents develops a pattern-matching instinct for their weaknesses. The approval rate for optimistically structured AI business cases has been declining since 2024 as CFOs have grown more experienced with the gap between projections and actual outcomes.

An AI business case built to survive scrutiny makes the opposite choices: specific about benefits with mechanism specification, honest about the full cost stack, explicit about measurement methodology, and named for accountability. This document is harder to build. It is also far more likely to win approval, sustain budget protection through the measurement period, and produce the organizational credibility that makes subsequent AI investments easier to approve.

What CFOs Are Actually Skeptical About

CFO skepticism about AI business cases is not generic. It clusters around specific failure modes that have appeared repeatedly in the documents they have reviewed.

Unvalidated productivity claims. Claims that AI will improve productivity by a large percentage, without specifying the task, the skill level of the worker, the redeployment mechanism for saved time, or the source of the estimate, do not survive scrutiny. The Noy and Zhang (Science, 2023) finding of 37% task completion acceleration is the most commonly cited productivity anchor in enterprise AI business cases. CFOs have seen it cited dozens of times, often without the context that makes it meaningful: the specific task studied, the finding that benefits accrued most to lower-skilled workers, and the fact that faster task completion only produces economic value if the saved time is demonstrably redeployed.

Missing baseline. If the business case does not specify what the current state is before AI deployment, there is no way to measure the delta the business case claims to produce. CFOs who ask "what is the current cost of this process?" and receive an estimate rather than a documented measurement recognize the problem immediately.

Opaque attribution. If the business case does not explain how AI's specific contribution will be isolated from other concurrent changes, the value claim is not attributable and therefore not auditable. Concurrent process redesigns, personnel changes, and market shifts can all affect the same metrics the AI deployment is supposed to move.

Incomplete cost accounting. Business cases that list API costs and seat licenses as the total cost of AI miss the engineering, compliance, rework, and change management costs that are typically larger. CFOs who have been through this once know to ask what the engineering cost estimate is. If the answer is "the engineering team's time is included in their headcount," that is a cost that exists but is not being counted.

No accountability structure. A business case that specifies a projected return but does not name who is responsible for measuring actual return against projection will not produce measurement. The measurement will be deferred, assigned to no one, and eventually abandoned when the team moves to the next priority.

The Structure of a Defensible Business Case

How to Handle the Productivity Claim

The Noy and Zhang finding is frequently misapplied in AI business cases. The research is legitimate and worth citing. The translation requires care.

The 37% task completion acceleration finding was observed in a controlled experiment on specific writing tasks. The benefit was largest for workers who were lower-skilled at the task without AI assistance. The implication is not that AI will accelerate all knowledge work by 37%. It is that AI can significantly accelerate specific tasks, particularly for workers where the current task performance reflects skill constraints rather than effort constraints.

Applying this finding to a specific business case requires: identifying the specific task, estimating the skill distribution of workers performing it, and specifying how the time savings will be captured as productive output rather than simply reducing visible effort without changing output. A business case that cites Noy and Zhang and then applies a 30% productivity improvement across all knowledge work is not a valid translation of the research. A business case that cites the study, identifies the specific task type, argues that it matches the studied conditions, and specifies the redeployment mechanism for saved time is a credible application.

The research supports the claim that AI accelerates specific tasks for specific workers under specific conditions. It does not support applying a blanket productivity multiplier to an organization's entire knowledge workforce.

Conservative vs. Aggressive Assumptions

The temptation in building an AI business case is to use the most favorable assumptions. The expected productivity gain is at the high end of the range. The cost estimates are at the low end. The volume estimate for the use case is at the high end. Each individual assumption may be defensible. The combination produces a business case that requires all favorable outcomes to materialize simultaneously, which is a condition that rarely holds.

CFOs who have reviewed many business cases recognize the structure of aggressive assumptions. They typically apply a mental discount factor to the projected value. The business case that projects $10 million in savings using aggressive assumptions may receive approval for a program that the CFO mentally values at $4 million. The business case that projects $5 million using conservative, well-documented assumptions is more likely to receive genuine confidence in the projection and more likely to produce a favorable outcome when actual results are reported.

McKinsey's State of AI in 2024 noted that organizations with formal AI measurement processes reported stronger outcomes than those without. The discipline of conservative assumption-setting is part of the same culture as formal measurement: both reflect an organizational commitment to knowing what AI actually produces rather than what it is hoped to produce.

The Accountability Structure

The single most common failure in enterprise AI business cases is not in the financial modeling. It is in the accountability structure, or rather its absence. A business case that projects return without assigning accountability for measuring actual return creates a prediction that cannot be verified. The measurement never happens because it was never anyone's job.

The accountability structure for an AI business case has three components. First, an owner: a named individual whose performance is connected to the measurement outcome. Second, a cadence: quarterly reporting is appropriate for most enterprise AI use cases, with an annual summary against the full projection period. Third, a consequence: what happens if the measurement shows the value hypothesis is not materializing? The business case should specify the decision process: iterate on the deployment, redefine the use case, or reallocate the budget.

Organizations that build this accountability structure find that it produces three benefits beyond simple financial accountability. It creates genuine feedback loops that improve AI deployments over time. It builds organizational credibility for AI investments by demonstrating that the program is managed with financial discipline. And it generates the institutional knowledge about what works and what does not that makes future use case selection more accurate.

What Happens When the Business Case Is Not Defensible

When an AI business case fails CFO review, the consequences extend beyond the immediate budget decision. A rejected business case signals that the AI program is not being managed with financial discipline, which creates skepticism about the next case. A pattern of rejected business cases creates the conditions for broader program cancellation or budget reallocation that can undo multiple years of capability building.

The alternative is not to avoid scrutiny by being vague. It is to build the case to withstand scrutiny before it arrives. Organizations that invest in building the baseline, value hypothesis, full cost accounting, and accountability structure before presenting a business case face a harder internal process before submission but a much smoother review. The work is the same whether it is done before or after the CFO review. The sequencing determines whether the program gets funded.

The EU AI Act (Regulation 2024/1689) adds a new dimension to the business case for high-risk AI deployments. Compliance costs under the Act, including conformity assessment, technical documentation, and ongoing monitoring requirements, must be included in the full cost stack. Equally, the penalties for non-compliance (up to 7% of global annual revenue for prohibited practices, up to 3% for high-risk system violations) represent a risk cost that responsible business cases should address. Organizations that include EU AI Act compliance costs and risk mitigation value in their business cases produce more complete and more credible financial analyses.

Stanford HAI's AI Index Report 2024 documented the acceleration of AI investment and the widening gap between deployment scale and outcome measurement across industries. The implication for business case builders is that CFO scrutiny has increased since the initial AI deployment wave: the contrast between high adoption rates and limited demonstrated return has made boards more demanding of evidence. Business cases that were adequate for approval in 2023 may no longer meet the standard in 2026. Building to the current standard of evidence is the appropriate response.

The seven-element framework described in this post is demanding. It requires more upfront work than most AI business cases currently include. That upfront investment is precisely what makes the difference between a document that wins approval and one that sustains it. A business case that produces genuine accountability for outcomes, specifies how returns will be measured, and uses conservative assumptions is a document that can be revisited at six months, twelve months, and eighteen months without creating an uncomfortable conversation about why projections were not met. The work done to build it rigorously is the work that protects the program through the measurement period. Cutting corners at the business case stage does not save time. It shifts the cost to the credibility of the program when actual results arrive.

The NIST AI Risk Management Framework 1.0 (2023) provides a governance structure that, when applied to AI program accountability, reinforces the business case disciplines described here. Organizations that use the NIST AI RMF as their governance foundation and integrate the business case accountability requirements described in this post into that framework create a single, coherent accountability structure for both responsible AI deployment and financial return demonstration. The integration reduces duplication and ensures that the measurement cadence required for ROI accountability is aligned with the ongoing evaluation cadence required for responsible AI governance.