Work out the return before you commit. Get that right and every spend decision becomes straightforward. Most business owners either skip the maths entirely and buy on hype, or they avoid automation altogether because the numbers feel too fuzzy to trust. Neither approach works.
Here is a straightforward way to run the calculation yourself, before you talk to anyone, before you sign anything.
Where Should an ROI Calculation Actually Start?
The sales pitch always starts with the tool. “This AI does X, Y, and Z.” That is the wrong starting point.
The right starting point is your time and your money. Specifically: which process in your business costs the most, and how much does it actually cost you right now?
That is the question the ROI calculation answers. The automation is just the proposed fix.
If you have not yet mapped where your biggest time drains live, What to automate first in your business is worth reading before you do the maths. The biggest return usually hides in the most boring, repetitive tasks, the ones nobody has questioned in years.
The Basic ROI Formula (and Why It Is Enough to Start)
ROI = (Value recovered minus cost of automation) divided by cost of automation, expressed as a percentage.
Say you spend 15 hours a week on a task. Your time, or your team’s time, is worth £40 an hour. That is £600 a week, £31,200 a year, sitting in one process.
That is a hypothetical example, not a guarantee. But it shows you the shape of the maths. The numbers in your business will be different. The method is the same.
The Four Inputs You Need
You need four things to run this properly.
1. Time spent on the task, per week
Be honest. Include every person who touches the process, not just the one who “owns” it. Approvals, data entry, chasing, reformatting, manually sending, filing. All of it.
2. Hourly cost of the people doing it
Use loaded cost if you can: salary plus employer NI plus any overhead allocation. If you are the one doing it, use your target hourly rate, what you want to be earning per hour. If that number makes you uncomfortable, that discomfort is the point.
3. Cost of the automation
This has two parts: build cost (one-off or spread over a few months) and running cost (subscriptions, maintenance, any tool fees). See AI Automation Cost for Small Businesses UK 2026.
4. Realistic recovery rate
Few automations handle 100% of a task. Most automations handle a portion of volume, the clean, predictable cases, not every case. Apply that percentage to your time figure, not the full 100%. Build the conservative case.
Show Me the Numbers: A Worked Example
A small trades business takes new job enquiries by phone, email, and web form. Someone manually logs each one into a spreadsheet, checks for duplicates, sends a holding reply, and flags it for the owner to review. Total time across two people: roughly 8 hours a week.
Say the blended rate is £35 an hour, that would be £280 a week, roughly £14,560 a year.
Say the automation handles most of the web form and email enquiries. For this example, say that is around 75% of volume: logging automatically, deduplicating, and sending a holding reply without anyone touching it. In this example that would recover around 6 hours a week, worth roughly £10,920 a year.
For a build like this, plug in your own quote for the build cost and your actual monthly running costs for tooling, then adjust to match any real figures you receive. The payback period will shift accordingly.
Even on conservative numbers, the payback period on a straightforward build like this is typically measured in months.
The Costs People Forget to Include
The tool subscription is the easy one. These are the ones that get missed.
Setup and configuration time. If you or your team build it, that is hours with a value. If you pay someone to build it, that is a direct cost. Either way, it belongs in the calculation.
Maintenance. Automations break when something upstream changes, a form field is renamed, a software update shifts an API. Budget a small amount of time each month for this, or factor in the cost of someone to handle it. See also Why Do Business Automations Fail?
Training time. If your team needs to change how they work to accommodate the automation, that changeover has a cost.
Error cost. What happens when the automation misfires? How often? What does it cost to fix each instance? Low-volume, low-stakes errors are usually fine. An automation running payroll with a 1% error rate is not.
When the ROI Maths Tells You to Walk Away
The calculation works in both directions. If the numbers do not stack up, that is the answer.
Common scenarios where automation is hard to justify:
- The task takes less than one or two hours a week total and is already straightforward. The build cost will not recover in any sensible timeframe.
- The process changes so frequently that the automation would need constant rebuilding. Maintenance cost eats the return.
- The task requires genuine judgement on almost every case. Automation handles the predictable. If every case is an exception, there is nothing for it to handle.
- You do not yet have a consistent process. Automating chaos produces faster chaos.
The question to ask is always: what is the payback period? A short payback period is generally worth doing; a longer one depends on strategic value; beyond that, simplify the process first.
What to Do With the Numbers Once You Have Them
Run the calculation for your top three or four candidates, the processes you suspect are costing the most time or money. Rank them by annual value recovered against build cost.
The one at the top is where you start. Not the most interesting one. Not the one someone told you would be easy. The one with the best return.
If you want a second pair of eyes on the numbers, or you want to see what a build actually looks like before you commit, that is exactly what a discovery call is for. You can also see what we build before you book.
FAQ
How do I put a value on my own time if I’m the business owner?
Use the rate you want to reach, not your current effective rate. If, say, you are doing low-value admin when you should be doing higher-value work, cost the admin at your target rate. That is the real opportunity cost. It also makes the case for automation far more clearly.
Does AI automation always have a clear ROI?
No. Some automations are primarily a quality or consistency improvement, fewer errors, faster response times, rather than a direct time saving. Those still have value, but it is harder to quantify. The strongest builds do both: they save time and improve consistency at the same time.
How long does it typically take to see a return?
It depends on the build cost and the volume of the process. A simple automation on a high-volume task can pay back in a matter of weeks. A more complex build on a lower-volume process might take six to twelve months. Run the payback period calculation before you start, not after.
What if I don’t know exactly how long a task takes?
Time it for one week. Ask whoever does it to log the minutes. It does not need to be perfect. A rough number beats a guess, and a week of data is usually enough to make the decision with confidence.
Should I automate everything with a positive ROI?
Start with the highest return, not the longest list. Attempting too many automations at once is one of the most common ways they fail. Build one, run it, verify the return, then move to the next.
