How to calculate the return on automation
Before you automate, it is worth doing a simple calculation: how much the manual process costs today and how much it would cost automated. The method, step by step.
April 8, 2026 · Possition team · 6 min read
The return on automation is not an act of faith: it is a calculation. Doing it before you start ranks priorities and avoids automating what does not justify the investment.
Step 1: how much the manual process costs
- Hours per week spent on the task × hourly cost of the people who do it.
- Cost of errors: rework, penalties for missed due dates, poorly served customers.
- Opportunity cost: what that time could produce if applied to something else.
Step 2: how much the automation costs
- Implementation: diagnostic, development, integration, and go-live.
- Operations: infrastructure, licenses, and monthly maintenance.
- The team's time during implementation (testing, validations, training).
Step 3: compare over time
With both numbers, the calculation is direct: in how many months the monthly savings pay for the implementation. High-volume administrative workflows usually recover the investment quickly; low-volume processes, by contrast, may not justify it, and knowing that in advance is also a good result of the analysis.
What the calculation does not capture
There are real benefits that are hard to monetize: traceability, information in time to decide, a team less frustrated by mechanical tasks. Do not invent them in the spreadsheet, but do not ignore them in the decision either.