Community Building Playbook

Purpose

This recipe builds a functioning startup community from zero to 50+ active members on a chosen platform (Discord, Slack, or forum), with a structured engagement model that drives community-led growth. The output is a fully configured community with channel architecture, onboarding flow, moderation, 8-week content calendar, and analytics tracking — ready to sustain organic conversations and convert engagement into product adoption and retention. [src1]

Prerequisites

• ICP definition — who your ideal community members are and why they'd participate
• Existing user base — minimum 20-30 users to seed initial conversations
• Product positioning — clear value proposition defining what the community is about
• Community owner — one person dedicated 10+ hours/week for first 8 weeks
• Email list or social following — at least one channel for launch invitations

Constraints

• Seed with 50+ active members before public launch — empty communities die within 2 weeks. [src4]
• Choose ONE primary platform — splitting across multiple platforms fragments engagement. [src2]
• Respond within 4 hours during business hours — unanswered questions drive members away. [src5]
• Run content calendar for 8 weeks minimum before evaluating viability. [src1]
• Do not monetize before 500+ engaged members — premature paywalls kill growth. [src6]

Tool Selection Decision

Which platform?
├── Developers / gamers / crypto / creators
│   └── PATH A: Discord — free, voice, bots, forum threads
├── B2B professionals / enterprise
│   └── PATH B: Slack — integrations, professional, threaded
├── Long-form discussion + SEO discoverability
│   └── PATH C: Forum (Discourse/Circle) — persistent, search-indexed
└── Non-technical / creators wanting courses + community
    └── PATH D: All-in-one (Circle/Skool) — courses + community

Execution Flow

Step 1: Define Community Purpose and Structure

Duration: 2-4 hours · Tool: Document editor

Use the CMX Community Strategy Canvas to define: who joins (persona), why they join (value proposition), what they do (activities), and how you measure success. You must be able to explain in one sentence why someone would join AND stay. [src1]

Verify: One-sentence community value proposition exists and resonates with 3+ potential members. · If failed: Interview 5-10 existing users about peer discussion needs.

Step 2: Set Up the Platform

Duration: 3-6 hours · Tool: Discord / Slack / Forum

Configure channel architecture: welcome (read-only), announcements, introduce-yourself, 2-3 topic channels, help, wins. Keep total under 15 channels at launch. Set up onboarding flow so new members can join, read rules, introduce themselves, and find discussions within 2 minutes. [src2]

Verify: New member can complete onboarding in under 2 minutes. · If failed: Simplify to maximum 8 channels.

Step 3: Seed with 50+ Active Members

Duration: 1-2 weeks · Tool: Email + DMs + personal outreach

Tier 1 (10-15): co-founders, team, advisors, power users. Tier 2 (20-30): engaged customers, beta testers. Tier 3 (20-30): extended network, adjacent community members. Seed 5-10 discussion threads before inviting. Personal invite → join: 30-50%. Join → active: 30-40%. Plan to invite 250-350 people. [src4]

Verify: 50+ unique members have posted. Daily messages > 10 without staff initiation. · If failed: Invite 50 more people and seed 10 new discussion threads.

Step 4: Build Content and Engagement Calendar

Duration: 3-4 hours · Tool: Notion or Google Sheets

8-week calendar: Monday (weekly prompt), Tuesday (expert tip), Wednesday (discussion question), Thursday (member spotlight/AMA), Friday (wins thread). Bi-weekly live events. React to every message within 4 hours. Recognize top contributors weekly. [src5]

Verify: 8 weeks planned with 5+ items per week, each with owner assigned. · If failed: Reduce to 3 high-quality items per week.

Step 5: Set Up Moderation and Guidelines

Duration: 2-3 hours · Tool: Platform moderation tools

Post community guidelines in read-only channel. Configure auto-moderation (spam, profanity). Set up escalation workflow: warning → mute → temp ban → permanent ban. Ensure at least 2 people have moderator access. [src2]

Verify: Guidelines posted, auto-mod active, 2+ moderators assigned. · If failed: Recruit 2-3 active members as volunteer moderators.

Step 6: Launch Growth Loops

Duration: 2-3 hours setup, then ongoing · Tool: Community platform + marketing channels

Activate three growth loops: Content → Discovery → Join (share discussions externally), Question → Answer → Invite (peer referrals), Event → Value → Share (event-driven growth). Share community highlights in newsletter, cross-pollinate with adjacent communities, convert support tickets to community discussions. [src6]

Verify: At least one loop produces 5+ organic new members/week. · If failed: Focus on content quality before adding growth tactics.

Step 7: Measure and Iterate

Duration: 1-2 hours weekly · Tool: Common Room / Orbit / spreadsheet

Track: daily active members (target 15% of total), messages/day (target 20+ by Week 4), 30-day retention (target 40%+), member-to-staff message ratio (target 5:1+). DAU/MAU below 10% = intervention needed; 20-30% = healthy. [src5]

Verify: Dashboard populated weekly. DAU/MAU trending upward or stable above 15% by Week 8. · If failed: Survey active members and pivot community focus.

Output Schema

{
  "output_type": "community_platform",
  "format": "deployed platform + documents + analytics",
  "columns": [
    {"name": "platform", "type": "string", "description": "Platform chosen and configured", "required": true},
    {"name": "total_members", "type": "number", "description": "Total members at launch", "required": true},
    {"name": "active_members", "type": "number", "description": "Members with 5+ messages in first 2 weeks", "required": true},
    {"name": "daily_messages", "type": "number", "description": "Average messages per day in Week 2", "required": true},
    {"name": "channels_configured", "type": "number", "description": "Active channels/categories", "required": true},
    {"name": "content_calendar_weeks", "type": "number", "description": "Weeks of content planned", "required": true},
    {"name": "growth_loop_active", "type": "boolean", "description": "Organic growth mechanism active", "required": true}
  ],
  "expected_row_count": "1",
  "sort_order": "N/A",
  "deduplication_key": "platform"
}

Quality Benchmarks

If below minimum: If DAU/MAU is below 10% after 8 weeks, survey active members and pivot focus. If messages/day below 10, improve content calendar or return to seeding.

Error Handling

Cost Breakdown

Anti-Patterns

Wrong: Launching a public community with zero seeded members

Opening to the public with no existing conversations creates a ghost-town effect. New members see silence and leave permanently. This is the most common reason startup communities fail. [src4]

Correct: Seed 50+ active members with pre-planted conversations

Personally invite founding members, seed 10-15 threads, and ensure daily message volume exceeds 10 before any public announcement.

Wrong: Creating 20+ channels on day one

Over-structured communities split conversations across empty channels. Each channel needs 3-5 messages/day to feel alive. [src2]

Correct: Start with 6-8 channels, add on demand

Launch with welcome, announcements, general, 2-3 topic channels, and help. Add channels only when organic demand appears.

Wrong: Treating community as a broadcast channel

Posting only product announcements turns community into a newsletter nobody subscribed to. [src6]

Correct: 80% member content, 20% staff content

Staff should primarily ask questions, respond, and facilitate. The community's value is peer-to-peer exchange, not one-way broadcasting.

When This Matters

Use this recipe when a startup needs to build an owned community from scratch on Discord, Slack, or a forum to drive retention, product feedback, or community-led growth. Requires at least 20-30 existing users for seeding. Covers platform selection through 50+ member launch and 8-week validation — not scaling beyond 1,000 members.