He approved the AI project in January. By November, his CFO was asking what it had actually delivered. He did not have a good answer.
Not because the project had failed technically. The model worked. The system was in production. But nobody had defined what success looked like before it started, so nobody could demonstrate it after.
This is one of the most common failure modes in enterprise AI – and one of the most avoidable. According to RAND Corporation’s 2025 analysis, 80% of AI projects fail to deliver their intended business value. Deloitte’s 2025 research found that 42% of companies abandoned at least one AI initiative that year, with an average sunk cost per abandoned project of $7.2 million. And McKinsey’s November 2025 Global AI Survey found that despite 88% of organisations now using AI in at least one function, only 39% see any measurable EBIT impact.
The gap between investment and return is real. But it is largely a measurement problem, not a technology problem.
Why AI ROI Is Hard to Measure After the Fact
Traditional IT ROI is relatively straightforward: you bought a system, it replaced a process, here is the before-and-after cost. AI ROI is harder because the value is often distributed, indirect, or counterfactual – you are measuring what did not happen as much as what did.
A fraud detection model prevents losses. A demand forecasting system reduces inventory waste. A document processing tool frees analyst time for higher-value work. None of these show up cleanly on a P&L unless you built the measurement framework before the project started.
The Three ROI Dimensions That Actually Matter
1. Cost Displacement
The most legible AI ROI: processes the AI performs that previously required human time. To measure it, document the current process in hours per week, multiply by fully loaded labour cost, and compare against the post-AI baseline. The critical discipline is measuring actual time reallocation – not assumed savings. If the AI frees two hours per analyst per day but those hours are absorbed by other low-value tasks, the real ROI is lower than the model predicts.
2. Revenue Enablement
Harder to attribute but often larger in value: revenue that AI makes possible – faster sales cycles, better conversion from AI-assisted qualification, pricing optimisation, reduced churn from early intervention models. Revenue enablement ROI requires a clear attribution model agreed before deployment. Which leads do you credit to the AI? What is the counterfactual conversion rate? These questions are much easier to answer if you designed the measurement before the system went live.
3. Risk Reduction
The most underestimated ROI dimension: costs avoided through better decisions, fewer compliance breaches, earlier detection of operational problems. Risk reduction ROI is measured against a historical baseline – how often did this type of error or event occur before AI, and what did each instance cost? The challenge is that this value is invisible when it works. A compliance system that prevents a breach does not show up as revenue. The discipline is assigning a financial value to the risk category before deployment, not after.
The Measurement Framework to Build Before You Start
Every AI project brief should define, before approval: the primary ROI dimension (cost, revenue, or risk), the baseline metric being improved and how it is currently measured, the target outcome and timeline, the data sources that will be used to track it, and who is accountable for reporting it.
McKinsey’s 2025 research found that organisations which redesign workflows before selecting their AI approach are twice as likely to report meaningful financial returns. The measurement framework is part of that redesign – it forces clarity on what problem you are actually solving before any technology decisions are made.
Where We Come In
At DoSystems, every AI engagement starts with a ROI framework session before scoping begins. Not because we need it for the contract – because clients who cannot answer ‘how will we know this worked?’ in week one almost never can answer it in month twelve. Getting that clarity upfront is what makes the difference between an AI project that gets funded for phase two and one that gets quietly discontinued. DoSystemsInc.com
Frequently Asked Questions
How do you measure ROI on an AI project?
AI ROI is measured across cost displacement (labour and process savings), revenue enablement (new or accelerated revenue), and risk reduction (costs avoided). Each dimension requires a baseline measurement and target outcome defined before the project starts.
Why do most AI projects fail to show ROI?
According to RAND Corporation’s 2025 analysis, 80% of AI projects fail to deliver intended business value. The most common cause is not technical failure but the absence of defined success metrics before deployment – making it impossible to demonstrate value after.
When should you define AI project success metrics?
Before the project is approved, not after it is built. McKinsey’s research shows organisations that redesign workflows and define outcomes before selecting technology are twice as likely to see measurable financial returns.
What is a realistic ROI timeline for an AI project?
Most AI projects require 6–12 months before ROI becomes measurable, because the baseline data, workflow changes, and adoption curve all take time. Projects that define ROI metrics upfront are better positioned to demonstrate value within this window.
#AIStrategy #AIROI #AIImplementation #DoSystems #AIConsulting #BusinessAI #AIProjects
Comments are closed