AI and businessAI economics · ROI · Decision-making

How to calculate the ROI of AI implementation so that the numbers survive scrutiny

Most calculations of the ROI of AI implementation fail one question from the finance director: what exactly will change in our costs. Below is a method that survives that question, and the mistakes that inflate the result several times over.

Four figures without which there is nothing to calculate

Monthly savings equal the volume multiplied by the cost per operation and by the share handed over, minus the running cost. The payback period is the project budget divided by those savings. Everything else in the calculation refines these four numbers.

Common mistakes in the calculation

Time saved is treated as money saved

Half an hour freed up for each of ten employees does not turn into money by itself. That time has to be filled with other useful work, or the next hire has to be skipped when volume grows. If neither happens, the savings exist only in the presentation.

One hundred per cent automation is assumed

The pilot establishes the realistic share you can hand over, and it is almost never complete. Calculate on a conservative estimate. Budget separately for the share of cases where a person checks the system’s work.

The cost of review is forgotten

While autonomy is partial, someone looks at the results. That work costs money and has to be in the calculation. Otherwise the project pays off on paper, while the workload simply moves from the person doing the work to the person checking it.

Tokens are counted instead of processes

The price of a thousand tokens says nothing about the cost of a solved task. One task can take dozens of calls, retries after errors and requests to external systems. The economics are measured by a completed business process, not by a request to the model.

The cost of data is ignored

If the task needs documents put in order or history collected, that is part of the project budget. This budget line is often larger than the development itself, and it is the one people forget most.

Three sources of effect, each calculated differently

  1. Lower costs: less manual work at the same volume. Calculated directly and easy to check. For a first project this is the most reliable type of effect.
  2. Lower losses: fewer errors, fines, missed deadlines and rework. Calculated from historical incident statistics, so those statistics have to be kept.
  3. Revenue growth: faster replies to customers, more requests processed, higher conversion. The most attractive source and the most disputable: too many factors affect it, so it is better left out of the case for a first project.

How to calculate before the project if there is no data

You can calculate without exact figures too, as long as you do not invent them. The order is this:

  1. Measure by hand: take 20–30 real operations and time each one. This is inexpensive and gives the calculation its base.
  2. Take a conservative share to hand over and calculate with it. Keep the optimistic scenario separate, for comparison.
  3. Budget the running cost with a margin: at the start it is the least known figure.
  4. Work out the volume at which the project stops paying off. That threshold is more useful than the ROI figure itself.

What a decision on the project should contain

When not to start the project

If payback comes out at more than a year, the reason is usually a scenario that is too broad, not the technology. Narrow the task to the part with the highest volume and calculate again. If it still does not add up, the process is either too rare or has to be redesigned first. Automating a bad process makes it fast and still bad.

More on this

Frequently asked questions

What payback period is normal for an AI project?

For a first project it is reasonable to aim for months, not years. A long horizon means the scenario is too broad or the effect is only loosely tied to money. Projects that pay back over more than a year are almost always worth breaking into narrower ones.

Can ROI be calculated before the pilot?

It can and it should, but as a range with explicit assumptions and not as an exact number. A calculation before the pilot answers two questions: whether the pilot is worth running, and below what volume the project loses its point.

How do you account for the effect of fewer errors?

From historical statistics: how many incidents there were over a period and what each one cost (direct losses, compensation, time spent investigating). If there are no such statistics, it is better to mark the effect separately as uncounted and not to invent a coefficient.

What if there are savings but the budget does not shrink?

Then the effect showed up as higher throughput. That is a legitimate result; it is just calculated differently: through the volume of work done without growing headcount, and through hiring avoided as the business grows.

How we help with this

Read next

Tell us about your problem

If you’re dealing with something similar, describe it in your own words in the form on the homepage. If it has a simpler solution than it seems, we’ll say so.

AVA calculator: your figures, no form, no price from us.

New write-ups on TelegramEmail hello@xteam.pro