Back to blog
b2b salesobjectionsai agentsAugust 3, 2026 · 4 min read

Why 80% of AI projects don't pay off

80% of AI projects fail to deliver the expected return, according to a RAND study. What to ask a conversational agent vendor before you sign.

Cristian Pereyra

Cristian Pereyra

Co-founder · Engineering

A RAND Corporation meta-analysis of 65 enterprise AI projects found that 80.3% failed to deliver the business value expected of them. Almost a third get abandoned before reaching production. Gartner confirmed numbers in the same range in April 2026, specifically in AI infrastructure. If your company already lived through a version of this (a pilot that died after the demo, a chatbot the team stopped using by month two), the skepticism you bring to evaluating the next vendor has a real basis behind it.

Why most AI projects never reach production

RAND identified three patterns that explain almost every failure in its sample, and none of them is a technology problem. 33.8% of projects get abandoned before entering production. 28.4% reach production but don't deliver the expected benefit. 18.1% work but never pay back what they cost. According to industry coverage of the study (published in late 2025 and picked up by Gartner in April 2026), the three underlying causes are poor data quality, no clear decision structure over who approves what, and a project scope that drifts over time until nobody remembers the original problem.

Out of every 100 AI projects, where they drop

  • 33,8%Abandoned before productionnever gets in front of a customer
  • 28,4%Ships without the expected benefitit works, and it doesn't move the number that motivated the project
  • 18,1%Works but doesn't pay backdelivers a result and still costs more than it returns
  • 19,7%Delivers the expected valuewhat's left after the three patterns above

RAND, meta-analysis of 65 enterprise AI projects (2025). The first three add up to 80.3%.

What changes when the project is a conversational agent, not an entire platform

An AI agent for sales or support has an advantage against those three patterns: its scope is small by definition, so scope drift matters less. The risk concentrates in the first pattern, data quality, and there it takes a very concrete shape: the agent got trained on a generic base (public FAQs, flows built by the vendor) instead of the real instructions the person who actually handles your customers or closes your sales follows today. The model isn't the problem. The problem is that it never saw how your team works.

The real objection behind "we already tried a chatbot and it didn't work"

In a sales conversation, this line comes up often, and it almost never means what it literally says. The prospect didn't stop believing in AI. They stopped believing a vendor can understand their business well enough to make trying again worth it. The previous bot answered with generic scripts, escalated anything that wasn't a manual-level question, or broke the moment someone asked something off-script. The underlying objection is about personalization, not whether the technology works. Treating it as a technical objection (showing a more polished demo) doesn't resolve it. Treating it for what it is (fear of paying again for the same thing with a different logo on top) does open the conversation.

What to ask before signing with an AI agent vendor

Four questions separate the projects that actually deliver from the ones that end up in RAND's statistic:

  • Does the agent train on the real instructions from your best salesperson or best support person, or on the vendor's generic base?
  • Does it integrate with the tools you already use (CRM, WhatsApp, your helpdesk), or does the project start by asking you to migrate systems?
  • What does the agent do when it doesn't know the answer? If the answer is "it guesses" or "answers with something close," that's the next broken chatbot.
  • Who defines, before starting, how success gets measured at 90 days? If that metric gets defined after launch, there's no way to know whether it worked.

What it looks like when it works

At Takenos, the fintech, the agent resolves 70% of conversations without human intervention. The model it runs isn't different from the one behind a generic chatbot. What changed was the training: the real flows the support team already used, integrated with the tools the fintech already had, instead of a template built by the vendor. That upfront work, not the model, explains the difference between that result and a chatbot nobody uses after the first month.

Next time you evaluate an AI agent after an experience that didn't work, ask less about the technology and more about the process: whether the vendor asks for your team's real instructions before writing a single line of script, or shows you the same generic demo with a different name on top.


Sources: RAND Corporation, meta-analysis of 65 enterprise AI projects (2025), via industry coverage of the study. Gartner, AI infrastructure report (April 2026).

Share X LinkedIn WhatsApp
Cristian Pereyra

Cristian Pereyra · Co-founder · Engineering, StudioChat

Want agents like these working for your team?

Talk to us now