How to Calculate Automation ROI: One Formula, One Worked Example, No Hype

The short answer

Automation ROI is the value you get back in a year, minus everything it costs you in that year, divided by that cost. Value is mostly hours saved multiplied by what those hours cost you, plus any revenue the automation recovers; cost is the build or setup, the monthly tools, and the time someone spends keeping it running. If the result is above 100% with honest numbers, the project pays back in under a year. The hard part is not the arithmetic, it is resisting the urge to count hours nobody will actually reclaim.

The automation ROI formula

Use a 12-month window; longer horizons flatter every project.

Annual value = (hours saved per month × loaded hourly cost × 12) + (errors avoided × cost per error × 12) + revenue recovered per year

Annual cost = one-time build or setup + (monthly tool fees × 12) + (monthly maintenance hours × loaded hourly cost × 12)

ROI = (annual value − annual cost) ÷ annual cost

Payback period (months) = one-time cost ÷ (monthly value − monthly running cost)

Three definitions matter. "Loaded hourly cost" is wages plus payroll costs and benefits, not the bare hourly rate. "Hours saved" means hours that will be spent on something else that earns money or avoids a hire, not hours that evaporate into a slightly quieter afternoon. "Revenue recovered" is only the revenue you can tie to the automation with a straight face, such as leads that used to go unanswered after hours. If you cannot name the mechanism, leave it at zero.

You can run these numbers in our free automation ROI calculator, which uses the same formula.

Where the numbers come from

For hourly cost, start from what you actually pay. Two public reference points for Canada as of October 2026: Statistics Canada's Labour Force Survey puts average hourly wages among employees at $37.64 in September 2026, and Ontario's general minimum wage rose to $17.95 an hour on 1 October 2026. Add roughly 15% to 25% for employer payroll costs and benefits to get a loaded figure, or use your bookkeeper's number.

For hours saved, time the task. Do it for one week with a stopwatch, or count the completed items and multiply by a measured average. Do not ask people to estimate; estimates of tedious work run high.

For tool costs, use list prices. As a reference, Zapier lists a free plan with 100 tasks a month limited to two-step automations, and its Professional plan at US$19.99 a month on annual billing for 750 tasks, rising to US$49 for 2,000 tasks, as of October 2026. A "task" is one action, so a five-step automation that runs 200 times uses 1,000 tasks. Our comparison of Zapier, Make, n8n and custom code explains when a build beats a subscription.

A worked example (hypothetical)

Everything below is invented to show the method. It is not a client, a case study or a Flowmatix price.

Imagine a 12-person HVAC company. Two office staff spend time every day re-typing completed job sheets from the field app into the accounting system to create invoices, then chasing payment by phone. The owner wants to automate the quote-to-invoice step and the reminder sequence; the process is laid out in our guide to automating invoicing and payments.

Input	Measured or assumed value	Note
Invoices per month	180	From last year's books
Minutes per invoice (create, send, chase, reconcile)	11	Timed for one week
Hours saved per month	33	180 × 11 ÷ 60
Loaded hourly cost	$34	Office wage of $28 plus 21% payroll costs and benefits
Billing errors avoided per month	2	Wrong tax code or missed line, each costing about 45 minutes to fix
Revenue recovered	$0	No mechanism identified, so excluded
One-time integration build	$6,500	Assumed fixed-price quote
Monthly tool fees	$60	Connector plan plus payment-link fees above the current plan
Maintenance	1 hour a month	Checking failed runs, updating templates

Annual value: 33 hours × $34 × 12 = $13,464, plus errors: 2 × 0.75 hours × $34 × 12 = $612. Total $14,076.

Annual cost: $6,500 + ($60 × 12 = $720) + (1 × $34 × 12 = $408). Total $7,628.

ROI: ($14,076 − $7,628) ÷ $7,628 = 0.85, or 85% in year one. In year two, with no build cost, the same value against $1,128 of running cost is roughly 1,150%.

Payback: $6,500 ÷ ($1,173 monthly value − $94 monthly running cost) = about 6 months.

