An automation business case should survive contact with real operations. Claims such as "save 80 percent of your time" are meaningless without a baseline, an adoption assumption and the cost of running the new process. A useful ROI calculation is deliberately conservative.
Establish the baseline
Measure how often the process occurs and the active time required per case. Include checking, corrections, handovers and reporting rather than only the obvious data-entry step. Multiply the monthly hours by the loaded cost of the people performing the work.
Then identify non-labour costs. These may include missed enquiries, late invoices, rework, external processing fees or penalties. Use recorded figures where possible and label estimates clearly.
Estimate the realistic benefit
Separate work removed from work shifted. If an automation drafts a response but a person still spends time checking it, count the net saving. Include expected exceptions, adoption and the period during which the old and new processes operate together.
Benefits may be capacity rather than payroll reduction. A team might handle more customers without adding headcount, respond faster or spend more time on work requiring expertise. Those are valid outcomes, but they should not be presented as cash savings unless they change actual expenditure.
Include the full cost
Add discovery, implementation, testing, staff training and internal project time. Recurring costs include workflow hosting, AI usage, integrations, monitoring and maintenance. Allow for changes when a connected service modifies its API or the business changes its process.
Use payback and sensitivity
Annual ROI can be expressed as annual net benefit divided by total first-year cost. Payback period is often easier for an SME: total initial investment divided by monthly net benefit.
Run at least three scenarios. The conservative case should assume lower adoption, more exceptions and higher support cost. If the project only works under the optimistic assumptions, the scope or price needs to change.
Measure after launch
Keep the same baseline measures after implementation. Workflow execution counts alone do not prove value. Track completion time, staff touch time, exceptions and the business outcome the project was intended to improve.
ROI is not a promise made in a proposal. It is a hypothesis that a production workflow must demonstrate. The most credible automation programmes stop or redesign projects that fail to produce the expected result.