Defensive math
60% of companies are getting almost nothing back from AI. The more interesting question is which math they ran.
Here's a strange pair of numbers. BCG found that 60% of companies are seeing little to nothing back from AI, even after significant investment. Fewer than a third say they're seeing significant ROI across the organization. These probably aren't companies that skipped this. It looks like they bought in - tools, contracts, maybe a task force or two. And most of them, by their own reporting, got very little back.
Let's look at how that happens, and then at what it looks like away from budgets.
Two kinds of math
A company can run two kinds of math on AI. Here's the first one, in my own words:
"defensive math" - justifying an investment by what it removes, instead of what it makes possible.
The second kind doesn't have a tidy name, but we could call it something like expansion math - justifying an investment by the capabilities it builds, even when nobody can price them yet. We'll get there.
The customer service line
The cleanest case of defensive math working is high-volume, routine work. Customer service interactions are the standard specimen. Abstractions are hard to walk through, so here's someone doing it.
Dana handles returns at a mid-size retailer. Let's walk one of her contacts:
Run that contact through Dana and it costs $3 to $6. Run the same contact through an AI agent - it reads the email, checks the order, issues the refund, or something close to it for routine cases - and it costs $0.25 to $0.50 per contact. In those specific workflows, the reported result is an 85 to 92% cost reduction. Honestly, that math is real. I'm not disputing it.
But notice what had to be true before any of that math could run. What makes a cost removable? It was counted first. Dana's contact shows up as a $3 to $6 expense because somebody, at some point, decided to track what a contact costs. Defensive math can only run on numbers a company is already keeping. A capability that doesn't exist yet has no line item, so it never enters the comparison - not because it failed the math, but because the math never saw it.
A floor under subtraction
Here's where I think the 60% comes from. Maybe subtraction has a floor. You can cut a cost once, optimize it twice, and then the line item is gone - and so is the gain. The other kind of math asks different questions: what could this team do that it couldn't do before? What could the company ask that it could never afford to ask? The trouble is those answers don't exist yet as numbers anyone is counting, which makes them hard to defend in a budget meeting. $0.25 to $0.50 per contact walks into that meeting with receipts. That asymmetry probably explains most of the gap between specific workflows posting an 85 to 92% cost reduction and fewer than a third of companies saying the investment paid off across the organization. The first kind has a number to put in the cell; the second doesn't, so it keeps getting deferred.
Where else it shows up
Alright. Let's climb out of it. This isn't really a corporate pattern. It looks like a human pattern wearing a corporate costume. Take personal health. Cutting calories is defensive math - countable, immediate, a number that moves every morning. Building a capacity you didn't have - strength, endurance, being able to say yes to the hike you would've dreaded - is the other kind. Most of us run the first kind and underinvest in the second, because the first kind reports back. (Though I don't always do it right.)
A household budget works the same way. Canceling subscriptions is defensive math. Learning to cook - so that restaurants shift from necessity to choice - is expansion. The first shows up on this month's statement. tbh, the second is harder to stick with because no statement ever confirms it.
It turns out the more you look for something, the more you find it. This shows up in careers - taking the raise versus learning the unpriced skill - and maybe in city budgets, in friendships, in how a person spends a Saturday. The cut has a number and the build doesn't, so the comparison isn't even happening on the same terms.
The part I haven't resolved
The part I have no answer for is how you budget for something whose value can't be counted until after it exists. I don't have a clean answer. The question I keep circling, in budgets and elsewhere, is whether the math I'm running asks what something removes or what it makes possible. I catch myself running defensive math in places that probably deserve the other kind. I don't always get that one right either.
Written by
Adam Roozen
Strategic Advisor. AI Strategy, Digital Commerce, Technology Transformation
Nearly 30 years of operating experience · Walmart · Sam's Club · Echidna
Work with Adam