Book a free audit

How to calculate automation ROI before you build

A plain method for estimating payback, with a worked example you can copy.

StrategyBy the Kairoscend team6 min read
Key takeaways
  • Time the manual work for two weeks. Estimates from memory are unreliable.
  • Use the fully loaded hourly cost, not the salary figure.
  • Include running costs: subscriptions, monitoring and maintenance.
  • Payback period is the number most owners actually decide on.

“It will save time” is not a business case. Before you spend money on automation you should be able to say roughly how much time, what that time is worth, what the build and running costs are, and how many months it takes to earn the money back. None of this needs a finance team. It needs a stopwatch and four numbers.

Step 1: measure the work as it is today

For two weeks, have the people who do the task record each time they do it and how long it took. Two things matter: how often it happens, and the minutes per occurrence. Measure, don’t estimate. People routinely misjudge repetitive work, in both directions.

Note the error rate too. If one invoice in twenty needs correcting, the time spent fixing it belongs in the total.

Step 2: cost the hours honestly

Use a fully loaded hourly cost: salary plus employer taxes, benefits and overhead, divided by the hours actually worked. It is noticeably higher than the salary alone, and it is the true cost of an hour.

Step 3: estimate what automation removes

Automation rarely removes a task entirely. Exceptions still need a person. A sensible planning assumption is that a well-built workflow handles the routine majority and leaves the unusual cases for review. Be conservative, and write the assumption down so that it can be checked after launch.

Step 4: count all the costs

  • Build: the one-off cost to design, build and test.
  • Subscriptions: the automation platform and any new tools.
  • Upkeep: monitoring and fixes when a connected app changes.
  • Your team’s time: the hours spent in discovery and testing.

A worked example

The figures below are illustrative. Substitute your own.

ItemFigure
Task frequency40 times a week
Time per occurrence12 minutes
Manual time8 hours a week
Share automated (assumption)80%
Hours saved6.4 a week, about 28 a month
Loaded hourly cost$35
Gross monthly savingabout $970
Running costs$150 a month
Net monthly savingabout $820
One-off build cost$4,000
Payback periodabout 5 months

The formula is simple: payback in months = build cost ÷ net monthly saving. First-year return is twelve months of net saving minus the build cost, divided by the build cost.

The benefits that don’t fit in the table

Some returns are real but harder to price: fewer errors reaching customers, faster responses to enquiries, work that no longer stops when one person is on leave, and the ability to take on more volume without hiring. List them next to the calculation. Don’t invent numbers for them. If the hours-saved case works by itself, these are a bonus. If it only works with generous assumptions about soft benefits, be cautious.

Use it to rank, not just to justify

The most useful output is a comparison. Run the same calculation for each candidate process and sort by payback period. The order is often surprising, and it gives you a defensible answer to the question of what to build first. Our guide on choosing your first process to automate walks through that ranking.

Written by the Kairoscend teamWe build CRM, sales and healthcare automation. Questions about this article? info@kairoscend.com

Keep reading

More from our resources

Next step

Put this into practice

Book a free call and we’ll look at one process together: where to start, what it involves and the likely return.