Back to Insights Educational article

The 2026 AI Adoption Curve: Where Things Actually Sit at Mid-Year

Halfway through 2026, the AI adoption curve looks less like a smooth S and more like three different curves stapled together. One mainstream, one cooling, one still mostly slideware.

Last updated: May 24, 2026 AI Adoption

~9 min read Reading time 6 Sections Data guide Data-rich article

Roughly halfway through 2026, the AI adoption curve looks less like a smooth S and more like three different curves stapled together: one mainstream, one cooling, one still mostly slideware.

01 The thesis

Three curves, not one

I keep getting asked the same question by operators planning their 2026 budget. Where are we on the curve. The honest answer is that there is no single curve. LLM assistants inside software people already use are mainstream and boring. Autonomous agents are a demo culture with a thin production tail. And the model labs themselves are quietly walking back some of the most ambitious 2024 promises. If you're choosing what to fund this year, the useful exercise is sorting your shortlist into those three buckets before you read another vendor deck.

The data that shaped this piece comes from a few places I trust more than vendor surveys. The MIT NANDA group's 2025 GenAI Divide study put a hard number on a feeling everyone in this work already had. Roughly 95% of enterprise GenAI pilots produced no measurable P&L impact. The Stack Overflow Developer Survey 2024 shows the opposite picture in one specific corner: code assistants. Daily developer use jumped past 60% in a year. And the McKinsey State of AI tracker keeps showing the same uncomfortable gap between adoption and reported financial benefit.

02 What's mainstream

Code assistants and embedded LLM features quietly won

The fight that's already over is the one almost nobody is reporting on. Code assistants, transcription, drafting inside email and docs, retrieval inside CRM and helpdesk software. GitHub Copilot, Cursor and Windsurf together moved the median engineering org to a place where opting out feels strange. Microsoft Copilot inside Office and Salesforce's Einstein layer turned LLM features into checkboxes the buyer barely thinks about. None of this is interesting anymore, and that is the point. When a category gets boring, it has crossed the chasm.

From the few projects we've shipped this year, the pattern that holds is the same. The thing that gets a result fast is almost always an LLM stitched into a workflow the team already runs, not a green-field agent. A draft-generation step inside an existing ticket pipeline. A retrieval layer on top of a knowledge base nobody had time to maintain. A structured-extraction job on PDFs that used to take a junior two hours each. If you're trying to figure out where to put the first dollar, our customer support playbook walks through one of the boring-but-pays variants in depth.

03 What's cooling

The autonomous agent story is mid-correction

The clearest tell is Klarna. They very publicly launched an OpenAI-powered support bot in January 2024 and spent a year telling the press it replaced 700 agents. By mid-2025 they were quietly rehiring humans and Sebastian Siemiatkowski was on stage admitting service quality had slipped. That isn't a one-off. It is the predictable shape of the cycle. Salesforce Agentforce launched into the same narrative. Cognition's Devin became a meme about the gap between demo video and real PR throughput. Microsoft's own internal Copilot rollout numbers, where leaked, suggest engagement that drops off after the first month.

“ The autonomous agent wave is roughly where chatbots were in 2017. Impressive demos, terrible at the long tail and most enterprise teams will regret going first.

I'm not saying agents won't work. I'm saying the gap between what a clean demo shows and what holds up against a real customer base on day 90 is much wider than vendor decks suggest. The MIT NANDA number was 95% of pilots producing no ROI, and most of those pilots were exactly the agent-shaped ones. If you're being pitched a multi-step autonomous workflow that touches money, refunds or anything legally regulated, that's the bucket I'd put it in. The piece on agents vs chatbots vs copilots sketches the boundary in more detail.

04 Mainstream vs hype

A sorting table for your 2026 shortlist

FIG. 01 – BUCKETS FOR MID-2026 Where each category actually sits

Category – Where it sits – What I'd do
Code assistants (Copilot, Cursor) – Mainstream. Past the chasm. – License them. Stop debating it.
Embedded LLM features in SaaS – Mainstream. Often free in your plan. – Audit which features you're paying for and ignoring.
Retrieval over internal docs – Production-ready when scoped narrowly. – Ship one team-sized version, measure, then expand.
AI-drafted customer support replies – Works as assist, fragile as full auto. – Keep a human on the send button this year.
Autonomous multi-step agents – Hype peak passing, cooling fast. – Pilot only if failure is recoverable. Avoid for money flows.
Voice agents (sales / support) – Improving fast, still uncanny. – Test inbound qualification, not outbound cold.
On-device / consumer AI features – Slipping (see Apple Intelligence). – Irrelevant to your 2026 budget. Skip.

05 The contrarian read

The labs are quietly walking back too

