Decision guide · Quebec SMEs
How to calculate the ROI of automation.
Automation becomes defensible when its total cost is compared with a problem measured before the project. The calculation must include time, errors, delays, transition, maintenance and risk—not only software price.
The short answer.
First calculate the observable monthly cost of the current process. Then estimate the complete cost of change and a conservative monthly gain. The payback threshold is the initial cost divided by the net monthly gain. If baseline data is missing, measure or run a small test before promising a return.
Step 1
Measure the cost of the current process.
Choose a representative period and follow complete cases. Count active task time, rework, information searches, status requests and approvals. Add only costs you can explain.
- cases processed;
- active minutes per case;
- important wait time and delays;
- errors, duplicates and rework;
- direct tools or subcontracting costs;
- lost opportunities only when documented.
Released time is capacity, not automatically cash. It becomes a financial gain when the business reduces a cost, avoids a hire, supports useful volume or reallocates the time to measured productive work.
Step 2
Count more than construction.
Diagnosis, design, integrations, data, testing and production.
Cleanup, temporary double operation, training and team adaptation.
Licences, hosting, alerts, support, backups and maintenance.
Data export, documentation and the ability to resume the process manually.
Step 3
Connect each gain to an observable signal.
If the problem is speed, measure delay. For duplicate entry, measure manual steps and discrepancies. For visibility, measure cases with no status or the follow-ups required. Useful signals include active time removed, comparable errors, cases handled, delay to next action, exceptions recovered correctly and tool costs actually cancelled.
Step 4
Calculate a conservative scenario.
Net monthly gain = measurable gains − added recurring costs. Payback period = initial and transition costs ÷ net monthly gain. Build conservative, expected and adverse scenarios. The decision should remain acceptable if value arrives later or maintenance costs more.
Compliance, continuity or major risk reduction may justify a project with uncertain financial gain. State that rationale directly instead of presenting it as financial ROI.
Step 5
Add quality and control to the calculation.
Review permissions, data quality, exceptions, vendor dependency, outage recovery and ownership. A small complete-flow test often reduces more risk than a large theoretical projection.
Ready-to-use checklist
Does the decision hold up?
1. Current cost uses an observed period and cases.
2. Released time is not automatically counted as cash.
3. Build, transition, operation and exit are included.
4. Every gain has a measure and owner.
5. The conservative scenario remains acceptable.
6. Exceptions and manual recovery are planned.
7. Post-launch measurement is assigned.
Compare the calculation with the right process.
Measure one or two irritants, then apply the first-process selection guide. If the data or exceptions remain unclear, a short diagnostic can prevent premature pricing.