---
name: community-plan
description: Design community as an instrumented funnel stage. Use when "start a Discord" is the plan and nobody has said what it's for.
---

Treat community as a channel with stages and a number.

1. **Where it sits in the funnel.** What is it supposed to convert, and from what to what? "Engagement" is not an answer.
2. **The stages.** B2C: superfans → ambassadors → organic growth. B2B: champions → advisors → references → pipeline. Define what moves someone between them.
3. **The first ten people.** Named. Real. What you'll ask each of them to do.
4. **The weekly loop** — what you personally do every week to keep it alive, in hours. If it's more than you'll sustain in month four, redesign it now.
5. **The number** that tells you it's working.

Write to `02-b2c/community-plan.md` or `03-b2b/community-plan.md`, matching the fork called in `01-roadmap/gtm-map.md`. Be honest that this channel is slow before it compounds — a community plan judged on month-one numbers gets abandoned in month two.
