Automation is sold as magic. The reality is arithmetic. Every automation has a cost to build, a cost to run, and a cost to maintain. The benefit is time saved, errors avoided, and capacity freed.
The baseline you need first
Before you can calculate ROI, you need a measured baseline of the manual process:
- How many times per day/week/month does the task run?
- How long does it take a human?
- What is the fully-loaded cost of that time?
- What is the error rate, and what does each error cost to fix?
The formula
(Manual cost per period × periods per year) − (Build cost amortised + Run cost per year + Maintenance cost per year) = Annual net benefit.
If the number is positive and the payback period fits your horizon, the automation makes sense. If not, the answer is not "build it anyway" — it is "redesign the workflow" or "do not automate".
Hidden costs that kill ROI
- Edge cases that require human review (adds time back).
- API changes that break the automation (maintenance).
- Monitoring and alerting infrastructure.
- Onboarding new team members into the automated flow.
We include all of these in the specification. The ROI thesis is on the first slide of the proposal, not hidden at the end.