The AI Briefing

Why 95% of AI Pilots Fail: The Hidden Scaling Problem Killing Your ROI

8 min · 6. jan. 2026
episode Why 95% of AI Pilots Fail: The Hidden Scaling Problem Killing Your ROI cover

Description

MIT research reveals 95% of AI pilots fail to deliver revenue acceleration. Tom breaks down why this isn't a technology problem but a scaling failure, and provides three critical questions to identify which pilots deserve investment. Show Notes Key Statistics * 95% of generative AI pilots fail to achieve rapid revenue acceleration (MIT, 2025) * 8 in 10 companies have deployed Gen AI but report no material earnings impact * Only 25% of AI initiatives deliver expected ROI * Just 16% scale enterprise-wide * Only 6% achieve payback in under a year * 30% of GenAI projects predicted to be abandoned by end of 2025 Core Problem: Horizontal vs. Vertical Deployments * Horizontal: Enterprise-wide copilots, chatbots, general productivity tools   * Scale quickly but deliver diffuse, hard-to-measure gains *   * Vertical: Function-specific applications that transform actual work   * 90% remain stuck in pilot mode *   Three Critical Evaluation Questions 1. Does this pilot solve a problem we pay to fix? 2. Can we measure impact in terms the CFO cares about? 3. Does it require process redesign or just tool adoption? Success Factors * Empower line managers, not just central AI labs * Select tools that integrate deeply and adapt over time * Consider purchasing solutions over custom builds * Be willing to retire failing pilots This Week's Action Items * Inventory current AI pilots * Categorize as: scaling successfully, stalled but salvageable, or stalled and unlikely to recover * Apply the three evaluation questions * Identify specific barriers for salvageable pilots Chapters * 0:00 - The 95% Problem: Why AI Pilots Aren't Becoming Products * 0:24 - The Research: MIT, McKinsey, and IBM Findings on AI Failure Rates * 1:49 - Why Pilots Stall: Horizontal vs. Vertical Deployments * 3:07 - What Successful Scaling Actually Looks Like * 4:11 - Three Critical Questions to Evaluate Your AI Pilots * 5:40 - The Permission to Stop: When to Retire Failing Pilots * 6:45 - Action Steps: What to Do This Week

Comments

0

Be the first to comment

Sign up now and become a member of the The AI Briefing community!

Get Started

1 month for 9 kr.

Then 99 kr. / month · Cancel anytime.

  • Podcasts kun på Podimo
  • 20 lydbogstimer pr. måned
  • Gratis podcasts

All episodes

35 episodes

episode Build vs Buy: Making Smart Decisions About Custom LLM Models artwork

Build vs Buy: Making Smart Decisions About Custom LLM Models

Tom explores the critical decision between building custom LLM models versus using off-the-shelf solutions. Drawing from insights at the AWS Expo, he breaks down the real costs, challenges, and strategic considerations for organizations evaluating domain-specific AI implementations. Build vs Buy: Making Smart Decisions About Custom LLM Models Key Topics Covered When to Build Custom LLM Models * Domain-specific applications requiring specialized knowledge * Handling proprietary or confidential information * Real-world example: AIDoc's experience at AWS Expo * Understanding your organization's unique requirements True Costs of Building 1. Data Preparation * Gathering organizational historical knowledge * Creating validation and training datasets * Organizing proprietary information 2. Training Expenses * GPU infrastructure costs (billions spent by OpenAI, Anthropic monthly) * Ongoing computational requirements * Budget considerations for organizations 3. Maintenance & Updates * Keeping pace with base model improvements * Avoiding being locked into outdated versions * Continuous investment requirements When to Buy Off-the-Shelf * Non-hyper-specific use cases * Data collation and comparison tasks * General analysis and processing needs * Cost-effective solutions for standard workflows Optimizing Model Selection * Using platforms like AWS Bedrock for model diversity * Balancing accuracy vs. cost vs. performance * Example: Claude Opus vs. Sonnet vs. Haiku trade-offs * Avoiding "overkill" with expensive models * Testing and validation strategies Key Takeaways * Don't default to the most expensive model * Test multiple options before committing * Understand total cost of ownership for custom builds * Match model capabilities to actual requirements * Consider the rapid pace of AI ecosystem changes Mentioned Companies/Platforms * AWS (Amazon Web Services) * AWS Bedrock * AIDoc * OpenAI * Anthropic (Claude models: Opus, Sonnet, Haiku) Resources * AWS Expo insights and presentations * Open source foundation models for custom building Chapters * 0:02 - Introduction: The Build vs Buy Debate * 0:25 - When Building Custom Models Makes Sense * 2:02 - The Real Costs of Building Your Own Model * 3:35 - Real-World Example: AIDoc at AWS Expo * 4:09 - The Case for Off-the-Shelf Solutions * 5:44 - Optimizing Model Selection and Cost * 6:46 - Final Recommendations and Wrap-Up

