InvestNot yet confirmed elsewhere1 publisher3 min readPublished
Gartner forecasts over 40% of agentic AI projects canceled even as a third of software ships with agents
Gartner expects over 40% of agentic AI projects to be canceled by the end of 2027 and a third of enterprise software to ship with agentic AI by 2028. Quartz's summary says both can hold at once. We think that argues for releasing agent budgets in tranches.
The Investor · Invest desk

What happened
- Gartner attributes the expected cancellations, as Quartz reports it, to rising costs, thin business value and weak risk controls.
- Gartner also forecasts that by 2028 at least 15% of routine work decisions will be made autonomously, up from almost none in 2024.
- Quartz names CRM, HR, procurement and IT service desks as the likeliest early homes, since they run on structured data and defined approval chains.
- Quartz says the gap shows up in audit logs, approval thresholds and clear ownership when an agent gets something wrong.
Why it matters
- decision A buyer has to separate budget for custom agent builds, where Quartz says write-offs concentrate, from budget for agent features arriving inside software already licensed.
- cost A single up-front release puts the full cancellation risk on the buyer. Tranches limit the loss to the amount in flight when a gate fails.
- constraint Audit logs, approval thresholds and named owners have to exist before an agent's scope widens. That gives the controls team a say over the pace of spend.
The two figures count different things. The 40% is a share of projects [2] (initiatives a company starts), the one-third is a share of applications [1] (products a vendor ships), and one buyer can land in both groups at once: a canceled in-house pilot on one side, an agent feature switched on inside software it already licenses on the other. On Quartz's reading, agent capability reaches users through software they already have, while a large share of the spending on custom-built versions ends up written off [5]. The Quartz piece does not say how many of the canceled projects were custom builds, how many projects Gartner counted, or what they cost, so the write-off cannot be priced from this source.
Take the cancellation figure at face value and the exposure is easy to show. Above 40% canceled leaves fewer than 60 of every 100 projects standing [6]. Split a budget evenly across 100 projects, release it on day one, and at least 40 of those shares go to work that is later stopped [7], with the money out the door before any of the causes Gartner cites had shown up [3]. A tranche structure stops payment at the first failed gate, so a doomed project costs one tranche and not the whole line.
The first tranches write themselves from the deployments Quartz describes as typical today: a customer-service agent that resolves a billing question but escalates any refund above a set threshold, and a procurement agent that sends a purchase order while a person signs off before payment [11]. Each has a threshold and a named human, which is exactly what a gate can test. Quartz adds that companies deploy before they understand what the software needs to run safely [12].
We think the budget that should not exist is a single multi-year line for a broad rollout. The case for staging is strongest for custom builds, or rather for the builds Quartz says get written off. The counter-thesis is that staging costs time. If embedded agents arrive on Gartner's schedule, a company that releases money slowly buys the same features at the vendor's pace anyway, having paid for gates it did not need. Waiting has its own limit: even the 2028 forecast leaves roughly two-thirds of applications without agentic capability [8], so most categories will still be buyable later, and nothing forces a rush.
We would be wrong on two counts. If the cancellations cluster in projects that already had audit logs, thresholds and owners, the gates do not predict survival. And if the final count for 2027 lands well under 40%, the loss that staging protects against is smaller than the delay it adds.
What to watch
- Gartner's full research note: the number of projects counted, and whether the 40% covers vendor-embedded agents or only custom builds.
- The end-2027 cancellation count against the 40% line, and whether the canceled projects lacked audit logs, thresholds and owners.
- Whether CRM, HR, procurement and IT service desk vendors ship agent features with approval thresholds and audit logs on by default.
Clarity's read
What the record supports and how the coverage leans. The claims behind it follow.
Reality
- Evidence35
- Adoption
- Insufficient
- Hype gap
- Insufficient
- Incentives
- Insufficient
- Confidence40
Claim ledger
Ranked by verification strength, evidence, and original report placement.
- [1]
Gartner forecasts that agentic AI will be embedded in a third of enterprise software applications by 2028, up from close to none in 2024.
- [2]
Gartner puts the proportion of agentic AI projects canceled by the end of 2027 above 40%.
- [3]
Gartner says agentic AI projects will be undone by rising costs, thin business value and weak risk controls.
- [4]
Gartner expects at least 15% of day-to-day work decisions to be made autonomously by 2028, a category of activity that barely existed in 2024.
- [5]
Quartz says both forecasts can be true: the capability spreads through tools people already use, while much of the money spent building custom versions gets written off.
- [6]
If more than 40% of agentic AI projects are canceled, fewer than 60 of every 100 projects remain.
- [7]
On a budget split evenly across 100 projects and released in full on day one, at least 40 of the 100 shares go to projects that are later canceled (assumes equal-sized projects).
- [8]
Even if Gartner's forecast holds, roughly two-thirds of enterprise software applications will not ship with agentic capability by 2028.
- [9]
Quartz names customer relationship management platforms, human resources systems, procurement software and IT service desks as the likeliest early homes for embedded agents, because they run on structured data and defined approval chains.
- [10]
Quartz says the gap between deployment and safe operation shows up in audit logs, approval thresholds and clear ownership when an agent gets something wrong.
- [11]
Quartz says most deployments today are narrower than fully autonomous: a customer-service agent might resolve a billing question but escalate any refund above a set threshold, and a procurement agent might send a purchase order while a person signs off before payment executes.
- [12]
Quartz says companies deploy before they understand what the software needs to run safely.
Sources
1 independent publisher whose own reporting we read for this story.
- qz.comAI agents are taking over your workplace — here's what Gartner says
1 article · October 12, 2026
Topics and entities
Follow any of these and your For You feed starts watching them — no settings page required.
Topics
- Agentic AI and tool useFollow
- AI GovernanceFollow
- Enterprise SoftwareFollow