In partnership with

I knew their raise wasn't going to be successful.

I didn't say it out loud, because the founders were sharp. Two ex-Google engineers, both with ML backgrounds, both deeply thoughtful about the problem they were solving. They'd built an AI tool that triages customer support tickets, routes them to the right team, and drafts initial responses. Clean UI. Solid demo. Real customers. Revenue growing 20% month over month. The kind of company that, two years ago, would have had a term sheet before the cappuccinos got cold.

But I'd been watching OpenAI, Anthropic, and Google ship agent frameworks that do exactly this, out of the box, for pennies on the dollar. The founders had built a house on a foundation that someone else owns, and the landlord just announced plans to move in. I could see it. Their next round of investors would see it too.

This is the dead zone. And it's everywhere right now.

VCs are saying the quiet part out loud

TechCrunch ran a piece in early March titled "Investors spill what they aren't looking for anymore in AI SaaS companies." The subtext was brutal. Thin workflow layers? Boring. Generic horizontal tools? Pass. Light project management with an AI sprinkle? Next. Surface-level analytics dashboards? Hard no.

Venture Pulse went further, reporting that VCs are now openly rejecting the majority of AI SaaS pitches they receive. Not because the founders lack talent, but because the products occupy categories where a foundation model update will do the same job natively within a year. The term they're using is "dead zone," and honestly, it's accurate.

Here's the math that makes this so painful. Around 14,000 new AI startups launched globally in 2024. By the end of 2025, roughly 3,800 had shut down. Another 1,800 closed in early 2026. That's a 40% mortality rate in under two years. And the survivors aren't safe either, because the ground keeps shifting beneath them every time OpenAI or Anthropic ships a new capability.

a16z put out a report earlier this year that crystallized the problem: software is eating labor now, which is a much larger market than software eating software ever was. But the flip side is vicious. If your AI startup is mostly an interface layer sitting on top of someone else's model, you're not selling software. You're selling a temporary head start.

Not a moat. A head start.

The AI your stack deployed is losing customers.

You shipped it. It works. Tickets are resolving. So why are customers leaving?

Gladly's 2026 Customer Expectations Report uncovered a gap that most CIOs don't see until it's too late: 88% of customers get their issues resolved through AI — but only 22% prefer that company afterward. Resolution without loyalty is just churn on a delay.

The difference isn't the model. It's the architecture. How AI is integrated into the customer journey, what it hands off and when, and whether the system is designed to build relationships or just close tickets.

Download the report to see what consumers actually expect from AI-powered service — and what the data says about the platforms getting it right.

If you're responsible for the infrastructure, you're responsible for the outcome.

The engineer's eye can see what the pitch deck hides

Here's where I think the SWE-to-VC background actually earns its keep. Because the dead zone is not obvious from a pitch deck. The pitch deck looks great. Revenue charts go up and to the right. Customer logos are impressive. The NPS scores are high. Everything points to product-market fit.

But if you've ever built production systems, you know to ask a different set of questions. What happens when you pull up the architecture diagram? Is this three API calls to GPT stapled to a React dashboard? (I've seen this exact setup more times than I can count.) Where's the proprietary training data? Is the model fine-tuned on domain-specific data that took years to collect, or is it running the same foundation model every competitor has access to?

The question I keep coming back to is this: if I gave a strong engineer two weeks and an API key, could they rebuild 80% of this product?

If the answer is yes, you're looking at a dead zone company. The technology is real, the product works, the customers are happy, and none of that matters, because defensibility doesn't come from building something that works. It comes from building something that's hard to replicate.

VCs are now looking for three types of moats that survive the foundation model tsunami. First, proprietary data moats, where each new customer or interaction makes the product smarter in ways a generic model can't match. Think specialized medical imaging data, construction project histories, legal precedent databases. Second, workflow moats, where the product is so deeply embedded in an industry's daily operations that ripping it out would be like replacing a database migration mid-flight (yes, I'm still having nightmares about that one time). Third, vertical depth, where the team doesn't just understand AI but understands, say, commercial insurance underwriting at a level that would take a generalist AI company years to develop.

The uncomfortable question for people like me

Let's be real. I've recommended deals that were probably dead zone companies. Early in my VC career, I saw a sharp team, a working demo, and strong early traction, and I thought that was enough. Sometimes it was. But in this market, where the underlying models improve on a quarterly cadence and the platform companies are aggressively expanding into every vertical, "working product with traction" is table stakes, not a thesis.

The hardest part of evaluating AI startups in 2026 is that the good ones and the dead zone ones look almost identical at seed stage. Both have smart founders. Both have growing revenue. Both can demo something impressive. The difference is in the technical plumbing, in the data pipeline, in the architecture choices that determine whether this company compounds over time or gets commoditized.

That's an engineering judgment call, not a financial one. You can't find it in the cap table or the revenue model. You find it in the codebase, in the data strategy, in the answer to "what happens to your product when the next model generation drops?"

AI startups convert pilots to purchases at a 47% rate, nearly double the 25% rate for traditional SaaS. That's a real signal. But the dead zone companies convert just as well, right up until the moment the platform eats their lunch. The conversion rate doesn't tell you whether the product survives. The architecture does.

Where this leaves us

I don't think the dead zone means AI startups are a bad bet. Far from it. The companies that are building on proprietary data, embedding deeply into workflows, and solving problems that require genuine domain expertise alongside AI capability? Those companies are going to be monsters. The opportunity is enormous, probably the largest venture opportunity since cloud computing.

But the window for "prompt pipeline stapled to a UI" as a fundable business is closing fast. If you're a founder reading this, the question isn't whether your AI product works. The question is whether it'll still work when the model you built on gets 10x better and costs 10x less and ships with the features you're charging for.

And if you're an engineer thinking about crossing into VC, or already here like me, this is your moment. The ability to pop the hood on an AI startup and tell the difference between a real engine and a nice paint job? That's the skill set that separates useful investors from the rest of us right now.

I'm still learning how to do it well. The dead zone is humbling. It means some of the smartest founders I've met are building companies that won't survive, and some of the most boring-sounding pitches (another vertical data platform, another compliance automation tool) might end up being the fund returners.

The market doesn't care if the demo is cool. The market cares if the moat is real.

— SWEdonym

Login or Subscribe to participate

Reply

Avatar

or to participate

Keep Reading