Automation ROI calculator
Estimate how many hours automating a task frees up and how long the investment takes to pay back. The values are pre-filled so you can see how it works: replace them with yours.
How many times per month it repeats. If you count per day, multiply by 22.
Real end-to-end time, including looking up the information.
Real cost, with social charges and indirect costs included.
Share of cases with no human intervention. The rest are exceptions.
Optional. If you don't know it, leave zero and look only at the saving.
Optional. Infrastructure and maintenance, if any.
How it's calculated
- Hours freed per month = tasks per month × minutes per task × share the system resolves, divided by 60.
- Annual saving = hours freed per year × real hourly cost, minus the monthly cost of running the system.
- Payback = initial investment divided by the net monthly saving.
What this calculator doesn't do
- It doesn't include errors avoided. That's usually the largest saving and also the hardest to estimate without your own data.
- It doesn't account for your team's time during implementation, which is a real cost and always gets forgotten.
- It doesn't distinguish between hours reassigned to higher-value work and extra capacity without hiring: those are different benefits.
- It doesn't replace a proper analysis. It tells you whether the conversation is worth having, not whether to approve a project.
Frequently asked questions
What automation percentage is realistic?
It depends on the process, but few workflows reach one hundred percent. Between 70 and 85 percent is common when rules are clear and data is accessible. If you don't know what to enter, leave 80.
How do I work out the real hourly cost?
It isn't salary divided by hours worked. Gross salary has to carry social charges and indirect costs on top, which typically add between forty and sixty percent.
Why does the result change so much with minutes per task?
Because the saving multiplies by frequency. A six-minute task happening two hundred times a month is twenty hours; the same task ten times a month is one hour. Frequency matters more than complexity.
Is this enough to approve a project?
It's enough to quickly rule out what doesn't add up and to prioritise between candidates. Deciding requires analysing the process: the number here is an estimate, not a quote.
Keep reading
Tell us which process you'd like to improve
We'll look at how it works today and send back a concrete diagnostic: what to automate, how, and what result to expect. No cost, no commitment.