,

Automation ROI: The Formula, Benchmarks and Payback Periods (2026)

Small repeated time savings accumulating into a large monthly return

Automation ROI is minutes saved per run, multiplied by runs per month, converted to hours, multiplied by what an hour of your time is worth, minus the tool cost. That’s it. The formula takes thirty seconds to run and it kills roughly half the automations people are excited about — which is exactly why it’s worth running before you build.

Below is the formula, the two inputs everyone gets wrong, a benchmark table for the most common small-business automations, and the payback thresholds that tell you whether to build now, later or never.

Key takeaways

  • The formula: (minutes saved × runs per month ÷ 60) × hourly value − tool cost = monthly return.
  • Frequency dominates everything. Two minutes saved 400 times beats an hour saved twice. Always.
  • Include build time or your ranking is wrong. Three hours to build at $50/hour is $150 against a $9/month plan.
  • Break-even on a $9 plan is about 11 minutes of saved time a month at a $50 hourly value. Nearly everything clears it.
  • Under 3 months payback: build now. 3–6 months: queue it. Over 6: don’t. The tool will have changed by then anyway.
Abstract diagram of small repeated units accumulating into a larger volume
Frequency is the dominant term. Small savings repeated often beat large savings repeated rarely.

How Do You Calculate Automation ROI?

Four inputs, one subtraction. Multiply the minutes each run saves by how often it runs, divide by 60 to get hours, multiply by your hourly value, then subtract what the tool costs per month.

Monthly return = (minutes saved per run × runs per month ÷ 60) × hourly value − tool cost

Worked example. An automation that saves 4 minutes of manual data entry, running 120 times a month, at a $50 hourly value, on a $9 plan:

  • 4 × 120 = 480 minutes saved
  • 480 ÷ 60 = 8 hours a month
  • 8 × $50 = $400 of recovered time
  • $400 − $9 = $391 net monthly return

That’s a 43× return on the subscription, which sounds absurd until you notice the subscription was never the real cost.

Which Two Inputs Do People Get Wrong?

Hourly value and build time. Get either wrong and the ranking that comes out is confidently misleading — which is worse than having no ranking at all.

Your hourly value is not your salary ÷ 2,080

For a business owner, hourly value is what you’d earn if you spent that hour on your highest-value work instead — selling, delivering, building the thing customers pay for. For most owners that’s meaningfully above their notional wage. Using the wage figure systematically understates every automation’s return and leads to under-investing.

For an employee’s time, the honest figure is fully-loaded cost: salary plus tax, benefits and overhead, typically 1.25–1.4× base.

Build time is a real cost and it’s front-loaded

A $9 plan is not what your automation costs. Two to four hours of building it is. At $50 an hour that’s $100–200 spent once, against $9 a month recurring — so a low-frequency automation can have a great monthly return and still take a year to pay back the build.

Input Common mistake Use instead
Hourly value Salary ÷ 2,080 What your best hour actually earns
Runs per month Guessing from memory Count it for one real week, multiply by 4.3
Minutes saved Total task time Only the part software replaces
Tool cost Full plan price per automation Plan price ÷ number of automations sharing it
Build time Excluded entirely 2–4 hrs first time, 1–2 hrs after
The “minutes saved” row is the subtlest. If a task takes 10 minutes and automation still needs 3 minutes of review, you saved 7, not 10.

What Are the Benchmark Returns by Automation Type?

Below are the most common small-business automations with typical time savings and frequencies, run through the formula at a $50 hourly value on a shared $9 plan. Substitute your own volumes — the ranking shifts with them, which is the entire point of doing this rather than copying a list.

Automation Mins/run Runs/mo Hrs/mo Monthly value Build Payback
Lead capture → CRM → alert 4 120 8.0 $400 2 hrs <1 week
Appointment reminders 3 90 4.5 $225 2 hrs ~1 week
Social post distribution 9 20 3.0 $150 3 hrs ~3 weeks
Invoice send + chase 7 25 2.9 $146 3 hrs ~3 weeks
Weekly reporting pack 45 4 3.0 $150 4 hrs ~4 weeks
Client onboarding sequence 25 8 3.3 $167 4 hrs ~4 weeks
Expense receipt filing 2 60 2.0 $100 2 hrs ~4 weeks
Support ticket routing 2 200 6.7 $333 4 hrs ~2 weeks
Worked arithmetic using the formula above at $50/hr on a shared $9/month plan — not survey findings. Payback counts build time at the same hourly value.

Two patterns worth naming. Lead capture and ticket routing win because of frequency, not because they save much per run — both save only 2–4 minutes each time. And the weekly reporting pack looks impressive per run (45 minutes) but ranks mid-table, because four runs a month can’t compete with 120.

What Payback Period Should You Accept?

