OZZZER · AI NEWS2 of 3 free stories opened
← Back to AI News

Automation & Agents · 13 Nov 2026 · 13:04 CET

Why Agentic AI Projects Get Canceled, and What an Eight-Week Pilot Gets Right

Unite.AI · 13 Nov 2026 · 13:04 CETRead original at Unite.AI ↗
Share
LinkedInXFacebookWhatsApp
Why Agentic AI Projects Get Canceled, and What an Eight-Week Pilot Gets Right

Publisher preview · OZZZER analysis pending editorial review.

PUBLISHER ARTICLE PREVIEW

From the original article

A customer asks for a refund, and the agent finds the order in the CRM, checks the returns policy and drafts a reply in under a minute. Then it stalls, because the refund approval sits in a finance system it was never connected to and the customer’s address doesn’t match between two databases.

Gaps of this kind rarely surface in a demo, yet they decide how much an agent costs to run and whether anyone can trust it, which puts the bigger risk in agentic AI inside the business the agent is dropped into rather than inside the model.

Gartner expects more than 40% of agentic AI projects to be canceled by the end of 2027, pointing to rising costs, unclear business value and weak risk controls. Read closely, that forecast is about how these projects get approved on the strength of a demo, with little view of what the work costs today or who owns the outcome.

The question I’d put to any leadership team is whether the business can support this agent doing the work every day, at a cost and level of risk it can live with. Answering it means looking hard at what I call the work after automation, meaning everything people still have to do once the agent has finished its part, and an eight-week pilot is a practical way to measure it before committing to a full rollout.

An agent rarely works on its own, since even a simple-looking task touches customer records, a couple of business applications and usually an approval step, and every connection limits what the agent can see and do. Where records are inconsistent or nobody is quite sure who signs off, the agent inherits the confusion along with the task.

Routine cases are seldom the problem; exceptions are, because that’s where operating costs pile up, and they’re precisely the part a demo is built to avoid. Deloitte’s 2026 research found that only 5% of organizations rate their business processes as highly prepared for AI agents, a number more telling than any model benchmark because it suggests the AI is ready well before most processes are.

Timing how fast an agent produces an output is the easiest way to overstate its value, since the figure that matters is how much effort the finished task takes. Say a request takes an employee 20 minutes to process, and the agent gets the first pass down to two, which looks like an 18-minute saving right up until someone spends 15 minutes checking the result and fixing errors.

Three minutes saved is a thin return once the cost of running the agent goes on the other side of the ledger.

McKinsey’s analysis of a banking customer-service agent shows the same pattern at scale: tokens made up 20–25% of variable operating costs and human oversight 70–75%, so most of the money sat outside the model. Without a baseline in place before anyone writes code, a pilot can show plenty of technical progress and still leave the investment case untested.

Adoption usually gets filed under change management, although in my experience it’s settled much earlier, by where the agent sits in the workflow.

Source

Unite.AI · 13 Nov 2026 · 13:04 CET

Open the original at Unite.AI ↗