An automation is worth it when the time it saves, valued at what your hour is really worth, pays back the setup and the tool cost within a few months. The calculator below does that math for you, and it also works in reverse: tell it how fast you want your money back, and it tells you the most you should spend.
Most automation ROI calculators online are built by agencies that sell automation projects, and their numbers lean optimistic. This one assumes some of the work stays manual, counts the time you'll spend fixing the scenario, and shows how many Make credits it will burn. Nothing to sign up for, and nothing to buy at the end.
Automation ROI calculator
Fill in your numbers to see the result.
- Hours saved per month
- –
- Value of that time
- –
- Net gain per month
- –
- Setup cost (your time)
- –
- Net gain in the first year
- –
Reverse ROI: your spending limit
- Most you should spend to build it
- –
- Most you should pay per month for tools
- –
Make credits
- Credits per month
- –
- Make plan
- –
Estimates only. Credit math assumes each check uses 1 credit and every other module uses 1 credit per item, which is how Make counts most actions.
The simple formula, and the three numbers people get wrong
Under the hood, the calculator runs one line of math:
Monthly gain = (hours saved × value of your hour) − tool cost
Payback (months) = setup cost ÷ monthly gainThe formula is easy. The inputs are where most estimates go wrong.
1. The value of an hour isn't the hourly wage. If an employee does the task, use their full cost: pay plus taxes, insurance and benefits. If you do it yourself, use what that hour is worth to the business, such as the rate you'd bill a client. Using a low number here makes good automations look pointless.
2. Automation never takes the work to zero. Someone still reads the alert, checks the odd result, or handles the case the scenario skips. I set the default to 15% for that reason. When I built my client onboarding scenario, my first test email said "Welcome to !" with the company name missing, and Make showed no error. Checking the output is part of the job.
3. Scenarios need upkeep. Apps change their fields, a connection expires, a sheet column gets renamed. Thirty minutes a month is a fair starting estimate for a small scenario. It's small, but leaving it out is how a three-month payback turns into six.
Reverse ROI: start from the payback you want
The usual question is "how long until this pays off?" A more useful one, before you spend anything, is "if I want my money back in three months, how much can I spend?"
That's what the reverse section of the calculator answers. It takes your monthly gain and multiplies it by your payback goal. The result is your ceiling: the most you should spend building the automation, or paying for tools, before it stops making sense.
This is the number to have in your head before you hire a freelancer, buy a template, or upgrade a plan. If someone quotes $800 to build a scenario and your ceiling is $340, you know the answer without a long debate. Automations built with Make usually pay back in weeks or a few months, so a goal of 3 months is a sensible default for a small business. Raise it if the task is critical and the savings are steady.
Two examples from scenarios I built and tested
Client onboarding
In my onboarding tutorial, the manual process took about 30 minutes per new client: create a folder, share it, copy the checklist, write the welcome email and tell the team. Here's the math for a business that signs 10 clients a month:
| Input | Value |
|---|---|
| Clients per month | 10 |
| Minutes each, by hand | 30 |
| Value of an hour | $40 |
| Work that stays manual / upkeep | 15% / 30 minutes |
| Setup time | 3 hours (one evening) |
| Modules / checks per day | 7 / 1 |
The result: 3.75 hours saved a month, worth $150. The $120 of setup time pays back in under a month, and the first year nets about $1,680. It uses 90 Make credits a month, well inside the Free plan. In my own test, onboarding one client used exactly the credits the formula predicts.
Duplicate lead check
My duplicate leads scenario checks every form submission against a Google Sheet before saving it. In my tests, each response used between 4 and 6 credits depending on the path. Say a form gets 60 submissions a month and checking each one by hand takes 3 minutes.
The savings are modest, about 2 hours a month. The interesting part is the schedule. Checking the form every 15 minutes means 96 checks a day, around 2,880 credits a month, almost three times the Free plan, before a single lead is processed. Checking every 2 hours drops that to about 600 credits in total. Same scenario, same leads, and the schedule alone decides whether it's free or paid.
The schedule costs more than the work. Each scheduled check uses a credit even when there's nothing new. Before you switch a scenario on, put your check frequency into the calculator. For most small business tasks, once or twice a day is plenty.
How many Make credits will it use?
Make bills in credits. According to its pricing page, each module action, like adding a row to Google Sheets or fetching Gmail data, counts as one credit, and routers don't count. The Free plan includes 1,000 credits a month, two active scenarios and a 15-minute minimum interval between runs. The Core plan starts at $12 a month for 10,000 credits.
The calculator estimates credits like this:
Credits per month = (checks per day × 30) + (items per month × (modules − 1))The "minus one" is the trigger module, which is already counted in the checks. Scenarios that loop over many items, or use Make's AI features, can use more, so treat the result as a floor and check the real usage in Make after the first week.
When automation is not worth it
Running the numbers also tells you when to walk away. In my experience, these are the usual cases:
- The task is rare. Something you do three times a month at 10 minutes each saves half an hour. It rarely beats the setup time.
- Every case needs judgment. If you'd have to check every result anyway, set "work that stays manual" to 50% or more and watch the gain disappear.
- The process keeps changing. Automating a process you redesign every month means rebuilding the scenario every month. Settle the process first.
- A mistake is expensive. Automated invoices or payments that go wrong cost more than the hours they save. Start with a version that drafts and lets you approve.
If you're not sure where to start, my guide to the processes to automate first ranks the usual candidates, and the cost of not automating shows what the manual version costs over a year.
Your next step
Pick the task that annoys you most this week, time it once with a stopwatch, and put the real numbers into the calculator. If it pays back inside your goal, build it. The lead capture, client onboarding and invoice reminder tutorials are good first candidates, and all of them run on Make's Free plan. If you don't have an account yet, you can create one for free.
Disclosure: the Make link in this article is an affiliate link. If you sign up for a paid plan through it, Biz Flow Craft may earn a commission at no extra cost to you. It doesn't change the calculator or the numbers above.
Frequently asked questions
How do you calculate the ROI of an automation?
Multiply the hours the automation saves each month by what an hour is worth to your business, then subtract the monthly tool cost. That's your monthly gain. Divide the setup cost by the monthly gain to get the payback time in months.
What is reverse ROI?
Reverse ROI starts from the payback time you want instead of the cost. Multiply your monthly gain by your target number of months, and you get the most you should spend on building or running the automation.
Is it worth automating a task I do only a few times a month?
Usually not. A task done three times a month at 10 minutes each saves about half an hour, which rarely covers the time to build and maintain the automation. Rare tasks are worth automating only when a mistake would be costly.
How many Make credits does an automation use?
Roughly one credit for each scheduled check plus one credit for each module that processes an item. A seven-module scenario that checks once a day and handles 10 items a month uses about 90 credits, inside Make's Free plan of 1,000 credits a month.
What is a good payback period for a small business automation?
For scenarios built with tools like Make, three months or less is a reasonable goal. Many simple automations pay back within the first month because the main cost is a few hours of setup.
Sources
- Make, Pricing & Subscription Packages, Free plan limits, Core plan price and credit rules, checked October 2026.
- Make Help Center, Credits and operations, checked October 2026.
- Credit usage and setup times from scenarios built and tested by the author for Biz Flow Craft, September and October 2026.