Four figures without which there is nothing to calculate
- Volume: how many operations pass through the process each month. Requests, documents, enquiries, checks.
- Cost per operation today: employee time multiplied by the cost of their hour, plus the cost of errors and rework.
- The share you can really hand over to the system. It will not be one hundred per cent: the complex cases will stay with people.
- Running cost: model calls or infrastructure, plus maintenance and quality control.
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
- 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.
- Lower losses: fewer errors, fines, missed deadlines and rework. Calculated from historical incident statistics, so those statistics have to be kept.
- 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:
- Measure by hand: take 20–30 real operations and time each one. This is inexpensive and gives the calculation its base.
- Take a conservative share to hand over and calculate with it. Keep the optimistic scenario separate, for comparison.
- Budget the running cost with a margin: at the start it is the least known figure.
- 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
- the success metric, fixed before the start;
- its value today, or there is nothing to compare against;
- when the effect is expected, and by what sign it will be clear that the hypothesis has not held;
- the cost of stopping: what is lost if the project is wound down after the pilot;
- who in the company is responsible for data and access. Projects stall here more often than in development.
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.