AI Field Notes
When does AI time saved become financial ROI?
By Ed Fassio ·
Time saved becomes a realized financial benefit when it produces an attributable, evidenced financial outcome. Financial ROI then compares those benefits with the costs of achieving them. Multiplying hours saved by a salary rate can estimate the value of capacity, but it does not establish that cash was saved or additional income was earned.
Keep forecasts separate from results
A forecast can be useful before results exist. It must identify the proposed conversion of time into value, its assumptions and its uncertainty. Keep that forecast separate from results already demonstrated.
In Bots in the Boardroom, Ed Fassio distinguishes released capacity from what that capacity actually becomes. The conversion might be a cost that falls, a planned hire no longer required, additional output or new revenue. It can also be something people keep, such as time returned or better work.
Follow the capacity into an outcome
Those outcomes require different evidence. Reduced spending needs records showing the reduction. Avoided hiring needs a credible hiring baseline and evidence that the need was removed. Additional revenue needs attribution, with the associated delivery costs considered before treating it as financial return. Faster output without demand or another measurable benefit does not automatically create money.
Count each benefit once, in the period it occurs. Do not count the same hours both as a salary-equivalent saving and as the avoided hire they enabled.
A hypothetical example
Suppose an AI-assisted workflow frees 100 hours a month. At a planning rate of $50 an hour, that is $5,000 of capacity. If payroll and other spending remain unchanged, the team has not demonstrated $5,000 in cash savings.
Now suppose the team uses that capacity to fulfill additional customer demand. After checking attribution, finance confirms $4,000 in incremental contribution for the month, after the additional delivery costs. Assume the complete AI investment cost allocated to that same month is $1,500, including implementation, tools, oversight and training, with no duplicated costs.
Under those deliberately simplified assumptions, net benefit is $2,500 and ROI is approximately 167 percent: $2,500 divided by $1,500. The financial benefit being counted is the $4,000 contribution, not that amount plus the $5,000 capacity estimate. This is an illustration, not a reported result or a return anyone should expect.
Build the measurement before the promise
A defensible engagement needs operational and financial participation:
- Map the actual workflow and establish a baseline.
- Check whether reported time savings survive adoption, review, errors and rework.
- Assign owners to the data and agree what evidence qualifies a benefit as realized.
- Record full costs and review the conversion plan over time.
- Separate cash reductions, cost avoidance and incremental contribution.
- State uncertainty where attribution is weak.
That work needs agreement from the people who run the process and the people who validate the numbers. A calculation cannot substitute for missing evidence.
Keep the human outcomes visible
The Dual Ledger (https://bytebrain.org/agentic-futures/dual-ledger.html) also asks what people received: returned time, paid learning, changes in workload, compensation and opportunity. These outcomes matter even when they do not become cash savings. Measure them directly rather than forcing every improvement into a financial ROI number.
A useful assessment can conclude that a workflow improved service or people’s working lives while its financial return remains unproven. That is a more informative result than calling all saved time money.
Sources and further reading