Our team will be out of office on Friday, May 1, 2026. We’ll be back and ready to assist you starting Monday, May 4th.

Why Do AI Agents Work In Testing And Fail With Real Customers?

Contents

A design answer for small business owners about to automate something, built on the two properties that separate agents that hold from agents that only demo.


“It worked perfectly for three days.”

That is how almost every one of these conversations starts. An owner built something, watched it run beautifully, turned it loose on real customers, and then spent a week discovering all the ways a working system is different from a demonstrated one.

Here is the direct answer to the question in the headline. AI agents fail in production because they were scoped by ambition instead of by boundary, and because nobody decided in advance what would be logged. The failure is almost never about model quality. The two properties that consistently separate agents that survive from agents that die are bounded scope, meaning one domain with a defined tool set and an explicit refusal of everything outside it, and observable behavior, meaning every tool call logged and every decision point traceable after the fact.

Both of those are decisions a business owner makes before a single instruction is written. Neither of them requires a stronger model. That is the good news buried inside a genuinely sobering set of numbers.

Key Takeaways

  • Gartner projects that more than 40 percent of agentic AI projects will be scrapped by 2027, driven by escalating costs, unclear business value, and inadequate risk controls rather than by model capability.
  • The agents that deliver production value share two properties: bounded scope with explicit refusal, and observable behavior where every tool call is logged.
  • Model quality does not appear on the list of things that distinguish successful agent deployments from failed ones.
  • Real production failures cluster around five specific breakages: state loss on crash, inability to resume mid-task, authentication expiry across restarts, unhandled rate limits, and absent monitoring.
  • Defining kill criteria before launch is what prevents a dead project from consuming budget for a year after it stopped working.

Ambition Is The Leading Cause Of Death

Gartner’s projection is that more than 40 percent of agentic AI projects will be scrapped by 2027. The stated drivers are escalating costs, unclear business value, and inadequate risk controls.

Read that list carefully, because what is absent matters as much as what is present. Nobody is on record predicting that these projects die because the models were not smart enough. The models kept getting smarter throughout. The projects died of scope, of vagueness about what success meant, and of nobody owning the failure modes.

I understand exactly how a project gets there, because the path is reasonable at every single step.

You start with a real irritation. Customer service takes too long. You describe the problem to an AI tool, and the tool is genuinely impressive, and somewhere in that conversation the ambition inflates from “answer refund status questions” to “handle customer service.” That inflation feels like vision. It feels like thinking big, which is what everyone told you to do.

Then you build it, and it works on the cases you thought of, because you thought of them. Then a real customer arrives with a case you did not think of, and the agent does not refuse, because you never told it to refuse. It improvises. And improvisation in front of a paying customer is where the money goes.

I have watched owners spend four months and real money on that arc. The heartbreaking part is that the small version, the one they would have been embarrassed to announce, would have been running profitably by week three.

But what if the embarrassing version is the only version that works?

The Failure Modes Are Boringly Specific

The community conversation on agent reliability has matured over the past year, and it has landed somewhere useful. Across r/AI_Agents and r/ClaudeAI, people have stopped debating whether agents break and started cataloguing precisely how.

Five failures come up repeatedly, and every one of them is invisible on a laptop.

State loss on crash. Anything the agent holds only in memory disappears when the process dies. On your machine it never dies. In production it dies at 2 a.m. on a Saturday.

No mid-flight resumption. A task that cannot pick up where it stopped has to start over. Starting over costs money in tokens and costs trust when a customer receives the same message twice.

Authentication expiry across restarts. Tokens expire. Restarts happen. Access dies silently, without a dramatic error, and the agent simply stops doing the thing you assumed it was doing.

Unhandled rate limits. Every provider throttles. An agent that does not back off gracefully does not slow down, it stops.

Absent monitoring. Nothing is watching, so you learn about failures from a complaint rather than from an alert.

There is a real-world illustration from February 2026 that makes the point better than any abstraction. n8n users found that a Vector Store Question Answer Tool began generating invalid JSON schemas. Both OpenAI and Anthropic rejected the calls. Enterprise-licensed production workflows stopped working entirely. The model was fine. The schema was not. Nobody was watching the seam between them.

Set that against what the same communities credit for production success. The agents delivering value share bounded scope, which means one domain, a defined tool set, and explicit refusal of anything outside that boundary, and observable behavior, which means every tool call logged and every decision point traceable so a team can reconstruct exactly what the agent did and why.

That is the whole list. It is not glamorous and it is not technical in the way people expect. It is the operational equivalent of writing a job description and keeping a timesheet.

The MIT Project NANDA research points the same direction from the enterprise side, finding that roughly 95 percent of integrated generative AI pilots showed no measurable profit and loss effect, and attributing the shortfall to organizational habits rather than to the technology. Critics have fairly noted that the study measured six-month ROI and excluded efficiency gains, so treat it as directional. But even directionally, the finger is pointing at how organizations approach these builds, not at what the models can do.

Scope It Down Until It Feels Too Small

