AI Automation ROI: How to Calculate Payback in 90 Days
Most UK SMEs automating their first workflow want one number above all else: when does this pay back? The formula is not complicated — hours saved multiplied by your fully-loaded hourly cost, set against the one-off build fee and ongoing run costs — and for a typical single workflow the answer sits between 60 and 90 days. This guide walks through the four-step calculation, a worked example, and the five most common mistakes that make payback look longer than it actually is.
The calculation at a glance
| Step | What you are measuring | Typical input |
|---|---|---|
| 1 | Hours saved per week | 5–20 hours |
| 2 | Fully-loaded hourly rate | £25–£60/hour |
| 3 | Build and run cost | £2,000–£5,000 build; £100–£600/month run |
| 4 | Payback period | 6–16 weeks typical |
Step 1 — Baseline the task
Before running any numbers, you need a reliable estimate of how many staff-hours the task currently consumes each week.
Count everyone it touches. A sales-follow-up process might involve one person for 4 hours a week. A monthly reporting pack might pull in a finance manager for 3 hours and two account managers for 1 hour each — 5 hours total. If a task spans teams, add them up.
Use the last 90 days of the task's actual run as your baseline, not a rough mental estimate. Self-reported time is usually low by 20–30%. Cross-check against calendar blocks, email thread lengths, or shared spreadsheet revision histories if you have access.
For recurring processes, annualise by multiplying weekly hours by 46 working weeks — the UK average after statutory holiday and a realistic allowance for sick leave and disruption.
Step 2 — Use the fully-loaded rate, not the salary
This is where most ROI calculations understate the true return. A £35,000/year employee costs a UK employer roughly £44,000–£46,000 once you include employer National Insurance at 13.8%, a 5% pension contribution, and a proportionate share of office overhead. Divide by 46 working weeks and 37.5 hours per week, and the fully-loaded rate comes to approximately £26–£28/hour.
For senior roles or directors who bill client time, the opportunity cost is higher — often £40–£80/hour — because hours saved can be redirected to revenue-generating work. Use the higher figure when you can defend it; it makes the ROI case more robust, not less, by capturing the real commercial value of the freed time.
If multiple roles are involved in the task, weight by the hours each role contributes and calculate a blended rate.
Step 3 — Cost the build and the run
AI automation projects carry two distinct cost layers, and conflating them is the most common reason buyers feel misled later.
Build cost is the one-off fee to design, build, test, and deploy the workflow. For a single well-scoped workflow, expect £2,000–£5,000. A multi-process programme covering four to six workflows typically runs £15,000–£40,000 — cheaper per workflow than buying individually, because discovery and tooling are shared across the set.
Run cost is what the workflow costs each month in production: orchestration platform fees (£20–£500/month depending on execution volume) and AI model API calls (£30–£500/month per workflow at production volume). A typical single workflow at moderate volume runs £100–£400/month all in.
For the ROI calculation, convert the run cost to an annual figure — multiply the monthly cost by 12 — then subtract it from the annual saving before calculating payback. Skipping this step makes payback look unrealistically fast. The full breakdown of what drives each cost is on the Process Automation service page.
Step 4 — Calculate payback and project year-two return
With those inputs, the payback maths works as follows:
- Annual saving = weekly hours saved × fully-loaded hourly rate × 46 weeks
- Annual run cost = monthly run cost × 12
- Net annual benefit = annual saving − annual run cost
- Payback in months = build cost ÷ net monthly benefit
Or put differently: how many months of net monthly benefit does it take to cover the build cost?
Payback example. A workflow saves 10 hours/week at a £28 fully-loaded rate — £12,880/year in time. Run costs are £250/month (£3,000/year). Net annual benefit: £9,880. Monthly benefit: £823. Build cost: £4,000. Payback: approximately 5 months. That is a realistic expectation for a mid-complexity workflow in a UK professional-services firm.
Year-two projection. Once the build cost is recovered, the only ongoing cost is the run cost. Year-two net benefit using the same example: £9,880, against zero additional build investment — a year-two ROI above 300%. The compounding effect across a portfolio of four automated workflows is larger still: freed capacity that rivals a full-time hire, running at a fraction of a salary.
Five mistakes that inflate the payback estimate
1. Using salary instead of fully-loaded cost. A £35,000 salary understates the true employer cost by 25–30%. The correct figure is the total cost of employment including NI, pension, and overhead.
2. Ignoring the run cost. Monthly platform and API fees are real and ongoing. Treating AI automation as a one-off investment produces an overly optimistic payback figure that surprises finance teams later.
3. Measuring a best-case week. Use a 90-day average, not the week when everything went smoothly. Volume varies; the baseline should reflect typical conditions.
4. Counting only direct hours. If a manual process causes downstream delays — a report that takes three days to produce rather than one — the cost is not just the operator's time but the knock-on effect on decisions and client delivery. Include knock-on costs when you can quantify them.
5. Ignoring the error rate. Manual tasks have error rates; fixing errors costs additional time. If the automated workflow reduces the error rate, the time saved on rework belongs in the numerator too. For document-heavy or data-entry tasks, this can add 10–20% to the stated saving.
A worked example — a UK recruitment firm
A 10-person recruitment firm was manually writing candidate summaries for every shortlist: three account managers each spending 90 minutes per shortlist, across 15 shortlists per week. Total weekly time: 67 hours. Fully-loaded rate for account managers: £32/hour. Annual cost of the task: roughly £98,000.
They automated candidate summary generation using an AI workflow fed by their applicant tracking system. Build cost: £4,500. Run cost: £350/month (£4,200/year). The AI draft still required 15 minutes of review per shortlist — reducing, not eliminating, the human time. Net time saved: 52 hours/week.
Annual saving: £76,600. Net annual benefit after run cost: £72,400. Monthly benefit: £6,033. Payback: under 1 month.
Year-two ROI: above 1,600%. That is not an outlier — it is what happens when a high-volume, high-touch process is automated with a clear scope and a solid baseline. Lower-volume workflows will show more modest numbers; the methodology is the same.
Frequently asked questions
How do I calculate AI automation ROI?
Multiply hours saved per week by your fully-loaded hourly rate to get annual savings. Subtract the annual run cost (platform and AI API fees), then divide by the one-off build cost. A workflow saving 10 hours/week at £30/hour with a £4,000 build cost: payback lands inside 10 weeks.
What is a good ROI target for AI automation in the UK?
A well-scoped workflow should return the build cost within 60–120 days for most UK SMEs. Year-one ROI of 150–300% is realistic; year-two climbs higher once the build cost is absorbed. Treat anything below 100% year-one ROI as a signal to narrow scope or pick a higher-value workflow.
How long does AI automation payback typically take?
For a typical single-workflow build costing £2,000–£5,000, payback takes 6–16 weeks depending on hours saved and the fully-loaded cost of the person previously doing the work. Higher-volume use cases pay back faster; lower-volume or lower-value tasks take longer.
What costs should I include in an AI automation ROI calculation?
Include the one-off build fee (£2,000–£5,000 per workflow), ongoing platform costs (£20–£500/month), AI model API calls (£30–£500/month per workflow), and any support retainer. Use the fully-loaded hourly rate — salary plus employer NI, pension, and overhead — when valuing the time saved.
Can small UK businesses achieve meaningful AI automation ROI?
Yes. The payback maths works at smaller scales than most assume: a sole-director firm saving 5 hours a week at a £50 opportunity cost recovers roughly £13,000/year against a £3,000 build. The constraint is usually finding a workflow that is genuinely repetitive and well-defined enough to automate.
Want to see what the ROI looks like for your specific workflow? Book a free 30-minute discovery call — you will leave with a recommended pilot, a payback estimate, and a timeline.