Yesterday7 min
episode Frontier AI Models & Cybersecurity: Protecting Your Organization in the LLM Era artwork

Frontier AI Models & Cybersecurity: Protecting Your Organization in the LLM Era

Explore the critical cybersecurity implications of frontier AI models and open-source LLMs for modern organizations. Learn about amplified attack vectors, supply chain vulnerabilities, and essential defense strategies as AI capabilities evolve rapidly. Frontier AI Models & Cybersecurity: Protecting Your Organization Key Topics Covered AI Model Security Landscape * Differences between closed systems (OpenAI, Anthropic) and open-source models * Guardrails in commercial AI platforms vs. self-hosted solutions * Jailbreaking risks and limitations of current safeguards Amplified Attack Vectors * Internal threats: Accelerated data access and reconnaissance * External threats: Previously non-viable attacks becoming scalable * Self-hosted model farms operating without safety constraints Supply Chain Security * Compromised dependencies and transient vulnerabilities * GitHub Actions exploitation * Pull request volume overwhelming developer validation * Upstream dependency infections Defense Strategies * Investing in InfoSec and cybersecurity departments * Leveraging LLMs for both offensive and defensive capabilities * Critical importance of update frequency and patch management * Operating system and library updates as security fundamentals Enterprise Recommendations * Implement proactive security policies before compromise occurs * Utilize specialized security tools (Snyk, ChainGuard mentioned) * Establish robust detection and mitigation protocols * Maintain vigilance as AI capabilities evolve Resources Mentioned * Snyk - Software security and dependency management * ChainGuard - Supply chain security solutions * Concept Cloud - conceptcloud.com for consultation and support Key Takeaway As frontier models increase in effectiveness, attack vectors will become more novel and critical to business operations. Organizations must implement comprehensive security measures NOW—waiting until after compromise is too late. For help securing your organization against AI-enabled threats, visit conceptcloud.com Chapters * 0:02 - Introduction: AI Models and Cybersecurity Implications * 0:41 - Guardrails: Closed vs Open-Source Models * 1:24 - Amplified Attack Vectors and Internal Threats * 2:44 - External Attacks and Enterprise Defense * 3:54 - Supply Chain Vulnerabilities and Dependencies * 5:47 - Mitigation Strategies and Proactive Security * 6:36 - Conclusion: Preparing for Evolving Threats

3. juli 20267 min
episode Why Most AI Vendor Solutions Are Underwhelming: Insights from AWS Expo artwork

Why Most AI Vendor Solutions Are Underwhelming: Insights from AWS Expo

Fresh from the AWS Expo in DC, Tom shares candid observations about the current state of AI vendor solutions and why most implementations fail to deliver real value. He explores what separates truly innovative AI companies from those simply adding AI features for upselling. Why Most AI Vendor Solutions Are Underwhelming Key Topics Covered AWS Expo Observations * Massive vendor presence at AWS Expo in Washington DC * Government and business organizations evaluating AI solutions * The overwhelming nature of vendor pitches and claims The AI Underwhelm Problem * Most AI use cases don't add significant value * Vendors using AI as an upselling strategy rather than innovation * Many "AI-powered" features could be accomplished manually at lower cost What Separates Winners from Followers * Cursor: Building tools that genuinely enhance workflow * Anthropic & OpenAI: True foundational model innovation * The importance of adding real value to user workflows The Future of AI Interaction * Moving beyond chatbot interfaces * The inefficiency of typing as an interaction method * Need for novel ways to interact with LLMs Key Takeaway Focus on use cases and practical implementation rather than getting caught up in AI hype Mentioned Companies * AWS (Amazon Web Services) * Cursor * Anthropic * OpenAI Action Items for Listeners * Critically evaluate AI vendors on actual value delivery * Think about novel use cases beyond chatbot interfaces * Consider whether manual solutions might be more cost-effective * Focus on workflow integration rather than feature checklists Chapters * 0:00 - Introduction: Return from AWS Expo * 0:34 - The Underwhelming State of AI Vendors * 1:41 - What Real AI Innovation Looks Like * 2:22 - Beyond the Chatbot: The Future of AI Interaction * 2:49 - Final Thoughts and Key Takeaways

