LaunchWeek.ai

Back to Day 1: Position

Moats & Defensibility: Why Customers Won't Leave (and Competitors Won't Catch Up)

Most founders skip thinking about moats until a competitor with $30M in funding clones their product in six months. Then they panic-add features, launch enterprise tiers they're not ready for, and watch churn climb. The fix isn't more features — it's having a deliberate moat from year one. Most early-stage SaaS has zero moat: features get copied in weeks, switching costs are zero, and "we're just better" is not a moat. The companies that survive the next decade have a deliberate, compounding source of defensibility built into the business model.

A working moat strategy answers: which moats are realistic for our category and stage, which one is our primary moat (you almost always have one — not five), how do we deepen it intentionally, and how do we communicate it without sounding paranoid. Done right, your moat lets you raise prices, slow features, and absorb competitive pressure without losing customers. Done wrong, you compete on price and feature parity forever.

This guide is the playbook for identifying, building, and deepening moats. Companion to Competitive Positioning, Category Creation Strategy, Vertical SaaS Positioning, and Pricing Strategy.

What Done Looks Like

By end of this exercise:

  • Honest assessment: do we have a moat, or is one realistic to build?
  • Primary moat identified (one — not a list of seven)
  • 2-3 year plan to deepen the primary moat
  • "Moat narrative" for fundraising / sales / hiring
  • Test for moat health (could a $30M competitor catch us in 18 months?)
  • Quarterly moat review on the leadership calendar

This pairs with Competitive Positioning, Category Creation Strategy, Vertical SaaS Positioning, Pricing Strategy, Pricing Packaging Tier Design, Pitch Deck, Market Sizing, Trust Center & Security Page, Customer Case Studies, Annual Contract Negotiation, Acquisition & Exit Strategy, Customer References, and Reduce Churn.

The Seven Moats (and Which Apply)

Most discussions of moats trace back to Hamilton Helmer's 7 Powers framework. They're roughly correct for SaaS in 2026 too — with adjustments.

Help me identify which moat is realistic for us.

The seven moats:

**1. Network effects**
Each new user makes the product more valuable to other users.
Examples: Slack (in-org), LinkedIn, Stripe Connect, Figma multiplayer.
SaaS reality: rare; usually only true at a specific layer (collaboration, marketplace).
Test: does adding the 1000th customer make the 999th's product better?

**2. Switching costs**
The pain of leaving exceeds the value of an alternative.
Examples: Salesforce (years of process customization), accounting software (data migration risk), HRIS (integrations with payroll/benefits).
SaaS reality: this is the most common B2B SaaS moat.
Test: how long does a typical customer take to leave even if they want to?

**3. Scale economies**
Bigger = cheaper per unit.
Examples: AWS, Stripe (volume pricing), Twilio.
SaaS reality: less common at indie scale; comes with $50M+ revenue.
Test: do we get cheaper per customer as we grow?

**4. Counter-positioning**
Incumbent can't copy us without cannibalizing their existing business.
Examples: Figma vs Adobe (browser-native vs desktop), HubSpot vs Salesforce (inbound vs outbound), Loom vs Zoom (async vs synchronous).
SaaS reality: powerful when it works; requires incumbent to have business model lock-in.
Test: if Salesforce/HubSpot/Adobe copied us tomorrow, would they hurt their existing revenue?

**5. Cornered resource**
Exclusive access to something rivals can't easily replicate.
Examples: proprietary data, exclusive partnerships, key talent, IP.
SaaS reality: less common; usually data network effects or domain expertise.
Test: do we have something a well-funded competitor literally cannot get?

**6. Process power**
Internal know-how compounded over time that's hard to copy.
Examples: Toyota production system, in-context: Datadog's reliability/scale of agents, Stripe's payment-orchestration depth.
SaaS reality: real but slow; usually shows up in operational margin and reliability.
Test: would a 50-person clone team replicate our last 5 years of operational learning?

**7. Brand**
Customers trust us / will pay more / will recommend.
Examples: Apple, Notion (consumer-grade B2B), Linear (developer trust).
SaaS reality: real but takes 5+ years; can't be the only moat.
Test: would buyers pick us over a cheaper, identical competitor?

