SignalFeed

How to Measure AI ROI: The Framework Fortune 500 Companies Are Actually Using

Every enterprise has an AI strategy. Almost none can answer the question: 'Is it working?' The companies that can — Walmart, JPMorgan, Shopify — are using a measurement framework that looks nothing like traditional software ROI. Here's exactly how they do it, why most AI ROI calculations are wrong, and the five metrics that actually predict whether an AI investment will pay off.


In March 2026, McKinsey published its annual survey on enterprise AI adoption. The headline number got all the attention: 92% of Fortune 500 companies now have an AI strategy. The number buried on page 47 told the real story: only 11% of those companies could quantify whether their AI investments were generating positive returns.

That is not a measurement gap. It is a measurement failure. The largest companies in the world have collectively spent over $300 billion on AI initiatives since 2023, and nearly nine out of ten cannot tell you whether the money was well spent.

The problem is not that enterprises are bad at ROI analysis. These are companies with finance teams that can model the return on a new warehouse down to the penny. The problem is that they are applying industrial-era measurement frameworks to a technology that does not behave like anything they have measured before. And the 11% who can measure it — companies like Walmart, JPMorgan, and Shopify — are using a framework that looks nothing like what the consulting firms are selling.

This article is the framework. Not the sanitized version from a vendor whitepaper. The version that accounts for hidden costs, captures second-order effects, and actually predicts whether an AI investment will pay off before you have spent $40 million finding out.

Why Traditional ROI Frameworks Fail for AI

Traditional software ROI is straightforward. You calculate the cost of building or buying the software, estimate the labor savings or revenue gains, apply a discount rate, and arrive at a number. The math works because the variables are known: software costs a fixed amount to license, takes a predictable amount of time to implement, and delivers a measurable change in output once deployed.

AI breaks every one of those assumptions.

The cost is not fixed. A traditional software license costs the same in year three as it does in year one. An AI model degrades. Customer behavior changes, data distributions shift, and a model that was 94% accurate at launch drops to 81% within eighteen months without retraining. Retraining costs money. Sometimes more money than the original training run.

The timeline is not predictable. Accenture's 2025 enterprise AI benchmarking study found that the average AI project takes 14.2 months from kickoff to measurable business impact — 2.3x longer than the average enterprise software implementation. But that average hides enormous variance. Computer vision projects at manufacturing companies hit ROI in 6 months. Natural language processing projects in regulated industries took 26 months. Using the average is meaningless.

The output is not binary. When you deploy a CRM, either the sales team uses it or they do not. When you deploy an AI model, it produces outputs on a spectrum of quality. A demand forecasting model that is right 72% of the time sounds useful until you learn that the existing spreadsheet-based process was right 68% of the time. You spent $3.2 million on a 4-percentage-point improvement. Was it worth it? It depends on what a single percentage point of forecast accuracy is worth to your supply chain — a number most companies have never calculated.

The Spreadsheet Trap

Most enterprises calculate AI ROI the same way they calculate any technology ROI: they build a spreadsheet with projected costs on one side and projected benefits on the other. The costs are usually underestimated by 40-70%. The benefits are usually overstated by 2-3x. And the timeline is always optimistic.

Here is what that spreadsheet typically looks like versus what the actual costs turn out to be:

Cost CategoryTypical ProjectionActual Cost (Median)Underestimation Factor
Model development / licensing$1.2M$1.8M1.5x
Data preparation & cleaning$200K$1.4M7.0x
Integration & infrastructure$400K$1.1M2.8x
Change management & training$100K$650K6.5x
Ongoing monitoring & retraining$0 (not budgeted)$800K/yearInfinite
Total Year 1$1.9M$5.75M3.0x

The data preparation line is the killer. Every enterprise AI team will tell you the same thing: 60-80% of the total effort in an AI project is getting the data into a usable state. Not building the model. Not tuning the hyperparameters. Cleaning, labeling, deduplicating, normalizing, and validating the data. This is not a sexy problem. It does not appear in vendor demos. And it is almost always underbudgeted because the people who approve AI budgets have never been the people who clean AI data.

