Why calculate payback before you build
Process automation is often championed with "it will save loads of time". Leadership, however, needs numbers: what it costs, what it saves and when the investment pays back. An ROI estimate also helps decide where to start. The best candidates are processes that are frequent, rule-based and error-prone — not necessarily the ones people complain about most.
The basic formula
Automation ROI can be estimated with three simple calculations:
Annual benefit = hours saved per year × fully loaded hourly cost + savings from fewer errors
Annual running cost = licences + maintenance and support
Payback period = one-off build cost ÷ (annual benefit − annual running cost)
A payback period measured in months signals a strong candidate. If it runs into years, consider a simpler solution or a different process.
Estimating time saved
The most common mistake is guessing from behind a desk. Measure the process briefly instead:
- How often does it run per day, week or month?
- How long does one run take, including switching between systems, looking up information and checking results?
- How many people perform it?
- What share of the work will automation actually remove? Rarely 100% — exceptions and approvals usually stay with people.
Use a fully loaded hourly cost that includes payroll taxes and overheads, not just gross salary.
What most estimates miss
Errors. Re-keying data between systems creates mistakes. Correcting a wrong invoice, handling a complaint or losing a customer costs far more than the processing time itself. If you know how many errors occur each month and what they cost to fix, include them.
Speed. Approving a purchase order in an hour instead of three days has value that hourly savings do not capture: faster delivery, better cash flow, happier customers.
Maintenance. Automation is not a one-off. Systems change, new exceptions appear and someone needs to monitor that flows keep running. Budget for it.
Licensing. Many Power Automate scenarios are covered by Microsoft 365 licences, but premium connectors, database integrations and RPA require paid plans. Confirm this before you finalise the business case.
An illustrative example
The figures below are fictional and serve only to illustrate the calculation.
A company manually enters supplier invoices received by email into its accounting system. One accounts clerk processes 400 invoices a month at around six minutes each — 40 hours a month, or 480 hours a year. An automated flow with data extraction and approval removes an estimated 70% of that work, roughly 336 hours a year.
At a fully loaded cost of €25 per hour, the annual benefit is about €8,400. If licences and maintenance cost €2,000 a year and the one-off build costs €6,000, the investment pays back in roughly 11 months — before counting the savings from fewer errors.
Choosing your first process
A good first automation candidate:
- runs frequently (daily or weekly),
- follows clear rules with few exceptions,
- works with digital inputs such as email, forms or system data rather than paper,
- has a clear owner willing to help with testing.
Typical examples include purchase order and invoice approvals, employee onboarding, data transfers between systems and recurring reports.
Run the numbers yourself
For a quick estimate, try our ROI calculator. Enter how often a task runs, how long it takes and your hourly cost, and you will instantly see the yearly hours and cost saved — a solid basis for deciding whether a deeper analysis is worthwhile.
Bottom line
You do not need a complex model to estimate automation ROI. Measure the time, estimate the share automation removes, and remember licences, maintenance and errors. Start with a frequent, simple, measurable process; an early win makes the next steps much easier.
If you would like to validate the numbers on your own processes, explore our Power Automate process automation services — we start with an assessment and a benefit estimate.