[ 01 ] ROI Calculator
Automation ROI calculator: does the workflow pay back?
Model one repetitive workflow, include the cost to build and operate it, then compare annual value, payback, and three-year return across three transparent scenarios.
The short answer
Automation usually has a defensible business case when a stable, high-volume workflow returns enough labor and rework value to repay implementation and operating costs inside the decision-maker's acceptable payback window. This calculator shows that threshold without adding speculative revenue.
What is automation ROI?
Automation ROI is the return an automated workflow produces against what it costs to build and run. Gross value is the labor and rework time the automation gives back, priced at a loaded hourly rate. Total cost is the one-time implementation plus monthly tools, hosting, monitoring, and support. Payback is how long the recovered value takes to repay the build.
- 3-year ROI
(3-year gross value − 3-year total cost) ÷ 3-year total cost × 100- Payback (months)
implementation cost ÷ (monthly gross value − monthly operating cost)- Gross annual value
(manual hours + rework hours) × loaded hourly rate × automation rate
If monthly gross value does not exceed monthly operating cost, there is no payback at any horizon and the calculator says so rather than printing a number. Full methodology and a worked example →
[ 02 ] Calculator
Model one workflow.
Use the numbers your operation can observe. The projection updates as you type.
Start with an example
Illustrative inputs only. Replace every value with observed operating data before making a decision.
[ → ] Projection
Invoice processing business case.
Steady-state annual net value
$12,975
gross workflow value minus twelve months of operating cost
Hours / year
525
Payback
11.1 mo
3-year ROI
95%
Business-case breakdown
- Annual cost of the current workflow $30,625
- Gross annual value returned $18,375
- Annual operating cost $5,400
- First-year net value $975
- Three-year net value $26,925
Scenario comparison
| Scenario | Payback | 3-year ROI | 3-year net |
|---|---|---|---|
| Conservative 40% | 21.0 mo | 30% | $8,550 |
| Expected 60% | 11.1 mo | 95% | $26,925 |
| Aggressive 75% | 8.2 mo | 144% | $40,706 |
[ 03 ] Method
How we count.
Current workflow cost
Monthly volume × minutes per task × loaded hourly cost, plus the labor required to correct errors. No revenue assumptions are added.
Three scenarios
Conservative, expected, and aggressive projections apply 40%, 60%, and 75% automation rates. The selected rate affects both labor and rework value.
Full cost included
Payback and ROI include the one-time implementation cost plus monthly tools, hosting, monitoring, and support across the full projection period.
What remains excluded
Revenue lift, faster response, risk reduction, and capacity value are excluded. Add them only when your business can measure them without guesswork.
Read the complete automation ROI methodology for formulas, a worked example, cost definitions, and interpretation limits.
When automation is the wrong answer
Do not automate a workflow that is still changing weekly, has too little volume to recover its costs, depends on judgment you cannot test, or would amplify a broken process. Standardize the work and measure a reliable baseline first.
Warehouse, RPA, and AI workflows use the same formula.
The label on the technology changes what you type into the inputs, not how the return is calculated. Every case below reduces to recovered hours priced against build and run cost.
Robotic process automation
For an RPA business case, bot licences and orchestrator fees belong in monthly operating cost, and the developer time to build the bot belongs in implementation cost. Attended bots usually justify a lower automation rate than the expected scenario because a person still handles exceptions. Open the RPA ROI calculator →
Warehouse and back-office operations
Warehouse automation ROI splits in two. Equipment carries capital cost this calculator does not model. The paperwork around it — receiving, put-away confirmations, cycle-count entry, carrier documents — is ordinary workflow automation, and that part belongs here. Open the warehouse ROI calculator →
AI agents and workflow automation
Model inference and platform subscriptions are monthly operating cost. Because an AI agent handles variation a rules engine cannot, the honest move is to measure its accuracy on real cases first, then set the automation rate to what you observed rather than what was promised.
Common questions.
How do you calculate automation ROI?
Price the hours the automation gives back, then subtract what it costs to build and run. Three-year ROI is three-year gross value minus three-year total cost, divided by three-year total cost, times one hundred. Gross value is manual hours plus rework hours, multiplied by the loaded hourly rate and by the automation rate you expect to achieve.
What is a good automation ROI?
There is no universal threshold, because the answer depends on the payback window your business accepts. A common bar for back-office workflow automation is payback inside twelve months and positive three-year ROI on conservative assumptions. If a workflow only clears the bar on the aggressive scenario, treat it as unproven rather than approved.
What automation rates do the three scenarios use?
Conservative applies 40 percent, expected applies 60 percent, and aggressive applies 75 percent. The rate is the share of the workflow the automation handles end to end, and it scales both the labor value and the rework value.
Which costs are included, and which are left out?
Included: the one-time implementation cost plus monthly tools, hosting, monitoring, and support across the whole projection period. Excluded: revenue lift, faster response times, risk reduction, and capacity value. Those are real but hard to measure, so adding them tends to manufacture a business case rather than test one.
How do you calculate RPA ROI specifically?
The same way. Put bot licences and orchestrator fees in monthly operating cost and bot development in implementation cost. If the process still needs a person to clear exceptions, lower the automation rate to match what the bot actually completes unattended.
When does the calculator not return a payback period?
When monthly gross value does not exceed monthly operating cost. The automation never repays its build cost at any horizon, so the calculator reports no payback instead of printing a misleading number.
[ 04 ] Next step
Take your number into a scoping call.
Request an assessment and bring your projection. We map the workflow behind it, then tell you plainly whether the math holds — and walk away if it doesn't.