How to Calculate the ROI of AI Automation
To estimate automation ROI, multiply how often a task happens by how long it takes, convert to hours per month, multiply by the share you can realistically automate and by the loaded hourly cost, then subtract monthly running costs. Payback period is the one-off build cost divided by that net monthly saving. Use cautious assumptions, include maintenance, and measure the real baseline before you build.
Most automation pitches promise to “save hours every week”. Before you spend anything, you should be able to put a number on that, using your own data rather than an industry average.
The formula
Hours saved per month = times per week × minutes each ÷ 60 × 4.33 × share automated
Value per month = hours saved × loaded hourly cost
Net value per month = value per month − monthly running costs
Payback (months) = one-off build cost ÷ net value per month
That’s it. The skill is in choosing honest inputs.
Choosing honest inputs
Times per week and minutes each
Measure, don’t guess. For one week, tally how often the task happens and time a few examples. People routinely underestimate small, frequent tasks (“it only takes a minute”) and overestimate occasional ones.
Share automated
This is the most important assumption, so be cautious:
- Rule-based, structured tasks (reminders, moving data between apps, status updates) can often be mostly automated.
- Language tasks with clear answers (FAQs, order status, data extraction from standard documents) can be largely automated, with exceptions going to a person.
- Judgement tasks (complaints, negotiations, legal or medical questions) are usually only partly automatable: AI drafts, and a person reviews.
When in doubt, use a lower number. You want the business case to survive contact with reality.
Loaded hourly cost
Use wages plus payroll taxes, benefits and overheads, divided by productive hours. If you, the owner, do the task, use what an hour of your time is worth to the business, which is often more than any wage.
Running costs
Include software subscriptions, AI usage, messaging fees (such as WhatsApp templates or SMS), hosting, and maintenance, whether that’s your own time or a care plan.
A worked example
Hypothetical numbers, for illustration. A small property agency answers listing enquiries by hand:
| Input | Value |
|---|---|
| Enquiries per week | 120 |
| Minutes per enquiry (first reply + basic questions) | 4 |
| Share automated (cautious) | 55% |
| Loaded hourly cost | $28 |
| Monthly running costs (AI, messaging, maintenance) | $150 |
| One-off build cost | $3,000 |
- Hours per month: 120 × 4 ÷ 60 × 4.33 = 34.6 hours
- Hours saved: 34.6 × 0.55 = 19 hours
- Value: 19 × $28 = $533 per month
- Net value: $533 − $150 = $383 per month
- Payback: $3,000 ÷ $383 = about 7.8 months
That’s a reasonable case on time alone. But the bigger benefit here probably isn’t time. It’s that every enquiry now gets an instant reply at 10pm instead of a slow one the next morning. If that converts even one extra client a month, the payback is much faster. Track those benefits separately so you don’t double-count.
Benefits that don’t show up in hours
- Speed: faster replies and quotes win more business.
- Consistency: the same correct answer every time.
- Fewer errors: no retyping mistakes in invoices or orders.
- Capacity: growing without hiring immediately.
- Availability: evenings, weekends and other time zones.
Estimate these where you can (for example extra conversions × average sale value), but keep them separate from time savings in your business case.
Red flags in an automation business case
- Only one optimistic scenario. Always do a cautious one too.
- No running or maintenance costs.
- Savings from a task nobody has measured.
- A payback period longer than the likely life of the process.
Do it in two minutes
Our free ROI calculator applies this exact method across multiple tasks and shows payback instantly. If you’re not sure which tasks to include, the free AI audit suggests them based on how your business works.
Frequently asked questions
What is a good payback period for an automation project?
For small businesses, many focused automation projects aim to pay back within a few months to a year. Shorter is better because business processes and tools change. If payback is longer than 12–18 months, simplify the scope or pick a different task.
Should I count time saved if I'm not reducing staff?
Yes, but be honest about what the time is used for. Time redirected to sales, customer service or growth has real value. If the saved time simply disappears, the benefit is smaller. Some benefits, like faster responses and fewer errors, are worth measuring separately.
What costs do people forget?
Ongoing maintenance and monitoring, AI usage that grows with volume, messaging fees, staff time for reviewing AI output, and the time to update knowledge when prices or policies change.
Put this into practice
Try the ROI calculator. It’s free, and you’ll get results in minutes.
Try the ROI calculator