How fast will an automation pay for itself?
Weigh what an automation costs to build and run against the time it saves and the revenue it protects. See the payback period, first-year return, and three-year ROI.
How the calculation works
- Monthly net benefit = hours saved × hourly cost + added revenue − running cost.
- Payback period = build cost ÷ monthly net benefit.
- Net return = monthly net benefit × months − build cost.
- Three-year ROI = (three years of benefit − build cost − three years of running cost) ÷ (build cost + three years of running cost).
What a good payback period looks like
Well-chosen small business automations often pay back within months, because they replace work that happens every day. If a project takes more than 18 to 24 months to pay back on conservative numbers, look for a simpler version, a different first project, or a way to reuse the work across more of the business.
Costs people forget
- Time to document the process and test the automation with real examples
- Training the team and updating how exceptions are handled
- Ongoing upkeep when a connected tool changes a field or an API
- Usage-based fees that grow with volume, including AI tokens
The automation ROI guide explains the method in more depth, with worked examples.
Frequently asked questions
How do you calculate automation ROI?
Add up the value of time saved and revenue gained over a period, subtract the build and running costs for the same period, and divide by those costs. This calculator uses three years, which suits most automations.
What is a payback period?
The time it takes for the monthly benefit of an automation to repay its upfront cost. A three-month payback means that after month three, the automation is pure return.
Should I include revenue gains or only time saved?
Include both if you can estimate them honestly. Many automations (lead follow-up, reminders, invoicing) are justified more by revenue protected than by hours saved. If unsure, run the numbers with revenue at zero first.