How to Calculate the ROI of Workflow Automation
A practical framework for measuring the return on investment of your automation projects. Includes our free ROI calculator template.
By Devma Labs · · Updated · 5 min read
Most automation business cases go wrong in one of two ways: they count every minute saved as cash, or they forget that workflows need upkeep. This framework avoids both. It takes about an hour with the people who do the work today, and you can run it in a spreadsheet with the template below or start with our ROI calculator.
Step 1: map the process
Pick one process, not a whole department. Write down:
- What starts it, such as a form submission, a new order or the end of the month.
- Each step a person takes, and which systems they touch.
- Where it goes wrong: typos, missed follow-ups, duplicate records, late reports.
Do this with the people who do the work. They know the exceptions that never made it into the documentation, and those exceptions decide how much of the process can really be automated.
Step 2: measure the baseline
Collect these from a few weeks of normal work, or from system logs:
| Input | Where to get it |
|---|---|
| Volume per month | Your CRM, inbox, help desk or order system |
| Minutes per item | Time a sample of real items, not the best case |
| Error rate | Share of items that need rework, from QA or support tickets |
| Minutes per error | Time to find and fix a typical error |
| Fully loaded hourly cost | Wages plus benefits, taxes and overhead, from finance |
Fully loaded cost matters. Salary divided by working hours understates what an hour of work costs the business.
Step 3: estimate what automation changes
Be specific about which steps the workflow takes over and which still need a person, such as approvals, judgment calls and unusual cases. From that, estimate the share of the work that is automated. A partial share is normal: most processes keep a human step somewhere.
Then work out the monthly value:
- Time value = volume × minutes per item ÷ 60 × share automated × hourly cost
- Error value = errors avoided per month × minutes per error ÷ 60 × hourly cost
- Monthly value = time value + error value
Some benefits are real but hard to price: faster replies to new leads, fewer late invoices, better data for decisions. List them next to the number instead of forcing a dollar value on them, so the core case stays credible.
Step 4: count every cost
| Cost | One-time or monthly |
|---|---|
| Discovery, design and build | One-time |
| Data cleanup and migration | One-time |
| Training and process changes | One-time |
| n8n Cloud plan, or hosting for self-hosted n8n | Monthly |
| AI model usage, if the workflow uses AI | Monthly |
| Paid app or API plan upgrades | Monthly |
| Monitoring, fixes and updates when connected apps change | Monthly |
Upkeep is the line most business cases skip. APIs change, fields get renamed and new edge cases appear. Budget for someone to own each workflow after launch.
Step 5: calculate ROI and payback
- Net monthly benefit = monthly value - monthly costs
- Payback period (months) = one-time costs ÷ net monthly benefit
- First-year ROI = (net monthly benefit × 12 - one-time costs) ÷ (one-time costs + monthly costs × 12)
If the net monthly benefit is zero or negative, the process is not a good first candidate. Look for one with more volume, or automate a narrower slice first.
A worked example
These are example numbers to show the math, not benchmarks.
An operations team copies 400 orders a month from email into their order system. Each takes 6 minutes, and 20 of them a month need fixing, at 20 minutes each. Their fully loaded cost is $45 an hour. A new workflow handles 80% of orders end to end and should avoid 15 of the 20 monthly errors. It costs $6,000 to build and roll out, plus $100 a month for the platform and AI usage and a $150 monthly allowance for upkeep.
- Time value: 400 × 6 ÷ 60 × 0.8 × $45 = $1,440
- Error value: 15 × 20 ÷ 60 × $45 = $225
- Monthly value: $1,665
- Net monthly benefit: $1,665 - $250 = $1,415
- Payback: $6,000 ÷ $1,415 = about 4.2 months
- First-year ROI: ($1,415 × 12 - $6,000) ÷ ($6,000 + $250 × 12) = $10,980 ÷ $9,000 = 122%
The ROI calculator template
Put the labels in column A and the values in column B of a spreadsheet, one sheet per process. Rows 1 to 9 are inputs; rows 10 to 13 calculate themselves.
| Row | Item (column A) | Example | Column B |
|---|---|---|---|
| 1 | Volume per month | 400 | Input |
| 2 | Minutes per item | 6 | Input |
| 3 | Share automated | 80% | Input |
| 4 | Fully loaded hourly cost | $45 | Input |
| 5 | Errors avoided per month | 15 | Input |
| 6 | Minutes per error | 20 | Input |
| 7 | Monthly platform and AI costs | $100 | Input |
| 8 | Monthly upkeep | $150 | Input |
| 9 | One-time costs | $6,000 | Input |
| 10 | Monthly value | $1,665 | =B1*B2/60*B3*B4+B5*B6/60*B4 |
| 11 | Net monthly benefit | $1,415 | =B10-B7-B8 |
| 12 | Payback (months) | 4.2 | =B9/B11 |
| 13 | First-year ROI | 122% | =(B11*12-B9)/(B9+(B7+B8)*12) |
Format B3 and B13 as percentages. To compare several processes, copy the sheet and add a summary tab that pulls rows 11 to 13 from each.
Using the Devma Labs ROI calculator
The calculator on our pricing page gives a quick first estimate from four inputs: people doing the work, hours each per week, the share you expect to automate and fully loaded hourly cost. It compares the result with a monthly plan and shows its formula on screen, with no hidden multipliers. Use it to decide whether a process deserves a closer look, then build the full case with the template above.
Review it every quarter
Volumes change, prices change and apps update their APIs. Once a quarter, compare the estimate with what actually happened: runs per month from n8n's execution history, error tickets and time spent on upkeep. Update the inputs, and track a few signals alongside the money, such as response times, backlog and error rates.
When a workflow pays back, use what you learned to pick the next one. If you would like help scoping it, workflow consulting covers process mapping and the business case.
Written by Devma Labs
Discuss this topicFrequently asked questions
What should I include in the cost of automation?
Build cost, the n8n plan or hosting, AI model usage, paid app or API upgrades, monitoring, and the time someone spends maintaining the workflows. Leaving out maintenance is the most common reason ROI estimates look better than reality.
How often should I recalculate automation ROI?
Every quarter, and whenever volumes, prices or the process change. Compare the estimate with what actually happened and update the inputs.
Does the Devma Labs ROI calculator use hidden assumptions?
No. It uses only the numbers you enter (people, hours each per week, the share you expect to automate and hourly cost) and shows the formula on screen.