AI ROI Calculator: Building the Business Case
AI ROI calculator guide with formulas, worked examples, and risk checks. Build a stronger business case before committing budget to AI projects.
AI ROI calculator guide with formulas, worked examples, and risk checks. Build a stronger business case before committing budget to AI projects.
Who this is for
Business leaders who need to justify AI investment to stakeholders, boards, or themselves, with real numbers rather than vendor promises.
Question this answers
How do I calculate whether an AI project is worth the investment, and what payback period should I expect?
What you will leave with
Every AI vendor will tell you their solution delivers "massive efficiency gains" and "transformative outcomes." But when it comes time to sign the proposal, you need actual numbers, not enthusiasm.
An ROI calculation does three things:
The framework has four steps. Each one takes 10 to 15 minutes with the right people in the room.
Before you can calculate savings, you need to know what the current process costs. This is almost always measured in staff hours.
| Input | How to measure |
|---|---|
| Hours per week on the task | Ask the team. Track for one week if unsure. |
| Number of staff involved | Count everyone who touches the process. |
| Fully loaded hourly cost | Salary + super + leave + overheads ÷ working hours. Typically $50 to $80/hr for admin, $80 to $150/hr for professionals. |
| Error/rework cost | How many errors per month? What does each one cost to fix? Include downstream impacts. |
Formula: Annual process cost = (hours/week × staff × hourly cost × 48 weeks) + (errors/month × error cost × 12)
How much of the current cost will AI eliminate? This is the hardest number to estimate, so use conservative benchmarks:
| AI use case | Conservative estimate | Optimistic estimate |
|---|---|---|
| Document processing (invoices, forms) | 50% time reduction | 75% |
| Email triage and routing | 40% time reduction | 65% |
| Knowledge search (RAG) | 30% time reduction per lookup | 60% |
| Approval workflow automation | 35% cycle time reduction | 55% |
| Report generation | 60% time reduction | 80% |
| Data entry automation | 55% time reduction | 75% |
Use the conservative estimate for your business case. If the ROI works with conservative numbers, it will definitely work in practice. If you need optimistic numbers to justify the project, the project is marginal.
Formula: Annual savings = Annual process cost × impact percentage
Include everything, not just the build cost:
| Cost item | Typical size |
|---|---|
| Discovery and scoping | Small next to the build |
| Development and deployment | The largest item (depending on complexity) |
| Annual hosting and infrastructure | Ongoing, every year |
| Annual maintenance and updates | Ongoing, every year (with hosting, 15 to 25% of the build cost) |
| Internal staff time during project | 40 to 80 hours (valued at their hourly cost) |
| Training and change management | Small next to the build |
Formula: Year 1 total cost = Build cost + hosting + maintenance + internal time + training
ROI: (Annual savings − Annual ongoing costs) ÷ Year 1 total cost × 100
Payback period: Year 1 total cost ÷ (Annual savings − Annual ongoing costs) × 12 months
A healthy AI project typically shows:
A mid-size business processes 200 supplier invoices per month. One AP clerk spends 25 hours per week on data entry and matching.
Marginal in year 1, but Year 2 ROI is strong, with only the ongoing costs set against $36K savings. Also factor in error reduction and faster payment cycle benefits.
A firm receives 150+ emails per day across shared inboxes. Two admin staff spend a combined 4 hours per day sorting, forwarding, and responding.
Also marginal purely on time savings, but add the value of faster response times (won leads, happier clients) and it becomes compelling.
An organisation with 50 staff who each spend 30 minutes per day searching for internal procedures and policies.
Strong ROI. This is why RAG projects are popular. The time savings multiply across every person who uses the system.
Most businesses have not. That is fine. Run a simple time study before you build the case.
It does not need to be perfect. It needs to be real enough that nobody can wave it away.
Pick your most promising AI use case and run through this framework. If the payback is under 12 months on conservative numbers, you have a strong business case. If it is over 18 months, consider whether a smaller scope or different use case would work better.
Need help with the numbers? Book a free consultation and we will work through the ROI calculation with you honestly, including the scenarios where the answer is "not yet."
Calculating return on investment (ROI) for an AI project takes four steps: cost the current process, estimate the AI impact, add up the total investment, then work out ROI and payback. The calculation works like any other business investment, comparing current cost, projected savings and project cost. ROI is annual savings minus annual ongoing costs, divided by the year 1 total cost, times 100.
An AI business case should use conservative impact estimates: around 40 to 60% improvement, not the 90% vendors promise. Conservative figures are a 50% time reduction for document processing, 40% for email triage and routing, 30% per lookup for knowledge search and 60% for report generation. If the return on investment works with conservative numbers, it will work in practice. If it needs optimistic numbers, the project is marginal.
An AI project budget should include everything, not just the build: discovery and scoping, development and deployment, annual hosting and infrastructure, annual maintenance and updates, internal staff time during the project, and training and change management. Costs people often leave out are data clean-up, scope creep, and security and compliance checks. For ongoing costs, budget 15 to 25% of the build cost each year.
A well-scoped AI project usually pays for itself in 6 to 12 months, and payback under 12 months on conservative numbers makes a strong business case. Payback is the year 1 total cost divided by annual savings minus annual ongoing costs, multiplied by 12 months. If payback is over 18 months, the scope might be wrong, so consider a smaller scope or a different use case.
Run a simple time study before building the AI business case. Ask five to ten people who do the task to note how long it takes them, every day, for one week. Average the figures and note the busy days as well as the quiet ones, then use that figure as the cost of the current process instead of a guess from a meeting. The figure does not need to be perfect, only real.
Ask the author
Ask it here and it comes straight to the founder. No sales call, no obligation, and a real answer even if the answer is that you do not need us.
Kasun Wijayamanna
Founder, replies within one business day
Tell us what you are comparing, replacing, or trying to improve. We will come back with a practical recommendation and realistic scope.
Built here. Your data stays here.
Thanks for reaching out. We will get back to you within one business day.
See what else we do