What is the AI ROI formula?
First-year AI ROI equals (year-one gross benefit − year-one total AI spend) ÷ year-one total AI spend × 100. AI Saves uses steady monthly capacity math, charging rollout setup once upfront and software or support fees every month.
Gross monthly benefit = net hours saved × loaded hourly rate × utilization rate. First-year net value = 12 × (gross monthly benefit − monthly AI cost) − setup cost, divided by total year-one spend (12 × monthly AI cost + setup cost).
That formula prices freed staff hours at employer payroll cost. Only claim direct cash savings where actual cash spend falls—such as cut overtime or canceled vendor invoices—and keep revenue upside or churn reduction in separate attribution models without double-counting.
Which inputs do you need for an AI ROI calculation?
You only need five operational building blocks to model any workflow credibly: team payroll burden, paid vs. task hours, net time savings after review, capacity utilization, and complete AI setup and run costs—all in a single currency.
| Input | Use | Evidence to collect |
|---|---|---|
| Team and loaded salary | Price total paid working hours accurately | Payroll ledger or documented finance estimate |
| Paid hours and task hours | Keep total paid time separate from target task hours | Schedules and workflow time logs |
| Net time saving | Bake QA verification and rework into the saving rate | Side-by-side pilot timings |
| Value realization | Filter out idle fragments of saved time | Hiring freeze, backlog plan, or overtime budget |
| AI running and setup costs | Capture the complete investment denominator | Vendor quotes and internal engineering time |
What is a complete worked AI ROI example?
Suppose a five-person team earns $5,000 a month per person before a 1.2 employer burden multiplier, working 40 paid hours across four weeks monthly. Under these assumptions, year-one ROI reaches 80%.
Loaded team payroll totals 5 × $5,000 × 1.2 = $30,000 a month over 5 × 40 × 4 = 800 paid hours, which sets the loaded hourly rate at $37.50. Each staff member spends 20 hours weekly on the target workflow, giving 5 × 20 × 4 = 400 in-scope hours per month.
Cutting 25% net time after QA frees 100 hours a month. Assuming 60% of freed hours go into productive backlog work, monthly capacity value is 100 × $37.50 × 60% = $2,250. Subtracting $750 in monthly AI spend leaves $1,500 net per month; against $6,000 upfront setup, first-year net value is $12,000 on $15,000 total investment: $12,000 / $15,000 × 100 = 80%.
How do you calculate AI payback time?
Divide one-off rollout spend by positive net monthly value to get simple payback in months—in our worked example above, $6,000 / $1,500 yields four months. Whenever monthly net value drops to zero or negative, the project never pays back under those inputs.
Remember that this ratio assumes steady gains starting from month one. Whenever user adoption ramps up gradually over quarters, sum month-by-month net balances until cumulative benefit crosses zero—and clearly flag whether payback reflects freed staff capacity or real cash returned to the bank.
What should you check before presenting the result?
Audit the investment denominator, pilot timing boundaries, and capacity reallocation plan before walking into a CFO review—clean arithmetic cannot rescue inflated starting assumptions.
- Derive hourly pay rates from full paid hours, never from target task hours alone.
- Deduct manual verification and fixes inside your net time-saving rate.
- Charge upfront rollout once and software or upkeep fees every active month.
- Put a conservative downside scenario right beside measured pilot inputs.
- Report ROI percentage as undefined whenever total investment spend equals zero.
Frequently asked questions
What is a good AI ROI percentage?
Hurdle rates vary with capital cost, risk appetite, competing priorities, and whether savings come from hard cash cuts or staff capacity—there is no single universal pass mark.
Why can ROI be negative?
Year-one ROI turns negative whenever usable time savings within the year fail to recover upfront rollout engineering and twelve months of software and QA costs.