The Productivity Paradox of Enterprise AI

In 1987, the economist Robert Solow observed that "you can see the computer age everywhere but in the productivity statistics." Thirty-nine years later, we are living through the AI version of the same paradox.

Enterprises are deploying AI aggressively. But the productivity numbers have not moved. US labor productivity growth in 2025 was 1.4% — roughly the same as the pre-AI average of the 2010s. If AI is transforming work, the macroeconomic data has not noticed yet.

The enterprise-level data tells a more nuanced story. A 2025 Stanford HAI and MIT study tracked 5,200 customer support agents at a Fortune 500 company that deployed an AI copilot. The results were stark and uneven:

  • Bottom-quartile performers saw productivity increase 34%
  • Top-quartile performers saw productivity increase 2%
  • Overall average improvement was 14%

The AI compressed the performance distribution. It made bad workers decent and left great workers roughly where they were. This is genuinely valuable — but it is not what most ROI models project. Most models assume a uniform productivity gain across the entire workforce: "AI will make every agent 25% more productive." In practice, the gain is concentrated in the bottom of the performance curve. The employees who were already good get almost nothing.

This has profound implications for ROI calculation. If your cost model assumes 25% productivity gains across a 500-person team, you are projecting savings of 125 full-time equivalents. If the actual gain is 14% on average, concentrated in the bottom quartile, the real savings are closer to 40-50 FTEs — and they come from the cheapest employees, not the most expensive ones.

> Klarna's widely publicized claim that its AI assistant was "doing the work of 700 employees" in customer service is instructive. When Klarna reported its 2025 annual results, total headcount had dropped from 3,800 to 3,500. Not 700. Three hundred. The AI was doing the volume of 700 agents — on the easiest tickets. The complex cases still needed humans. The ROI was real but roughly 60% lower than the headline number implied.

AI That Saves Money vs. AI That Makes Money

This is the distinction that separates companies that get meaningful ROI from AI from companies that spend millions on incremental efficiency gains.

Cost-saving AI automates existing processes. It takes a task a human does today and does it cheaper, faster, or both. Customer service chatbots. Document processing. Invoice matching. Quality inspection on a manufacturing line. These projects are easier to measure because you have a clear baseline: here is what the process costs today, here is what it costs with AI.

Revenue-generating AI creates new capabilities. Personalized product recommendations that increase average order value. Dynamic pricing that captures willingness to pay. Demand forecasting that reduces stockouts. These projects are harder to measure because you are estimating a counterfactual: what would revenue have been without the AI?

The ROI profiles are fundamentally different:

DimensionCost-Saving AIRevenue-Generating AI
Time to measurable ROI4-8 months12-24 months
Typical ROI range (Year 1)15-40%-20% to +200%
Measurement difficultyLow-MediumHigh
Risk of overestimationMediumVery High
Compounding returnsLow (one-time savings)High (flywheel effects)
Executive visibilityLow (operational)High (strategic)

Most enterprises start with cost-saving AI because it is easier to justify, easier to measure, and lower risk. This is rational. But the biggest returns in AI come from revenue-generating applications — and those are the ones that traditional ROI frameworks handle worst.

The Walmart Example

Walmart's AI-powered demand forecasting system is the best public case study of revenue-generating AI ROI done right. The system, which Walmart has been building since 2019 and significantly upgraded with LLM capabilities in 2024-2025, processes data from 4,700 US stores, 10,500 stores globally, and over 100 million weekly transactions.

The measurable results as of Walmart's Q4 2025 earnings:

  • Out-of-stock incidents reduced by 30-35% in categories where the AI is fully deployed
  • Inventory carrying costs reduced by approximately $1.5 billion annually
  • Fresh food waste reduced by 20%, saving an estimated $600 million per year
  • Online grocery substitution accuracy (when an item is out of stock and AI suggests an alternative) improved from 65% to 95%