Under three months, build it now. Three to six months, queue it behind the fast ones. Over six months, don’t build it — the tool, the process or the business will have changed before it pays back.

Payback Decision Reasoning
Under 1 month Build today Every week you wait is pure loss
1–3 months Build this month Comfortably inside any planning horizon
3–6 months Queue it Fine, but only after the sub-3-month ones
6–12 months Don’t build Your process will change first
Over 12 months Don’t build You’re solving the wrong problem — fix the process
The six-month cut-off is deliberately aggressive. Automation is cheap and fast now; if payback is slow, the task is the problem.

One important exception to the payback rule: automations that prevent errors rather than save time. An invoice chase sequence that recovers one forgotten $2,000 invoice a year has a payback you cannot calculate from minutes. Score those on risk reduction, not time.

Ascending stepped bars representing shortening payback periods
Build the short-payback automations first. The long tail rarely survives contact with a changing business.

How Does the Tool You Pick Change the Math?

Less than most people assume, but not zero — and the difference is about how each platform meters work rather than the headline price. All three major platforms cost between $9 and $50 a month at small-business scale, which is a rounding error against a $400 monthly return.

Platform Entry paid Included Billing unit
Make Core $9/mo 10,000 credits One module run
Zapier Professional $19.99/mo annual 750 tasks One action step
n8n Cloud Starter €20/mo annual 2,500 executions One whole workflow run
Read off each vendor’s pricing page, 26 July 2026.

Where it does matter: high-frequency automations on per-step billing. The support-ticket-routing row above runs 200 times a month. On Zapier with three action steps that’s 600 tasks — most of a 750-task plan for one automation. On n8n it’s 200 executions. Same return, different tool cost, and at high frequency that changes which plan tier you need.

Our comparison of AI automation tools prices the same automation on all three, and there are dedicated breakdowns for Make’s credit math, Zapier’s per-step tasks and n8n’s per-execution model.

How Do You Verify the Return Was Real?

Measure runs per month from your platform dashboard after 30 days and compare it to your estimate. That single comparison catches almost every bad assumption, because run count is the term the formula is most sensitive to and the one people guess worst.

Check Where to find it Red flag
Actual runs vs estimate Platform execution log More than 30% below estimate
Failure rate Error notifications Above 5% means the rules don’t match reality
Time still spent manually Honest self-assessment Any manual fallback means it isn’t trusted
Review time added Honest self-assessment If you check every output, subtract that time
The last row is the one that quietly destroys ROI. An automation you verify every time saved you less than you think.

Re-run the formula with the real numbers at day 30. If the return holds, move to the next automation. If it doesn’t, you now know which input you misjudged — and that correction makes every future estimate better.

Frequently Asked Questions

How do you calculate ROI on automation?

Multiply minutes saved per run by runs per month, divide by 60 for hours, multiply by your hourly value, then subtract the monthly tool cost. Include build time as a one-off cost when working out payback period.

What’s a good ROI for business automation?

Payback inside three months. High-frequency automations like lead capture typically pay back their build time in under a week, because they run 100+ times a month even though they only save a few minutes each time.

Should I include my own time in automation ROI?

Yes, on both sides. Your time saved is the return, and your time spent building is the cost. Skipping build time makes low-frequency automations look far better than they are.

How much does business automation software cost?

$9 to $50 a month for most small businesses — Make Core from $9, Zapier Professional from $19.99, n8n Cloud from €20, all billed annually. Against a typical $150–400 monthly return, the plan price is rarely the deciding factor.

What hourly rate should I use for the calculation?

For your own time, what you’d earn spending that hour on your highest-value work — usually above your notional wage. For staff time, fully-loaded cost: salary plus tax, benefits and overhead, roughly 1.25–1.4× base.

Why does frequency matter more than time saved?

Because it multiplies. Saving two minutes 400 times is 13.3 hours; saving an hour twice is 2. The automations that feel most annoying are usually low-frequency, which is why annoyance is a bad ranking signal.

The Bottom Line

Automation ROI is arithmetic, not judgement, and the arithmetic is simple enough to do in your head. The discipline is in using honest inputs: your real hourly value, a counted rather than remembered run frequency, only the minutes software actually replaces, and build time on the cost side.

Run it on your top five candidates before building any of them. Sort by payback. Build the sub-three-month ones and leave the rest. Then check the real numbers at day 30 and correct your estimating — that feedback loop compounds faster than any individual automation.

For the full build sequence and a scoring rubric, see the business automation playbook. For the inverse framing — what staying manual costs you — see the cost of not automating.

Want one practical automation you can set up in 15 minutes, delivered twice a month? Join the free AI automation newsletter.

Sources

All sources retrieved 26 July 2026. All ROI and payback tables are worked arithmetic using the formula above at a $50 hourly value — they are illustrative models, not survey findings. Substitute your own volumes.