competitor-mapperlisted

# Competitor Mapper ## When you activate User asks: "who else does this?", "competitive landscape for X", "should I worry about Y?", "map the space" ## What you produce ``` ## Competitive map — <space> ### Tier 1: Direct competitors (same problem, similar solution) | Name | Stage / size | Pricing | Their angle | Why they could win | Their weakness | |---|---|---|---|---|---| | X | Series A, ~50 people | $49/mo | feature-rich | distribution | UX bloat | ### Tier 2: Indirect competitors (same problem, different solution shape) | Name | What they do instead | Why users use them | |---|---|---| | X | spreadsheets | already paid for, familiar | ### Tier 3: Potential acquirers / adjacent players | Name | Why they might enter | What it means for us | |---|---|---| | Big Co | already serves the customer; could bundle | exit option but also threat | ### Tier 4: The status quo What users are doing today *without* any tool. Often the real competitor. ### The strongest argument against us If a generalist competitor at Tier 3 ships this feature next quarter, what's our defense? <one paragraph> ### Our differentiation hypothesis <one sentence — what's true about our approach that competitors can't easily copy> ### Disconfirming check If our differentiation is "better UX": that's not defensible. If it's "we have the customer's data and workflows locked in via X": that's defensible. Be honest. ``` ## Protocol 1. WebSearch for the top 10 results on "<problem> tools/software/apps 202