The Honest Math of Automation ROI
Automation business cases often count savings twice and costs once. An honest way to calculate the return.
By Owen Hartley, Partner, operations and technology , 1 min read
Automation business cases often count savings twice and costs once. An honest calculation protects the next project’s budget. Automation business cases often count savings twice and costs once. An honest way to calculate the return.
Count the full cost
Include licences, implementation, internal time, maintenance and the change effort for the people affected. Then count only savings that will actually be realised, such as overtime removed or hires avoided, not theoretical hours.
Measure after ninety days
Compare the business case with actual results after a quarter and share the comparison openly. Teams that do this get better at estimating, and leaders become more willing to fund the next idea.
How we apply this with clients
In client work this usually becomes one priority on the quarterly plan, with a named owner and a measure the leadership team reviews every month. Our technology & ai partners start with a short diagnostic of where the business is today, then agree the smallest change that will make a visible difference within ninety days.
Key takeaways
- Include internal time and change effort in costs.
- Count only savings that will be realised.
- Compare actual results with the case after ninety days.
Want to apply this in your business? Book a discovery call with a Maia Lafortezza partner.
Owen Hartley
Owen Hartley leads the firm's operations and technology practice. An industrial engineer by training, he spent twelve years running distribution and manufacturing operations before moving into advisory work. He redesigns workflows, operating rhythms and supply chains for logistics, manufacturing, healthcare and service businesses, and helps clients choose and implement technology, including practical AI, where it pays back. He is based in Milan.
More from Owen
Discussion