How to Calculate ROI on Business Automation

Most businesses make automation decisions on vibes: "this feels like it'll save time" or "everyone says AI is the future." That's how you end up either automating the wrong thing or paying too much for the right thing. The fix is a five-minute calculation, not a finance degree.

What inputs do you need to calculate automation ROI?

Four numbers, all of which you likely already know or can estimate in an afternoon:

1. Hours saved per week — how much manual time the current process takes, multiplied by how much of it the automation actually removes.
2. Loaded hourly rate — what an hour of that person's time actually costs the business (see below — this is almost always higher than their hourly wage).
3. Implementation cost — what it costs to build and deploy the workflow, one-time.
4. Ongoing cost — usage-based costs (API/model calls, any subscriptions) plus light maintenance time, per year.

Get these four and the rest is arithmetic.

What's the basic ROI formula?

Annual hours saved = hours saved per week × 52
Annual savings ($) = annual hours saved × loaded hourly rate
Total annual cost = ongoing cost + (implementation cost ÷ years of use, or full amount in year one)

ROI (%) = (Annual savings − Total annual cost) ÷ Total annual cost × 100
Payback period (months) = Implementation cost ÷ (Annual savings ÷ 12)

That's the whole model. Everything else is just plugging in better numbers.

Worked example

Say a brokerage automates certificate-of-insurance requests (see our insurance automation guide for the full workflow):

Running the formula:

• Annual hours saved = 10 × 52 = 520 hours
• Annual savings = 520 × $45 = $23,400
• Total year-one cost = $12,000 + $3,600 = $15,600
• Year-one ROI = ($23,400 − $15,600) ÷ $15,600 = 50%
• Payback period = $12,000 ÷ ($23,400 ÷ 12) = ~6.2 months

From year two onward, the implementation cost is already sunk, so ROI jumps to ($23,400 − $3,600) ÷ $3,600 ≈ 550% — which is the more realistic long-run picture for a workflow like this.

What's a "loaded hourly rate" and why does it matter?

Your loaded hourly rate is what an hour of someone's time actually costs the business — salary plus payroll taxes, benefits, and overhead — not just their hourly wage. A $25/hour employee often has a loaded rate closer to $32-38/hour once you account for the full cost of employing them.

Using raw wage instead of loaded rate is the single most common mistake in DIY ROI math, and it always understates the case for automation. If you don't have an exact figure, a reasonable shortcut is wage × 1.25-1.4.

How do you estimate hours saved before you've automated anything?

You don't need a time-and-motion study. A quick, defensible method:

1. Time a representative sample. Clock how long the manual process takes for 10-20 real instances, including the messy ones, not just the easy ones.
2. Multiply by weekly frequency. How many times does this happen in a typical week?
3. Apply a conservative automation rate. Assume the workflow fully handles 70-85% of instances and a human still touches the remainder (exceptions, edge cases, anything low-confidence). Don't assume 100% automation on day one — good implementations keep a human in the loop for ambiguous cases.
4. Multiply it out. (Manual time per instance × frequency per week × automation rate) = hours saved per week.

This deliberately errs conservative. If the real number comes in higher once the workflow is live, that's a pleasant surprise instead of a broken promise.

What ROI should you actually expect?

Treat under-12-month payback and 100%+ first-year ROI as your screening bar (see the FAQ below for why). If your numbers come in well short of that, either the process isn't high-volume enough yet to justify the build cost, or it needs to be scoped more narrowly to the part that's actually repetitive.

Try it yourself: the NeuroLoop ROI calculator

Rather than doing this math by hand every time, plug your own numbers into the ROI calculator — enter hours saved per week and your loaded hourly rate, and it returns annual savings and payback period instantly. It's the fastest way to sanity-check a workflow before you commit budget to it.