Jul 16, 2026 The ROI Gap 14 min read
The ROI Gap · Part 4 of 6: Where It Works ← Start from Part 1

Where AI Actually Delivers ROI (and Where It Doesn't)

By Arjun Jaggi  ·  July 16, 2026  ·  Enterprise AI Strategy

Not all AI use cases have the same return profile. Some categories deliver measurable, recurring value within months. Others have consistently disappointed regardless of implementation quality. Knowing which is which before you invest changes the math.

The failure to distinguish between use cases with strong and weak return profiles is one of the most expensive mistakes in enterprise AI portfolio management. Organizations that selected use cases based on enthusiasm, vendor recommendations, or peer benchmarks rather than return profile analysis have portfolios heavy with investments that cannot produce the returns they were approved on.

Use case selection is not permanent. Organizations that recognize they are invested in low-return use cases can reallocate. But the cost of being in the wrong use cases for two to three years, including the opportunity cost of not being in better ones, is significant. Getting use case selection right in the first instance matters more than it might appear.

High
return use cases share four characteristics: high volume, clear quality metric, measurable baseline, and human review that catches failures before they propagate
Low
return use cases tend to have subjective quality criteria, low volume, high pre-existing baseline quality, or accountability gaps that make error costs hard to contain
Domain
matters: healthcare and regulated industries have specific cost structures from compliance requirements that change the ROI calculation for every use case category

The High-Return Categories

Several categories have produced measurable, recurring AI ROI across multiple enterprise contexts. The common thread is not the specific AI technology used. It is a set of structural characteristics that make value both large and measurable.

Document Processing and Extraction
High return

Extracting structured data from unstructured documents: contracts, invoices, medical records, regulatory filings, and similar artifacts. Why it works: volume is high and predictable, quality metrics are clear (extraction accuracy against known ground truth), the baseline (manual extraction time per document) is easily measurable, and errors are catchable by downstream validation. The Noy and Zhang (Science, 2023) finding of 37% task completion acceleration is consistent with what document-heavy organizations report when AI assists structured extraction work.

Key metric: cost per document processed · Baseline: manual extraction labor hours per document type
Code Generation and Review
High return

AI-assisted code generation, completion, and review for software development teams. Why it works: engineers have a clear sense of what good code looks like, code has automated quality gates (tests, static analysis, build pipelines), the baseline (time to produce equivalent code without AI) is measurable, and the volume of code produced by a software organization is large enough to compound small per-unit gains into significant aggregate value. The Anthropic Economic Index (2025) noted concentration of AI use in computer and mathematical occupations, consistent with software engineering being an early and strong return category.

Key metric: time to production per feature or bug fix · Baseline: engineering throughput without AI assistance
Customer Support Deflection with Quality Guardrails
High return

AI handling initial customer queries, resolving those it can resolve accurately, and routing those it cannot to human agents. Why it works: volume is high, cost per interaction is easily measurable, deflection rate (percentage of queries resolved without human intervention) is a clear metric, and quality guardrails prevent AI errors from reaching customers without human review. The key is the quality guardrail: implementations without them produce customer-facing errors that offset the deflection savings.

Key metric: cost per resolved interaction · Baseline: cost per interaction fully handled by human agents
Internal Knowledge Retrieval
High return

AI-assisted search and retrieval against internal enterprise knowledge: policies, procedures, product documentation, technical specifications, and similar corpora. Why it works: the volume of internal queries in large organizations is substantial, the time cost of failed or slow knowledge retrieval is measurable (time spent searching versus time spent on productive work), and the corpus is bounded and controllable in ways that public-domain AI queries are not. Return scales with corpus quality: investments in cleaning and structuring internal knowledge compound into better retrieval results.

Key metric: time to answer for common internal queries · Baseline: search and retrieval time before AI implementation

The Low-Return Categories

Open-Ended Creative Tasks Without Quality Gates
Low return

AI-generated marketing copy, creative briefs, and similar open-ended content without structured quality criteria. Why it underperforms: quality is subjective, which means revision rates are high, which means the time saved in generation is often consumed in editing and approval. The human in the loop spends as much time reviewing and revising as they would have spent generating, and the AI introduces a quality floor that may be below what skilled practitioners produce unaided.

Strategic Decision Support Without Accountability Structures
Low return

AI-generated strategic analysis, market assessments, or executive summaries used directly in decision-making without an accountable human reviewing the underlying reasoning. Why it underperforms: the cost of a bad strategic decision dwarfs any productivity gain from faster analysis production, and AI strategic analysis is prone to confident-sounding errors that experienced practitioners would catch but that non-specialists may not. Without an accountability structure that assigns a human owner to validate AI strategic outputs, the error cost is unbounded.

Use Cases Where the Baseline Was Already Very Good
Low return

Applying AI to processes where skilled humans already achieve high accuracy and appropriate speed. In these contexts, the improvement AI can offer is marginal, the risk of AI errors in a high-stakes process is significant, and the overhead of AI validation may exceed the productivity gain. A diagnostic process that expert practitioners handle with 98% accuracy is a poor candidate for AI improvement unless volume is so high that even a small accuracy improvement produces material value at scale.

The use cases with the highest AI ROI share a common structure: high volume of repetitive work, an objective quality metric, a measurable baseline, and a human review layer that catches failures before they propagate to customers or decision-makers.
Fig. 1: AI use case return profile scoring. Qualitative assessment of key ROI drivers across use case categories. Higher scores indicate stronger return profile.
USE CASE VOLUME MEASURABILITY BASELINE QUALITY RETURN PROFILE Document processing High High (extraction accuracy) Often constrained Strong Code generation High High (test pass rate) Variable by team Strong Support deflection High High (deflection rate) Moderate Strong (with guardrails) Internal knowledge retrieval High Moderate (time to answer) Often poor (search) Strong Open-ended creative Variable Low (subjective quality) N/A Weak Strategic decision support Low Low (decision quality) Often high (expert) Weak Qualitative assessment based on pattern analysis. Individual use case outcomes depend on specific organizational context and implementation quality.

The Domain Factor

Domain context changes the return profile of every use case category. The two most significant domain factors in enterprise AI are regulatory complexity and data sensitivity.

Healthcare: Regulatory requirements under HIPAA, FDA guidance on Software as a Medical Device, and clinical accountability standards all add compliance cost to every AI use case. The MEDFIT-LLM study (Rao, Jaggi, Sonam Naidu, IEEE RMKMATE 2025, DOI: 10.1109/RMKMATE64574.2025.11042816) demonstrated that fine-tuning small language models on domain-specific healthcare data using LoRA produces meaningfully better performance for clinical applications than using general-purpose models. This finding has a direct ROI implication: domain-specific fine-tuning reduces the error rate in clinical AI applications, which reduces the rework cost and the compliance risk. The investment in domain-specific model preparation is a cost that does not appear in generic AI ROI frameworks but that significantly affects the actual return in healthcare contexts.

Legal and financial services: The EU AI Act (Regulation 2024/1689) classifies AI systems used in certain legal and financial contexts as high-risk, requiring conformity assessments, technical documentation, and human oversight requirements that add cost to every deployment. The compliance overhead changes the minimum volume threshold required for any use case to produce positive ROI.

The Volume Threshold

AI ROI is inherently a compounding return story. The value of reducing cost per unit by a fixed percentage scales linearly with volume. The cost of the harness infrastructure required to make AI reliable in enterprise contexts is largely fixed. This means that AI ROI requires sufficient volume for the fixed harness cost to be amortized against a large enough base of unit cost savings.

The practical implication is that low-volume use cases rarely justify the full enterprise AI investment. A process that handles 200 transactions per month may produce demonstrable AI productivity gains per transaction while never recovering the engineering, evaluation, and maintenance costs of a reliable enterprise deployment. The same process at 20,000 transactions per month has a fundamentally different math.

A Use Case Scoring Framework

Before committing to any AI use case, scoring it on four dimensions identifies whether it belongs in the high-priority portfolio:

Volume: Is the scale sufficient to amortize fixed costs?

Estimate the monthly volume of units this use case processes: documents, queries, interactions, or decisions. Compare that volume against the estimated harness investment. If the investment does not amortize over a 12-18 month horizon at current volume, reconsider unless volume is expected to grow significantly.

Measurability: Is there a clear quality metric with a known baseline?

Specify the primary quality metric for this use case before deployment. Is it measurable objectively rather than subjectively? Does a baseline exist or can one be established before deployment begins? Use cases that cannot answer both questions should not proceed until they can.

Baseline quality: Is the current process good enough that AI improvement is marginal?

Honestly assess current performance. If skilled practitioners already achieve high accuracy on this task, the AI improvement ceiling may be too low to produce material return. The largest AI gains tend to appear in tasks where current performance is constrained by time or scale rather than by practitioner skill level.

Regulatory complexity: What compliance overhead does this domain add?

Identify the applicable regulatory requirements before building the business case. Healthcare and financial services use cases require compliance cost estimation that may materially change the return profile. Use cases in lightly regulated contexts have simpler cost structures and typically shorter paths to measurable return.

Applying the Framework: A Portfolio Audit Approach

For organizations with existing AI deployments, the use case scoring framework described above can serve as a portfolio audit tool. Walking through each active use case and scoring it on volume, measurability, baseline quality, and regulatory complexity often reveals a portfolio that is overweighted in low-return use cases and underweighted in the categories that reliably produce value.

The audit process itself is valuable beyond the scores it produces. It forces a conversation about each use case's value hypothesis that many organizations have not had since the initial deployment decision. Use cases that cannot generate a clear answer to "what specific outcome are we expecting AI to change, and how would we know if it is changing?" are candidates for redesign or exit regardless of their scores on the four dimensions.

McKinsey's State of AI in 2024 found that AI high performers allocate their AI investments more selectively than lower performers, concentrating on use cases where both business value and technical feasibility are high. The use case scoring framework described here is one approach to operationalizing that selective allocation discipline. Organizations that apply it before committing to new use cases, rather than after, build portfolios with better return profiles from the outset.

The WEF Future of Jobs Report 2025 highlighted that the highest AI productivity gains have appeared in tasks characterized by high repetition, clear quality criteria, and high baseline time investment. This finding from the workforce analysis perspective is consistent with the use case scoring framework from the business investment perspective: they independently arrive at the same conclusion about which types of work respond best to AI augmentation.

What the Research Supports About Use Case Selection

The research base on enterprise AI ROI is still developing, but the patterns visible in the available evidence are consistent with the use case scoring framework described above. Noy and Zhang (Science, 2023) demonstrated that AI productivity gains were largest for specific tasks where worker performance was currently constrained by skill or speed rather than by information access or judgment quality. That finding directly supports the scoring framework dimension on baseline quality: use cases where current performance reflects skill constraints have more headroom for AI improvement than those where current performance is already expert-level.

The Anthropic Economic Index (2025) documented that AI use is concentrated in computer and mathematical occupations, with document and information management as the most common use patterns. The concentration reflects revealed preference: workers who choose to use AI intensively are gravitating toward the task types where it demonstrably helps them. That revealed preference is consistent with the high-return use case categories identified above, since software development and document processing are both high-volume, high-measurability contexts that fit the scoring framework's strong profile.

The MEDFIT-LLM research (Rao, Jaggi, Sonam Naidu, IEEE RMKMATE 2025) demonstrates that domain context affects use case performance in ways that matter for portfolio management. The finding that domain-specific fine-tuning using LoRA materially improves performance for clinical AI applications has a direct analog in enterprise contexts: use cases in specialized domains with high accuracy requirements benefit from domain-specific investment that general-purpose AI does not provide. Portfolio managers who treat healthcare AI, legal AI, and general enterprise AI as interchangeable are making a category error. The return profiles differ because the performance requirements differ, and the investment required to meet those requirements differs accordingly.

The practical implication for enterprise AI portfolio management is that use case selection is not a one-time exercise. Portfolios should be reviewed at least annually against the scoring framework, with use cases that no longer meet minimum thresholds on volume or measurability considered candidates for exit. The budget freed by exiting underperforming use cases is better deployed in high-return categories where the framework's conditions are met. This active portfolio management approach is what distinguishes AI programs that improve over time from those that maintain the same profile of mixed performance indefinitely.

Use case selection is the highest-leverage decision in your AI portfolio.

Arjun works with CIOs and AI leaders to audit existing use case portfolios and build selection frameworks that identify where AI investment produces genuine return. If your portfolio needs a ROI-based assessment, book a working session.

Book a Session

References

  1. Noy, S. and Zhang, W. "Experimental evidence on the productivity effects of generative artificial intelligence." Science 381(6654):187-192, 2023. doi.org/10.1126/science.adh2586
  2. Rao, A.K.G., Jaggi, A., and Naidu, S. "MEDFIT-LLM: Evaluating Large Language Models for Medical Fitness Assessment." IEEE RMKMATE 2025. Domain-specific fine-tuning using LoRA improves clinical AI performance. DOI: 10.1109/RMKMATE64574.2025.11042816
  3. Chen, L., Zaharia, M., and Zou, J. "FrugalGPT: How to Use Large Language Models While Reducing Cost and Improving Performance." arXiv:2305.05176, 2023. Model cascading for inference cost reduction. arxiv.org/abs/2305.05176
  4. Anthropic. The Anthropic Economic Index. 2025. Concentration of AI use in computer and mathematical occupations and within-occupation variation in AI adoption intensity. anthropic.com
  5. European Parliament and Council. Regulation (EU) 2024/1689 (EU AI Act). Official Journal of the EU, 2024. High-risk classification adds compliance cost structure to AI deployments in regulated industry contexts. eur-lex.europa.eu
  6. McKinsey & Company. The State of AI in 2024. McKinsey Global Institute, May 2024. AI high performers allocate investments more selectively, concentrating on high business value and technical feasibility use cases. mckinsey.com
  7. World Economic Forum. Future of Jobs Report 2025. WEF, January 2025. Highest AI productivity gains in tasks characterized by high repetition, clear quality criteria, and high baseline time investment. weforum.org