community

# community Run the community like a **product with a job**, not a vanity chat room. The space — a Discord server, a Telegram group+channel, a Circle — is the product. **Onboarding is activation, rituals are the feature, moderation is reliability, and one north-star metric tied to your purpose is the only number that matters.** A room with 5,000 silent members is a failed product, not a big one. Design the system around the conversation, not the conversation itself. ## When NOT to use — route instead | The ask | Route to | |---|---| | Stop *paying customers of a product/SaaS* from churning (win-back, lifecycle, NPS) | `retention` | | Write the one-to-many broadcast email that nurtures the list | `../newsletter/SKILL.md` | | Schedule / cross-post public posts across X, LinkedIn, Instagram | `../social-publisher/SKILL.md` | | Run a single timed live event end-to-end (registration, speakers, replay) | `webinar` | | Build an automated support desk / ticket triage | `customer-support` | | Actually code or host the Discord/Telegram bot (gateway, slash handlers) | `whatsapp-telegram`, `automation-flows` | | Define the voice/name/tone the community speaks in | `../brand-voice/SKILL.md` | You own the **persistent, two-way space and its ongoing operating rhythm.** The boundary that bites most: `retention` keeps *buyers of a product* from churning; you keep *members of a shared space* active and contributing. They rhyme (cohorts, re-activation) but the subject differs — a SaaS seat ...