Back to list
mattgierhart

prd-v03-moat-definition

by mattgierhart

PRD-driven Context Engineering: A systematic approach to building AI-powered products using progressive documentation and context-aware development workflows

9🍴 2📅 Jan 24, 2026

SKILL.md


name: prd-v03-moat-definition description: Assess competitor defensibility and define our own moat strategy during PRD v0.3 Commercial Model. Triggers on requests to analyze competitor moats, define our defensibility, assess switching costs, identify vulnerabilities, find wedge opportunities, or when user asks "what's our moat?", "how defensible are they?", "where can we compete?", "switching costs?", "defensibility", "who to target". Consumes Competitive Landscape (v0.2) CFD- entries. Outputs CFD- entries for competitor moats and BR- entries for targeting rules and our defensibility strategy.

Moat Definition

Position in HORIZON workflow: v0.2 Competitive Landscape → v0.3 Moat Definition → v0.3 Pricing Model Selection

Moat Type Taxonomy

Every moat falls into one of six types. Identify primary + secondary moats per competitor:

Moat TypeDefinitionStrong WhenWeak When
Switching CostsFriction to leave (data, workflow, contracts)Multi-year data, deep integrationsEasy export, monthly contracts
Network EffectsValue increases with usersTwo-sided marketplace, content platformSingle-player tool, linear value
Data/IPProprietary data or algorithmsUnique training data, patentsCommodity ML, public datasets
Brand/TrustRecognition, credibilityRegulated industry, high-risk decisionsLow-stakes, undifferentiated
Scale/CostVolume economicsInfrastructure-heavy, marginal cost near zeroLabor-intensive, linear cost
RegulatoryCompliance barriersCertifications required, government contractsNo compliance requirements

For micro-SaaS: Switching costs and brand/trust matter most. Network effects and scale rarely apply.

Moat Strength Tiers

Rate each competitor's defensibility:

TierCriteriaEvidence SignalsTargeting Implication
ImpenetrableMulti-layered moat, 10+ years data lock-in"Would take years to switch"Avoid direct competition
StrongSignificant switching friction, 1-2 year contractsHigh NPS + low churn despite complaintsTarget underserved segments only
ModerateSome friction, workarounds existChurn 5-10%, export optionsWedge opportunity exists
WeakEasy to replace, commodity offeringMonthly plans, high churn, price shoppingDirect competition viable
ErodingFormer strength decliningNew alternatives gaining shareAggressive targeting

Gate rule: Don't compete where incumbent has Impenetrable or Strong moat unless targeting segment they explicitly ignore.

Switching Cost Inventory

Quantify ALL switching costs — the sum determines moat strength:

Cost TypeHigh ImpactLow ImpactHow to Assess
Financial>6mo contract, early termination feesMonthly billing, no penaltyCheck pricing page terms
Time/Effort40+ hr migration, retraining<4 hr setup, familiar UXTrial the competitor
Data MigrationProprietary format, no exportStandard export (CSV, API)Test export function
Workflow RetrainingUnique methodology, team habitsStandard patternsRead onboarding docs
Integration ReworkDeep API dependenciesStandalone toolMap their integrations

Calculation: Sum hours + dollars. >$5K or >40hr = material switching cost.

Targeting Decision Framework

Use moat analysis to determine where to compete:

Moat Impenetrable/Strong → DON'T COMPETE HERE
                          ↓ unless
                          Target ignored segment (SMB, specific vertical)
                          
Moat Moderate → WEDGE STRATEGY
                ↓ identify
                Entry point that bypasses switching friction
                
Moat Weak/Eroding → DIRECT COMPETITION
                    ↓ execute
                    Feature + price attack on their core

Wedge Opportunity Signals

A wedge exists when:

  • Competitor moat doesn't apply to specific segment
  • One feature has LOW switching cost (can start there)
  • Integration allows coexistence (not replacement)
  • Price sensitivity > switching friction

Analysis Workflow

Step 1: Pull Competitor Data

Retrieve CFD- entries from v0.2 Competitive Landscape. For each competitor, you need: pricing, complaints, feature set.

Step 2: Identify Moat Type

For each competitor, determine primary moat type. Use evidence from reviews, pricing structure, integration depth.

Step 3: Rate Moat Strength

Apply tier criteria. Flag if insufficient evidence (Tier 4-5 confidence).

Step 4: Inventory Switching Costs

Complete the 5-category switching cost assessment. Quantify hours + dollars.

Step 5: Identify Vulnerabilities

Where is their moat weakest? Which segments do they ignore? What's eroding?

Step 6: Generate IDs

CFD entries (customer_feedback.md): Template: assets/cfd-moat-analysis.md

CFD-MOT-###: [Competitor] Moat Analysis — [Moat Type], [Strength Tier]

BR entries (BUSINESS_RULES.md): Template: assets/br-targeting.md

BR-TGT-###: [Targeting Rule] — based on [Competitor] moat weakness

Anti-Patterns to Avoid

Don'tDo Instead
"They're big"Specify which moat type + evidence
Assume low switching costQuantify: hours + dollars
Only analyze direct competitorsInclude Type 4-5 (workarounds, inertia)
Underestimate integration moatMap actual dependency depth
Ignore eroding moatsTrack signals: new entrants, complaints
Target where moat is strongFind the segment where moat doesn't apply

Output Requirements

Before advancing to Our Moat Articulation:

  • ≥3 competitors with moat type identified
  • ≥2 competitors with switching costs quantified
  • Moat strength tier assigned (with evidence)
  • Targeting decision per competitor (compete/avoid/wedge)
  • CFD-MOT entries created (≥3)
  • BR-TGT entries created (≥2)

Downstream Connections

ConsumerWhat It NeedsFormat
v0.3 Our Moat ArticulationWhere competitors are weak, what moats workCFD-MOT entries
v0.3 Pricing ModelWhat price points bypass switching frictionBR-TGT entries
v0.5 Red TeamRisks of competitor responseMoat strength tiers
v0.9 GTMPositioning against competitor moatsTargeting rules

Detailed References

  • Good/bad examples: See references/examples.md
  • CFD-MOT template: See assets/cfd-moat-analysis.md
  • BR-TGT template: See assets/br-targeting.md

Score

Total Score

75/100

Based on repository quality metrics

SKILL.md

SKILL.mdファイルが含まれている

+20
LICENSE

ライセンスが設定されている

+10
説明文

100文字以上の説明がある

+10
人気

GitHub Stars 100以上

0/15
最近の活動

1ヶ月以内に更新

+10
フォーク

10回以上フォークされている

0/5
Issue管理

オープンIssueが50未満

+5
言語

プログラミング言語が設定されている

+5
タグ

1つ以上のタグが設定されている

+5

Reviews

💬

Reviews coming soon