Community

---
name: community
description: "Use this skill when the user needs to build a user community, start a Discord or forum, create a community strategy, reduce support load through peer-to-peer help, or use community as a growth channel. Covers community platform selection, launch strategy, engagement tactics, and scaling community without it consuming all your time."
---

# Community Building

Community is a leverage multiplier — when done right, your users help each other, advocate for your product, and provide a constant stream of feedback. This skill helps you decide when to start a community, which platform to use, and how to keep it alive without it consuming all your time.

## Core Principles

- Community is a product, not a channel. Treat it with the same care as your app.
- Don't start a community until you have at least 100 active users. Below that, it's a ghost town.
- The goal is user-to-user value, not founder-to-user broadcasting. You're facilitating, not performing.
- A small, engaged community beats a large, silent one. 50 active members > 500 lurkers.
- Community reduces support load only after you invest in it. It increases load at first.

## When to Start a Community

### Start When:

- You have 100+ active users
- Users are already talking to each other (in support tickets, on social media, in reviews)
- You're answering the same questions repeatedly (community enables peer answers)
- Your product has a learning curve that benefits from shared knowledge
- Users create things with your product that they'd want to share

### Don't Start When:

- You have fewer than 50 active users (not enough for critical mass)
- You're still validating the product (focus on 1-on-1 conversations instead)
- You think community will replace support (it supplements it, doesn't replace it)
- You don't have 2-3 hours/week to invest in it

---

## Platform Selection

| Platform | Best For | Cost | Effort |
|----------|----------|------|--------|
| **Discord** | Technical products, developer tools, real-time chat | Free | Medium |
| **Slack** | B2B SaaS, professional communities | Free (limited) | Medium |
| **GitHub Discussions** | Open-source, developer tools | Free | Low |
| **Circle** | Course creators, premium communities | \$89+/mo | Medium |
| **Forum (Discourse)** | Long-form Q&A, searchable knowledge | Free (self-hosted) | High |
| **Reddit (own subreddit)** | Large consumer products | Free | Low |

### Decision Framework

```
Is your product for developers? → Discord or GitHub Discussions
Is your product B2B/professional? → Slack or Circle
Do you want searchable, long-form discussions? → Discourse or Circle
Do you want real-time, casual chat? → Discord or Slack
Is budget zero? → Discord (free, full-featured)
```

**For most bootstrapped SaaS founders: Start with Discord.** It's free, full-featured, and your users likely already have it.

---

## Community Structure

### Discord/Slack Channel Structure

Start minimal. You can always add channels later.

```
#welcome          — Rules, intro, what this community is about
#introductions    — New members introduce themselves
#general          — Main conversation
#help             — Product questions and troubleshooting
#feature-requests — Ideas and suggestions
#show-and-tell    — Users share what they've built/achieved
#announcements    — Product updates (post-only for admins)
```

**Don't create:**
- More than 7 channels at launch (overwhelming)
- Channels nobody uses (archive quickly)
- Separate channels for every feature (too granular)

### Community Guidelines

```
Welcome to the [Product] community!

This is a space for [audience] to [purpose].

Rules:
1. Be helpful and respectful.
2. Search before asking — your question may already be answered.
3. Share what you've built or learned — we love seeing your work.
4. No spam or self-promotion unrelated to [product/domain].
5. Bug reports go to [support channel/email], not here.

The team reads every message but can't respond to everything.
Helping each other is what makes this community great.
```

---

## Launching Your Community

### Pre-Launch (1-2 Weeks Before)

```
- [ ] Set up the platform with initial channels
- [ ] Write welcome message and community guidelines
- [ ] Invite 10-20 of your most engaged users personally
- [ ] Ask them to introduce themselves and start conversations
- [ ] Post 3-5 conversation starters yourself
- [ ] Make sure it doesn't feel empty when new members arrive
```

### Launch Sequence

```
Week 1: Invite top 20 users → seed conversations
Week 2: Announce to full user base via email
Week 3: Add community link to app UI (sidebar, help menu)
Week 4: First community-only event or content
```

### Seeding Conversations

The community will feel dead if you just open the doors. Seed it:

```
Conversation starters:
- "What's the first thing you built with [Product]?"
- "What's your biggest challenge with [domain]?"
- "Share your setup — how do you use [Product] in your workflow?"
- "What feature do you wish existed?"
- "Introduce yourself: What do you do, and what are you working on?"
```

---

## Engagement Tactics

### Weekly Rituals

Recurring events give members a reason to come back:

| Day | Ritual | Example |
|-----|--------|---------|
| Monday | Weekly thread | "What are you working on this week?" |
| Wednesday | Tip of the week | Share a power-user tip or workflow |
| Friday | Show and tell | Members share what they've built or achieved |

### Founder Engagement

Your presence matters, especially early on:

```
Daily (15 minutes):
- [ ] Check #help — answer or acknowledge every question
- [ ] React to 3-5 messages (shows you're present)
- [ ] Reply to one conversation with a thoughtful comment

Weekly (30 minutes):
- [ ] Post an update on what you're building
- [ ] Highlight a community member's contribution
- [ ] Start a discussion topic
```

### Empowering Super Users

Your most active community members are your biggest asset:

- Identify members who consistently help others
- Give them a special role (Moderator, Community Champion)
- Give them early access to new features
- Ask for their input on product decisions
- Thank them publicly and privately

---

## Community as a Support Channel

### How It Reduces Support Load

```
Without community:
User has question → Emails support → You answer (1:1)

With community:
User has question → Posts in #help → Another user answers (1:many)
You review and verify the answer (quality control)
```

### Making It Work

- Pin answers to common questions
- Create a #faq channel with the top 10 questions
- Encourage users to search before posting
- Thank users who help others
- Verify community answers for accuracy (wrong answers are worse than no answers)

---

## Measuring Community Health

```
Monthly Community Review:
- [ ] Active members (posted in last 30 days)
- [ ] New members this month
- [ ] Messages per day (trend, not absolute)
- [ ] Questions answered by community vs. by you
- [ ] Support tickets reduced? (compare to pre-community)
- [ ] Signups attributed to community (referrals, word of mouth)
- [ ] Time you spent on community this month (keep it manageable)
```

### Health Signals

| Healthy | Unhealthy |
|---------|-----------|
| Members answer each other's questions | Only you answer questions |
| New members introduce themselves | New members join and never post |
| Conversations happen without you starting them | All threads are started by you |
| Members share wins and creations | Only complaints and feature requests |
| Steady growth in active members | Member count grows but activity doesn't |

---

## Common Mistakes

| Mistake | Fix |
|---------|-----|
| Starting too early (< 50 users) | Wait until you have 100+ active users |
| Too many channels at launch | Start with 5-7 channels. Add when needed |
| Treating it as a broadcast channel | Facilitate conversations, don't just announce |
| No community guidelines | Set rules on day 1. Enforce consistently |
| Ignoring it after launch | 15 min/day minimum. Community dies without founder presence |
| Trying to control every conversation | Let members lead. Step in only when needed |
| Not empowering super users | Give active helpers roles and recognition |
| Expecting it to replace support | It supplements support. It's not a replacement |

---

## Success Looks Like

- Members helping each other without your intervention
- Community is a place users check regularly (not just when they have a problem)
- Support ticket volume decreased since community launched
- New users discover your product through community word-of-mouth
- You spend less than 3 hours/week on community management
- Super users emerge organically and advocate for your product

---

## Related Skills

- **support** — Community supplements (doesn't replace) support
- **retention** — Community engagement reduces churn
- **feedback** — Communities surface feature requests and bug reports
- **content** — Community insights fuel your content strategy