For my company:
- Stage: [seed/A/B/...]
- Customer count: [N]
- Product category: [...]

Output:
1. Which moats are real for us today
2. Which are realistic to build in 3 years
3. Which are not realistic
4. Primary moat candidate

The pragmatic answer for most B2B SaaS: switching costs + counter-positioning are the two real moats you can build deliberately. Network effects and scale economies are mostly luck-of-category. Brand and process power compound slowly. Cornered resource is rare.

The Moat Audit

Before you can build a moat, you need an honest read of what you have today.

Help me audit my current moat.

The questions, answered honestly:

**Switching cost audit**:
- Average customer tenure today
- What does a customer have to do to leave (export data, retrain team, redo integrations)?
- How long does that take?
- How long does it take for a brand-new customer to "go live" with us?
- Net Revenue Retention (NRR) — proxy for switching cost / value
- Gross Revenue Retention (GRR) — proxy for involuntary churn / friction
  - GRR > 90% = real switching cost
  - GRR 80-90% = some switching cost
  - GRR < 80% = no switching cost

**Network effect audit**:
- Does the 100th user make the 99th user's experience better?
- Are there workspace-internal effects (more users = more value to that account)?
- Are there cross-customer effects (customers benefit from other customers using product)?
- If yes: how does that compound?
- If no: don't claim network effects

**Counter-positioning audit**:
- Who would be the natural copier? (Incumbents, hot-funded competitors)
- What would they have to give up to copy us? (Existing revenue stream, sales motion, partner channel)
- Is that giveup big enough to deter them?
- Honest answer: many startups think they're counter-positioned; few are

**Cornered-resource audit**:
- Do we have data nobody else has? (Unique sources, customer-shared data with consent)
- Do we have IP / patents that matter?
- Do we have key partnerships that are exclusive?
- Most early-stage companies: no, but this is okay

**Process audit**:
- What do we do operationally that took us 2+ years to figure out?
- Reliability, accuracy, latency, support quality
- Could a clone team match it in 6 months? In 24 months?

**Brand audit**:
- Do prospects ask for us by name? 
- Do we have category recognition? (G2 leader, customer reviews, founder brand)
- Would buyers pick us over a $5K-cheaper identical clone?

For my company: [data]

Output:
1. Today's moat (honest, not aspirational)
2. Strongest moat candidate
3. Weakest claimed moat (probably overstated)
4. Verdict: do we have a moat?

The honest verdict for most pre-Series-A SaaS: you don't have a moat yet. That's fine — moats compound. The question is which moat are you investing in. Picking is the strategy.

Primary Moat: Pick One

Founders love to claim five moats. "We have network effects AND switching costs AND brand AND data AND..." Almost always: you have one real moat and four nice-to-haves. Pick the one and over-invest.

Help me pick my primary moat.

The selection criteria:

**1. Realism**:
Is this actually defensible at our stage and resources?

**2. Compounds with growth**:
Does this moat get stronger as we get bigger?
- Switching costs: yes (more data, more integrations, more habit)
- Network effects: yes (each user adds value)
- Scale economies: yes
- Brand: yes (slowly)
- Counter-positioning: stable, not compounding
- Cornered resource: stable
- Process: yes (with deliberate investment)

**3. Aligned with category**:
Different categories have different natural moats.
- Marketplaces: network effects
- Workflow/CRM/ERP: switching costs
- Developer tools: switching costs + brand
- Analytics: data + switching costs
- Vertical SaaS: counter-positioning + process
- Infrastructure/platform: scale economies + switching costs

**4. Aligned with strengths**:
What are you good at building?
- Strong engineering team → process power, scale
- Strong distribution → brand, counter-positioning
- Strong data acquisition → cornered resource, network effects
- Strong customer-success → switching costs

**5. Doable in 24 months**:
You should be able to make material progress in 24 months.
"We will dominate in 10 years" is not a strategy.

For my company:
- Category: [...]
- Strengths: [...]
- Audit results: [...]

Output:
1. Top 2-3 candidate primary moats
2. Pick one
3. Why
4. What "primary moat win" looks like in 24 months

