How to calculate workflow automation ROI
Short answer: Workflow automation ROI = (annual value created − annual cost of the automation) ÷ total cost, shown as a percentage. The value is mostly hours recovered (staff time × loaded hourly cost) plus error reduction and faster cycle times. A well-scoped SMB automation that removes 15–30 hours of manual work a week typically pays back its build cost in 3–9 months and returns 200–400% in year one.
Every automation proposal eventually meets the same question: “what do we actually get back?” Here’s how to calculate it honestly, with a worked example you can copy.
The formula
ROI (%) = (Annual value − Annual cost) ÷ Total cost × 100. Three inputs matter: the value the automation creates in a year, what it costs to build, and what it costs to run.
Step 1 — Quantify the value
- Hours recovered. Tasks removed per week × minutes each × your team’s loaded hourly cost (salary + overhead, usually 1.25–1.4× base). This is almost always the biggest line.
- Error and rework reduction. Fewer mistakes = fewer refunds, chargebacks, and cleanup hours.
- Faster cycle time. Quicker responses and fulfilment lift conversion, retention and capacity you’d otherwise hire for.
- Revenue enabled. Leads answered in seconds instead of hours, or reps freed to sell instead of doing admin.
Step 2 — Add up the cost
Build cost (a fixed-scope pilot is typically $5K–$80K depending on complexity) plus annual running cost (model/API usage, hosting, monitoring, maintenance) — usually 25–35% of the build per year.
A worked example
| Input | Value |
|---|---|
| Manual work removed | 20 hrs/week |
| Loaded hourly cost | $45/hr |
| Annual hours value | 20 × 45 × 48 wks = $43,200 |
| Error/rework savings | $8,000 |
| Annual value | $51,200 |
| Build cost (pilot) | $30,000 |
| Annual running cost | $9,000 |
Year-one ROI = ($51,200 − $9,000 − $30,000) ÷ $39,000 × 100 = 31%, with payback around month 9. In year two — build cost already paid — the same automation returns ($51,200 − $9,000) ÷ $9,000 = ~470%. This is why automation compounds: the value repeats every year, the build cost is paid once.
Common mistakes that inflate (or hide) ROI
- Using base salary, not loaded cost. You under-count value by 25–40%.
- Ignoring the running cost. A build-only quote hides a third of the real spend.
- Automating a low-volume task. If it only happens twice a week, even perfect automation returns little. Start with the highest-volume, most repetitive workflow.
- No baseline. If you don’t measure the “before,” you can’t prove the “after.”
How to de-risk the number
Ship a fixed-scope pilot on one workflow, capture a baseline first, and measure hours saved against it. That turns ROI from a spreadsheet guess into a measured result before you scale to the next workflow — which reuses the same infrastructure, so its ROI is even higher.
Related guides
- How much does an AI agent cost in 2026?
- AI agent vs chatbot
- Services: Workflow Automation · AI Agents · CRM Automation
Sources & further reading
Find your fastest-payback workflow
The AI Automation Readiness Checklist is a free 12-point scorecard that tells you which workflow to automate first — and whether it needs an agent, a chatbot, or neither.
Get the checklist → See our AI Agents service →Frequently asked questions
How do you calculate workflow automation ROI?
ROI (%) = (annual value created minus annual cost) divided by total cost, times 100. Value is mostly hours recovered (tasks removed x loaded hourly cost) plus error reduction and faster cycle times.
What is a typical payback period for automation?
A well-scoped SMB automation that removes 15-30 hours of manual work per week typically pays back its build cost in 3-9 months and returns 200-400% in year one, then far more in year two.
Why does year-two ROI jump so much?
The build cost is paid once, but the value repeats every year. After year one you only carry the running cost (about 25-35% of the build), so the return multiplies.
What's the biggest mistake in automation ROI math?
Using base salary instead of loaded cost, ignoring ongoing running costs, or automating a low-volume task. Start with the highest-volume, most repetitive workflow and capture a baseline first.