Building developer tools usually goes like this: build the functionality first, make it fast, then worry about the experience later. Ship the API, then document it. Launch the platform, then polish the onboarding. Get the features out, then clean up the rough edges. This made sense in an era when developers had limited options. But we’re not in that era anymore.

Today’s a lot of engineering problems have multiple tools, often robust open source alternatives exist. Cloud infrastructure makes migrations easier so the trend is in favour of switching costs which are increasingly coming down or non-existent for some cases. Human attention, on the other hand, is a scarce resource, much like compute power these days.

Take the example of Stripe which entered the payments market with their famous 7-line integration which was concise but also complete. Test mode, live mode, error handling, webhook setup. Developers could copy, modify, and have a working integration and reach their Aha moment in a few minutes. Even though it didn’t have the most comprehensive feature set. What they had was an integration experience that took minutes instead of weeks. They weren’t first. They weren’t cheapest. And this initial experience triggered a cascade.. word of mouth spread, blog posts appeared, conference talks referenced this as an example of “how APIs should work.” and over time Stripe has built a benchmark in DX.

Some other examples - Vercel’s deployment experience. Tailwind’s documentation. Supabase’s onboarding. Made them grow quickly because it impressed developers who then would spread out the word - productivity brag! But that’s just the entry point. The real difference shows up when companies keep creating these word-of-mouth-worthy experiences across the rest of the product. That’s what actually drives long-term retention. And that’s where DX starts turning into a moat.

This matters even more now with AI. When every tool can spin up a decent baseline experience, that just becomes the table stakes. So in a world where building SaaS is getting cheaper and faster, UX isn’t just how you enter a market anymore (like Stripe or Linear did), it’s also how you keep users around.

It becomes a moat because it’s genuinely hard to do consistently. It shows up in the small decisions. It takes years. Most users won’t consciously notice it, but they’ll feel it. And it requires clear principles guiding thousands of tiny decisions across the product.

And those decisions only work when product, engineering, go-to-market, DevRel, support and all other functions are pulling in the same direction. Not just for one launch, but over years. Most companies struggle with this because scaled coordination is hard and incentives don’t always line up.