Notice what was not counted: faster payment. The automation sends invoices the day the job closes and reminds on schedule, which almost certainly brings cash in sooner. That is real, but it is a cash-flow benefit, not revenue, and it is hard to attribute cleanly, so it stays out of the ROI and goes in the narrative instead.

Costs people forget

• Your own time. Specifying the process, testing it, and answering the builder's questions. Count it at your loaded rate.
• The cleanup. Automations expose messy data: duplicate customers, inconsistent product names, missing tax codes. Budget hours to fix them before launch.
• Failure handling. Someone must see when a run fails and fix it. One hour a month is a fair minimum; zero is a fantasy.
• Change. When a connected tool updates its interface or pricing, the automation may need attention. Custom code is more stable here than browser-based bots; connectors sit in between.
• Usage fees that scale. Per-task, per-token and per-call pricing grows with success. Our explainer on AI token pricing shows how to estimate it before you commit.

Value people overstate

• Hours that do not convert. Saving 20 minutes a day across six people is 10 hours a week on paper, but unless those minutes become billable work, extra sales calls or an avoided hire, the saving is comfort, not cash. Count it at a discount, or count only the hours that change a decision.
• Vendor averages. "Businesses like yours save 30%" is marketing. Measure your own process.
• Revenue without a mechanism. If you cannot say which leads, which orders or which renewals the automation touched, do not put a number on it.

The research backs the caution. The MIT NANDA report covered by Fortune in August 2025 found that about 95% of corporate generative-AI pilots produced no measurable profit-and-loss impact, with the authors blaming integration and a learning gap rather than the technology. Plain business process automation has a far better record precisely because its value is countable: an invoice either got created or it did not. For a wider view of what the evidence says, see AI agent ROI in 2026.

A decision rule

Run the formula with conservative inputs: measured hours, a 25% haircut on hours saved, zero unattributed revenue, and a maintenance hour a month. Then:

• Payback under 6 months: do it now, probably with a connector or a small build.
• Payback 6 to 12 months: do it if the process is stable and will exist in two years.
• Payback over 12 months: fix the process first, or wait for volume. Automating a bad process just makes it fail faster.

Our breakdown of what AI automation really costs a small business covers the cost side in more depth, and business process automation describes how we scope a fixed-price build so the one-time cost in your formula is a number, not a guess.

Key takeaways

• ROI = (annual value − annual cost) ÷ annual cost, on a 12-month window with loaded labour rates.
• Measure hours with a stopwatch, haircut them, and count only revenue you can trace.
• Include your own time, data cleanup, failure handling and usage fees in cost.
• Payback under six months is a clear yes; over twelve means fix the process first.

Frequently asked questions

What is a good ROI for business automation?

With honest inputs, a first-year ROI above 50% to 100% (payback inside 8 to 12 months) is a sound project, and routine automations such as invoicing or lead intake often do better because their value is easy to count. Year-two ROI is usually several times higher because the build cost is gone and only running costs remain.

How do I estimate hours saved before I automate?

Time the task for one week, or count completed items and multiply by a measured average per item. Then apply a 25% haircut, because some of the saved minutes will not convert into other productive work. Avoid staff estimates; people overestimate time spent on tedious tasks.

Should I include faster payments or happier staff in automation ROI?

Not in the formula. Faster cash is a real cash-flow benefit and lower frustration is a real retention benefit, but neither is revenue you can attribute cleanly. Describe them alongside the number so the decision-maker sees them, and keep the ROI figure conservative so it survives scrutiny.

Sources

1. Labour Force Survey, September 2026 — Statistics Canada, The Daily, 9 October 2026
2. Minimum wage, Your guide to the Employment Standards Act — Government of Ontario, rate effective 1 October 2026
3. Plans & Pricing — Zapier, accessed October 2026
4. MIT report: 95% of generative AI pilots at companies are failing — Fortune, 18 August 2025

How Flowmatix can help

We put this into practice for businesses in Toronto and around the world through our Business Process Automation services. Want to know what it would take for your business? Get a personalised quote in about 3 minutes.