How a promising pilot gets stuck in purgatory and never ships

Give the pilot a path to production from the start, sponsorship, clear KPIs, and integration, and it graduates. Leave those out and it loops forever as a perpetual experiment nobody kills or scales.

B

Balagei G Nagarajan

3 MIN READ


A pilot looping endlessly in purgatory, never graduating to production
One built as a pure proof of concept loops until the enthusiasm runs out.
— from “How a promising pilot gets stuck in purgatory and never ships”

Key facts.

  • Organizations with dedicated executive sponsors are reported to be about 1.8 times more likely to scale AI successfully and the lack of one is a common reason pilots stall.source
  • MIT NANDA's State of AI in Business 2025 finds the divide between stalled and scaled GenAI is organizational, integrating the tool into workflows and ownership, not a model-capability gap.source

Why do pilots get stuck?

Pilot purgatory is a specific failure: the pilot proved the idea works in a controlled setting and then it just sits there, neither killed nor scaled. Everyone waits for someone to push it forward. The usual causes are organizational, not technical. There is no executive sponsor to fund and force the jump to production. There are no clear KPIs, so nobody can say whether the pilot succeeded enough to graduate. And there is no integration plan, so moving it into real workflows means work no one scoped. The model was never the blocker; the path to production was never built.

The way out is to design that path into the pilot from the start. Line up the sponsor before you begin. Define the metric that decides graduation and plan the integration so production is a step, not a cliff. The sponsorship data shows how much that one factor moves the odds and the MIT NANDA research names what graduation actually requires: closing the learning gap of integrating the tool into real workflows and ownership. A pilot built with those in view graduates. One built as a pure proof of concept loops until the enthusiasm runs out.

A stuck loop of a pilot cycling without an exit to production, with the missing exits labeled

What gives a pilot an exit?

ElementStuck in purgatoryPath to production
SponsorNoneNamed, before the start
Success metricVagueDefined graduation KPI
IntegrationUnscopedPlanned as a step
OutcomeLoops foreverGraduates

The graduation KPI only works if the agent's reliability is something you can actually measure. Is what the Pattern Intelligence Layer provides. VibeModel makes reliability legible at the pattern level. "ready for production" is a number a sponsor can act on rather than a debate and the pilot has a clear, evidence-backed exit instead of an indefinite stay in purgatory.

Frequently asked questions

Will the next model finally push our pilot into production?
Pilots stall on gaps, not the model; a newer model gives no sponsor, metrics or workflow fit, MIT NANDA's learning gap, so purgatory defers rework. (source)

What actually keeps pilots stuck?
Organizational gaps: no sponsor, no graduation KPI, no integration plan. The model usually works; the path to production was never built.

When should you plan for production?
Before the pilot starts. Designing the sponsor, metric and integration in from the start is what turns a proof of concept into something that ships.

Is the production gap a model problem?
Rarely. MIT NANDA's research shows it is organizational, integrating the tool into workflows and ownership, which is exactly what a perpetual pilot defers.


Share this post

Join the discussion

Have a take, a war story, or a question? Sign in with GitHub to comment and react. Comments are powered by GitHub Discussions, ad-free and yours to moderate.

Continue Reading

Find where your agent breaks, before you build it

Faultmap maps where your agent will fail from the goal and your data, then hands you the first test suite it has to pass.