What Makes a Business Unbreakable When Software Costs Nothing to Build
- 01Theme 1: AI Destroys Effort-Based Moats, But Cannot Compress Time
- 02Theme 2: Operational Data Loops Are the New Data Moat
- 03Theme 3: Regulatory Access Is a Multi-Layered, Durable Moat
- 04Theme 4: Physical Infrastructure Creates Irreversible Head Starts
- 05Theme 5: Moat Stacking
1. Key Themes
Theme 1: AI Destroys Effort-Based Moats, But Cannot Compress Time
The core thesis is that AI has eliminated the competitive buffer that used to come from building complex software. What remains defensible is anything that requires real time to accumulate — trust, data, physical infrastructure, regulatory relationships.
"AI can fake effort. It cannot fake time. You can write code faster. You cannot speed-run earning a customer's trust. You cannot prompt-engineer a physical supply chain. You cannot generate a community of loyal users overnight."
Theme 2: Operational Data Loops Are the New Data Moat
Static data advantages are eroding — models improve, synthetic data fills gaps. What survives is data that is generated continuously as a byproduct of operating the business, creating a compounding loop competitors can't shortcut.
"The moat is not the dataset. It is the operational process that keeps producing it... If the advantage were the data itself, they could try to buy it or simulate it. When the advantage is operational, they have to replicate the entire system that generates it, matching volume, consistency and real-world exposure over years."
Theme 3: Regulatory Access Is a Multi-Layered, Durable Moat
The article reframes regulation not as friction but as a compounding advantage. The first layer is licenses and clearances. The second — and more durable — layer is the institutional muscle built while earning that permission: auditable systems, cleared teams, procurement relationships, and hard-won trust.
"Writing code is something you can accelerate. Earning permission to deploy that code in consequential systems is not. The timeline is set by institutions. Those clocks do not move faster because the technology does."
Theme 4: Physical Infrastructure Creates Irreversible Head Starts
As the "endgame is increasingly physical," the gap between what can be designed quickly with AI and what can be deployed in the real world is where durable advantage lives. Permits, supply chains, manufacturing yields, and grid connections all move on their own timeline.
"That gap between what you can design and what you can build is where the advantage lives... The companies that accepted those constraints early and started building anyway carry a lead that increases every month others wait."
Theme 5: Moat Stacking — The Most Defensible Businesses Layer Multiple Constraints
The most important structural insight is that the leading companies aren't relying on one moat — they're compounding multiple time-gated advantages that reinforce each other, making competitive catch-up require simultaneous progress across several fronts.
"Replicating the position becomes hard not because any single element is unbeatable but because catching up requires time across several fronts simultaneously... Single moat companies are more exposed than they look. Pressure on one dimension with no other layer to absorb it is a real vulnerability in a world where AI compresses timelines on individual advantages faster than before."
2. Contrarian Perspectives
Perspective 1: More Data Is Not a Moat — Static Datasets Are a Liability
The popular view in tech is that whoever accumulates the most data wins. The article challenges this directly: size of a dataset is not the defensible asset. A static dataset can be approximated, bought, or bypassed with synthetic data. Only continuously replenishing operational data is genuinely defensible.
"Having the most data is not a real moat... Models improve. Synthetic data fills gaps. What once looked like a defensible edge turns into a baseline that anyone can approximate given enough time and computing power."
The article substantiates this with Tempus AI: its 45 million patient records and 400+ petabytes of data are defensible not because of their size, but because they are generated fresh by genomic sequencing labs running every day — a process competitors cannot simulate.
Perspective 2: Regulation Is a Competitive Weapon, Not Just Friction
The conventional tech founder instinct is to view regulation as an obstacle to route around. The article argues the opposite: in high-stakes domains (defense, healthcare, finance), the process of earning regulatory permission builds a second moat — institutional knowledge, cleared personnel, auditable infrastructure — that is arguably harder to replicate than the license itself.
"There is a persistent instinct in tech to treat regulation as friction... That instinct worked in domains where the downside of failure was limited. It holds much less in systems where getting it wrong is measured in lives, capital, or national security."
Shield AI's case is instructive: it turned down a significant early investment to preserve its defense focus, and by 2025 held contracts across Romania, Japan, Greece, Canada, and the US Coast Guard — each contract compounding the next.
Perspective 3: Capital at Scale Has Become a Structural Moat, Not Just Fuel
The common framing is that capital is a resource you deploy to build the real advantage. The article argues that in a world racing toward physical AI infrastructure, the ability to credibly raise and deploy capital at scale is itself the moat — earned through years of execution history that new entrants cannot fabricate.
"In a world where the endgame is increasingly physical, capital at scale has started behaving like a moat in itself... Investors fund projects at this scale when they believe the team can execute over long time horizons and that belief is earned through years of delivering on increasingly complex systems."
Evidence: Amazon committed ~$100B in capex in 2025, Microsoft guided $80B. Once that infrastructure exists, smaller players "operate on top of a layer they do not own."
3. Companies Identified
Tempus AI
- Description: AI-driven healthcare company running genomic sequencing labs
- Why mentioned: Prime example of an operational data moat — not just aggregating data, but generating new molecular data tied to patient outcomes daily
- Quote: "By 2025, they had accumulated 45 million patient records across more than 400 petabytes of data. Revenue was growing at roughly 85% year-over-year... Every additional test expands the dataset in ways that improve diagnostic models, making the platform more valuable to the next clinician and the next researcher."
- Description: Global payments network processing billions of transactions daily
- Why mentioned: Classic example of an operational data flywheel — transaction volume trains fraud detection models in ways no generalist AI can replicate without equivalent history
- Quote: "Mastercard processes billions of transactions daily, continuously training fraud detection systems on patterns that only emerge at that volume. Patterns no generalist model can replicate without equivalent transaction history."
- Description: Collaborative design platform for UI/UX and product teams
- Why mentioned: Best current example of a product becoming embedded infrastructure across multiple organizational roles, making switching a systemic — not individual — decision
- Quote: "Replacing Figma would not mean adopting a different design tool. It would mean unwinding shared systems and rebuilding coordination patterns across the entire organization. By mid-2025, it had 10,000+ community-built plugins and was embedded in 95% of Fortune 500 companies."
- Description: Defense technology company building AI-enabled military systems
- Why mentioned: Showcases stacked moats — regulatory access + operational data from deployed hardware + institutional relationships + capital credibility, culminating in a ~$20B US Army enterprise agreement
- Quote: "In early 2026, the US Army consolidated over 120 separate procurement actions into a single enterprise agreement with Anduril, a fixed-price, multi-year deal with a ceiling of roughly $20 billion... What made that unification possible was everything underneath it. Years of working inside the system, building integrations that hold up under real conditions, maintaining cleared teams."
Shield AI
- Description: Defense AI company focused on autonomous military systems
- Why mentioned: Illustrates how early conviction in a regulated domain — and willingness to turn down capital to protect focus — compounds into an international network of defense contracts
- Quote: "Shield AI turned down its first significant investment because accepting it would have required abandoning its defense focus. That stubbornness paid off. By 2025 it held contracts with Romania, Japan, Greece, Canada and the US Coast Guard."
- Description: Aerospace manufacturer and satellite internet provider
- Why mentioned: The clearest example of moat stacking — physical infrastructure (rockets), capital-at-scale credibility, and a global data/connectivity network all reinforcing each other
- Quote: "Starlink generated an estimated $10.6 billion in revenue in 2025, giving SpaceX internal cash flow to fund everything else... Physical infrastructure, capital at scale and a global data network from Starlink intersect and reinforce each other. Starlink's revenue funds the next layer of infrastructure."
Tesla (Megapack)
- Description: Energy storage division deploying grid-scale battery systems
- Why mentioned: Example of how physical deployment experience compounds into cost structure, failure-mode knowledge, and supplier relationships that cannot be replicated by writing a larger check
- Quote: "Tesla has been deploying grid-scale battery systems for years, accumulating manufacturing efficiency, installation expertise and utility relationships that do not show up in a spec sheet... It is another data point on a learning curve that has been running for years, shaping cost structure, failure mode knowledge and supplier terms in ways a new entrant cannot replicate."
- Description: Chinese battery manufacturer; the world's dominant EV/energy storage cell supplier
- Why mentioned: Manufacturing-world case study in physical moats — vertical integration from cell chemistry to system integration, with yields and supply chain terms embedded through years of production runs
- Quote: "New entrants are not competing against where CATL is today. They are competing against where it will be by the time they catch up."
- Description: Data analytics and AI platform for government and enterprise
- Why mentioned: Institutional network effects example — government position built contract-by-contract through relationships, integrations, and trust accumulated over years
- Quote: "Its position in government is built on relationships, integrations and trust accumulated contract by contract, over years. Each deployment deepens the footprint and makes future contracts easier to win."
4. People Identified
The article does not name individual people beyond the newsletter's author. No named individuals are cited as experts, founders, or executives within the article's analysis.
Ruben Dominguez
- Description: Author of The VC Corner newsletter
- Why mentioned: Writer and analyst presenting the framework
- Quote: N/A — author attribution only
5. Operating Insights
Insight 1: Ask Whether Your Moat Requires Years to Accumulate — Not Just Whether It's Defensible Today
The article provides a sharp heuristic for evaluating competitive advantage: a moat that a well-funded team with good AI tooling could close in 18 months is real but temporary. The right test is whether replication requires years of real-world operating conditions.
"When you look at what protects a business, the right question is not whether it is defensible today. It is whether the things protecting it required years to accumulate. If a well-funded team with good tooling could close the gap in eighteen months, the advantage is real but temporary. If catching up requires years of operating under real conditions, you are looking at something that actually holds."
Insight 2: Design Your Business to Generate Data as a Byproduct of Operations — Not as a Collection Initiative
The article signals a concrete build decision: structure the business so that serving customers automatically produces proprietary, improving data. The flywheel must be operational, not curatorial.
"Every transaction, every interaction, every cycle of use produces new information that feeds back into the system. More usage leads to better data, which leads to better outcomes, which attracts more usage."
Insight 3: Deliberately Layer Moats — Stacking Is a Strategy, Not a Byproduct
The article's most actionable structural point is that founders should choose to build toward multi-constraint positions, even when individual components take longer to accumulate. Single-moat businesses are more fragile in an AI-accelerated world.
"This does not happen by accident. It comes from choosing, repeatedly, to build things that take time to accumulate rather than things that can be shipped quickly. The easier path is optimizing for speed. The harder path is committing to systems that only make sense over years."
6. Overlooked Insights
Insight 1: The Network Effect Cold Start Problem Has Gotten Harder, Not Easier
The article makes a subtle but important point that is easy to miss: cheap AI-assisted software development floods markets with feature-equivalent alternatives faster, which means the cold start problem for network-effect businesses has actually intensified. Getting to density is now more competitive, not less — making early-mover density advantages more durable, not less relevant.
"When building a product costs almost nothing, markets flood with well-executed alternatives that reach feature parity quickly. The challenge is no longer building something good enough. It is getting enough users, fast enough, for the system to sustain itself. Whoever already has density compounds. Everyone else burns capital trying to reach escape velocity."
Insight 2: Capital Credibility Is Itself a Compounding Asset
The article briefly notes — but doesn't dwell on — the idea that the track record of deploying large capital effectively creates a feedback loop that lowers the cost of future capital and increases deployment flexibility. This is distinct from simply having capital; it's about the institutional credibility that makes capital accessible on favorable terms over time.
"Teams that have proven they can deploy large sums effectively raise faster, at lower cost and with more flexibility. That feeds back into execution, which strengthens the case for the next raise. Building that track record is not something you can accelerate by being smart. It takes time and delivers results."