Switch to light mode

The AI ROI Reckoning: Why Founders Are Hitting a Wall

- 7 min read

A founder looking at financial data on a computer screen with uncertainty

A founder I work with sent me a message last week. Two days before a board meeting, his CFO asked for something they’d never asked before: “Where’s the ROI on our AI spending? We’ve deployed agents, upgraded to Claude Pro, invested in training. What’s it buying us?”

He didn’t have an answer. Not a good one.

This conversation is happening at hundreds of startups right now. The pilot phase is over. Boards are done with the “AI is strategic” narrative. They want to see dollars and cents. And a lot of founders are discovering that AI spending feels easier to justify as a hypothesis than it is to measure as an outcome.

This is actually healthy. Here’s why, and what to do about it.

The Reckoning Is Real

Let me give you the context everyone’s missing. A recent survey found that enterprises are deferring 25% of planned AI investments to 2027. Not canceling. Deferring. Because CFOs and boards are asking the exact question your board is asking: Where’s the value?

And here’s the brutal stat underneath that: fewer than one-third of decision-makers can currently link AI spending to financial growth. Not “we don’t know yet.” Not “it’s too early to measure.” Can’t. Link. It.

Meanwhile, 79% of tech leaders cite driving business outcomes as their top priority. But there’s a gap between saying that and demonstrating it. AI felt like the obvious investment that would move the needle. Now people are asking whether it actually did.

Your board isn’t wrong to ask.

The problem isn’t that AI doesn’t create value. It does. The problem is that value is invisible in the way founders measure it. Your developers are shipping features 30% faster. Your operations team is automating routine tasks. Your sales pipeline is better organized. These are real wins. But they don’t show up on a P&L as a line item, so they feel intangible to people whose job is to hold you accountable for spending.

What Actually Happened in the Last 18 Months

Here’s the timeline:

Late 2024 - Mid 2025: AI is the answer to everything. Every startup adopts it. Budgets open up. Everyone’s experimenting.

Mid 2025 - Early 2026: Deployments happen. Claude Pro seats get allocated. AI agents start running workflows. Individual productivity goes up. This looks like success.

Mid 2026 - Now: Boards start asking “what did we get for this?” And founders realize they’ve been measuring the wrong thing.

The confusion happened because there are two different AI ROI stories, and nobody distinguished between them:

Story 1: Individual Productivity ROI. “Claude saves my developers an hour a day, so we ship features 20% faster. That’s valuable.”

This one is real, but it’s limited. It’s like saying “we bought faster computers so people work faster.” Sure. But if your bottleneck isn’t developer speed, faster developers don’t move the business needle.

Story 2: Organizational Leverage ROI. “AI lets us do X with fewer people / faster / better, which means Y outcome for the business.”

This is the story that changes numbers. It’s also the one that’s harder to execute, because it requires connecting a technical capability to a business outcome.

Most founders spent money on Story 1 and hoped Story 2 would follow. It didn’t.

The Gap Nobody’s Talking About

Here’s what I’m seeing consistently: founders treat AI as a solution to a velocity problem, when what they actually have is a clarity problem.

They say: “AI will let us build faster.”

What they often mean: “AI will solve the ambiguity about what we’re building or who we’re building it for.”

But AI can’t do that. Claude can’t write better requirements. Agents can’t make product decisions. AI is a force multiplier on clarity, not a replacement for it.

So you end up with faster development of the wrong thing. You ship more. You measure velocity. You miss the fact that you’re not moving toward your goal, just moving faster in place.

The founders who are successfully showing AI ROI right now aren’t the ones who invested the most in AI tooling. They’re the ones who invested in clarity first - crystal-clear processes, clear metrics for success, explicit business outcomes - and then used AI to amplify those.

Here’s what I’m actually seeing work: A company I work with had unclear job scheduling that was costing them real money - they couldn’t fix it manually because visibility was too fragmented. They used AI agents to build visibility into the constraint, let humans make the high-level decisions, and automated execution. The economics changed because they solved a clarity problem with AI, not a speed problem.

What Your Board Actually Needs to Hear

When your CFO asks “where’s the ROI,” they don’t want a technology explanation. They want a business answer.

So don’t say: “Our developers use AI tools that increase coding speed by 30%.”

Say: “We deployed AI agents for [specific task]. That task was costing us [specific amount] in time, error rate, or margin. After implementation, that cost dropped to [new amount]. Year-one savings: [number]. Three-year payback: [period].”

If you can’t make that connection for a specific AI investment, that’s not a communication problem. That’s a signal that the investment wasn’t clear to begin with.

Here’s what to do:

First, audit what you’ve already spent. AI tools, training, experimentation. Get a number. I’d guess it’s between $50K and $500K for most Series A companies, depending on size and how aggressively you’ve invested.

Second, identify what actually changed. What processes run differently now? What takes less time? What’s more reliable? Don’t guess - talk to the people doing the work.

Third, calculate the value. If it’s developer speed, what’s the cost per developer hour? How many hours did you actually save? If it’s error reduction, what’s the cost of errors? If it’s process automation, how much labor time went away? Get a number.

Fourth, be honest about what you don’t know. If you can’t attribute a business outcome to a specific investment, say so. Then decide: Is this an experiment worth continuing? Is it foundational infrastructure that’s hard to isolate for ROI? Or is it spending that doesn’t have a clear business case?

And honestly - that last category is fine. Some AI investments are about readiness, about having people and infrastructure in place for when the right use case emerges. That’s a legitimate business decision. Just make it consciously.

The Actual Future

The deferment of AI spending isn’t a problem for your startup. It’s an opportunity.

Most companies are going to pause and reassess. They’ll continue AI investments but demand stronger ROI justification. The weak use cases will disappear. The strong ones will get funding.

But here’s where it gets messy: you might find that half your AI spending can’t be traced to an outcome. Maybe it’s foundational. Maybe it enabled something else that’s hard to isolate. Maybe it was just a failed experiment. That’s not a problem if you can say that out loud - “we’re building the infrastructure” or “this didn’t work, we’re moving on.” The problem is founders who can’t articulate it either way.

Spend the next month connecting your AI investments to outcomes - either business outcomes or explicit infrastructure/readiness plays. Not to perfect the answer, but to have one you can defend.

Your board isn’t trying to kill AI. They’re trying to figure out whether you’re running a project or a business.

© 2024 Shawn Mayzes. All rights reserved.