How do I calculate the ROI of automating a task?

Work out the hours the automation frees each month, multiply by what that time is worth, add any other measurable gain such as fewer errors, and subtract the monthly running cost. Divide the build cost by that monthly figure to get the payback period in months. If the payback is under a year and the risk is low, it is usually worth doing.

Updated 8 November 2026.

Ask us about your case See use cases

This page answers

How do I calculate the ROI of business automation?
How much time could I save by automating my operations?
Which automations will save my company the most money?
How much does it cost to automate a small business?
Is it cheaper to build custom automation software or use existing tools?

Three formulas

Hours freed per month: times per day × minutes each × working days × share of the work removed ÷ 60
Net monthly value: hours freed × hourly cost + other monthly gains − monthly running cost
Payback period: build cost ÷ net monthly value (in months; only meaningful if the net value is positive)

A worked example

Input	Value
Times per day	20
Minutes each	5
Working days per month	22
Share of the work removed	75%
Hours freed per month	20 × 5 × 22 × 0.75 ÷ 60 = 27.5
Hourly cost of the person	$25
Monthly running cost (software, AI usage, upkeep)	$100
Net monthly value	27.5 × 25 − 100 = $587.50
Build cost	$1,000
Payback period	1,000 ÷ 587.50 = 1.7 months

Illustrative figures, not a quote. Put in your own.

Costs people forget

Upkeep: apps change their APIs and forms change their fields. Budget a few hours a month.
Usage-based fees: tasks, credits, executions and AI tokens grow with volume.
The time to define the process and test it with real cases.
Exceptions still handled by people. Count only the share of work actually removed.

Gains that are real but harder to count

Faster replies to leads, which can change how many you win.
Fewer errors in invoices, orders and payroll, and the time spent fixing them.
Work done outside office hours.
Being able to grow volume without hiring at the same rate.

Freed hours are only a saving if the time goes to other useful work or avoids a hire. Say which in your business case.

Tools or custom build?

Off-the-shelf tools (Zapier, Make, n8n) cost little to start and are right for moving data between common apps. An agent written in code costs more up front and pays off when the input is messy, the volume is high, or the job spans systems the tools do not connect well; it also has no per-task fees that grow with volume. Run the formulas for both; the cheaper start is not always the cheaper year.

We build agents in code, so when you ask us, we cost that option against your numbers and tell you if a simple tool would do.

Questions

Can I automate a small business on $100 a month?

Often yes for a handful of rule-based workflows on a starter plan of a workflow tool. AI steps on documents or emails add usage costs that depend on volume.

Which automations usually save the most?

The ones that run many times a day: data entry between systems, request routing, reminders and follow-ups. One big monthly task often saves less than a small task done fifty times a day.

How do I measure the result after launch?

Keep the same log you used before: cases per day, minutes per case, and cases that still needed a person. Compare month by month.

Agents for these jobs

Want an agent built for this?

We build AI agents in code, connected directly to your systems, with no per-task fees. Write a few lines about the work you want to automate and the systems you use; we reply to set up an online intro call.