Strategy

How to Calculate Automation ROI: Formula and Worked Examples

By Rowan Ellis · Updated October 7, 2026

A step-by-step automation ROI formula using your own hours and rates, with worked examples priced on Zapier, n8n, Make and Pipedrive list prices.

Automation ROI is annual value minus annual cost, divided by annual cost. For a time-saving workflow, annual value is hours saved per week x weeks per year x the loaded hourly rate of the person who used to do the work. Annual cost is the tool plan, the hours spent building and watching it, and any usage overage. The worked examples below put list prices from Zapier, n8n, Make and Pipedrive into that formula, with the hours and hourly rates left for you to replace with your own.

The formula, written out

ROI = (Annual value - Annual cost) / Annual cost

Break the two sides into inputs you can measure:

  • Annual value = hours saved per week x weeks the task really happens x loaded hourly rate. "Loaded" means salary plus the employer costs you would normally add, divided by paid hours. Ask finance for the figure; do not guess it from a job-board salary.
  • Annual cost = tool fees x 12 + build hours x rate + monitoring hours per month x 12 x rate + overage.

Two assumptions are doing a lot of work in that value line, so state them every time: how many weeks per year the task actually runs (the examples below use 48, not 52, because holidays and quiet weeks mean the manual work was not happening every week), and whether the saved hours are redeployed to something else or just disappear into the day. Hours saved are capacity, not cash, unless you avoid a hire, cut overtime or ship something you otherwise would not have.

Step 1: Measure the baseline before you build

You cannot show an improvement without a before. For two to four weeks, have the person who does the work log three things: how many times the task came up, how long each took, and how long fixing mistakes took. Use the median week, not the best or worst one. For CRM and support tasks you can read the run count directly from the system (deals moved, tickets tagged, trial accounts created) and only need to time a handful of examples. Write the dates of the baseline next to the numbers, because the "after" measurement must use the same definition of one run.

Step 2: Count the full cost

The most common error is to count only the subscription. A complete cost line has five parts:

  • Tool fee at the tier you will actually need. Zapier meters tasks, n8n meters executions and Make meters credits, so the right tier depends on volume. See the usage arithmetic in the automation mistakes guide before picking one.
  • Seats, but only the increment. If you already pay for a CRM seat, the cost of a better plan for that seat is the difference, not the full price.
  • Build hours at the loaded rate of whoever builds it, including testing against awkward records.
  • Monitoring and fixes, in hours per month. A workflow that needs an hour a month of attention costs twelve hours a year, and that is often more than the subscription.
  • Overage. Zapier's pricing page says pay-per-task billing is charged at a higher per-task rate than your base tasks; Make says extra credits are sold in bundles at the fixed price in your subscription. Add a line for it if your volume is close to a tier boundary.

Worked example 1: a Zapier workflow that saves 5 hours a week

Inputs (replace each with yours): the workflow copies new paid customers from billing into the CRM, posts a welcome task to the account owner and updates a tracking sheet. Someone used to do this by hand for 5 hours a week. Their loaded rate is $40 an hour. The task runs 48 weeks a year. You build it in 10 hours, spend about an hour a month checking it, and assume its tasks fit the entry task tier of Zapier's Professional plan, listed from $19.99 a month.

Line Working Year 1
Value: hours saved 5 h x 48 weeks x $40 $9,600.00
Cost: Zapier Professional $19.99 x 12 $239.88
Cost: build 10 h x $40 $400.00
Cost: monitoring 1 h x 12 months x $40 $480.00
Total cost $1,119.88
ROI ($9,600.00 - $1,119.88) / $1,119.88 about 757%

Two derived numbers are more useful than the percentage. Payback: monthly value is $800, monthly running cost is $19.99 plus $40 of monitoring, so the $400 build is repaid in about half a month of operation. Break-even: the total year-one cost of $1,119.88 divided by $40 x 48 hours of annual value per weekly hour gives 0.58 hours a week, or roughly 35 minutes. If the manual task takes less than that, the automation does not pay for itself in year one.

Worked example 2: the same workflow when volume pushes you up a plan

Now suppose the workflow runs about 3,000 times a month and you price it on n8n instead. n8n's pricing page counts one execution per run of the whole workflow regardless of steps, and lists Starter at $20 a month billed annually for 2.5K executions and Pro at $50 a month billed annually for 10K. At 3,000 runs you need Pro, so the tool line becomes $50 x 12 = $600.

Total cost is $600 + $400 + $480 = $1,480. ROI is ($9,600 - $1,480) / $1,480, about 549%, still strongly positive, but the tool fee is now the biggest line and the plan boundary matters. Had the volume stayed under 2,500, Starter at $20 x 12 = $240 would have kept the total at $1,120. The lesson: price the plan at your real volume, then check how close you are to the next boundary. Make's Core plan is listed at $9 a month billed annually, or $10.59 billed monthly, for 10k credits, so on Make the same sum would use the credit count of the workflow instead of its run count.

Worked example 3: CRM automation priced per seat

Seat-priced tools change the cost logic, because the plan applies to every user. Suppose five sales reps each save one hour a week of follow-up work by using automations and sequences. Pipedrive's pricing page lists Lite at US$14 per seat per month billed annually and Growth, the first plan with automations and nurturing sequences, at US$39. The reps already need a CRM, so only the step from Lite to Growth counts: $39 - $14 = $25 per seat per month, or 5 x $25 x 12 = $1,500 a year.

