How defensible is your product, really?

You built something that works. Users like it. Revenue is growing. Then a competitor launches something similar, or a platform vendor adds your feature to their free tier, or an open-source project appears that does 80% of what you do. Suddenly the question isn't "does it work?" but "can it survive?"

Most teams don't think about defensibility until it's already under threat. By then the moat is either there or it isn't, and if it isn't, you're competing on features and price — which is a race you eventually lose.

The problem with gut-feel defensibility

Ask a founder what their moat is and you'll hear: "our technology", "our data", "our brand", "our team." These might be true. They might also be stories the team tells itself because the alternative — that anyone could build this — is uncomfortable to sit with.

Real defensibility is structural. It lives in switching costs, network effects, data assets that compound, regulatory barriers, integration depth, and ecosystem lock-in. It's not about being better. It's about being harder to replace.

The problem is that structural analysis requires examining your product from eight different angles simultaneously. Your team is good at one or two of those angles because that's where they live every day. The other six are blind spots.

Eight analysts, eight angles

The /moat-audit pipeline runs eight specialist analysts in parallel:

Moat Definition (Report 01) — What is the moat, really? Not the marketing pitch — the structural reality. Five dimensions: technology depth, data advantage, network effects, switching costs, and ecosystem integration. Each gets a depth assessment: shallow (replicable in months), moderate (replicable in 1-2 years), or deep (structural, possibly permanent).

Differentiators (Report 02) — What's unique and what's table stakes? Every claimed differentiator gets a defensibility rating: is this a feature that competitors could add next quarter, or is it an architectural advantage that requires rebuilding from scratch? The most dangerous finding is a "differentiator" that's actually table stakes — something you think is special that everyone else already has.

Competitive Set (Report 03) — Four-tier competitive landscape. Tier 1: direct competitors building the same thing for the same audience. Tier 2: adjacent products that could pivot into your space. Tier 3: platform vendors who could bundle your feature for free. Tier 4: open-source projects that could commoditize your technology. Each tier gets a feature matrix and threat timeline.

Competitive Pressures (Report 04) — Eight pressure vectors: pricing pressure, feature pressure, platform risk, talent competition, regulatory shifts, market timing, customer concentration, and technology commoditization. Each gets an urgency rating: monitor, prepare, or act now.

Innovation Pressures (Report 05) — What must be built next to maintain the moat? Not a feature wishlist — a strategic analysis of which innovations widen the moat and which are distractions. The distinction matters: building the wrong feature can actually narrow your moat by spreading resources without deepening defensibility.

Inflection Points (Report 06) — Market moments that shift competitive position. A regulatory change that favors or threatens you. A technology shift that makes your approach cheaper or obsolete. A competitor acquisition that changes the landscape. These are the events worth war-gaming because they change the rules.

Value Planes (Report 07) — Where does value accrue in the stack? Is it in the infrastructure layer, the platform layer, the application layer, or the data layer? Where you capture value determines who can compete with you and how. If your value is in a layer that's being commoditized, the moat is eroding even if the product is thriving.

Control Planes (Report 08) — What you actually control versus what you depend on. Six planes: data, computation, distribution, identity, integration, and pricing. For each: what's your perceived control versus your actual control? A product that depends on a single cloud provider's API for its core feature has less control than it thinks.

Report 00 is the executive summary — the overall moat score, the three most important findings, and the strategic action plan.

What makes this different from a SWOT analysis

SWOT is a brainstorm. This is a structured forensic analysis with specific frameworks, scoring rubrics, and evidence requirements. The moat definition uses five named dimensions. The competitive map uses four named tiers. The pressure analysis uses eight named vectors. Nothing is left to "strengths: we're innovative."

Every finding points to specific evidence in the codebase, the market, or the product architecture. "Our data moat is moderate" comes with the specific data assets, their replaceability timeline, and the competitive implications if they were replicated.

When to run it

Before fundraising. Investors will ask about defensibility. Have an answer that's structural, not aspirational.

When a competitor appears. The competitive set and pressure reports tell you exactly how worried to be — and where to invest to widen the gap.

Annually, as a strategy exercise. Moats erode. What was defensible two years ago might be table stakes now. The inflection point analysis catches the shifts before they arrive.

Before a pivot decision. The value plane and control plane analyses tell you which pivots strengthen your position and which abandon your existing moat.

---

Resources

Pipeline reference: /moat-audit — 9 reports, 8 specialist analysts, moat framework reference.

Related reading:

• 03. Documenting projects that don't document themselves — doc suite provides the foundation the moat audit builds on
• 07. How much does your infrastructure actually cost at scale? — cost structure affects defensibility

Download: Full toolkit (252KB) — all 16 commands, all 11 skills, installs in 30 seconds.

---

Part of the Claude Skills Library.