The moat isn't the model. It's the mud on your boots.

Everyone in the vertical SaaS conversation right now is talking about Agentic AI — and they should be. The speed of development and innovation within the AI space is unprecedented. Large horizontal SaaS providers simply cannot iterate with the agility and effectiveness required to serve specific industries with the depth those industries demand. I firmly believe that vSaaS providers, building focused and immensely valuable modules that either enable or deeply rely on Agentic AI, are uniquely positioned to lead the next phase of enterprise software.

At NXT, we are building Agentic AI environments across multiple verticals as part of a vSaaS wedge strategy. The capabilities are real and they are accelerating.

But here is what I continue to come back to — and what the market continues to underweight: the technology is the accelerant. It is not the fire.

The fire is operator knowledge.

True vSaaS is more than well-written code. It involves workflows and feature sets built on real-time insights into lead generation, sales cycles, vendor relationships, payment dynamics, and all the other vital components of a thriving company within a specific industry. No matter how skilled the software engineering team or how advanced the tech stack, a platform will inevitably fall short if it is not developed through an iterative process grounded in real-world, daily experience within the industry it serves.

This is a conviction I hold not from theory but from the field. When we venture into a new industry, our approach involves becoming a participant first — as a retailer, distributor, or operator. We develop software to empower our team in lead generation, sales processing, order fulfillment, service requests, regulatory compliance, and logistics management. Only then do we have the right to build technology for that vertical. Only then does our software carry the weight of authentic operational understanding.

There is a version of vertical SaaS — and increasingly, of AI-powered vertical software — that looks clean on paper. You identify an underdigitized industry, map its workflows, build elegant software, deploy AI agents, and go to market with a wedge product. It is a well-understood playbook and a good one. But what it misses, and what I believe separates the companies that achieve lasting dominance from those that plateau, is the depth of industry fluency that only comes from operating inside the problem.

The most durable software companies are starting to look less like technology companies and more like firms. Like organizations where institutional knowledge, accumulated through years of practice within an industry, is the primary asset — and technology is the mechanism through which that knowledge is delivered and monetized at scale.

The code is important. The AI models are important. But they are expressions of something deeper: a proprietary understanding of how an industry actually works, developed through immersion, not observation.

I think about it like a foxhole.

There is a reason the bonds formed in foxholes are among the strongest that exist. It is not because the people in them chose each other. It is because they shared something that cannot be faked — the discomfort, the uncertainty, the daily reality of facing the same conditions together. You do not earn trust in a foxhole by showing up with a better map. You earn it by being there. Muddy. Tired. Shoulder to shoulder.

The same principle applies to building technology for an industry. When you have sat with a frustrated customer whose order was botched by a fulfillment process that the rest of the industry simply accepts as normal. When you have personally negotiated shipping rates and watched the margin math change overnight. When you have stared at your own dashboard trying to understand why a retention metric moved in a direction it should not have. When you have dealt with a vendor's legacy system that operates on logic only an insider would recognize as rational — that is when you start to understand what the software actually needs to do. Not what it could do in a demo. What it needs to do on a Tuesday afternoon when everything is going sideways.

And critically, that is when your customers — your future technology subscribers — begin to trust you. Not because you have a product. Because you have shared their experience. You have been in the foxhole with them. You understand the mud.

This is the intangible moat.

Technology can be replicated. Models are increasingly commoditized. Features can be copied. But the accumulated, compounding knowledge that comes from years of operating within an industry — the pattern recognition, the relationship capital, the instinct for what matters and what does not — that compounds in ways that code alone never will. The stickiness and long refresh cycles inherent in vertical software are a direct reflection of the depth of these relationships. Customers stay for decades when they believe their software provider understands their world — not just their workflow.

This is also why the vSaaS wedge model works. When you enter an industry as an operator, the wedge is not merely a product — it is credibility. You solve one painful workflow because you have lived that pain yourself. That earns you the right to solve the next one. And the next. Each module you deploy is informed by the same operational DNA, and each new capability reinforces the trust that was earned in the trenches. The AI agents you build are trained not on generic data but on proprietary knowledge acquired through daily participation in the vertical. The wedge deepens because the understanding deepens.

I am convinced that the most durable vertical SaaS and Agentic AI companies will not be built by pure technologists entering industries from the outside. They will be built by operators who have earned the right to automate — who have built credibility through years of facing the same daily, mundane, unglamorous challenges as the people they intend to serve, and who then apply technology as a force multiplier on that hard-won understanding.

The operator-to-SaaS path is slower. It is messier. It requires you to build a real business before you build a software business. But the moat it creates is qualitatively different from anything you can engineer from a standing start. It is a moat built on relationships forged in shared difficulty. On product intuition earned through operational scar tissue. On an industry's willingness to trust you with their workflows because they watched you struggle with the same ones.

Technology is the right accelerant for monetizing industry experience. But the experience has to come first. The relationships have to come first. The credibility that only comes from being a student of the industry — from showing up every day and doing the mundane work alongside the people you want to serve — that has to come first.

The moat is not the model. The moat is the mud on your boots.