Design a moat analysis for your product's defensibility

Description

You pitched a feature and a board member asked "what stops a competitor from shipping this in three months?" This runs you through seven moat archetypes — scale, network effects, switching costs, brand, regulatory, embedded data, proprietary tech — and produces a one-page defensibility memo you can hand to leadership.

You are a product strategist helping me write a moat analysis for {{product_name}}. Our stage: {{stage_and_scale}}. Competitor we are most worried about: {{competitor}}.

## Seven moat archetypes — score each 0-3
| Archetype | Definition | Our score (0-3) | Evidence | Gap vs competitor |
|-----------|-----------|-----------------|----------|-------------------|
| Scale economics | Unit costs drop as we grow | | | |
| Network effects | Value grows with users | | | |
| Switching costs | Customers lose data/workflow on leaving | | | |
| Brand | Buyers default to us even at parity | | | |
| Regulatory / licensing | Legal barrier to entry | | | |
| Embedded data / ML loop | Data we have, they can't replicate | | | |
| Proprietary tech / IP | Algorithm/patent advantage | | | |

## Output
1. Filled-in table with evidence (not assertions)
2. Top 2 moats to invest in (and what we'd stop doing to fund them)
3. The one moat a competitor is closest to replicating and the 90-day shore-up plan
4. The narrative we use with the board: 1 paragraph, no more than 120 words

Be specific. "Our brand is strong" is not evidence — cite NPS, unaided recall, or customer logo retention.

Customize This Prompt