How to Measure Enterprise AI ROI: A Framework With Real Numbers
"What's the ROI of AI?" is the wrong question. The right question is: which specific cost or revenue line will this system move, by how much, and by when?
After eleven years of building production AI — and being accountable for the numbers afterward — here's the framework I use to measure return, with real figures from real deployments.
The four kinds of AI ROI
Every AI business case I've ever seen reduces to one of four value types:
1. Labor displacement (hours returned)
The system does work people currently do by hand.
Real example: at Fitter Law, document AI cut contract review from 4.2 hours to 3 minutes at a 99.7% compliance rate. The measurable return: roughly $420K per year in labor cost for a mid-sized firm, plus 40% more case capacity from the same team.
How to measure: (hours saved per unit) × (units per year) × (loaded hourly cost). Only count hours that get redeployed to billable or backlogged work.
2. Direct cost reduction (spend eliminated)
The system removes spend that currently leaves the building.
Real example: cloud cost forecasting and automated remediation at CVS eliminated over $10M in annual cloud spend by predicting usage and reclaiming waste — 92% of identified waste removed, rolled out in three weeks.
How to measure: this is the cleanest ROI type — the number shows up on an invoice. Baseline three months of spend before launch, compare after.
3. Revenue acceleration (more wins, faster cycles)
The system increases throughput of a revenue-generating process.
Real example: the LLM proposal engine I built at ATS in 2018 — before ChatGPT existed — cut RFP turnaround from six months to two weeks and enabled 8x more submissions. Outcome: over $1B in contracts won.
How to measure: conversion rate and cycle time, before vs. after, on the same pipeline definition. Resist the urge to claim the whole win; claim the delta.
4. Risk reduction (losses that don't happen)
The system prevents expensive events.
Real example: real-time threat detection at Zorel.ai cut breach response time by 87%, translating to roughly $4.6M in prevented risk exposure across finance and enterprise networks.
How to measure: hardest of the four. Use (incident frequency) × (average incident cost) × (reduction rate), and be conservative — credibility compounds.
The formula, and the trap
The math is simple:
ROI = (annual value delivered − annual total cost) / annual total cost
The trap is in "annual total cost." Include:
- Build cost (or vendor fees)
- Infrastructure and inference costs
- Integration and change-management time
- Ongoing operation — monitoring, retraining, support
That last line is the one every optimistic business case omits, and it's why I insist every engagement defines an operating plan, not just a launch date.
Set the target before the build
The single highest-leverage moment in an AI project is before any code exists: write down the one number the system must move and the level that makes it a success. Every deployment I've listed above had that number agreed in week zero.
This is also the honest filter for whether to do the project at all. If the problem's annual cost can't justify the build, the right answer is "don't build it" — and a good AI partner will tell you that on the first call.
Frequently asked questions
How soon should AI show ROI?
For labor and cost-reduction use cases, within one quarter of launch. Revenue and risk cases need longer measurement windows, but leading indicators (cycle time, detection rate) should move within weeks.
What ROI multiple should we expect?
Anything below 2x annually usually isn't worth the organizational effort. The deployments above ranged from roughly 3x to well past 10x.
How do we avoid vanity metrics?
Insist that the metric exists in a system of record you already trust — an invoice, a CRM, a time-tracking system. If the metric only exists inside the AI tool's own dashboard, be skeptical.
Want help putting a defensible ROI target on an AI initiative? That's literally step one of how I work. Book a free scope call.
Work with me
Putting this into practice?
If you're weighing an AI implementation like this one, a 30-minute working session will save you months of wrong turns.
Book a strategy session