How to calculate, present, and defend the ROI of an AI engagement. Includes the methodology, industry benchmarks, implementation cost ranges, and an interactive calculator you can use live in client meetings.
Five steps. Conservative assumptions. The numbers must be defensible in a board presentation.
For each automation opportunity, record how many staff are involved and how many hours per week they spend on that specific process. Be conservative — underestimating is better than overselling. Use interview data and direct observation where possible.
AI does not eliminate the process — it accelerates and assists it. A realistic efficiency factor is 40–70% for most document-heavy or approval-based processes. Use 30% for complex analytical tasks, up to 80% for pure data entry or routine routing. Never use 100%.
Use the fully-loaded cost of the staff doing the work — salary plus on-costs such as leave, benefits, and workspace. Use the client's own numbers where available; if you must estimate, state the assumption clearly rather than hiding it.
Weekly saving × 52 = annual saving in hours. Multiply by hourly rate = annual dollar saving. Divide implementation cost by annual saving = payback period in years. Calculate the payback period explicitly rather than asserting one in advance.
The most compelling ROI argument is not cost saved — it is what the freed capacity enables. If the finance team saves 8 hours/week, frame it as: 'Your finance team can close faster, improve forecasting, or take on the ERP project you've been deferring.' Quantify the opportunity cost of not having done this.
Model a single automation opportunity. Use this live in the client meeting — adjust the inputs together and watch the numbers update. It turns an abstract conversation into a shared exercise.
Presentation framing: “Based on the numbers you confirmed — 3 people spending 6 hours each per week on this process — a conservative 50% improvement would recover $39,780 per year. The implementation pays for itself in 3.6months.”
Use these as illustrative starting assumptions for your ROI model. Validate them with client interview data before presenting a case.
| Process | Typical volume | Est. annual hours | Annual ROI range (AUD) | Confidence |
|---|---|---|---|---|
| Invoice processing (receipt to payment) | 50 invoices/week | 1300 hrs | $35k–$70k | High |
| Meeting summaries and action tracking | 40 meetings/week across org | 520 hrs | $15k–$30k | High |
| Staff onboarding (IT provisioning and comms) | 2 hires/month | 96 hrs | $5k–$12k | Medium |
| Weekly reporting (manual data pulls) | 5 reports/week | 520 hrs | $15k–$35k | High |
| Contract review routing and approval tracking | 20 contracts/month | 360 hrs | $15k–$40k | Medium |
| IT helpdesk ticket triage and routing | 100 tickets/week | 1040 hrs | $25k–$55k | High |
| Email triage and prioritisation | Per knowledge worker/week | 52 hrs | $3k–$6k per person | High |
| Document search and retrieval | Per knowledge worker/week | 26 hrs | $1.5k–$3k per person | Medium |
ROI ranges assume a 50% efficiency factor and a $75/hr fully-loaded cost unless otherwise noted. Adjust for role seniority and actual process volume. High confidence = frequently observed across multiple engagements. Medium = observed but varies significantly by org maturity.
Illustrative ranges for scoping conversations. Adjust for local market rates, client size, and engagement complexity. These are not catalogue prices — use them to sanity-check your scope.
The numbers are only half of it. A good readout makes the assumptions visible, ties the model back to client evidence, and leaves room for challenge.
Most executives respond better to 'your team gets 400 hours back per year' than '$28,000 saved'. Start with capacity, then convert. Capacity = possibility. Cost = accountant language.
Reference something they said in the interview. 'You mentioned that invoice approval takes three days and always involves three back-and-forth emails. We can get that to same-day.' Specificity is persuasive. Generic savings are not.
Never present only the high number. Show a conservative case (30% efficiency gain) and a realistic case (55% efficiency gain). Let the client choose which to use in their business case. This builds trust and avoids overselling.
ROI without payback period is incomplete. Most SMB decision-makers think in 12-month cycles. If payback is under 12 months, lead with it. If payback is 18+ months, frame it as investment, not saving.
For governance and security work, ROI is not savings — it is incident cost avoidance. A data breach for an SMB costs $39,000+ in direct costs (Australian Cyber Security Centre data) plus reputational damage. A $12,000 governance engagement that prevents one incident has a 3:1 ROI.
Email the IT manager or operations lead the day before: 'I want to make sure I have the right numbers for tomorrow's presentation — is it roughly correct that your team processes X invoices per week and it takes about Y minutes each?' Getting confirmation means the numbers are theirs, not yours.
Discovery scripts to get the data. The assessment guide to run the engagement. The ROI model to explain the business case. Together they form a complete assessment workflow.