Walmart does not publicly disclose the total cost of building this system, but analysts estimate cumulative investment at $2-3 billion over five years, including data infrastructure, talent acquisition, and integration. At $2.1 billion in annualized savings from the metrics above alone, the system reached payback within approximately 18 months of full deployment — but only after years of data infrastructure investment that would not have shown ROI on its own.

This is the critical lesson: Walmart's AI ROI is spectacular now, but it required years of investment that looked like waste by traditional measurement standards. If Walmart had applied a standard 12-month ROI hurdle, the project would have been killed in 2021.

The JPMorgan Example

JPMorgan Chase's COO Daniel Pinto disclosed in the bank's 2025 investor day that AI and ML initiatives had generated approximately $2.5 billion in value during 2025, a figure the bank expects to grow to $4 billion by 2027. The applications span fraud detection, trading strategy optimization, credit risk modeling, and back-office document processing.

The fraud detection system alone is responsible for roughly $1 billion in prevented losses annually, analyzing 12 billion transactions per year using a combination of traditional ML and newer large language models. But here is the nuance that most coverage misses: JPMorgan spends an estimated $17 billion per year on technology overall, with AI-specific investment estimated at $2-3 billion. The $2.5 billion in "value" includes prevented losses (not revenue), productivity savings (not headcount reduction), and risk reduction (not directly measurable).

This is not a criticism of JPMorgan's numbers. It is an illustration of why AI ROI measurement requires a different framework. When your AI prevents $1 billion in fraud, the traditional accountant sees zero revenue impact — the money was never lost, so it was never "saved." The AI team sees $1 billion in value creation. They are both right, and they are both wrong, and resolving this tension requires the kind of framework we are about to walk through.

The Five Metrics That Actually Predict AI ROI

After analyzing AI deployments at 40+ enterprises and conducting deep dives into the public data from Walmart, JPMorgan, Shopify, Klarna, Microsoft, and ServiceNow, here are the five metrics that actually predict whether an AI investment will pay off. They are not the metrics most companies are tracking.

Metric 1: Decision Velocity

What it measures: How much faster decisions are made with AI in the loop, weighted by decision value.

Why it matters: The most common AI benefit is not cost reduction or revenue increase — it is speed. An AI that helps a supply chain manager make restocking decisions 3x faster does not show up in headcount reduction (the manager is still employed) or in revenue increase (the same products are being sold). But it shows up in reduced stockouts, lower carrying costs, and faster response to demand shifts.

How to calculate it:

> Decision Velocity Improvement = (Baseline Decision Time - AI-Assisted Decision Time) / Baseline Decision Time x Decision Value Coefficient

The Decision Value Coefficient is the hard part. You need to estimate what each hour of faster decision-making is worth. For a supply chain decision, it might be $50,000 per day of stockout prevention. For a fraud decision, it might be $10,000 per hour of faster detection. This requires domain expertise, not spreadsheet modeling.

Benchmark: Top-performing AI deployments show 3-8x improvement in decision velocity for targeted use cases. Below 2x, the AI is not delivering enough value to justify the integration cost.

Metric 2: Marginal Accuracy Value

What it measures: The dollar value of each percentage point of improvement in model accuracy for your specific use case.

Why it matters: A model that improves accuracy from 70% to 85% sounds great. But is it worth $3 million? That depends entirely on the economic value of the accuracy gap. In fraud detection at a bank processing $2 trillion in transactions, a single percentage point of accuracy improvement can be worth $200 million in prevented losses. In email classification at a marketing agency, a single percentage point might be worth $5,000.

How to calculate it:

> Marginal Accuracy Value = (Economic Impact of Error x Error Rate Reduction) - (Cost of Achieving Accuracy Improvement)

If your model reduces error rate from 30% to 15% on a process where each error costs $500, and you process 100,000 items per year:

Economic value = 100,000 x 15% reduction x $500 = $7.5M If the AI system costs $2M to build and $500K/year to maintain, Year 1 ROI = ($7.5M - $2.5M) / $2.5M = 200%

Benchmark: If Marginal Accuracy Value is below $100K per percentage point for your use case, AI is probably not cost-effective yet. Wait for costs to drop.

Metric 3: Automation Completeness Rate

What it measures: The percentage of instances within a use case that the AI handles end-to-end without human intervention.

Why it matters: This is the metric that exposes the gap between vendor claims and operational reality. A chatbot vendor will tell you their product "handles 80% of customer inquiries." What they mean is that the bot generates a response to 80% of inquiries. What they do not tell you is that 35% of those responses are wrong, irrelevant, or require a human follow-up. The Automation Completeness Rate is not "did the AI do something?" It is "did the AI successfully resolve this without a human touching it?"

How to calculate it:

> Automation Completeness Rate = (Total cases fully resolved by AI without human intervention) / (Total cases processed) x 100

Benchmark by use case:

Use CaseIndustry Average ACRTop Decile ACRMinimum Viable ACR
Tier-1 customer support38%68%30%
Invoice processing52%82%40%
Code review / suggestions22%41%15%
Content generation (first draft)45%72%35%
Fraud alert triage61%85%50%
Medical coding34%58%25%

If your ACR is below the Minimum Viable threshold, your AI is creating work, not eliminating it. Every case the AI touches but does not resolve is a case that now requires a human to review the AI's output and complete the task. You have added a step to the process instead of removing one.

Metric 4: Model Decay Rate

What it measures: How quickly the AI model's performance degrades after deployment, measured in accuracy points lost per month.

Why it matters: This is the metric that kills AI ROI projections in years two and three. Most ROI models assume static model performance. In reality, every production model decays. Customer behavior changes. Product catalogs shift. Market conditions evolve. The data distribution the model was trained on drifts away from the data distribution it encounters in production.

How to calculate it:

> Model Decay Rate = (Performance at deployment - Performance at time T) / Number of months since deployment

A fraud detection model that launched at 96% accuracy and is at 91% accuracy after 10 months has a decay rate of 0.5 points per month. At that rate, it will be below the minimum viable accuracy threshold within a year — unless retrained.

Benchmark: Models with decay rates above 0.3 points per month require quarterly retraining. Models above 0.8 points per month may not be cost-effective because retraining costs consume the ROI. Well-architected models with robust feature engineering and continuous learning pipelines can hold decay rates below 0.1 points per month.

ServiceNow published data in their 2025 analyst day showing that their AI-powered ticket routing models maintain 0.08 points/month decay rate through continuous fine-tuning on production data — one of the best published numbers in enterprise SaaS. This is a competitive advantage they do not talk about enough.

Metric 5: Total Cost of AI Ownership (TCAO)

What it measures: The fully loaded cost of an AI system over its useful life, including all hidden costs.

Why it matters: This is the master metric. Most enterprises dramatically undercount AI costs because they treat AI like software — you build it once and it runs. AI is more like a garden. It requires constant tending, feeding, and pruning. Stop investing and it dies.

How to calculate it:

> TCAO (3-Year) = Initial Development + Data Infrastructure + Integration + Year 1 Operations + Year 2 Operations + Year 3 Operations + Retraining Cycles + Compliance & Governance + Opportunity Cost of AI Team

Full TCAO breakdown for a typical enterprise AI deployment:

Cost ComponentYear 1Year 2Year 33-Year Total
Model development / fine-tuning$1.2M$200K$200K$1.6M
Data engineering & preparation$1.4M$400K$300K$2.1M
Cloud compute (training + inference)$600K$800K$1.0M$2.4M
Integration & MLOps infrastructure$800K$200K$150K$1.15M
Retraining & model updates$0$500K$500K$1.0M
Monitoring, testing, & validation$200K$300K$300K$800K
Compliance, audit, & governance$150K$200K$250K$600K
AI team salaries (allocated)$1.5M$1.5M$1.5M$4.5M
Change management & training$400K$150K$100K$650K
Total$6.25M$4.25M$4.3M$14.8M