The most common pick for B2B SaaS at $1M-$10M ARR: switching costs. You're not big enough for network effects to matter, your brand is too new, you don't have process scale yet. Switching costs compound from day one — every customer you onboard makes their next migration harder.

Building Switching Costs Deliberately

Since switching costs are the most universal B2B moat, here's the build plan.

Help me build switching costs deliberately.

The five flavors of switching cost:

**1. Data lock-in**
Customer's accumulated data inside your product is too valuable to abandon.
Build: deep history, calculated metrics that recompute on data going back years, ML models trained on customer data.
Don't build: data that's easy to export — switching cost requires "data PLUS context."

**2. Workflow/process lock-in**
Customer's team has built processes around your product.
Build: customizable workflows, automations the customer wires up, role-based permissions specific to their org.
Examples: Salesforce process builder, Zendesk macros, Linear workflow automations.

**3. Integration lock-in**
You're plugged into their other systems; unplugging breaks things.
Build: deep two-way integrations with their other tools (HRIS, ERP, payroll, marketing automation).
This is why "10 integrations" matters — each integration is a switching-cost moat.

**4. Habit/skill lock-in**
Users know your interface; retraining is painful.
Build: keyboard shortcuts, distinctive UI patterns users internalize, certifications.
Examples: Excel, Photoshop, Salesforce admins (whole job category).

**5. Network/social lock-in (intra-account)**
The team has built shared context inside your product.
Build: comments, shared dashboards, cross-team workflows, threaded conversations.
Examples: Slack channels with years of history, Notion workspaces, Linear cycles.

Where to invest in next 24 months: [pick 1-2]

Tactical builds:
- Auto-imports for migrations (paradoxically: easy in = hard out)
- Annual contracts → habit lock-in by giving 12 months of usage
- Native integrations (start with top-3 customer integrations)
- Workflow customization that customers configure themselves
- Reporting that requires N months of historical data to be useful

Anti-patterns:
- Forcing data export to be hard — customers notice; harms brand
- Refusing integrations to "keep them captive" — makes you uncompetitive vs new entrants
- Switching costs ≠ user-hostile; they should be a side-effect of value, not friction

For my product:
- Current switching costs: [audit]
- Top opportunity: [pick]

Output:
1. 24-month switching-cost roadmap
2. Top 3 builds
3. Anti-patterns to avoid
4. Metric to track (NRR, GRR, average tenure)

The crucial framing: switching costs are a side-effect of value compounding, not a hostage strategy. If your customer says "I'd love to leave but you've made it impossible," your moat is fragile. If they say "I could leave but it would cost more than staying," your moat is durable.

Counter-Positioning: When Incumbents Can't Copy You

Counter-positioning is the most powerful moat when it works. The incumbent literally cannot copy you without hurting their existing business. Examples:

Help me identify counter-positioning opportunity.

The pattern:

Incumbent has business-model commitments that prevent them from copying us.

**Pricing-model lock-in**:
- Salesforce sells per-seat → can't switch to usage-based without revenue cliff
- Adobe sells perpetual → can't go SaaS without revenue smoothing painful
- Microsoft sells suite → can't unbundle without losing ASP

**Channel/sales-motion lock-in**:
- HubSpot built inbound; can't copy outbound-heavy without confusing brand
- Salesforce built field sales; can't go self-serve without channel conflict
- Big incumbents have $1M+ ACV motion; can't profitably serve $50/mo SaaS

**Architecture lock-in**:
- Adobe is desktop-native; can't go browser-native without rewriting and breaking 30 years of plugins
- Old vendors built single-tenant; can't go multi-tenant without rebuilding
- Pre-AI products built without AI as core; can't retrofit without architecture redo

**Brand lock-in**:
- Premium brand can't go low-end without hurting premium positioning
- Enterprise brand can't go SMB without confusing buyers
- B2C brand can't go enterprise without distrust

**Distribution lock-in**:
- Partner-channel-only can't go direct without channel revolt
- Marketplace-only can't go direct-sales without conflict

The test: "If incumbent X copied us tomorrow, what would they LOSE?"

