How to measure AI ROI
Most businesses can't say whether AI is paying for itself. Not because the benefit isn't there, but because nobody wrote down what things took before. Once that baseline is gone, all you're left with is impressions — and impressions lose to a spreadsheet at budget time.
Measure tasks, not people
"Are we more productive?" is unanswerable. "How long does it take to produce a monthly client report?" is answerable, and that's the level to work at.
Pick three or four tasks that are:
- Repeated — weekly or more, so you get real data quickly
- Bounded — a clear start and finish you can time
- Owned — someone can tell you honestly how long it takes
- Plausibly AI-assisted — writing, summarising, researching, formatting, categorising
Resist measuring everything. Four tasks measured properly beats twenty measured vaguely.
The calculation
Per task:
(minutes before − minutes after) × times per month × hourly cost ÷ 60
Then, against it:
licences + training hours × hourly cost + setup time
Keep the hourly cost honest — salary plus on-costs, not just the wage. Overstating it inflates the result and the number stops being believable.
An Australian small-business example
A 12-person Adelaide engineering consultancy picks three tasks:
| Task | Before | After | Per month | Saved |
|---|---|---|---|---|
| Site report first draft | 90 min | 35 min | 12 | 11 hrs |
| Tender summary | 120 min | 50 min | 4 | 4.7 hrs |
| Client update emails | 15 min | 6 min | 40 | 6 hrs |
That's about 21.7 hours a month. At $75/hour loaded, roughly $1,630. Against around $400 in licences and an initial 20 hours of training and setup.
The training cost is recovered in the first month, and the ongoing figure is defensible because it's built from timed tasks rather than a feeling. Note what's absent: no claim about "transformation", no company-wide percentage. Three tasks, measured.
What to watch out for
- Measuring your enthusiasts. The person who loves the tool isn't representative. Include someone indifferent to it.
- Ignoring the review step. If a draft takes 35 minutes but needs 15 minutes of checking, the honest figure is 50.
- Counting the same hour twice. Time saved in two places is still one hour.
- Stopping after the pilot. Re-measure at six months. Some gains grow as people improve; some fade as novelty passes.
The part most businesses skip
Decide what the recovered hours are actually for before you start. More client work? Faster turnaround as a selling point? A vacancy you don't need to fill?
Without that decision, twenty hours a month diffuses into slightly longer breaks and slightly less pressure — real for the people involved, invisible on any measure. That's how a project with genuine returns ends up looking like it delivered nothing.
Frequently asked questions
How long before we can measure anything?
What if the time saved just becomes slack?
Should we count quality improvements?
What's a realistic saving?
Do we count the training time as a cost?
Put this to work
Ad On Group runs AI training and enablement for Australian teams through Ad On AI — a three-month, self-paced program that takes non-technical staff from their first prompts to working AI agents.