Playbook for building, growing, and sustaining online communities from zero to 10,000+ members with engagement frameworks and metrics.
| Platform | Best For | Pros | Cons |
|---|---|---|---|
| Discord | Dev/gaming/crypto communities | Rich features, free, real-time | Noisy, hard to search, onboarding friction |
| Slack | B2B, professional communities | Familiar, threaded, integrations | Expensive at scale, message limits (free) |
| Circle | Course/membership communities | Clean UX, spaces, events built-in | Paid, less real-time |
| GitHub Discussions | OSS projects | Near the code, async-friendly | Limited to dev audience |
| Reddit (subreddit) | Public discovery | SEO, massive reach | Less control, trolls |
📢 announcements (read-only, major updates)
👋 introductions (new members post here first)
💬 general (main discussion)
❓ help / support (Q&A, encourage helping each other)
💡 ideas / feedback (product input, feature requests)
🎯 show-and-tell (members share what they built)
🔧 off-topic (human connection, non-work chat)
── Staff/Mod channels (private) ──
🛡️ mod-log (actions taken)
📊 team-internal (strategy, planning)
Start with fewer channels. Add only when conversation naturally splits.
Goal: New member → first meaningful interaction in <24 hours.
| Metric | How to Measure | Healthy Benchmark |
|---|---|---|
| DAU/MAU ratio | Active users daily vs monthly | >20% for engaged community |
| Messages per active user | Total messages / active users | 3-10/week |
| Response time | Time to first reply on questions | <4 hours |
| Retention (30-day) | Members active after 30 days | >40% |
| New member activation | % of joiners who post within 7 days | >30% |
| Lurker ratio | Read-only members / total | <80% (some lurking is fine) |
Track weekly. Use Discord analytics, Orbit, Common Room, or manual sampling.
Criteria to join:
- Active for 60+ days
- Consistently helpful (answers questions, welcomes newbies)
- Aligned with community values
Benefits:
- Private channel with team access
- Early access to features/roadmap
- Swag, event invites, reference/resume credit
- Direct influence on product direction
Responsibilities:
- Welcome 3+ new members/week
- Answer questions in support channels
- Flag issues/toxicity to mod team
- Attend monthly ambassador sync
Start with 3-5 champions. Scale to ~1 per 200 members.
Rules (post in #rules, keep short):
Escalation: Warning → 24h mute → 7-day ban → permanent ban. Document everything in mod-log.
Tooling: Discord AutoMod for keyword filtering. Assign mod role to trusted members.
| Stage | Focus | Key Actions |
|---|---|---|
| 0→100 | Seed & personal touch | Invite individually, be in every conversation, DM everyone |
| 100→1K | Habits & rituals | Weekly events, onboarding flow, first champions |
| 1K→5K | Systems & delegation | Mod team, ambassador program, documented processes |
| 5K→10K+ | Culture & self-sustaining | Members help members, UGC engine, sub-communities |
Critical insight: 0→100 is founder-led. You personally invite, personally welcome, personally engage. There's no shortcut.
See references/ for onboarding message templates, mod guidelines, and metrics dashboard setup.