Skip to content
IvarAutomation
Back to Insights

ROIinvestmentcalculation

The ROI of Automation: How to Calculate It

Automation ROI calculations easily end up too optimistic or too narrow. Here's how to build one that holds up when someone looks closely.

What do we get back?

It's a fair question to ask before automating anything. An automation is an investment, and an investment should be something you can put numbers on.

Automation ROI calculations easily end up in one of two ditches. Either they're too optimistic and count savings that assume everything works from day one. Or they're too narrow and only count the hours freed up. A good calculation supports a decision, and it should hold up once someone starts asking follow-up questions.

What ROI means for an automation

The formula is simple: ROI = (net gain / investment) × 100%.

What makes it harder is that an automation isn't a pure one-off expense. It consists of:

  • a setup cost, meaning what it costs to get the flow running
  • an ongoing operating cost for licences, model calls and hosting
  • an ongoing saving, meaning what you get back every month

Time matters too. An automation that pays for itself in five months is a very different thing from one that takes five years, even if the total happens to come out the same.

Four parts on the value side

The value of an automation can be split into four parts. Not all of them always apply, but it's worth thinking each one through.

1. Time saved

This is the easiest part to calculate. How much time does the work take today? Multiply by working weeks, by an hourly cost and by the share of the work the automation actually removes.

Use the fully loaded hourly cost and not just the salary. It also includes payroll taxes, pension, office space and equipment. Your finance team can usually produce the figure.

The share that disappears is never 100 percent. There are always exceptions, checks and steps that need judgment, so it's better to be cautious here.

2. Fewer errors

A manual mistake costs more than the time it takes to fix. A wrong invoice becomes a credit note and a new invoice, and perhaps a late payment. The consequences show up later and are rarely linked back to the original mistake.

Don't know how often errors happen? Ask the team to note every correction for a month, with the time spent and a short description. That gives you much better input than a guess.

3. Faster flows

When the work moves faster, customers hear back sooner and money comes in sooner. For invoicing, the cash-flow effect can be calculated directly:

Working capital freed ≈ (days paid earlier / 365) × annual invoiced volume

This is capital released once. It doesn't recur every year, so keep it separate from the recurring items in your calculation.

4. Capacity freed up

This part is the hardest to put a number on but often the most interesting. What does the person do with the time they get back? Sell more, or look after more customers?

It's an opportunity and nothing you can count on. Either leave it out of the calculation and mention it separately, or apply a cautious share you can justify.

The cost side

ROI is a fraction, and the denominator needs the same care as the numerator. These items should be included:

  • Setup, with scoping, build, testing and handover. The more systems the flow touches, the more the integration costs.
  • Ongoing operation, with licences, cloud services and model calls. For flows with an AI agent, the cost depends on both which model is used and the volume, so calculate on your actual volume.
  • Your own team's time during rollout. It's often forgotten. Someone on your side needs to describe the work, test and sign off.
  • Maintenance. Systems get replaced and APIs change, and an automation that works today may need adjusting when the accounting system is updated. If an AI agent is involved, tests and evaluation need to be rerun when the model or the flow changes, and monitoring with logs and tracing also costs money. Budget an annual line for it.

An illustrative worked example

The figures below are made up to show how the calculation works. They say nothing about what your business would save.

Suppose a company where two people together spend 12 hours a week on order handling: reading orders, entering them into the ERP and sending confirmations. The fully loaded hourly cost is €50 and the year has 46 working weeks.

Today

  • Time: 12 h × 46 weeks = 552 hours a year, or €27,600
  • Error correction: 4 hours a month = 48 hours a year, or €2,400

After automation

  • 70 percent of handling time disappears: €19,320 a year
  • Correction time is halved: €1,200 a year
  • Full gross saving: €20,520 a year
  • For the first three months we assume half the effect while the flow settles in

Why 70 percent? In our first invoicing project, roughly 70 percent of the manual time went away. That's a single project and a different kind of work from order handling, so the figure could be different here. That's why we test the calculation with a lower figure further down.

Costs (also made up)

  • Setup: €6,000 (one-off)
  • Your team's time during rollout: 20 h × €50 = €1,000 (one-off)
  • Operation: €150 a month = €1,800 a year
  • Maintenance from year 2: €600 a year

Result

  • Year 1: 20,520 × 0.875 − 1,800 − 6,000 − 1,000 = €9,155 net
  • Year 2: 20,520 − 1,800 − 600 = €18,120 net
  • Year-one ROI: 9,155 / 7,000 ≈ 130%
  • Payback: just over six months

If the effect is smaller

If only 40 percent of the time goes away instead of 70, the gross saving drops to €12,240 a year and year one lands at roughly €1,900 net. The case still works, but the margin is much thinner. Always run this test. If the investment only works in the optimistic case, it's better to know that before the decision.

Pitfalls to avoid

  • Freed time isn't the same as money earned. Three hours back a week doesn't automatically mean three more hours of sales.
  • Full effect from day one is rarely realistic. Allow for a transition period, as in the example above.
  • Keep one-off and recurring costs apart. A €6,000 setup is an investment that has to pay for itself, and it becomes misleading if it's spread out as a monthly cost.
  • Less stress and happier customers have real value, but describe them next to the calculation. That makes the number more credible.
  • Calculate over the whole period you expect to use the automation and not just the first year.

When ROI isn't the most important number

Some automations exist mainly to prevent expensive mistakes, such as wrong VAT or personal data sent to the wrong recipient. Then the calculation is about what such an incident would cost and how often it could happen, more than about hours saved.

If the business plans to grow, the question is also whether you can take on more customers without admin growing at the same rate. That capacity can then outweigh this year's ROI.

How to do a first calculation yourself

  1. Pick a workflow the team itself points to as time-consuming.
  2. Measure for two weeks how much time it actually takes.
  3. Work through the four parts on the value side. Be cautious about value and generous about costs.
  4. Get a real figure for setup and running costs.
  5. Check whether the case holds if the effect is only half as large.

Want to put numbers on a specific workflow in your business using your own figures? Get in touch and we'll go through it together and build a case you can make a decision on.

Next step

Does any of this sound familiar?

Tell us how things look for you, and together we'll see what can be automated.

Free of charge · No obligation