Developers loving your product and developers paying for it are two completely different things

Developer tools have the most enviable growth engine in software: product-led growth. An engineer tries it, loves it, and pulls it into their team — no salesperson, tiny acquisition cost, viral spread, and eventually the tool becomes a de facto standard. Atlassian is the legend of this motion. When it works, it looks unstoppable.

But there’s a gulf running straight through the middle of it — the gulf between developers’ love and the enterprise’s payment. A tool can sit on a mountain of free users and an intense community and still struggle to monetize, because the free version is already “good enough,” and the person who actually pays (enterprise procurement, weighing security, compliance, support, scale) runs on completely different logic than the individual who fell in love. “Many users” and “much money” are, in developer tools, often two different things.

The financials make the gulf concrete. Atlassian, already at ~$1.79B in quarterly revenue, still posts a GAAP net loss (~$98.39M) — driven largely by stock-based comp (~$408M that quarter, roughly 4× the loss), a reminder that here you must look past popularity to cash-flow quality net of SBC. GitLab, ~$264M/quarter, sits near break-even. Great products, long road to clean shareholder return. And there’s a second threat: cloud vendors can wrap a popular open-source project into their own hosted service and capture the monetization directly — the reason for several famous “open-source license wars.”

The gulf is also why revenue quality varies so wildly across seemingly similar dev-tool companies. Two can boast the same downloads and GitHub stars, yet one converts free enthusiasm into locked-in enterprise contracts while the other never crosses from adored to indispensable. Popularity is the top of the funnel; the moat is whether that popularity survives contact with a procurement department and a budget cut.

Then comes the plot twist that makes this chapter the first outpost of the AI story. AI coding assistants are changing how software is made — writing, testing, and debugging code. That’s an earthquake under every tool in this stack, with two opposite possibilities: AI could supercharge the incumbents, or a wave of AI-native newcomers could steal their communities overnight. So assess any dev-tool company past the hype: paid conversion, enterprise and large-customer share, NRR, and cash-flow quality net of SBC. A tool everyone loves, that’s hard to monetize and coveted by AI upstarts, can be a dangerous high-valuation trap.

This is Chapter 13 of “Compounding in the Cloud.”