A credible business case shows the current cost, the achievable change, the investment required, and how recovered capacity will actually be used. Time saved is not automatically cash saved.
Define value before calculating it
Automation can create capacity, reduce direct cost, shorten cycle time, improve consistency, or protect revenue. These are different forms of value and should not be combined carelessly.
Recovered hours matter only when the organisation can redeploy them: serving more clients, reducing backlog, improving quality, or avoiding planned hiring.
- Capacity value
- Cashable cost reduction
- Revenue protected or enabled
- Risk and quality improvement
Calculate the current operational baseline
Count the people involved, time spent per person, frequency, loaded hourly cost, rework, and waiting. Use a representative sample rather than relying on memory.
Include coordination work around the workflow. Chasing an approval or rebuilding a report is part of the cost even if it sits outside the official process.
Model an achievable change, not a perfect one
Assume exceptions, review, adoption time, and residual manual work. A range is more honest than a single precise forecast when evidence is limited.
Create conservative, expected, and strong cases. State exactly which percentage of work is removed or accelerated in each.
- What remains manual
- How often a human reviews output
- Expected adoption level
- Time to reach steady use
Include the full implementation investment
Count discovery, design, integration, testing, training, change support, licences, monitoring, and ongoing ownership. A low build quote is not the same as a low total cost.
For the first year, compare annual value with implementation and operating cost. For recurring value, show the ongoing run cost separately.
- Initial implementation
- Software and usage
- Internal team time
- Maintenance and control
Turn the estimate into a decision
Agree what evidence is needed to proceed, what would stop the project, and when the business case will be reviewed. The calculation should make uncertainty discussable—not disguise it.
Use the one7x estimator for a directional capacity view, then validate the workflow and baseline before committing investment.