Most automation projects fail not because the technology does not work, but because nobody calculated whether the investment made financial sense in the first place. A €10,000 automation that saves €3,000 per month pays for itself in less than four months. The same €10,000 automation saving €500 per month takes nearly two years — and by then, requirements have changed. The difference between these two scenarios is not luck; it is math done upfront.
This article gives you the formula, the variables, and a framework to calculate automation ROI before you commit a single euro.
The core formula
Automation ROI boils down to one equation:
Monthly savings = (hours saved × hourly cost) + (errors avoided × cost per error) + (opportunity value gained)
Payback period = total automation cost ÷ monthly savings
Annual ROI = ((monthly savings × 12) - total automation cost) ÷ total automation cost × 100%
The numbers are straightforward once you measure the inputs honestly. The hard part is measuring honestly.
Step 1: Measure the current process cost
Before automation, document the real cost of doing things manually:
Direct labour cost:
- How many people touch this process?
- How many hours per week/month does each person spend?
- What is their fully loaded hourly cost? (Salary + benefits + overhead, typically 1.3–1.5× gross salary in Croatia)
Error cost:
- How often do errors occur? (Once per week? Once per day?)
- What does each error cost to fix? (Rework hours, lost revenue, customer churn)
- What is the downstream impact? (A €5 data entry error that causes a €500 shipping mistake is a €505 error)
Opportunity cost:
- What could these people be doing instead? (Revenue-generating work, customer relationships, strategic thinking)
- What revenue is lost because the process is too slow? (Delayed invoicing = delayed cash flow)
Example: manual invoicing
| Variable | Value |
|---|---|
| Hours per month | 12 |
| Fully loaded hourly cost | €35 |
| Direct labour cost | €420/month |
| Errors per month | 3 |
| Cost per error (rework + late fees) | €80 |
| Error cost | €240/month |
| Opportunity cost (delayed collections) | €200/month |
| Total monthly process cost | €860/month |
Step 2: Estimate the automation cost
Automation cost is not just the build. Include everything:
| Cost component | Range | Notes |
|---|---|---|
| Discovery and scoping | €1,000–€3,000 | Defines the automation properly |
| Development | €2,000–€15,000 | The actual build |
| Integration with existing systems | €1,000–€5,000 | APIs, data mapping, testing |
| Training and change management | €500–€2,000 | Getting people to actually use it |
| Annual maintenance | 15–25% of build cost | Bug fixes, updates, small changes |
For our invoicing example, a realistic total: €6,000 build + €1,000 annual maintenance.
Step 3: Calculate payback and ROI
Using our invoicing example:
- Monthly savings: €860 (the cost we measured in step 1 — automation eliminates most of it, assume 85% savings = €730/month)
- Automation cost: €6,000
- Payback period: €6,000 ÷ €730 = 8.2 months
- Year 1 ROI: ((€730 × 12) - €6,000 - €1,000 maintenance) ÷ €7,000 = 25%
- Year 2 ROI: (€8,760 - €1,000) ÷ €7,000 = 111%
By year two, the automation has generated more than double its cost in savings. This is a strong investment.
When the math says “don’t automate”
Not every process should be automated. The math says stop when:
- Payback period exceeds 18 months. Technology changes, processes evolve, and requirements shift. If the automation will not pay for itself within 18 months, the risk of it becoming obsolete is too high.
- Monthly savings are under €300. The maintenance cost alone (€100–€200/month for most automations) eats the savings.
- The process changes frequently. Automating a process that gets redesigned every quarter means rebuilding the automation every quarter.
- Error rates are already low. If the manual process has a 99.5% accuracy rate, automation savings come only from time — which may not justify the cost.
The hidden variables most calculations miss
Three factors that distort ROI calculations when ignored:
1. Adoption rate. If only 60% of the team uses the automation, you capture only 60% of the savings. Budget for training and change management — a €500 investment in adoption can double the effective ROI.
2. Integration maintenance. APIs change, third-party tools update, and your own systems evolve. Budget 15–25% of the build cost per year for maintenance. An automation that “works but nobody maintains” breaks within 12–18 months.
3. Scale effects. A process that handles 100 items per month today may handle 500 in a year. Automation scales better than manual labour — the ROI improves over time. Include projected growth in your calculation.
A framework you can use today
For any process you are considering automating, fill in this table:
| Variable | Your numbers |
|---|---|
| Hours per month on this process | ___ |
| Fully loaded hourly cost (€) | ___ |
| Errors per month | ___ |
| Average cost per error (€) | ___ |
| Estimated opportunity cost per month (€) | ___ |
| Total monthly process cost (A) | ___ |
| Estimated automation build cost (€) | ___ |
| Annual maintenance (15–25% of build) (€) | ___ |
| Total first-year automation cost (B) | ___ |
| Payback period (B ÷ (A × 0.85)) | ___ months |
If the payback period is under 12 months, automate. If it is 12–18 months, proceed with caution. If it is over 18 months, find a different process to automate first.
Frequently asked questions
What if I cannot measure the current process cost accurately? Start with time. Ask the people doing the work: “How many hours per week do you spend on this?” Then multiply by their hourly cost. Even a rough estimate is better than guessing whether automation is worth it.
Should I include “soft” benefits like employee satisfaction? Not in the primary ROI calculation. Soft benefits are real but hard to quantify. Use them to break ties between two automation candidates with similar hard ROI.
How do I account for one-time vs recurring savings? Some automations (like data migration) produce a one-time saving. Others (like invoicing) produce recurring monthly savings. Only recurring savings compound into a strong ROI. One-time savings must justify the cost on their own.
Related articles
- Where automation actually pays back: 8 processes worth automating first — The specific processes with the best ROI.
- Signs your business needs process automation — How to recognise when manual processes are costing you.
- AI + automation stack for SMBs — What to build, what to buy, what to integrate.
Want to calculate ROI for your process?
Book a free 30-minute call. We will map your process, estimate the automation cost, and calculate the payback period together — before any commitment.
Reach out at [email protected] or via the form on our homepage.