How do you calculate automation ROI?

The calculator annualizes how often the task runs (per day times the days a week it runs times 52, per week times 52, per month times 12), turns that into hours at the minutes you set, and multiplies the share automation removes by your hourly labor cost to get gross savings. It subtracts the monthly tool cost for net savings, then compares a year of gross savings against the one-time build cost plus a year of tool cost for payback period and first-year ROI.

Why is there a percent automated slider?

Few automations remove 100 percent of the manual time. There are usually exceptions, edge cases, and a little oversight left over. The slider lets you set a realistic share, defaulting to 85 percent, so the result is honest rather than best case.

Does the payback period include the build cost?

Yes. Payback is the one-time build cost divided by the net monthly saving, where net already has the tool subscription removed. The monthly savings figure itself excludes the one-time build, since that is paid once, not every month.

Is the calculator free and does it store my data?

It is free with no sign-up. The math runs entirely in your browser. Your inputs are kept only in your own browser so the page remembers them, and are added to the link only when you choose to copy it. Nothing is sent to a server.

Free tool

Automation ROI calculator: what a repetitive task really costs

Put a number on a manual task. Enter how often it runs, how long it takes, and what an hour of that work costs, and see the hours freed, money saved, payback period, and first-year ROI of automating it. Adjust the inputs and the result follows live. Copy the link to send your numbers to a boss or client. Runs in your browser, no sign-up, nothing stored on a server.

Hours freed Net savings Payback period First-year ROI Shareable link

The task you might automate

What is the task?

Only labels your result. It does not affect the math.

Currency

How often does it run?

Minutes per run, done by hand

min

Cost of an hour of that work

$ / hr

How much of the time does automation remove? 85%

Most automations leave a little manual work: exceptions, edge cases, a quick check. 85% is a realistic default. Slide to 100% only if the task is fully hands-off.

One-time cost to build it

Monthly tool / subscription cost

$ / mo

Hours freed / year

about 0 hrs / month

Net savings / year

after tool cost · excludes one-time build

Payback period

—

to earn back the build

First-year ROI

—

net value vs total cost

Adjust the inputs to see your payoff.

Get in touch

A worked example

How to read the result, with real numbers.

Say a small team handles lead follow-up emails 20 times a week. Each one takes about 8 minutes by hand, and an hour of that person's time costs $15. You expect automation to remove 85% of the manual work and leave the rest for exceptions, you pay a developer $600 once to build it, and it runs on a $25 a month tool. Those are the numbers the calculator opens with, and here is how much automating that task saves and how to read each figure.

Time saved by automation: about 118 hours a year

Twenty runs a week is 1,040 a year; at 8 minutes each that is about 139 hours of manual work, and removing 85% of it frees roughly 118 hours, near 10 hours a month. Lead with this number, because freed time is the real product of automation. Whether it is worth money depends on the next figures.

Net savings: about $1,468 a year

Those 118 hours at $15 are roughly $1,768 of time value, the gross saving. Subtract the $300 a year tool subscription and the net automation cost savings come to about $1,468, or $122 a month. The one-time $600 build is not in this monthly figure, because you pay it once, not every month.

Payback period: about 4.9 months

Divide the $600 build by the $122 net monthly saving and the automation pays for itself in just under five months. After that, the saving keeps adding up. A short payback period is the clearest single signal that a task is worth automating.

First-year ROI: about +96%

In year one you free $1,768 of time against $900 of total cost, the $600 build plus $300 of tool. That is a return on investment near 96%, so the task returns almost double what it costs in the first year. ROI after year one is far higher, since the build is already paid for.

Change any input and every number follows live. Lower the percent automated for a more cautious estimate of how much automating a task saves, switch the rate to per day to set the days a week it runs, or copy the link to send your own automation ROI estimate to a colleague or client.

How it works

The math, in plain terms.

From minutes to money

Your runs are annualized: per day × the days a week it runs ×52, per week ×52, per month ×12. Monthly figures are the yearly one divided by 12, so the two always agree.
Annual runs × minutes give the hours a year; the "percent automated" slider decides how many of those actually go away.
Freed hours × your hourly cost is the gross saving.
Minus the tool subscription, that is your net saving.

Payback and ROI

Payback period is the one-time build cost divided by net monthly saving.
First-year ROI compares a year of gross savings against the build plus a year of tool cost.
The monthly net saving excludes the one-time build, because you pay that once, not every month.
If the numbers go negative, the tool says so instead of hiding it. It is an estimate to size the opportunity, not a quote.

Honest scope

An estimate, not a promise.

Why the defaults are conservative

The slider defaults to 85% automated, not 100%, because real workflows keep a few exceptions a human still handles. Build and tool costs vary by task and platform; the figures here are placeholders for you to replace with your own.

What it does not do

It does not count softer wins like fewer mistakes, faster response, or work that only happens once it is automated. Those are real, but harder to pin to a number, so this stays on the time-and-cost math you can defend.

Got a number worth acting on?

If automating that task pays back fast, the next step is scoping it. See real workflow examples I have built, compare tools in the Zapier vs Make vs n8n pricing breakdown, or read how I approach automation and optimization.

Get in touch