If the answer is "nothing meaningful" → no counter-positioning
If the answer is "10%+ of revenue or strategic position" → counter-positioning real

For my company:
- Likely incumbent copiers
- Their commitments
- Our position relative to those commitments

Output:
1. Counter-positioning thesis (1-3 sentences)
2. Strongest copier and what they'd lose
3. Risk: are we wrong about their commitments?

The historical examples: Figma (browser-native vs Adobe desktop), HubSpot (inbound vs outbound-Salesforce), Square (small-business POS vs traditional banks), Zoom (consumer-easy vs enterprise WebEx). In all cases, incumbents literally tried to copy and failed because their business model couldn't absorb the change. That's a real moat.

When You Don't Have a Moat (and That's Okay)

Most early-stage SaaS doesn't have a moat yet. The question is: are you investing in one?

Help me think about no-moat status.

The honest cases:

**Pre-PMF (you don't need a moat yet)**:
- Goal is figuring out the product
- Moat investment now is premature
- Default behavior: build product, find users, iterate

**Post-PMF, pre-$1M ARR (start picking your moat)**:
- Have early signals product works
- Moat candidate becomes part of strategic decisions
- Annual contracts? Integrations? Workflow customization?
- Pick one to over-invest in

**$1M-$10M ARR (build your moat deliberately)**:
- Each product decision either compounds your moat or doesn't
- Hire, prioritize, partner around moat
- Track NRR and GRR religiously

**$10M+ ARR (defend and deepen)**:
- Competitor pressure is real
- Moat is your survival path
- Acquisitions, partnerships, IP all in service of moat

If you're at no-moat stage, the trap is:
- Claiming moats you don't have (in fundraising decks)
- Investing in 5 moats simultaneously (none deepens)
- Mistaking features for moats
- Mistaking brand for moat (it's a moat eventually, not yet)

The honest no-moat strategy:
1. Acknowledge you're competing on execution and speed
2. Build moat as side-effect of right product decisions
3. Communicate "compounding moat" not "we have a moat"
4. Track moat metrics quarterly

For my stage: [...]

Output:
1. Stage-appropriate moat strategy
2. What to claim publicly
3. What to invest in privately
4. Honest read of timeline

The thing investors hear most often: "we have network effects" from a 50-customer SaaS. Investors know you don't. The honest "we're building switching costs deliberately and here's how" is more credible and more strategic.

Communicating the Moat (Without Sounding Paranoid)

Your moat narrative is part of your company narrative. Used in: pitch deck, sales calls (when buyers ask "why won't you go away"), hiring (great engineers want defensible companies), customer renewals (subtly: "you're betting on us; we're investing in lock-in via deeper value").

Help me write the moat narrative.

The structure:

**1-sentence moat thesis**:
"As more customers integrate [X], their switching cost compounds — and our flywheel of [Y] keeps deepening."

**3-bullet defensibility**:
- Why we're hard to copy (specific to our category)
- Why we'll get harder to copy over time (the compounding angle)
- Why incumbents struggle (counter-positioning if applicable)

**Evidence**:
- NRR, GRR, customer tenure data
- Integration count
- Average integrations per customer
- Time-to-value vs time-to-leave

**The investor / employee / customer version**:

Investor (be precise): "Our primary moat is switching cost driven by [specific mechanism]. We're at NRR 115%, GRR 92%, average tenure 3.2 years. Competitors who've tried to enter our segment have struggled because [counter-positioning]."

Employee: "We're building a category-defining product. The thing that's hard for competitors is [moat] — and that's why your engineering work compounds."

Customer (subtle): "You're investing in us; we're investing in your stack. The deeper we integrate, the more value we deliver — and the harder it gets for either of us to walk away. We see that as a feature."

For my company: [data]

Output:
1. Moat thesis (1 sentence)
2. Pitch-deck slide
3. Hiring narrative
4. Customer-conversation language

The framing trap: founders pitch moats as "we have you locked in" — buyers and investors detect this and react badly. The right framing is "compounding value." The moat is a side-effect of compounding value; the language reflects that.

Moat Metrics to Track Quarterly

Help me set up moat metrics.

The metrics, by moat type:

**Switching cost metrics**:
- NRR (Net Revenue Retention) — target: 110%+ for SMB, 120%+ for mid/enterprise
- GRR (Gross Revenue Retention) — target: 90%+ SMB, 95%+ mid/enterprise
- Average customer tenure
- Integration count per customer
- Time-to-value (onboarding friction; lower = faster lock-in)
- Active integrations per account
- Custom configurations per account (workflows, fields, automations)

**Network effect metrics**:
- Active users per workspace (intra-account network)
- New-user activation rate when invited (vs cold sign-up)
- Cross-customer engagement (if applicable)

**Brand metrics**:
- Inbound demand share (organic traffic / branded search / referrals)
- NPS / G2 score / category leader status
- Founder/team awareness in target audience

**Counter-positioning metrics**:
- Competitive win rate vs incumbent
- Switching-from-incumbent customer count

**Process metrics**:
- Reliability (uptime, p99 latency)
- Support response time
- Customer time-to-resolution

The quarterly review:
- Are these metrics improving?
- If not, what's the moat investment lagging?
- What's our "if-the-moat-doesn't-deepen" backup plan?

For my company: [pick metrics]

Output:
1. 5-7 moat KPIs
2. Quarterly review template
3. Owner per metric
4. Target benchmarks

The single most important number: NRR. A B2B SaaS with 120% NRR is uncatchable; a B2B SaaS with 90% NRR is in trouble regardless of how clever the strategy looks. NRR is the moat measured.

Common Moat Mistakes

Help me avoid moat mistakes.

The 10 mistakes:

**1. Claiming five moats**
"Network effects + switching costs + brand + data + scale" = no moat thesis at all. Pick one.

**2. Mistaking features for moats**
A feature can be copied. A feature that creates switching cost is the moat — not the feature itself.

**3. Mistaking brand for current moat**
Brand is a long-term moat, not a current one. Don't claim it pre-revenue.

**4. Building "lock-in" instead of "value"**
Hostile lock-in (hard data export, missing integrations) hurts brand and invites regulatory pressure. Value lock-in is durable.

**5. Ignoring counter-positioning timing**
Counter-positioning works only when you're early. Once incumbent has copied, it's gone. Move fast.

**6. Network-effect cargo cult**
Most products don't have network effects. Saying "user-generated content!" is not the same as having compounding network value.

**7. Relying on one big customer = cornered resource**
Customer concentration is a risk, not a moat. Don't confuse them.

**8. Copying competitor's moat**
"Salesforce has switching costs, so we'll have switching costs!" — only if you have their distribution. Pick a moat that fits *your* shape.

**9. Not investing in the moat**
Identifying the moat is 10%; deliberately deepening it for 5 years is 90%. Quarterly review with budget allocation, not just slides.

**10. Patent-based "IP" moat for software**
Software patents are weak in 2026. Don't bet your moat on patent enforcement. Trade secrets, data, and process power are stronger.

For my company:
- Which mistakes are risks?
- Mitigation per risk

Output:
1. Top 3 risks
2. Mitigations
3. Founder accountability

The single most lethal mistake: claiming network effects when you don't have them. Investors fact-check. Employees sense the gap between pitch and reality. Customers don't care. You damage credibility for the moat you actually have (probably switching costs).

What Done Looks Like

A working moat strategy delivers:

  • Honest assessment of moat today (probably: "weak, but we know which one we're building")
  • Primary moat picked deliberately (one — not five)
  • 24-month plan to deepen it
  • Moat narrative for investors / employees / customers
  • Quarterly moat-metrics review on leadership calendar
  • Defensibility test: a $30M-funded competitor — could they catch us in 18 months? If yes, deepen the moat.

The proof you got it right: you can answer "why won't a competitor catch you?" in 30 seconds with specifics. Your team gives the same answer. Your investors give the same answer. Your customers feel the answer (without needing to articulate it).

See Also

← PreviousMission & Vision Statements: Write Ones Your Team Actually ReadsNext →Build a Pitch Deck — Even If You Never Plan to Raise