The other thing I find people aren't tracking is the tone shift inside the model labs. Apple Intelligence shipped late, with the more ambitious Siri overhaul pushed past 2026. Anthropic's positioning between Claude Sonnet 4.5 and Opus 4.7 is much more about cost per task and reliability than about new capability tiers. OpenAI keeps re-pricing access rather than announcing a generational leap. None of this is a crisis. It is the normal flattening that happens after a bubble of expectations. Capability is still improving, but the marginal next-year gain looks more like 15% on hard tasks than the 5x jumps that drove 2023 and 2024.

The practical implication for an operator is the opposite of what most people read into it. If capability is plateauing, the advantage stops accruing to whoever has the smartest model and starts accruing to whoever wires the existing models into their business the most carefully. That makes 2026 a build year, not a wait year. Which is a strange thing to say given the cooling vibes, but I think it's correct.

The 95% number is real, the conclusion isn't

The MIT NANDA finding that 95% of GenAI pilots produced no ROI is going to be used by every laggard CFO for the next two years as a reason to wait. That reading is wrong. The same data, read honestly, says the 5% that did produce ROI were the ones with a clearly scoped workflow target before they started, a real owner inside the business and a willingness to kill the pilot at six weeks if numbers didn't move. The conclusion isn't "don't do AI". It's "stop doing AI like a science fair." Our 90-day implementation roadmap is built around exactly that shift, and the measuring AI ROI piece covers how to scope the target.

06 How we'd actually approach this

Pick one boring win, ignore the agents for a quarter

If you have one quarter of attention and a modest budget, here is what the pattern I keep seeing in production says to do. Pick one workflow with a number attached to it. Response time, draft hours per week, manual extractions per month, qualified leads per rep. Pick an LLM-inside-existing-tool approach, not a new agent. Give it a six-week kill date. If the number moves, expand. If it doesn't, stop and pick a different workflow. Skip anything that requires a press release. The teams who do this in 2026 will be in a much better position to evaluate agents in 2027, when the agent stack has had another year of failure data to learn from.

If you want a second pair of eyes on which workflow is the right first pick, that's the conversation we have at the start of every engagement. The services overview describes how we run it.

Frequently Asked Questions

Is the 95% pilot failure number a reason to wait?+ No. The 5% that worked shared a specific shape: scoped workflow target, real owner in the business, six-week kill date. The failure rate is a process problem, not a technology problem. Waiting another year doesn't fix it; running the next pilot differently does. Should I be funding autonomous agents in 2026?+ Only if failure is recoverable. A multi-step agent that books meetings or triages internal tickets is fine to pilot. One that issues refunds, makes pricing decisions or talks to regulated customers without a human in the loop is the bucket I would skip until 2027 data is in. What's the safest first-year AI bet for a mid-market business?+ Code assistants for your engineering team and an LLM-powered retrieval layer on top of internal docs or your knowledge base. Both have years of real-world deployment data. Both have clear measurement (developer hours, ticket resolution time). Both stop short of replacing human judgment on customer-facing decisions. How do I know if a vendor is selling me hype?+ Two questions usually do it. First: 'Show me a customer with a number, not a logo.' If the answer is a quote from a press release, that's a flag. Second: 'What's your six-week failure rate on first deployments?' Honest vendors have one and will tell you. Vendors who never lose deals don't actually ship. Is Apple Intelligence's slippage a signal for enterprise plans?+ It's a signal that consumer-facing on-device AI is harder than the 2024 keynotes implied. It doesn't change much for an enterprise buyer running LLMs inside existing workflows. Your stack doesn't depend on a Siri overhaul. Treat the Apple story as evidence that the bubble is normalizing, not as evidence that the underlying tech doesn't work. When does it make sense to revisit autonomous agents?+ Late 2026 at the earliest, probably 2027. By then there will be another full year of public failure data. The surviving agent frameworks will have shaken out. The pricing should reflect actual reliability rather than demo-driven optimism. Going first costs more than going second in this category.

ANM SOLUTIONS / CONTACT US

Need help applying this to your business?

We turn AI insights into measurable business outcomes. Tell us about your workflow and we'll show you the highest-impact place to start.

AI Adoption

The Hidden Cost of Not Using AI, Honestly Counted

The cost of ignoring AI is real but narrower than the doom pieces claim. A practitioner view on which workflows actually pay an efficiency tax, where the FUD is wrong and how to decide when to move.

Read article

Implementation

The 90-Day AI Implementation Roadmap: From Scope to Production

A practitioner's view of the first 90 days of an AI implementation. Boring stack, eval-first, kill switch by day 90. Where most plans go wrong and what to do instead.

ROI

Measuring AI ROI: How to Get a Number You Can Defend (2026)

An opinionated guide to measuring AI ROI for CFO-leaning operators. Three return layers, a defensible formula, honest evidence standards and when to wind a project down.

Published: 2026-04-19 · Author: A&M Flow