2. juli 20263 min
episode LLM Uptime Crisis: What Happens When AI Services Like Claude Go Offline? artwork

LLM Uptime Crisis: What Happens When AI Services Like Claude Go Offline?

When Anthropic's Claude went offline over the weekend, it raised a critical question: How are businesses ensuring uptime for mission-critical systems built on LLMs? This episode explores the infrastructure challenges of depending on frontier AI models and strategies for maintaining business continuity. LLM Uptime Crisis: What Happens When AI Services Go Offline? Key Topics Covered The Anthropic Outage Reality * Recent weekend outage at Anthropic * Frequency of downtime incidents * Questions about root causes: compute spikes vs. SRE capabilities Business Impact Comparisons * Parallels to AWS and Azure outages * How cloud service dependencies halt operations * Netflix-style business impact scenarios for AI services Infrastructure Strategies for LLM Reliability * Multi-model backend configurations * Load balancing across providers (Anthropic, Bedrock, Foundry) * Seamless failover between AI services * The multi-cloud analogy for LLM dependencies Real-World Examples * Cursor's approach: combining proprietary models with Anthropic * Organizations building on frontier models * Mission-critical LLM applications Key Questions for Business Leaders * Do you accept downtime or build redundancy? * When is multi-model architecture worth the complexity? * How dependent is your business on specific LLM providers? * What's your failover strategy when AI services go offline? Resources * Host Website: conceptcloud.com * Host: Tom * Podcast: The AI Briefing Action Items for Listeners * Audit your LLM dependencies and single points of failure * Evaluate multi-provider strategies for critical applications * Consider load balancing architectures for AI services * Document your acceptable downtime thresholds Chapters * 0:00 - Introduction: The Anthropic Outage * 0:31 - Comparing AI Outages to Cloud Service Dependencies * 1:38 - The Real Business Impact Question * 2:33 - Multi-Model Strategies and Load Balancing * 2:42 - The Multi-Cloud Analogy for LLMs * 3:21 - Planning for LLM Unavailability

25. juni 20263 min
episode The $13K Company Backlog: Why Private Equity Must Prioritize Data to Exit Successfully artwork

The $13K Company Backlog: Why Private Equity Must Prioritize Data to Exit Successfully

Private equity faces a 13,000 company backlog with a critical challenge: returning capital. This episode explores why data quality—not just AI—is the key to unlocking portfolio value and successful exits in 2026 and beyond. Episode Show Notes Overview A focused discussion on the current private equity crisis and how data infrastructure directly impacts company valuation and successful exits. Key Topics Covered The Private Equity Backlog Crisis * 13,000 companies currently in PE portfolios awaiting exit * The shift from deal-making to capital return as the primary challenge * Why firms that bought at market peaks are struggling to monetize returns The Data Infrastructure Gap * How lean back-office operations limit value creation * The disconnect between AI ambitions and data readiness * Why many firms aren't leveraging existing data assets effectively Practical Solutions for Value Creation * The importance of data quality over data quantity * Building trust in existing data systems * Dashboard analytics vs. AI-driven insights * Maximizing revenue through better data utilization Key Takeaways 1. You don't need more data—you need to trust and properly use what you have 2. AI is only as good as the underlying data quality 3. Small improvements in data infrastructure can unlock significant company value 4. This applies beyond private equity to any data-driven organization Resources Mentioned * Article: "The 13,000 Company Backlog Redefining Success in Private Equity" * Tom's LinkedIn post on data quality and AI readiness About The AI Briefing Daily insights on AI, data strategy, and business transformation with Tom. Duration: 3 minutes 2 seconds Chapters * 0:02 - Introduction: The Private Equity Backlog Crisis * 0:22 - Why 2026's Biggest Challenge Is Returning Capital * 0:45 - The AI Opportunity and Data Quality Problem * 1:26 - The Infrastructure Gap in Private Equity Firms * 1:55 - How to Monetize Your Existing Data Assets * 2:22 - Data Quality: The Foundation of All Insights

24. juni 20263 min