Line Working Year 1
Value: rep time 5 reps x 1 h x 48 weeks x $50 $12,000
Cost: plan step-up 5 x ($39 - $14) x 12 $1,500
Cost: build 12 h x $50 $600
Cost: monitoring 1 h x 12 months x $50 $600
Total cost $2,700
ROI ($12,000 - $2,700) / $2,700 about 344%

The seat count is the sensitive input. Value rises with each rep but so does the fee, so if only two of the five reps would use the sequences, only two seats should be on Growth. Premium is listed at US$59 for lead generation and routing, so check that a routing rule needs the extra $20 per seat before you pay for it.

Worked example 4: revenue-side automation, such as failed-payment emails

Revenue examples are where inflated ROI claims usually come from, so use only numbers from your own billing reports. The formula: incremental recoveries per month x average invoice x 12 x gross margin. "Incremental" matters. Stripe's documentation says Stripe Billing can automatically retry failed subscription and invoice payments, so any invoice that a retry would have recovered anyway is not value created by your email flow. Count only the payments recovered after the customer received your message and updated their card.

To show the arithmetic only, suppose your report shows 8 such invoices a month at $49 and your gross margin is 75%: 8 x $49 x 12 x 0.75 = $3,528 a year. Those numbers are placeholders. Change any of them and the answer changes, which is the point of writing the formula down before you build.

What to measure for each kind of automation

No universal ROI range exists for these categories, and none is given here: results depend on your baseline, your audience, your build quality and how you attribute value. Use the table to choose the metric and window for each workflow, then fill the formula with your own measured numbers.

Automation Type How to value it Measurement window
Dunning sequences Model recovered gross margin; avoid counting prevented churn as certain revenue Depends on failure volume and recovery lag
Trial conversion Compare cohorts with the same trial definition and acquisition mix Usually requires a full trial cycle
Onboarding sequences Measure activation or support reduction, not opens alone Often several weeks to a quarter
Lead scoring/routing Count only qualified opportunities accepted by sales Depends on sales-cycle length
Support deflection Validate resolution quality and repeat-contact rate Track by issue type
Data sync workflows Value saved labor only where the process would otherwise run Depends on volume and failure cost

Step 3: Re-measure after launch and recompute

Four to eight weeks after launch, repeat the baseline measurement with the same definition of one run. Replace the projected hours with the measured ones, replace the estimated monitoring time with the time actually spent (the first month is usually the heaviest), and read the real usage from the vendor's usage page. Then recompute. If the measured value is half the projection, the ROI is still the number you computed from measurements, not the number you promised.

Your own calculation, line by line

Fill the table with your inputs. Every row is one of the lines used in the examples above, so you can check your arithmetic against them.

Line Where the number comes from Your figure
Hours saved per week Baseline log minus post-launch log, median week  
Weeks per year it runs Your calendar, not 52 by default  
Loaded hourly rate Finance, for the person who did the work  
Tool fee per year The plan at your measured volume, from the vendor's pricing page  
Build hours and monitoring hours Time tracked, multiplied by the builder's rate  
ROI (value - cost) / cost  

Ranking what to automate next

With several candidates, rank them by payback rather than by ROI percentage, because a small workflow can show a high percentage and still save very little. Payback in months is the build cost divided by monthly value minus monthly running cost. In example 1 that is $400 / ($800 - $59.99), about half a month. Then discount each candidate by how much you trust its baseline: a measured baseline deserves full weight, a guess deserves much less. The order of the list is usually obvious after that.

Mistakes that inflate the answer

  • Counting the whole seat price of a CRM or helpdesk you were paying for anyway, or, in the opposite direction, ignoring a plan step-up that the automation requires.
  • Assuming 52 working weeks for a task that follows the sales or support calendar.
  • Taking the best week as the baseline, or the worst one, instead of the median.
  • Crediting the automation with changes made at the same time, such as a new pricing page or a new onboarding screen, when a number moved.
  • Forgetting monitoring, which for small workflows is often a larger cost than the tool.
  • Valuing saved hours at the full rate when the person still spends the time, only on something of lower value. Use the rate of the work they actually do with it.

Questions people ask about automation ROI

What loaded hourly rate should I use?

Use your own: total employer cost of the role per year divided by the hours that person is paid to work. The examples use $40 and $50 only so the arithmetic is easy to check. If the person is a founder, use what an hour of their alternative work would earn or cost, and say which.

Should I include the cost of building it?

Yes, through the build line. Ten hours of an engineer's time is priced at that engineer's rate, not at the tool fee. If building displaces other work, the real cost is the value of that work.

Is a free plan enough to run the workflow?

Rarely for production work. Zapier's Free plan includes 100 tasks a month and two-step Zaps, and Make's Free plan includes 1,000 credits a month with 2 active scenarios and a 15-minute minimum interval between runs, so a workflow with real volume or more than a couple of steps outgrows them quickly. Use the free tier to build the baseline and a prototype, then price the paid plan you will actually need.

Pick the tool before you price it

Browse the automation tools covered on this site, each with its billing unit and list price.

View All Automation Tools