AI ROI for SaaS is measurable per workflow, not company-wide: set a baseline on one metric, subtract review time and the full AI cost, and price it at today's list. The question is not AI against its promises. It is today against two years ago.
The market may be correcting, and someone has probably told you that proves the whole thing is hype. It does not follow. Independent bodies have reported real time savings, and they have also documented why those savings so often fail to reach the P&L. Both findings hold at once, and the gap between them is something you can measure inside your own company. It is one measurement inside our guide to SaaS metrics that matter in the AI era.
Quick Answer: Measure One Workflow at a Time, Net of Review Time, at Today's Prices
- Baseline. Record a metric the workflow already had before AI touched it: cost per ticket, time-to-activation, hours per published piece.
- Ledger. Gross gain, minus review and fix time, minus the full AI cost. Report net dollars and the metric that moved, not a ratio that hides its inputs.
- Re-test. When the binding cost line changes, re-run the arithmetic. A pilot is a reading at one price on one date, not a verdict.
There is no blended “good AI ROI” number worth quoting, because any single figure averages workflows with different baselines, review loads and cost lines. You have probably seen the two most-quoted numbers anyway, and they sit very far apart.
Why Do the Two Most-Quoted AI ROI Numbers Disagree?
The 20 to 50% saved and the 95% with zero return disagree because they measure different layers. Three independent bodies each reported one, and the readings do not contradict each other.
| Layer | Who measured it | Date | The reading |
|---|---|---|---|
| One task | Bank for International Settlements, Annual Economic Report | 28 June 2026 | Task-level studies: “often to the tune of between 20 and 50% in time savings” |
| One organisation's P&L | MIT NANDA, “The GenAI Divide”: 300+ public initiatives, interviews at 52 organisations, 153 senior leaders surveyed | July 2025, window January to June 2025 | 95% of organisations getting zero return |
| The whole economy | BIS; US Federal Reserve staff note | 28 June 2026; 17 July 2026 | Under 1% over a long horizon; micro gains “not adding up in aggregate” |
Read row one against row two: time saved at the task, no return at the organisation. Value is leaking somewhere between the task and the ledger, which is a different claim from “AI does not work”.
NANDA names the self-inflicted half. About 50% of GenAI budgets go to sales and marketing, while “back-office automation often yields better ROI. This bias reflects easier metric attribution, not actual value.” Its measurable savings showed up in support, software engineering, administration and back-office work.
Neither number proves hype or success, and neither measured your workflow. That is the whole case for keeping your own ledger.
Is the AI Market Correcting, and Does That Change Your Math?
A market correction changes vendor prices and vendor survival. It does not change whether a workflow of yours saved hours last quarter. A narrative is not your P&L, and this article takes no position on asset prices.
Matching GPT-4 on PhD-level science questions got about 40x cheaper per year. Epoch notes the fastest falls came in the final year of its window and may not hold.
Anthropic's published price list, read on 2026-11-06, shows output tokens at $50 per million for its most expensive model, $10 for the mid-tier and $0.50 for the cheapest. The full argument is in why inference prices fell unevenly. Capability is moving too: per the Federal Reserve note, METR's agent task-completion horizon has been doubling roughly every several months as of mid-2026.
The counterweight is that clear winners are few. NANDA found only 2 of 8 major sectors showing meaningful structural change, and the Federal Reserve note says usage stays shallow even where adoption is broad. It calls the evidence consistent with “a buildout phase”, and notes that measured gains from general-purpose technologies historically “lag investment by years”.
So compare today with two years ago, workflow by workflow. Whether the SaaS category survives is a different question; see category survival in the AI era. This article stays on one team's cost side.
Which Workflows Already Have a Number to Beat?
The ones that were measured before AI arrived. One commenter in an r/SaaS thread (28 February 2026) said AI shows measurable ROI “usually the moment it touches a workflow that already had a number on it.” That is one small thread: anecdote, not data. The ranking below is that reading plus our judgment, not a measurement.
| Workflow | Baseline it usually has | Before and after |
|---|---|---|
| Support deflection | Cost per ticket, first-response time | Cleanest |
| Onboarding | Time-to-activation | Clean if cohort mix is stable |
| Content and SEO ops | Hours per piece | Moderate; quality is hard |
| Sales workflow | Meetings booked, stage conversion | Hardest to attribute |
NANDA says sales and marketing take about half the spend because attribution is easy there. Your clean return may sit one function over, in support or onboarding. If a workflow has no prior number, set a baseline for one to two weeks before judging. Otherwise you have a vibe, not a return.
The Ledger: Gross Gain, Minus Review Time, Minus the Full AI Cost
Strike “AI” and the method works for any tool. Three facts make the AI version different. Cost is variable per use. Output is probabilistic, so someone reviews it. And the unit price moves, by 9x to 900x per year at fixed quality in Epoch's data. The ledger keeps all three on the page.
- Gross gain: baseline cost avoided, in dollars. Count time only if it was redeployed or avoided as cost.
- Review and fix time: hours spent checking, correcting or redoing output, at their hourly cost. A column, not a footnote.
- AI cost at today's price: model usage plus platform seat, integration and eval-harness time. Per-token pricing means the vendor bills by tokens consumed, so cost scales with use. An eval harness is a fixed set of test cases you re-run to score output against your quality bar.
The Federal Reserve note draws a similar split: a fixed cost of adjustment, which is your seat, integration and eval time, and the marginal cost of inference, your token bill, which it calls “more readily observable”.
Worked example A: support deflection. Our arithmetic on invented inputs, not a measurement.
| Line | How it is built | Amount per month |
|---|---|---|
| Gross gain | 1,200 tickets, 25% deflected is 300, at $6.00 each | $1,800 |
| Review and fix time | 15% of 300 is 45 tickets at 8 minutes, 6 hours, at $40 an hour | $240 |
| AI cost | 3.6M output tokens at $10 per million is $36, plus a $120 platform fee | $156 |
| Net | 1,800 minus 240 minus 156 | $1,404 |
The model costs $36; review labour costs $240. Halving the model price barely registers. Halving the rework does.
What Do You Do With a Pilot That Failed Last Year?
A failed pilot is a reading at an old price. Re-run its cost line at today's list, at the same quality bar. Epoch measures price at a fixed quality level, so a cheaper model must clear the same eval, not just be cheaper.
The limit, stated up front: the rule only pays where the AI cost line is the binding line, meaning token-heavy, agent-loop or long-context work. Example A shows where it does not.
Worked example B: a token-heavy research workflow. Our arithmetic on invented inputs, not a measurement. 400 runs a month at 150,000 output tokens each is 60M tokens. Each run is worth $5, so $2,000 gross a month.
| Tier, output price read 2026-11-06 | Cost for 60M tokens | Net before review and platform | Verdict |
|---|---|---|---|
| Most expensive, $50 per million | $3,000 | -$1,000 | Stop at this price |
| Mid-tier, $10 per million | $600 | +$1,400 | Re-test passes |
| Cheapest, $0.50 per million | $30 | +$1,970 | Passes, if quality holds |
| Verdict | Trigger | What you do |
|---|---|---|
| Keep | Net is positive and stays positive at today's price | Re-check when the price list or the workflow changes |
| Re-test | Net is negative, cost is the binding line, a cheaper tier is plausible | Set a calendar date; run the cheaper tier through the same eval harness |
| Stop | The binding line is review time or output quality | Stop or redesign; price cuts do not fix this |
A 30-Day Measurement Plan You Can Run and Show Your Boss
Week 1: baseline
Pick one workflow and record its existing metric.
Week 2: run and log
Run the workflow and log review and fix time on every output.
Week 3: fill the ledger
Gross gain, review time, full AI cost at today's list. Compute net dollars.
Week 4: decide
Keep, re-test or stop, using the grid. If re-test, write the date and the price line that triggers it.
Report net dollars, the metric that moved, and the next re-test date. For the approval conversation, see getting a budget approved for an AI growth initiative, and for the dashboard, board reporting for SaaS metrics.
Do not stop because the market wobbles, and do not scale because a vendor says so. The saving is real and measured at the task level. You are probably looking for it in the wrong function and pricing it with a stale number.
FAQ: AI ROI for SaaS
What is a good ROI for SaaS?
There is no universal AI figure. Credible readings run from 20 to 50% time saved per task (BIS) to zero return at the P&L for most organisations (MIT NANDA, preliminary), because returns depend on the workflow, its baseline and its review load. Use net dollars from your own ledger.
What will AI do to SaaS companies?
The Federal Reserve staff note of July 2026 calls current evidence consistent with a buildout phase, not broad displacement. These are staff views, not Board positions.
On whether the category survives, read our analysis of B2B SaaS in the AI era.
How do you measure AI ROI when the benefit is time saved, not cash?
Convert only time that was actually redeployed or avoided as cost. Price those hours, subtract the review time the output required, and report the remainder as net dollars. A saved hour that removed no cost and added no output is spare capacity, not a return.
Should you cut AI spend if the AI market is correcting?
Not because of the market. Market and workflow are different units: a correction can move vendor prices and vendor survival, not last quarter saving. Read the ledger, then re-test on price changes.
How long before AI pays back?
None of the sources behind this article gives a payback figure, and this article will not invent one. The Federal Reserve note says gains from general-purpose technologies have historically lagged investment by years at the economy level. At workflow level, the 30-day reading is a method, not a promise.
Where to Go Next
Next: the pillar, SaaS metrics that matter in the AI era, and the follow-up step, a SaaS revenue forecasting model.
We publish one sourced teardown or playbook like this every week. The SaasFlywheel newsletter sends them as they land.
Sources
- MIT NANDA(Challapally, Pease, Raskar, Chari), “The GenAI Divide: State of AI in Business 2025”, July 2025, labelled “Preliminary Findings”, research period January to June 2025. Project page. The copy read for this article is a public mirror of the PDF.
- Bank for International Settlements, Annual Economic Report 2026, Chapter I, “Progress and peril”, 28 June 2026.
- Federal Reserve Board, FEDS Notes, “The AI Buildout and the Economy” (Soto, Thieu, Allen), 17 July 2026. Staff views, not Board positions.
- Epoch AI, “LLM inference prices have fallen rapidly but unequally across tasks”, 12 March 2025, prices from Epoch AI and Artificial Analysis.
- Anthropic, published pricing, read 2026-11-06.
- Fortune, 18 August 2025, NANDA coverage, cited only for its sample description.
- Reddit r/SaaS, 28 February 2026, one comment, quoted as anecdote.