Why are CFOs rejecting AI proposals in 2026?
CFOs are rejecting AI proposals because most cannot demonstrate a financial return. Forrester's 2026 predictions report that enterprises will defer 25% of planned AI spend to 2027 as financial scrutiny tightens, and fewer than one-third of decision-makers can tie AI value to measurable financial growth.
The pattern is consistent across industries. Forrester also found that only 15% of AI decision-makers reported an EBITDA lift from AI in the past 12 months. The technology often works. The financial story around it usually does not.
This shifts the burden onto the sponsoring executive. In 2026, the department head who wins AI budget is not the one with the most impressive demo. It is the one who presents a business case built the way a CFO evaluates any other capital investment.
What does a CFO actually need to see in an AI business case?
An AI business case is a financial document that maps a specific AI deployment to a measurable P&L outcome: cost reduction, revenue growth, or risk mitigation. It states a baseline, a target, a timeline, and an owner. Anything that cannot be expressed in those terms is a research project, not an investment proposal.
CFOs evaluate four elements. First, the baseline: what does the process cost today, measured before any deployment. Second, the mechanism: exactly how the AI changes that number. Third, the payback window: when cumulative savings exceed cumulative spend. Fourth, the exit criteria: what result, by what date, triggers a stop decision.
Notice what is absent from that list: model benchmarks, vendor rankings, and productivity anecdotes. A CFO does not fund "efficiency" in the abstract. A CFO funds a specific number moving in a specific direction.
How do you set a measurement baseline before deployment?
Set the baseline by measuring the target process for 4 to 8 weeks before any AI touches it. Record volume, unit cost, cycle time, and error rate. Without this pre-deployment snapshot, any later improvement claim is unverifiable, and unverifiable claims are why finance teams discount AI proposals.
Baselines fail when they measure activity instead of cost. "Our team answers 3,000 enquiries a month" is activity. "Each enquiry costs HK$47 in staff time and takes 9 hours to resolve" is a baseline a CFO can audit.
A practical test: hand the baseline to someone in the finance team and ask whether they could recalculate it from your data. If they cannot, the business case will not survive the first review meeting.
Which AI use cases pass CFO review most easily?
Use cases with directly measurable outcomes clear financial review fastest. Forrester's analysis of 2026 spending patterns shows investment holding steady in fraud detection, customer service automation, supply chain optimisation, and targeted software development acceleration, while diffuse "general productivity" initiatives are the ones being postponed.
The common trait is a countable unit. These use cases share three features:
--- A transaction that repeats at volume, such as an enquiry, an invoice, or a shipment
--- A unit cost that finance already tracks in existing systems
--- A before-and-after comparison that needs no new measurement infrastructure
If your first AI proposal is a company-wide assistant with benefits spread across every team, consider re-scoping. A narrow deployment in one process, with one owner and one KPI, builds the credibility that funds the broader roadmap later.
How should you structure the financial model?
Structure the model in three tiers matched to initiative maturity: efficiency gains in the first 6 months, process redesign gains in months 6 to 18, and new capability gains beyond that. Presenting all three as one blended ROI number is the most common modelling mistake, because it forces speculative long-term value to carry near-term costs.
Tier one covers direct substitution: the same work done cheaper or faster. This tier should carry the payback argument on its own. If the proposal only works when tier three materialises, the CFO will see that immediately.
Tier two and three belong in the model as upside scenarios with explicit assumptions, not as committed returns. Labelling them honestly builds more credibility than inflating the base case, and credibility is the real currency of budget negotiations.
State costs with equal honesty. Include integration work, data preparation, staff training time, and ongoing inference or licence fees, not just the vendor contract. Finance teams notice when the cost side looks suspiciously thin.
What are the most common mistakes that get AI proposals rejected?
The most common rejection triggers are: no pre-deployment baseline, benefits expressed as time saved rather than cost removed, a blended ROI that hides weak near-term returns, and no stop-loss criteria. Each one signals to a CFO that the sponsor has not thought like an investor.
"Time saved" deserves special caution. Saving each employee 30 minutes a day only becomes financial value if that time converts to reduced headcount growth, higher billable output, or measurable revenue. State the conversion mechanism explicitly, or the finance team will strike the line item.
The stop-loss point is counterintuitive but powerful. Proposing your own kill criteria, for example "if unit cost has not fallen 15% by month six, we halt and reassess", signals discipline. Executives who define failure conditions in advance are the ones trusted with larger budgets later.
The takeaway: fund the number, not the technology
The AI investment conversation in 2026 is a financial conversation. The leaders winning budget are those who present a baseline the finance team can audit, a mechanism they can interrogate, a payback window they can hold you to, and a stop-loss that protects the downside.
None of this requires deep technical expertise. It requires treating AI the way your organisation treats any other capital allocation decision, with the same rigour and the same honesty about uncertainty.
That is also where the right partner matters. With UD, AI works for you, not the other way around. UD has spent 28 years helping Hong Kong enterprises turn technology decisions into business outcomes, making technology feel human along the way.
Ready to Build a Business Case That Gets Approved?
Before you present to your CFO, know exactly where your organisation stands. UD's AI Ready Check assesses your readiness across process, data, and measurement, and we'll walk you through every step, from baseline design to deployment and performance tracking, backed by 28 years of enterprise experience in Hong Kong.
