AI ROI Calculation: Costs, Cash Flow and Worked Examples

Calculate AI ROI by subtracting project costs from attributable financial benefits, then dividing the difference by those costs over a stated period. Include implementation and operating costs. Use net present value to account for when cash moves, and show how the result changes with adoption, performance and cost assumptions.

Every numerical example in this guide is hypothetical. The inputs were invented to explain the calculations. They do not describe client engagements, supplier quotes, industry averages or expected results for your organization.

Define what the investment must change

Start with a specific workflow and a measurable baseline: documents processed, handling time, errors, contribution per sale or losses. Describe the alternative against which the AI project will be evaluated. That might be the current process, an upgrade to existing software or a simpler automation.

Record the period and conditions behind each estimate. A trial on straightforward documents may not represent a queue containing exceptions, missing information and poor scans. Measure human checking, corrections and escalation alongside processing speed.

Keep three results visible:

An unchanged salary bill does not fall because a task takes fewer minutes. Released capacity can still support more work or better service. Identify that use and avoid counting the same hours again as cash savings.

Build a cost estimate from the work required

For investment appraisal, identify future cash flows caused by the decision. Keep money already spent separate from the decision to continue. ACCA’s investment-appraisal guidance explains this distinction and the need for consistent treatment of tax and inflation.

Use supplier quotes, measured usage and estimates from the people doing the work. A fixed percentage of implementation spending is a weak substitute for estimating operating costs.

Show internal effort even when it does not create additional payroll expense. If employees are diverted from other work, record what is delayed or forgone. Where that displacement has a measurable incremental financial effect, include it once. Keep a separate resource view for effort that cannot yet be valued reliably.

Attach a reason to each contingency allowance: uncertain data cleanup, an untested interface or a contract dependency. A budget reserve becomes an actual cost only when spent; state how much of it the forecast assumes will be used.

Hypothetical example: document intake

Consider a fictional document-intake project. The example assumes the new process maintains the required quality level and reduces total human handling from eight to five minutes per document, including review and corrections.

Invented inputs

The 40%, 60% and 80% figures describe the share of the year’s eligible documents actually processed through the new workflow. They already account for uptake during each year. The separate 50% assumption describes how much released time reduces paid expenditure.

The €90,000 initial outlay is an invented budget: €50,000 for implementation and integration, €10,000 for data preparation, €15,000 for training and backfill, €10,000 for assurance and setup, and a €5,000 reserve assumed fully spent. The €30,000 annual operating amount is also invented. Human review already included in the five-minute handling time is not charged again as an additional review cost.

This simplified model is before tax. It assumes no price changes, financing cash flows, working-capital changes, residual value or displaced-work cost. Annual cash flows occur at each year end. A real appraisal needs the relevant adjustments and a consistent discount rate agreed with finance.

Calculate released capacity and cash benefits

At full use, the time reduction would release:

120,000 documents × (8 − 5) minutes ÷ 60 = 6,000 hours per year

Apply the workflow-use and cash-realization assumptions:

Annual cash benefit = Eligible volume × Minutes saved ÷ 60
                      × Workflow-use share × Cash-realization share
                      × Avoidable paid cost per hour

The remaining released hours are capacity benefits. They are excluded from this cash calculation. Any additional financial value from using that capacity would require a separate estimate with overlap removed.

Calculate ROI, NPV, payback and IRR

The four measures below use the same fictional project and cash flows. Keep the period and cost definition consistent across them.

Return on investment

Here, ROI means cumulative net financial benefit divided by all included project costs over three years:

ROI = (Total benefits − Total costs) ÷ Total costs × 100%

The example has €270,000 of cash benefits and €180,000 of costs: €90,000 initially plus €90,000 of operating costs. Its three-year ROI is:

(€270,000 − €180,000) ÷ €180,000 × 100% = 50%

This is a cumulative three-year return on the defined costs. It is not an annual rate. It also does not account for the timing of payments and receipts.

Net present value

NPV discounts cash flows to a common point in time. A positive result means projected inflows exceed outflows in present-value terms at the chosen discount rate. See OpenStax’s explanation of the NPV method.

NPV = −Initial outlay + Σ [Net cash flow in year t ÷ (1 + r)^t]

For the hypothetical example, r = 10%:

Present values are rounded for display; the total is calculated before rounding. The hypothetical NPV is approximately €54,478. The 10% rate is an illustration, not a recommended rate for AI projects. Match the rate to the project’s currency, risk and treatment of tax and inflation.

Payback period

Payback is the point at which cumulative net cash flow recovers the initial outlay. This measure helps show how long cash remains committed, but simple payback ignores discounting and cash flows after recovery.

Under the stated year-end timing, simple payback occurs at the end of Year 2, or 24 months. Discounted payback occurs later: the cumulative discounted balance becomes positive at the end of Year 3. Use dated monthly cash flows when payment timing matters; annual totals alone do not establish a precise within-year payback date.

Internal rate of return

IRR is the discount rate at which NPV equals zero. For the example’s cash flows of −€90,000, €30,000, €60,000 and €90,000, the annual IRR is approximately 36.2%.

Use IRR alongside NPV. Percentage returns can obscure differences in project size, and cash flows with repeated sign changes can produce multiple IRRs. OpenStax discusses these limits in its IRR method chapter.

