My partner Jim has a line I keep coming back to: "code is not the moat." It is certainly true today, and really, it has been true for a long time now. For many years it’s been possible to develop code fairly quickly, or replicate it, but for a long while there was at least a “head start” to code. These days, and it’ll get even more true with every passing day, that head start has shrunk down to nothing.
So, it begs the question - what is the “moat”, and do any exist any longer? Obviously, everyone is looking for moats outside of code: data, hardware, services, distribution, relationships, etc. But is there any opportunity for software to still deliver a “moat”? In a way, I would say yes - and I don’t think it is as much about how embedded a platform is (though that helps, I think that moat will grow shallower over time too) - but it’s not quite the same type of “moat.” I think, though, that there is a similarly strong value driver - maybe more so - which is consistent strength in product development.
Product development, and product management in particular, matters more than it has in years. Not because the product itself is the moat, but because deep customer, market and technology understanding - ultimately … product judgment - is what will really keep companies ahead and growing fast in this new world. In fact, the company performance data we've seen recently supports this case, with the fastest-growing companies typically spending more on product development than the average.
Code Was Never Much of a Moat (It Just Bought You Time)
A few years ago, a decent code base around a good idea gave you a head start. Code took time and effort to write, and that friction created a little breathing room. But code itself wasn’t the challenge - it was the underlying understanding of the customer’s problem and how to solve it with technology. Today, code replication is easier than it has ever been, and the tools keep improving - but smart problem solving is still very valuable.
Now, a quick distinction, because "moat" gets used loosely. The things we see that are often actually distinctive for a software business are often structural and really are built up over time: proprietary and learned data, deep integrations, domain logic that took years to encode, customer trust, bespoke relationships. (If you read my Defensibility series, you'll recognize much of that list.) Those are the benefits of incumbency that get built up over time. But without continued smart innovation, those benefits can erode quickly in today’s market.
The Product Dev Race
In some ways, an interesting analogy is a treadmill - and that treadmill of product development has sped up a lot lately. It was always there - you had to keep innovating, because if you slowed too much, eventually you’d fall off. In the “old days,” the treadmill moved slowly enough that you could really refocus on other parts of the business, while cruising on the treadmill: reach a certain scale and leverage the core of the existing code base for some time, while you redirect your energy to sales or marketing. Obviously, all companies need to focus more holistically as they grow, and they start to mature their product development efforts, but I just don't think that's possible for very long anymore. Competitors, from AI-native upstarts to the incumbents that have been there for a while, are all more within striking distance. Stalled product quickly gets lapped.
The Shift in the Bottleneck
For most of software's history, the scarce resource was engineering throughput. You had a long list of things worth building and limited ability to build them. AI coding tools actually flip that constraint. The new bottleneck is judgment and product management: understanding the market, the customer, the problem and the available toolkit, well enough to know which problems to solve, in what order, and how to deliver a solution that's secure, simple and solves the problem.
This is where product management earns its keep, and its scope keeps widening. Choosing what to build and when to build it - and what doesn’t get built - is the competitive advantage. Teams with deep customer & market understanding, with strong judgement, compound their data, their integrations, and their customer relationships with each release. Teams without it just run faster in the wrong direction.
How an Upstart Wins
None of this means incumbents have it easy, and I'd argue that upstarts have a real opening. But it takes discipline and focus. Strong delivery of value for customers, with continued innovation that delivers more value against adjacent problems, delivers an opportunity to take space from those incumbents and yields a greater share of their wallet. That share of wallet grows through product, and that's growth you can't manufacture from sales and marketing alone. It's the same discipline whether you're an upstart building out from an initial wedge, or an established company extending there from a broad position of strength.
What About Go-to-Market?
To be clear, I'm not arguing against go-to-market investment. As a company scales, it should mature its sales and marketing, and the right balance between the two is one of the hardest calls a management team makes. My point is narrower. For years, more “growth-stage” companies often focused more on go-to-market and less on product. I think that is changing in this new world, and that product needs to remain a serious part of the investment, with a solid balance across the organization - which is not an easy task.
It's tempting to think this is a story for the outlier outcomes, the unicorns that never stop building, but I don't think so. Companies that compound steadily, growing and expanding in their markets without making headlines, face the same pressure. The companies that decide well what to build, and keep building it, will be in the strongest position in whatever market they play in. As mentioned above, the data we've seen supports this dynamic. If you want to review our latest private software growth index data, you can find it here.
The code isn't the moat. But the judgment behind what gets built, release after release, is what keeps value growing.