Durable moats.

AI is splitting software into the exposed and the entrenched. We advise companies built to capture the shift, not be captured by it.

Why moats matter now

Built to outlast the shakeout.

The next few years will separate companies with structural defensibility from those whose advantage was simply being first to build the obvious thing. We look for the former, and we price a sale on the strength of the moat, not the size of the feature set.

The list below is what we underwrite. Most great companies have one or two. The rare ones compound several.

The moats

Six sources of durable value.

Six moats that survive AI. Each holds for a structural reason, and each shows up in the financials as pricing power and retention.

Moat 01

Proprietary data.

Scarce, hard-won data that compounds with every customer and can’t be scraped, bought, or synthesized.

Why it holds under AI

As models commoditize generic knowledge, value migrates to the proprietary inputs they can’t reach. Whoever owns that data sets the limit on how good anyone’s product can get.

What it looks like

A decade of labeled outcomes, exclusive supply relationships, or a dataset competitors cannot reconstruct at any price.

Moat 02

Regulatory lock-in.

The compliance burden that protects the incumbent: rules that make switching expensive and new entry slow.

Why it holds under AI

AI lowers the cost of building software, not the cost of being audited. Regulated workflows stay sticky because the risk of getting them wrong is asymmetric.

What it looks like

Certifications, audit trails, and approval cycles embedded in the product; customers who can’t switch without re-certifying.

Moat 03

Network effects.

Value that grows with every participant: a network no new entrant can cold-start.

Why it holds under AI

A better interface doesn’t move a two-sided market. The liquidity is the moat, not the UI, and liquidity is the hardest thing to copy.

What it looks like

Marketplaces, multi-party workflows, and data that improves for everyone as each new customer contributes to it.

Moat 04

Transaction embedding.

Software that sits in the flow of funds: payments, billing, or capital running through the product.

Why it holds under AI

Once money moves through you, you’re load-bearing. Rip-and-replace risk climbs, and monetization compounds as the customer grows.

What it looks like

Embedded payments, take-rate revenue, or working-capital and credit products underwritten on proprietary data.

Moat 05

System of record.

The database the business runs on: where the canonical data lives and every other tool reads from.

Why it holds under AI

AI may capture the interface, but the system of record owns the data underneath. The agent still has to write back to you.

What it looks like

The ERP, PMS, or ledger of an industry: the source of truth that downstream applications integrate against.

Moat 06

Control point.

The operational layer customers build around: not an app they use, but the rail everything else runs on.

Why it holds under AI

Control points accumulate workflow gravity. As an ecosystem forms around them, displacement means rebuilding everyone’s integrations, not just one vendor’s.

What it looks like

The platform third parties plug into; the workflow others extend rather than replace.

How the moat gets built

The control points underneath the moat.

Moats are the outcome. Control points are the mechanism: the specific ways vertical software earns a position competitors can’t dislodge. We use these eight patterns to pressure-test how durable an advantage really is.

Pattern 01

Incremental demand

Software that brings the customer more revenue: new demand, better conversion, or additional sales channels.

Demand generation beats pure efficiency
Pattern 02

Bring in funds

Embedded credit, insurance, or working capital that gives customers financial access.

Sticky when underwriting is hard
Pattern 03

Success take-rate

The vendor shares in customer success through payments, take rates, and revenue-linked products.

The vendor grows as the customer grows
Pattern 04

Consumer layer

Improving the end-customer experience across a fragmented value chain.

Workflow gravity outside legacy systems
Pattern 05

Integrate & surround

Don’t rip out the legacy system. Integrate, extract its data, and build the modern layer around it.

Wins where the PMS / ERP is entrenched
Pattern 06

Industry ledger

A cross-stakeholder source of truth spanning suppliers, employees, consumers, and regulators.

Leaps over company-specific records
Pattern 07

Run & do the work

AI moves the software from administering a workflow to actually executing the task.

The system-of-action evolution
Pattern 08

The ecosystem

Third parties and industry participants build directly on the vendor’s platform.

Platform economics reinforce gravity
For founders weighing a process

Have a moat? Let’s price it.

30 minutes with the senior team. We’ll tell you which of these you actually have, and what it’s worth to the right buyer.

Schedule a Working Session
Newsletter

Quiet Leverage.

The deal terms that quietly move value, monthly, from Shane. No spam, no marketing, no padding. Just the writing that founders actually keep.

or Follow on LinkedIn →