# Landscape Mapping

How to systematically map a competitive space.

## Search Order

1. **Solana ecosystem** — solana-new catalogs (repos, skills, MCPs)
2. **Broader crypto** — Ethereum, Base, Arbitrum, Sui equivalents
3. **Hackathon projects** — Colosseum, ETHGlobal, Superteam submissions
4. **Dead projects** — GitHub archives, shut-down announcements, post-mortems
5. **Non-crypto substitutes** — Traditional tools solving the same problem

## For Each Competitor, Capture

| Field | What to Record |
|-------|---------------|
| Name | Project name and tagline |
| URL | Website or GitHub |
| Status | Live / Beta / Dead / Pivot |
| Chain | Solana / Ethereum / Multi-chain / Off-chain |
| Users | Estimate: daily active, TVL, GitHub stars, social followers |
| Strength | What they do well |
| Weakness | Where they're vulnerable |
| Threat Level | Low / Medium / High |

## Competitive Matrix Layout

Organize competitors on two axes:
- **X-axis**: Scope (narrow tool → full platform)
- **Y-axis**: Target user (developer → end consumer)

This reveals which quadrants are crowded and which are open.

## Crowdedness Scale

- **Empty**: No projects found. Either the idea is novel or the search was bad. Verify.
- **Sparse**: 1-2 early-stage projects, none with traction
- **Moderate**: 3-5 projects, some with traction but no clear winner
- **Crowded**: 5+ projects, at least one with strong traction
- **Saturated**: Many projects, a dominant winner, high switching costs