88% of AI agent pilots never reach production, Forrester and Anaconda find — the gap between 'we tried Claude Code' and 'it runs our business'

New Forrester and Anaconda research puts the AI agent pilot-to-production failure rate at 88%, with evaluation gaps, governance friction and model reliability cited as the top blockers — a sharp contrast to adoption figures that show most developers already using AI coding tools daily.

Adoption and deployment have quietly become two different numbers. Stack Overflow’s 2026 developer survey puts daily AI coding agent use at 71% of professional developers, and GitHub Copilot alone claims 40% adoption in large enterprises. But new research from Forrester and Anaconda finds that 88% of AI agent pilots never reach production — the largest gap between “we’re using this” and “this is load-bearing” that either firm has recorded.

The blockers aren’t mysterious. Leaders cite evaluation gaps — no reliable way to test whether an agent’s output is actually correct before it ships — as the top obstacle (64%), followed by governance friction (57%) and model reliability (51%). None of these are solved by a better model. They’re solved by the unglamorous work of building test harnesses, review gates, and rollback paths around the model, which is exactly the part a Cursor or Claude Code subscription doesn’t include.

The industry split makes the pattern clearer still. Banking and insurance run 47% of their AI agent pilots through to production; software and internet companies aren’t far behind at 44%. Healthcare and government trail badly, at 18% and 14%. That’s not a capability gap — it’s a compliance and procurement gap. The sectors with the strictest audit and governance requirements are the ones where “it worked in the demo” is furthest from “it’s safe to ship,” because they’re the only ones forced to prove it before they can.

So what

If your organisation has AI coding tools in every developer’s hands but nothing running in production, you’re not behind — you’re at the median. The 88% figure is a useful gut-check against any vendor pitch that treats agentic coding as already-solved: the model is rarely the constraint anymore, the surrounding engineering discipline is. That’s also the case for treating “vibe coded” prototypes as production-ready without the evaluation, governance, and reliability work layered on top. If you’re weighing whether to build a pilot in-house or bring in a team that’s already solved the production gap, our approach to AI-assisted development is built around exactly that gap, or get in touch to talk through where your pilot actually stands.

← All research

More research.

VS Code 1.145 lets Copilot run local automations on a schedule with custom agents

GitHub's 6 November 2026 Copilot weekly release adds cron-scheduled local automations with custom agents in VS Code 1.145, alongside Copilot in JetBrains Air and a unified Copilot CLI settings dashboard.

Read ›

@GitHub in Slack and Teams is generally available: from a chat message to a pull request

GitHub's 6 November 2026 release makes @GitHub in Slack and Teams generally available, letting teams investigate bugs, create issues and open pull requests with an AI coding agent from a chat conversation.

Read ›

GitHub secret scanning cuts false alarms for AWS, Google and Alibaba cloud keys and adds a SpaceX detector

GitHub's 5 November 2026 secret scanning update tightens detectors for AWS, Google Cloud and Alibaba keys, relevant to teams building software with AI coding tools that can paste credentials into code.

Read ›

GitHub's Copilot code review can now be managed by API, with review effort levels and AI credit costs shown

GitHub's 6 November 2026 update lets organisations manage Copilot code review by API and see the review effort and AI credits each AI code review used, a sign AI-assisted development is becoming auditable.

Read ›

GitHub's Copilot impact dashboard now counts chat and VS Code agent use, and drops the 'passive users' label

On 6 November 2026 GitHub added Copilot Chat and the VS Code Agents window to its Copilot impact dashboard, bringing it to nine tracked experiences, and renamed 'Passive users' to 'Chat-first users'.

Read ›

Claude Code 2.1.319: a setting that denies permission prompts so AI agent runs don't stall

Claude Code 2.1.319 (6 November 2026) adds a permissions.denyInsteadOfPrompting setting and moves long MCP tool calls to the background, a sign AI-assisted development is being built for unattended runs.

Read ›

Start a project

Building with AI? Let's talk.

Tell us what you are building. We'll give you an honest view of the right approach.

Start a projectSee our work