Selling Developer Experience When AI Changes the Rules

I’ve spent 20 years building tools for developers. Some as products, some as internal platforms, some as open source that a handful of people actually used. Through all of that, one thing stayed constant: developers are the hardest customers on earth.

They’ll rewrite your tool over a weekend just to avoid signing up. They’ll mass-migrate off your platform because of a single bad API decision. They’ll adopt your competitor not because it’s better, but because one blog post made it look cooler.

Now add AI to that mix. The DevEx product market is getting squeezed from four directions at once, and if you’re building developer tools right now, you should understand which walls are closing in.

What you built yesterday is free today

A year ago, you could charge for a code review bot. For a test generator. For a CLI that scaffolds boilerplate. Today? Claude, Copilot, and a dozen open source tools do all of that for zero dollars. The feature you spent six months building is now a prompt away.

This isn’t slowing down. Every month, the baseline of what AI gives away for free creeps higher. If your product is a thin wrapper around something a foundation model can do natively, you’re on borrowed time.

Developers got cheaper to please and harder to charge

Open source already trained developers to expect free tools. AI made it worse. Why would I pay for your fancy dashboard when Claude Code gives me the answer in my terminal?

The bar for “worth paying for” used to be convenience. Now convenience is table stakes. Your DevEx product has to solve something that free tools genuinely can’t touch. That’s a much smaller surface than it used to be.

The product surface shifted under your feet

Developers used to want UIs. Dashboards. Web apps with graphs. Now the best developer experience is often no interface at all. It’s an API that an AI agent calls. It’s a CLI that outputs structured data. It’s a config file that gets generated automatically.

If your DevEx product still assumes a human sitting in a browser clicking through workflows, you’re building for last year. The interface layer is collapsing. Agents are the new users, and agents don’t care about your beautiful design system.

Big companies stopped buying

This is the one that kills quietly. Large engineering orgs look at commercial DevEx tools and increasingly say: we’ll build it ourselves.

Sometimes your tool genuinely breaks at their scale. A thousand engineers hitting your code review bot reveals every edge case. But often it’s not even about bugs. Your tool doesn’t quite fit their monorepo, their deployment model, their specific flavor of CI. Close enough isn’t close enough when you’re standardizing across a thousand people.

And now there’s a third reason: building in-house got cheap. A senior engineer with Claude Code can prototype in a week what used to take a team a quarter. The NIH instinct that managers used to squash? It’s becoming rational. Why negotiate a vendor contract when you can just… build the thing?

So what survives?

Honest answer? I don’t know. And I don’t think anyone does right now.

But I can see the shape of something. The tools that lasted in my career weren’t the technically best ones. They were the ones where I felt like I belonged to something. Where trust built up between the people making the tool and the people using it. Not trust in the code. Trust in the humans behind it. That part is hard to prompt your way into.

Open source might be changing too. When someone can reproduce your tool with a good test suite and an AI assistant and an afternoon, what’s the moat? Maybe it was never the code. Maybe it was always the people.

And here’s what I keep coming back to: the users are shifting. Developers aren’t going away, but what they do is changing. And alongside them, AI agents are becoming primary consumers of the tools we build today. They call your APIs. They read your CLI output. They configure your systems. A whole new layer of DevEx tooling will emerge just to manage the complexity that agents themselves create. We’re not losing DevEx. We’re watching its audience transform.

Some of the things we’re building right now feel safe. They’re genuinely complex. AI can’t handle them today. But nothing I’ve seen suggests the improvement curve is flattening. What AI can’t do this year, it’ll probably handle in one or two. The complexity moat is real, but it’s shrinking. Betting your company on “this is too hard for AI” is a countdown, not a strategy.

Nobody has clean answers for any of this. The four walls I described are real. The squeeze is real. But so is the fact that every time developer tooling got disrupted, something new grew in the gap. I’ve seen it happen three or four times in 20 years.

Things will change. That much is certain. What comes next? We’ll see.