Here is the framework I now use with every owner who wants to automate something. It has four parts and the first one does most of the work.

Draw the boundary first. Before you write a single instruction, write down what the agent must refuse. Not what it does. What it hands back. If your agent handles refund status lookups, then billing disputes, cancellation requests, and anything involving a dollar amount above your threshold go to a human, with specific language that makes the handoff feel like service rather than a dead end. The refusal list is longer than the capability list in every agent I have seen work.

Define finished in checkable terms. Write an acceptance checklist specific enough that a person could verify an output in under two minutes. If you cannot write that checklist, you do not yet understand the task well enough to delegate it to anything, human or otherwise.

Decide what gets logged before anything runs. Every tool call, every decision point, every input the agent received. You are building the ability to answer a customer complaint about what happened, in a format a non-technical person can read. Decide this now, because after something goes wrong is the worst possible time to discover you have no record.

Set kill criteria in advance. Error rate threshold, cost ceiling, time limit. Write them down before launch, while you are still objective, because the person reviewing this project in four months will be emotionally invested in it and that person is you.

Then run it in shadow mode. The agent produces output, a human reviews it, and the human decides whether it goes out. Two weeks of that will teach you more about your process than two months of planning, and it costs you nothing in customer trust because no customer is exposed to a mistake.

Only expand after the narrow version has run clean for a month. Each new capability gets added against specific reliability criteria, not against enthusiasm.

Your First Agent, Correctly Scoped

1. List every recurring task in your business, then pick the most boring one.
You want high frequency, clear rules, low consequence when wrong, and easy verification. Refund status lookups. Appointment confirmations. Intake form triage. If the task feels too small to be impressive, you have probably found the right one.

2. Write the one-sentence business case with a real number.
“This must save at least six hours per week within 60 days” is a business case. “This will make us more efficient” is a wish. If you cannot produce the number, do not build yet.

3. Cost it honestly, including failures.
Count retries, failed attempts, human review time, and maintenance. Agent projects die of cost creep more than of anything else, and the creep is almost always in the retries nobody modeled.

4. Write the refusal rules before the capability rules.
List every adjacent request the agent should hand back. Anything involving money above a threshold, legal commitments, or unusual customer data goes to a person, always, with the exact handoff language written out.

5. Set up logging you can actually read.
For each completed task, record what came in, what tools were called, what decision was made, and what went out. You are not building an engineering system. You are building the ability to answer “what happened with my order” honestly.

6. Run shadow mode for two weeks with a human gate.
Track how often the human accepts the output unchanged. When that number is boringly high and stays there, you are ready. When it is not, you have learned something cheap.

7. Write your kill criteria and put a review date on the calendar.
Error rate ceiling, cost ceiling, and a date. Review it dispassionately. Killing a project that is not working is a competent act, not a failed one, and the 40 percent projection exists largely because that review never happens.

Frequently Asked Questions

What percentage of AI agent projects actually fail?
Gartner projects more than 40 percent of agentic AI projects will be scrapped by 2027. The cited causes are escalating costs, unclear business value, and inadequate risk controls. Model capability is not among the listed drivers, which suggests most failures are design and governance problems rather than technology problems.

What does bounded scope mean for an AI agent?
Bounded scope means the agent handles one domain with a defined set of tools and explicitly refuses anything outside that boundary rather than improvising. In practice, the list of things the agent hands back to a human is usually longer than the list of things it handles itself.

Do I need a more powerful model to make my agent reliable?
Usually not. The properties that distinguish production-ready agents are scope discipline and observability, neither of which improves with a stronger model. Define your minimum acceptable output first, then test whether a smaller or cheaper model already clears it.

What should an AI agent log?
Every tool call, every decision point, the inputs it received, and the output it produced, in a format a non-technical person can read. The test is whether you could reconstruct exactly what happened when a customer complains, without asking a developer.

How long should I test an agent before customers see it?
Run it in shadow mode for at least two weeks, where the agent produces output and a human reviews and decides whether to use it. Go live when the human is accepting output unchanged at a consistently high rate, not when the demo impresses you.

The Close

“It worked perfectly for three days.”

I want you to hear that sentence differently now. It is not a story about a tool that let someone down. It is a story about a system that was never given a boundary, never given a record, and never given a definition of what finished looked like.

More than 40 percent of these projects are expected to be scrapped. That number is not a warning to stay out. Read the causes again, because every one of them is a decision, and decisions are the one category of problem a business owner is fully qualified to solve.

You do not need a better model. You need to give your agent one job, the authority to say no, and a paper trail. That is unglamorous work. It will not impress anyone at a conference. It is also the entire difference between the agents that get shut down in 2027 and the ones that are quietly still running.

Build the version you would be slightly embarrassed to announce. It is the only one that will still be working when the announcements stop.


Jonathan Mast is the founder of White Beard Strategies, where he helps entrepreneurs build AI systems that survive contact with real customers. He teaches the Perfect Prompt Framework to a community of tens of thousands of business owners and has watched enough ambitious automations die to have strong opinions about scope.

About the Author