Test what would make the project unattractive

Hypothetical scenarios

These scenarios change uptake and costs. Document volume, the three-minute time reduction, the 50% cash-realization share and the €50 avoidable hourly cost remain the same. The scenarios are chosen illustrations with no assigned probabilities.

The downside does not recover its costs within the modeled period. This is useful information for a decision about scope and spending. It identifies assumptions that need stronger evidence before committing the full budget.

Isolate one uncertain assumption

Keep the base case unchanged and vary only the share of released hours that removes paid expenditure:

The NPV reaches zero at approximately 37.6% cash realization under these particular assumptions. A finance owner could therefore test whether that level of avoidable expenditure is plausible and contractually achievable. Additional capacity may have value even where the cash case is negative; document the alternative use before assigning a monetary benefit.

Test processing time, rollout delays and operating costs in the same way. Apply each adjustment once. For example, reducing the share of documents processed through AI and then applying another discount for the same low uptake would count that effect twice.

Model other benefits with their own evidence

The following mini-examples are also hypothetical. They are independent of the document-intake model and should not be added to its totals.

Quality improvement

Avoided error cost = Affected volume × (Old error rate − New error rate)
                     × Avoidable cost per error

Suppose 20,000 cases incur an external reprocessing charge of €25 whenever an error occurs. A reduction from 4% errors to 2% would avoid 400 errors and €10,000 of charges over that period. This excludes project costs. If error correction only consumes existing staff time, first report the hours released and establish how they will be used.

Revenue contribution

Incremental contribution = Incremental completed sales
                           × Contribution per sale

With 40,000 eligible visits, a conversion increase from 3% to 3.4% would produce 160 additional orders. At an assumed €25 contribution per order, that is €4,000 before AI project costs. State which variable costs and returns the contribution figure includes. Convert it into dated cash flows for NPV.

In a real project, use a credible comparison group or other evidence to distinguish the AI effect from promotions, pricing changes and shifts in traffic. State whether an uplift is measured, forecast or supplied by a vendor.

Expected loss reduction

Expected loss = Event probability × Loss if the event occurs
Expected benefit = Expected loss before − Expected loss after

Assume at most one event per year, an unchanged €100,000 loss if it occurs, and an annual probability reduced from 10% to 6%. Expected annual loss falls from €10,000 to €6,000, producing an expected benefit of €4,000 before project costs. It is a probabilistic estimate, not a guaranteed annual saving. A model covering repeated incidents needs event frequency and severity instead of this single-event simplification.

Keep the business case usable after approval

Before funding, record each material input with its evidence, owner, date and plausible range. Distinguish measured pilot results from supplier estimates and assumptions that still need testing. Set limits for acceptable quality and service performance alongside financial targets.

During rollout, compare actual volume, usage, handling time, error rates and expenditure with the forecast. Explain deviations before revising the model. More users, faster completion and lower invoices measure different things.

Present the investment decision in a short summary: the alternatives, amount requested, expected cash flows, NPV, downside exposure and next decision point. Report learning, service quality and reusable capabilities separately where their financial value has not been established. A positive forecast does not establish operational readiness or acceptable risk.

For related planning topics, see AI readiness assessment, AI change management and AI governance.

Frequently Asked Questions

What is the formula for AI ROI?

For the cash-based definition used here, subtract total project costs from attributable cash benefits over a stated period, divide by total costs and multiply by 100%. Include both initial and operating costs. Show NPV separately because cumulative ROI does not reflect cash-flow timing.

What is a good ROI for an AI project?

A useful target depends on the alternatives, project risk, capital constraints and evaluation period. This guide supplies no verified industry-wide benchmark. Its hypothetical 50% result illustrates a calculation; it is not a performance target or a prediction.

How long should an AI project take to pay back?

Calculate payback from the project’s cash flows and compare it with the organization’s funding requirements and the expected useful life of the investment. The fictional example recovers its outlay in 24 months under its stated assumptions. It does not establish a normal payback period for AI projects.

How should time savings enter the model?

Start with hours released after review, corrections and exceptions. Identify which hours remove paid expenditure or support measurable additional output. Keep capacity without an established financial use visible outside the cash-benefit total.

Which discount rate should I use?

Ask finance for a rate suitable for the project and its cash-flow basis. A company-wide cost of capital may need adjustment where project risk differs. Do not mix a rate after tax with cash flows before tax without an appropriate reconciliation. The 10% used here is an invented teaching input.

Should the model include internal employee time?

Yes, in the resource plan. Include incremental payroll, backfill and measurable financial effects of displaced work in the appraisal where relevant. Allocating existing salary to a project does not itself create a new cash payment. Avoid adding both the allocation and the same underlying cost.

Should I evaluate each use case or the whole program?

Use individual cases to test specific benefits and a program view to capture shared costs and dependencies. Allocate shared spending consistently so it is counted once. A use case that depends on new infrastructure should not appear profitable merely because its share of that infrastructure has been omitted.

Start with the baseline

Choose one workflow, document its current performance and costs, and identify the assumptions a pilot must test. Build the cash-flow model around that evidence and revise it as observed results arrive.

Discuss an AI business case.