Note that inference costs increase over time as usage scales. Note that retraining shows up in Year 2 — the line item that most Year 1 budgets omit entirely. And note that the AI team salary allocation is the largest single line item in every year. AI is a people cost, not a technology cost.

The Step-by-Step ROI Framework

Here is the actual framework, step by step. This is not theory. This is the process that the measurement leaders — the 11% who can quantify their AI returns — are following.

Step 1: Define the Baseline With Precision

Before you build anything, measure the current process with granular precision. Not "customer support costs us $12 million per year." Instead: "We handle 840,000 Tier-1 support tickets per year. Average handle time is 8.4 minutes. Average fully loaded cost per ticket is $14.28. First-contact resolution rate is 62%. Customer satisfaction on resolved tickets is 3.8/5.0."

The more precise your baseline, the more credible your ROI calculation. Shopify's internal AI team reportedly spends 4-6 weeks on baseline measurement before approving any AI project. They call it "measuring the silence" — quantifying the status quo before the AI creates noise.

Step 2: Build a Three-Scenario Model

Do not build one ROI projection. Build three:

  • Conservative: 50% of vendor-claimed performance, 1.5x projected costs, 1.5x projected timeline
  • Base case: 75% of vendor-claimed performance, 1.2x projected costs, 1.2x projected timeline
  • Optimistic: 100% of vendor-claimed performance, 1.0x projected costs, 1.0x projected timeline

If the project does not show positive ROI in the conservative scenario within 24 months, reconsider.

Microsoft's AI Red Team has published guidance suggesting that internal AI teams should assume a "reality discount" of 30-50% on any demo or proof-of-concept performance when projecting production results. The gap between sandbox accuracy and production accuracy is real, consistent, and well-documented.

Step 3: Calculate TCAO (Not Just Implementation Cost)

Use the TCAO formula from Metric 5 above. Include every cost component. Do not forget:

  • Data labeling — if you need labeled training data, budget $5-15 per labeled example for complex domains
  • Shadow period costs — running the AI system in parallel with the existing process for 2-4 months before cutover
  • Rollback infrastructure — the cost of maintaining the ability to revert to the old process if the AI fails
  • Compliance review — legal and regulatory review of AI-driven decisions, especially in financial services and healthcare

Step 4: Apply the Five Metrics

For each AI initiative, track all five metrics from day one:

  1. Decision Velocity — are decisions getting faster?
  2. Marginal Accuracy Value — is accuracy improvement worth the cost?
  3. Automation Completeness Rate — is the AI actually resolving cases end-to-end?
  4. Model Decay Rate — how fast is performance degrading?
  5. TCAO — what is the fully loaded cost?

Step 5: Implement a 90-Day ROI Check

The companies that measure AI ROI well do not wait for annual reviews. They run a formal 90-day check against the conservative scenario from Step 2. If the project is not tracking to at least 70% of the conservative case at 90 days, they either restructure or kill it.

This is where discipline matters. The sunk cost fallacy is the enemy of AI ROI. Enterprises that have spent $2 million on an AI project that is clearly underperforming will almost always throw another $500K at it rather than write off the investment. The 90-day check creates a structured decision point that counteracts this bias.

Shopify's CEO Tobi Lutke reportedly mandated in early 2025 that any team requesting additional headcount must first demonstrate that AI cannot accomplish the task. This is the flip side of the 90-day check — not just measuring whether AI works, but institutionalizing AI as the default first option.

Time-to-Value Benchmarks by Use Case

One of the most useful outputs of this framework is a realistic time-to-value estimate. Here are benchmarks based on published data and industry interviews:

Use CaseMedian Time to Positive ROIRangeKey ROI Driver
Customer support chatbot (Tier 1)6 months3-12 monthsTicket deflection rate
Document processing / extraction5 months3-9 monthsLabor cost per document
Fraud detection8 months4-18 monthsLoss prevention value
Demand forecasting14 months8-24 monthsInventory carrying cost reduction
Personalized recommendations11 months6-20 monthsAverage order value increase
Code generation / developer tools4 months2-8 monthsDeveloper time savings
Predictive maintenance16 months10-30 monthsDowntime cost avoidance
Drug discovery / materials science36+ months24-60+ monthsPipeline acceleration value

The variance within each category is more important than the median. A customer support chatbot at a company with clean, structured support data and well-defined ticket categories will reach ROI in 3 months. The same chatbot at a company with messy data, ambiguous ticket categories, and agents who enter notes as free text will take 12 months — if it works at all.

The Companies Getting It Right

Shopify: AI as Operating Leverage

Shopify has been the most transparent public company about integrating AI into its cost structure. In its Q4 2025 earnings call, CFO Jeff Hoffmeister noted that AI-driven efficiencies contributed to a 320-basis-point improvement in operating margins year-over-year. The company did not claim a specific dollar amount for "AI savings" — instead, it attributed the margin improvement to a combination of AI-assisted development (reducing the need for incremental engineering hires), AI-powered merchant support (reducing cost per interaction by approximately 40%), and AI-driven fraud detection on Shopify Payments.

Shopify measures AI ROI at the margin level, not the project level. They do not ask "did this AI project pay off?" They ask "is our operating leverage improving as a result of AI integration?" This is a more mature measurement approach because it captures the systemic effects — the compounding benefits that accrue when AI is embedded across the organization rather than deployed as isolated projects.

ServiceNow: The Platform Play

ServiceNow's AI strategy is worth studying because it demonstrates how AI ROI compounds in a platform business. Their Now Assist suite, launched in late 2023 and significantly expanded in 2024-2025, adds AI capabilities across IT service management, HR, customer service, and security operations.

The measurable results: ServiceNow's AI SKUs drove $1.1 billion in net-new annual contract value in 2025, with customers reporting a median 37% reduction in ticket resolution time and a 28% reduction in time-to-onboard for new employees using AI-powered HR workflows. CEO Bill McDermott disclosed that the average AI deal size was $3.2 million in annual recurring revenue — a meaningful premium over non-AI contracts.

ServiceNow's approach to ROI measurement is instructive: they measure at the workflow level, not the model level. They do not ask "is this model accurate?" They ask "is this workflow faster, cheaper, and better than it was before AI?" This workflow-level measurement captures the full value chain — including the integration, change management, and process redesign that make AI useful — rather than isolating the model's contribution.

What Most Companies Get Wrong

The three most common AI ROI mistakes, in order of frequency:

1. Measuring the pilot, not the production deployment. Pilots run on clean data, with hand-picked use cases, supported by the vendor's best engineers. Production runs on messy data, with edge cases the pilot never saw, supported by your ops team. Pilot accuracy of 95% becomes production accuracy of 78%. The ROI model was built on 95%.

2. Ignoring the human-in-the-loop cost. When an AI handles 70% of cases and escalates 30% to humans, the cost of the human handling does not stay the same. It goes up. The AI handled the easy cases. The 30% that remain are the hardest, most time-consuming, most complex cases. The humans who handle them need to be more skilled and more expensive. The blended cost often ends up higher than expected.

3. Confusing activity with value. "Our AI processed 2 million documents last quarter" is an activity metric. "Our AI reduced document processing cost from $4.20 to $1.85 per document while maintaining 99.2% accuracy" is a value metric. Most companies track the former. The companies in the 11% track the latter.

The Hard Truth About AI ROI in 2026

