Free AI diagnosis: 30 minutes, and you leave with a plan

How-to

How to calculate automation ROI step by step

A six-step method to put numbers on an automation before you build it, with a worked example so you can follow each calculation.

Updated 5 min read

The short answer

To calculate automation ROI, measure what the process costs today, estimate the yearly gain, subtract the one-time and running costs, and divide net gain by total cost. Then check the result against a pessimistic case.

Key points

  • Start from today's hours and cost
  • Count every cost, one-time and running
  • Use one formula for net gain over cost
  • Convert the result into payback in months
  • Test the estimate with lower savings

Step by step

Six steps to measure the return

Follow them in order. Each step feeds the next one.

  1. Measure the baseline

    Record how many hours the process takes each week and who does the work.

  2. Put a cost on that time

    Multiply hours by the loaded hourly cost, then by the weeks in a year.

  3. Estimate the yearly gain

    Count hours saved, errors avoided and any extra revenue you can trace to the process.

  4. Add every cost

    Include build or setup, software fees, maintenance and the time your team spends reviewing.

  5. Apply the formula

    Subtract total cost from gain, divide by total cost and show it as a percentage.

  6. Check payback and risk

    Divide total cost by monthly gain, then rerun the numbers with lower savings.

Why measuring the return matters

Without a number

  • Choosing by gut feeling
  • Surprise at the cost
  • No way to judge success

With a number

  • Ranked by payback
  • Costs known upfront
  • Results checked after launch

Calculating ROI for automation projects keeps the decision about numbers, not enthusiasm. It also tells you which process to automate first, as our automation ROI guide explains.

Returns often take longer than teams expect. Payback takes patience. Deloitte's 2025 survey shows six percent of respondents recovering AI costs within a year, while most reached satisfactory returns in two to four years.

A written estimate lets you compare what you expected with what happened.

Build the baseline first

  • Hours per week

    Time one normal week of the process.

  • People involved

    Count everyone who touches the work.

  • Hourly cost

    Use the loaded cost, benefits included.

  • Error rate

    Note rework and fixes it causes.

Every gain is measured against the baseline, so it must be honest. Time one normal week instead of trusting memory.

Repetitive work is common. About half of workers lose two or more hours a day to manual, repetitive work (Formstack, 2022), which is why baselines surprise people.

Count the gains and the costs

Gains

  • Hours saved
  • Errors avoided
  • Traceable extra revenue

Costs

  • Build and setup
  • Software fees
  • Maintenance and review

Gains are hours saved times hourly cost, plus avoided errors and extra revenue. Only count revenue you can trace to the process.

Costs have two parts. One-time costs cover the build and setup. Running costs cover software fees, maintenance and review time.

Leaving out running costs is the most common way to overstate ROI. Add them before you divide anything.

The formula and a worked example

  1. 01

    Benchmark

    $9.40 average vs $2.78 for top teams, per invoice.

  2. 02

    Yearly gain

    500 invoices a month save $39,720 a year.

  3. 03

    Total cost

    $12,000 build plus $6,000 running.

  4. 04

    ROI

    Net gain of $21,720, about 121 percent.

  5. 05

    Payback

    About five and a half months.

The formula is simple: ROI equals yearly net gain divided by total yearly cost, shown as a percentage. Payback in months equals total cost divided by monthly gain.

Worked example, built on a published benchmark: Ardent Partners' 2025 survey of 212 AP and finance professionals puts the average cost to process an invoice at $9.40, and $2.78 for the top-performing teams.

Take a team that handles 500 invoices a month and closes that gap. It saves $6.62 an invoice: $3,310 a month, or $39,720 a year.

Now assume the build costs $12,000 and running costs add $6,000 a year. Year-one cost is $18,000, net gain is $21,720 and ROI is about 121 percent.

Payback takes about five and a half months. The invoice volume, closing the full gap and both costs are assumptions for this example, not a client result or a quote.

Test the estimate before you trust it

Strong case

  • Pays back with lower savings
  • Costs include running fees
  • Baseline was timed

Weak case

  • Needs perfect results
  • Ignores review time
  • Baseline was a guess

Every input is a guess until the system runs. Cut the savings by a third and raise the costs by a quarter, then see if the project still pays back.

In the invoice example, that leaves $26,480 of gain against $22,500 of cost: ROI falls to about 18 percent and payback stretches to about ten months.

If it only works with perfect results, treat it as risky. If it still pays back, you have a strong case.

After launch, compare real hours with the baseline and update the numbers.

Our data

What AI answers when buyers ask

We asked ChatGPT, Gemini and Perplexity 10 buyer questions about business process automation. They named 123 companies, and 86% appeared in only one of the three.

CriterionChatGPTGeminiPerplexity
Companies named394560
Sites cited mostibm.com and promenteur.com (4 of 10)zapier.com and dailyemerald.com (2 of 10)dailyemerald.com (6 of 10)

Nexum measurement, October 20, 2026, via DataForSEO: 10 buyer questions to each AI, US English, 30 answers in total. 4 companies appeared in all three. Google showed an AI Overview for 8 of the 10 questions.

FAQ

Questions about automation ROI

  • Return on investment compares what an automation earns or saves with what it costs. A positive number means the gains are larger than the total cost over the period you measured.

  • Subtract total cost from total gain, divide the result by total cost, and multiply by 100. For automation, include both one-time and running costs in the total.

  • For every dollar spent, you got that dollar back plus 20 cents. Whether that is good depends on payback time, risk and what else the money could do.

  • Use a range. Calculate a pessimistic, expected and optimistic case, and judge the project by the pessimistic one. Replace the estimates with real data after launch.

  • Time the same process again and compare hours, errors and cost with the baseline. Repeat monthly for the first quarter, since early results often shift.

  • Returns vary widely. Deloitte's 2025 survey found only six percent of respondents saw payback within a year, while most expected satisfactory returns in two to four years.

  • Running costs: software subscriptions, maintenance, monitoring and the time staff spend reviewing outputs. Training time and process changes also belong in the total.

  • Read the automation ROI guide for the wider picture, or browse AI use cases to see measured results.

Related

Keep reading

Final step

Pick a time. Let's talk.

You leave knowing which processes to automate first and what each one costs you today, whether we work together or not.

You can keep paying for manual work, or find out this week exactly what it costs you.

What happens on the call

  1. Before

    You answer 3 quick questions when you book, so we come prepared.

  2. On the call

    We find the manual work that costs you most and put a number on it, live.

  3. Decide

    An honest read on whether we're the right fit. If we're not, you'll hear it on the call.

Once you book, we look at your site and tools before the call, so the 30 minutes go to your numbers, not introductions.

Prefer to write first? Email us directly: contact@nexumautomations.com

30 minutes · Video call · Free