A defensible business case
ROI is not just hours multiplied by salary.
A useful automation estimate separates capacity value from cash savings, includes the work that remains after launch, and compares custom development against the best realistic alternative.
Price the current process
Count every person, repetition, handoff and costly error. Use loaded hourly cost rather than salary alone.
Keep residual work visible
Automation rarely removes every exception. Model the manual work and error cost that will remain.
Compare the alternatives
The choice is not automation versus nothing. It is manual versus buy versus build over the same period.
Demand a margin of safety
A small theoretical advantage does not justify custom software risk. The upside should be meaningful.
The core calculation
How automation ROI is calculated
Current annual costLabour cost + error and rework cost
Automation total costUpfront cost + recurring software cost + residual labour and errors
ROI(Manual cost avoided − automation total cost) ÷ automation total cost
Payback periodUpfront cost ÷ monthly operating savings
Questions worth asking
Before approving an automation project
How do you calculate automation ROI?
Add the labour cost and error cost of the current process. Estimate the residual manual work, residual errors, setup cost and recurring cost after automation. Over the chosen period, ROI is the value saved minus the automation cost, divided by the automation cost.
What should be included in the cost of a manual process?
Include every person who touches the task, the frequency and duration, loaded hourly cost, error and rework rate, and the cost of each error. Waiting time, missed sales and customer delay can be important too, but they should be added only when you can defend the estimate.
When is buying software better than building it?
Buying is usually better when the process is common, a product covers the important requirements and the business can adapt without losing an advantage. It reduces upfront cost and implementation risk. Test products using real work before committing.
When does custom automation make financial sense?
Custom automation makes sense when standard products leave costly gaps, the workflow connects several systems, or the process is part of how the business competes. The expected advantage should comfortably exceed the extra upfront cost and risk.
Does saving employee time always create cash savings?
No. Recovered time creates financial value only when it is redeployed to useful work, increases throughput, avoids additional hiring or removes overtime. This calculator shows capacity value, which should not automatically be treated as a headcount reduction.