Barriers to entry collapsed across software categories, permanently raising the competitive intensity floor

The software companies that feel safest right now are, paradoxically, the most exposed. They built their competitive position on the assumption that what they had built was hard to replicate. Millions of lines of code. Years of accumulated integrations. Engineering teams numbering in the hundreds. The moat was complexity. Complexity just got cheaper.

This is not a temporary disruption. It is a permanent change in the competitive floor beneath every software category.

The Complexity Moat

For most of the software industry's history, the barrier to entry was the cost of building. A competitive product required a large engineering team, months (often years) of development, significant infrastructure investment, and the institutional knowledge that accumulates slowly inside organisations that have shipped production software at scale. Small teams could prototype. But shipping a real product, one that handled edge cases, scaled under load, integrated with existing systems, and survived contact with actual enterprise buyers, required resources that most startups could not assemble.

This was the complexity moat. Not a patent. Not a brand. Not a network effect. Just the sheer difficulty of building something that worked. And for a long time, it was enough. But "enough" had an expiry date that nobody checked.

At Schneider Electric, I worked on an IoT thermostat product where the complexity moat was practically visible. The product required hardware design, firmware engineering, cloud infrastructure, a mobile application, and the integration layer that connected all four. Each component was challenging on its own. The combination was formidable. Small competitors would occasionally appear with a clever interface or a cheaper device. But they could not replicate the full stack. The integration complexity was the barrier, and it held for years.

That barrier is dissolving now. AI coding tools and cloud platforms have made the integration work dramatically easier. What required a team of specialised firmware engineers, cloud architects, and mobile developers can increasingly be assembled by a smaller team using AI-assisted development in a fraction of the time. The complexity moat did not get breached by a smarter competitor. It got lowered by better tools available to everyone.

The Eight-Week Competitor

I advise a SaaS startup that demonstrated this shift in terms I found genuinely startling. Three founders. Eight weeks. A vertical CRM built to compete directly with an established player that had raised over forty million in funding and employed more than a hundred engineers.

The product was not a toy. It handled the core workflows, integrated with the standard tools their target customers used, and looked polished enough that prospects in early demos did not ask whether it was "real." But the quality was not the surprising part. Two years ago, building the same product would have required a team of fifteen and at least six months. I know this because I have been in rooms where those resource estimates were made, and they were not inflated. The work genuinely took that long with conventional development approaches.

The incumbent's response to learning about this new competitor was to cut prices. Which is always the last move before the moat drains entirely. Price cutting is what you do when you have no other differentiator. When your response to a new entrant is to make your product cheaper rather than better, you are announcing that the barrier was cost, not value.

When the barrier to entry drops, the barrier to differentiation rises.

The Competitive Floor

Here is what most incumbents have not absorbed yet. The barrier collapse is not a one-time event. It is a permanent change in the structure of competition. The competitive floor, the minimum level of product quality and capability required to enter a category, has risen. But the competitive ceiling, what it takes to win, has risen even faster.

I call this the competitive floor effect. Before the barrier collapse, the floor was low (anyone could build a prototype) and the distance between a prototype and a production product was enormous. That distance protected incumbents. But now the floor is much higher. A small team can build a production-quality product quickly. But the ceiling is also higher, because when everyone can build, building is no longer what differentiates you.

The new differentiators are the things that AI tools cannot generate from a prompt.

Domain expertise is one. Understanding the specific workflows, regulations, and pain points of a particular industry takes years of immersion. You cannot prompt your way to knowing that oil rig operators need buttons sized for gloved hands, or that hospital procurement cycles run on fiscal years that vary by state. I have spent twenty years across petroleum, aviation, SaaS, IoT, and consumer products, and the pattern is consistent: the teams that win are the ones that know something about their customers that cannot be found in a public dataset.

Data is another. A startup can build a competitive product in eight weeks. But it cannot build eight years of customer usage data, behavioural patterns, and trained models in eight weeks. Proprietary data, accumulated through years of actual customer interactions, is a moat that gets stronger over time. But only if the company is actually using it. Plenty of incumbents are sitting on gold mines of data they have never properly analysed, which makes them vulnerable in an entirely different way.

Distribution is the third. Building the product is now the easy part. Getting it in front of customers, earning their trust, integrating into their procurement processes, and building the relationships that enterprise sales require: none of that got easier because AI can write code faster. Distribution is still slow, expensive, and deeply human. But that is precisely what makes it defensible. The startup that builds in eight weeks still needs twelve months to build a sales pipeline.

The Uncomfortable Implication

The uncomfortable implication for every software company is this: if your competitive advantage was primarily the difficulty of building your product, that advantage is structurally weaker than it was twelve months ago. And it will be weaker still twelve months from now.

This is not a reason to panic. It is a reason to be honest about what your actual moat is.

At Schneider Electric, the real moat was never the firmware complexity. It was the relationships with HVAC distributors and the understanding of building management workflows that took years to develop. The complexity moat was the visible one. But the domain and distribution moat was the real one. The team spent most of its energy defending the complexity moat because it was easier to measure and easier to explain to executives.

The companies that will maintain their competitive position are the ones that can answer a simple question: if a three-person team could replicate our product in eight weeks, what would they still not have? If the answer is "nothing," the competitive position is already gone. If the answer involves domain knowledge, proprietary data, distribution relationships, or customer trust, those are the assets worth investing in.

The moat was complexity. Complexity just got cheaper. What remains is everything that was always harder to build than software.

Some of it takes decades. That is the point.