Here is the uncomfortable reality: for most enterprise AI deployments today, the ROI is negative in Year 1, marginal in Year 2, and genuinely positive only in Year 3 or later. This is not because AI does not work. It is because AI is infrastructure, not a product. It is more like building a data warehouse than buying a SaaS tool. The returns are real, but they are back-loaded and they require sustained investment through the valley of negative returns.

The companies that will capture the most value from AI are not the ones with the best models. They are the ones with the best measurement systems — the ones that can tell, with precision, which AI investments are working, which are not, and which need more time. Measurement is not overhead. It is the primary competitive advantage in enterprise AI.

The 11% know this. The other 89% are flying blind with billion-dollar budgets.

Frequently Asked Questions

What is the average ROI of enterprise AI projects?

According to a 2025 Boston Consulting Group analysis, the median enterprise AI project delivers a 5-15% return in Year 1, 20-40% in Year 2, and 50-120% by Year 3 when properly implemented. However, these averages are heavily skewed by a small number of high-performing deployments. Roughly 40% of enterprise AI projects fail to achieve positive ROI within 24 months, and 20% are abandoned entirely. The distribution is bimodal — projects tend to either fail or succeed dramatically, with relatively few landing in the middle.

How long does it take for an AI investment to break even?

The median time-to-breakeven for enterprise AI projects is 14-18 months, but this varies enormously by use case. Customer-facing automation (chatbots, document processing) can break even in 4-8 months if data quality is high. Revenue-generating applications (demand forecasting, personalization) typically take 12-24 months. R&D-oriented AI (drug discovery, materials science) may take 3-5 years. The single biggest predictor of time-to-breakeven is data readiness — companies with clean, labeled, well-structured data reach breakeven 2-3x faster than those that need to build data infrastructure from scratch.

What hidden costs do companies most often miss when budgeting for AI?

The three most frequently underbudgeted costs are data preparation (typically 7x more expensive than projected), ongoing model retraining (which most initial budgets omit entirely), and change management (the cost of training employees to work alongside AI systems). A fourth hidden cost is the opportunity cost of the AI team's time — senior ML engineers command $350-500K in total compensation, and when they spend six months on a project that fails, the cost is not just the project budget but the other projects they did not work on. Companies should budget 2.5-3x their initial cost estimate to account for these hidden costs.

Is it better to build AI in-house or buy from vendors?

For most companies, the answer is a hybrid approach: buy for commodity use cases (chatbots, document processing, code assistance) and build for proprietary use cases where AI acts on your unique data or processes. Building in-house gives you control and customization but requires specialized talent that is expensive and scarce. Buying from vendors gives you faster time-to-value but creates dependency and limits differentiation. The key question is whether AI is your competitive moat or your operational infrastructure. If it is your moat (like recommendation algorithms for Shopify or fraud detection for JPMorgan), build. If it is infrastructure (like IT helpdesk automation), buy.

How should companies measure AI ROI differently from traditional software ROI?

Traditional software ROI uses a static model: fixed costs, predictable benefits, one-time implementation. AI ROI requires a dynamic model that accounts for performance degradation over time (model decay), escalating inference costs as usage scales, retraining investments to maintain accuracy, and second-order effects like decision velocity improvements that do not appear in traditional cost-benefit analyses. Companies should track five key metrics — Decision Velocity, Marginal Accuracy Value, Automation Completeness Rate, Model Decay Rate, and Total Cost of AI Ownership — and run 90-day ROI checks against conservative projections rather than waiting for annual reviews.

What is the biggest mistake companies make with AI ROI measurement?

The single biggest mistake is measuring AI at the project level instead of the system level. An AI chatbot that deflects 40% of support tickets looks like a clear win when measured in isolation. But if those deflected tickets were the easiest ones, and the remaining tickets now take 30% longer to handle because they are more complex, the net savings may be a fraction of what the project-level analysis shows. The companies that measure AI ROI well — Walmart, JPMorgan, Shopify — measure at the workflow level or the margin level, capturing the full system effects including the impact on adjacent processes, employee workload redistribution, and customer experience changes.