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.

Best for: Business owners, CFOs, operations managers Practical guide for business decision-makers

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

  • A step-by-step framework for calculating AI project ROI
  • How to quantify the cost of your current process
  • Realistic impact estimates for common AI use cases
  • Example calculations for three common scenarios

Why calculate AI ROI?

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:

  • Justifies the spend. To your board, your CFO, or yourself. An AI project is easy to approve when the payback is 8 months.
  • Right-sizes the scope. If the ROI does not work for the full project, maybe a smaller version targeting the highest-value workflow does.
  • Sets realistic expectations. Saving 200 hours per year is worth celebrating. Promising 2,000 hours and delivering 200 is a failure of expectation management, not technology.

The ROI framework

The framework has four steps. Each one takes 10 to 15 minutes with the right people in the room.

Step 1: Cost of the current process

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)

Step 2: AI impact estimate

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

Step 3: Total investment

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

Step 4: Calculate ROI and payback

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:

  • ROI of 100 to 300% over the first year
  • Payback period of 4 to 12 months
  • Year 2+ ROI improves significantly (no build cost, only ongoing costs)

Example calculations

Example 1: Invoice processing automation

A mid-size business processes 200 supplier invoices per month. One AP clerk spends 25 hours per week on data entry and matching.

  • Current annual cost: 25 hrs × $55/hr × 48 weeks = $66,000
  • Conservative AI impact: 55% time reduction = $36,300 savings/year
  • Year 1 investment: $35K build + $6K hosting/maintenance + $4K internal time = $45,000
  • Payback: 45,000 ÷ (36,300 − 6,000) × 12 = 17.8 months

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.

Example 2: Email triage for professional services

A firm receives 150+ emails per day across shared inboxes. Two admin staff spend a combined 4 hours per day sorting, forwarding, and responding.

  • Current annual cost: 20 hrs/week × $50/hr × 48 weeks = $48,000
  • Conservative AI impact: 45% time reduction = $21,600 savings/year
  • Year 1 investment: $22K build + $4K hosting/maintenance + $3K internal time = $29,000
  • Payback: 29,000 ÷ (21,600 − 4,000) × 12 = 19.8 months

Also marginal purely on time savings, but add the value of faster response times (won leads, happier clients) and it becomes compelling.

Example 3: Internal knowledge search (RAG)

An organisation with 50 staff who each spend 30 minutes per day searching for internal procedures and policies.

  • Current annual cost: 50 staff × 2.5 hrs/week × $70/hr × 48 weeks = $420,000
  • Conservative AI impact: 35% reduction in search time = $147,000 savings/year
  • Year 1 investment: $55K build + $8K hosting/maintenance + $6K internal time = $69,000
  • Payback: 69,000 ÷ (147,000 − 8,000) × 12 = 6 months

Strong ROI. This is why RAG projects are popular. The time savings multiply across every person who uses the system.

What if you have never measured the time?

Most businesses have not. That is fine. Run a simple time study before you build the case.

  • Ask five to ten people who do the task to note how long it takes them, every day, for one week.
  • Average it out, and note the busy days as well as the quiet ones.
  • Use that figure in Step 1, not a guess from a meeting.

It does not need to be perfect. It needs to be real enough that nobody can wave it away.

Costs people leave out

  • Change and training. Showing people the new way, updating procedures and handling the early complaints. Plan for it by name.
  • Data clean-up. If the data needs real work before the system can use it, that is a project inside the project.
  • Scope creep. "Can it also do this?" is the most expensive question in any build. Agree the scope and hold to it.
  • Security and compliance checks. Testing, data handling agreements and any audit your industry needs. Often missed in the first budget.

Common mistakes

  • Comparing the cost to zero. Doing nothing is not free. It is the ongoing cost of the manual work, the errors and the slow answers.
  • Ignoring adoption. A system nobody uses returns nothing. Allow for how many people will really use it, and how soon.
  • Using vendor numbers. Vendors cite best-case scenarios from their best clients. Use your own data and conservative estimates.
  • Ignoring ongoing costs. AI systems need hosting, monitoring, and maintenance. Budget 15 to 25% of the build cost annually.
  • Counting hours that will not be recovered. If AI saves someone 30 minutes per day but they just fill the time with other tasks, the saving is real only if you redeploy that capacity deliberately.
  • Forgetting internal time. Your team will spend time on requirements, testing, feedback, and training. Include it.
  • Only counting time savings. Quality improvements (fewer errors, better compliance, faster customer response) have real value. Include them even if they are harder to quantify.

Next steps

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."

Key takeaways

  • AI ROI is calculated like any other business investment: current cost vs projected savings vs project cost.
  • The biggest mistake is overestimating AI impact. Use 40 to 60% improvement, not the 90% vendors promise
  • Include all costs: build, deploy, maintain, train, and the staff time during implementation
  • Most well-scoped AI projects pay back in 6 to 12 months. If the payback is over 18 months, the scope might be wrong
  • Quality improvements and risk reduction have value too. Don't only count time savings.
AI ROIBusiness CaseAI StrategyCost Analysis

AI project return on investment: common questions

How do you calculate the return on investment for an AI project?

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.

How much time saving should I assume when building a business case for AI?

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.

What costs should be included in an AI project budget?

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.

How long should an AI project take to pay for itself?

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.

How do I measure staff time for an AI business case when nobody has tracked it?

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

Still have a question?

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 Kasun Wijayamanna
Founder, replies within one business day

Get Started

Want help choosing the right next step?

Tell us what you are comparing, replacing, or trying to improve. We will come back with a practical recommendation and realistic scope.

Australian owned and operated

Built here. Your data stays here.

  • No offshore development. Everything is written by our own team in Australia. Nothing is subcontracted overseas.
  • Your data stays onshore. Hosted in Australia, on infrastructure you own, under Australian law.
  • Every state, not just ours. Perth, Melbourne, Sydney, Brisbane, Adelaide and everywhere between.