Build and grow developer and user communities from scratch — covering ambassador programs, community-led growth (CLG), event operations, content strategy, an...
SKILL.md

---
name: community-building-playbook
description: >
  Build and grow developer and user communities from scratch — covering ambassador programs,
  community-led growth (CLG), event operations, content strategy, and health metrics.
  Grounded in real playbooks from Notion, Lovable, AFFiNE, ClickUp, Asana, and Lark.
  Use when: building a community for an open-source project, SaaS product, or brand;
  recruiting and managing ambassadors or community leaders; planning community events
  (online/offline meetups, AMAs, hackathons); designing ambassador tier/points systems;
  setting community health KPIs; launching a Build-in-Public strategy; setting up Discord,
  Slack, or Lark communities; running developer relations (DevRel); or when the user asks
  about community operations, ambassador programs, CLG, user advocacy, KOC/KOL cultivation,
  UGC flywheels, community monetization, or any variation of "how do I grow my community".
tags:
  - community-building
  - community-led-growth
  - ambassador-program
  - devrel
  - open-source
  - saas
  - startup
  - developer-community
  - ugc-flywheel
  - community-growth
  - claude-code
  - ai-agent-skill
  - discord-slack
  - event-ops
  - latest
metadata:
  category: growth
---

# Community Building Playbook — Developer & User Community Growth

Real-world frameworks distilled from Notion, Lovable ($50M ARR in 6 months via CLG), AFFiNE (0→60K GitHub Stars), ClickUp, Asana, and Lark's global community operations. Read [`references/benchmarks.md`](references/benchmarks.md) for deep dives into each case study when you need them.

---

## The Core Principle

**You cannot build a community. You can only create the conditions for one to form.**

The flywheel: Great Product → Organic Love → Self-Generated Content → Community Formation → Ambassador Identification → Ambassador Enablement → More Content + Events → More Users → Repeat.

Every failure to build community traces back to one of two mistakes: starting too early (pre-PMF), or treating community as a distribution channel rather than a mutual-value ecosystem.

---

## Phase 0: Are You Ready?

Before any community program, run this checklist. If more than two items are unchecked, stop and build product.

- [ ] Internal team uses own product daily (Notion's commercial readiness signal — they waited until 2016 to start)
- [ ] Product has a usable core loop (create → use → share works smoothly)
- [ ] You can share something (templates, tutorials, roadmap direction, or user cases)
- [ ] Someone owns community full-time (even 20% of one person's time counts)
- [ ] You can handle inbound (someone reads and responds to community posts within 24h)

**The stage decision:**

| Stage | Suitable? | Strategy |
|-------|-----------|----------|
| Pre-PMF | ❌ Not yet | Find 50–100 deep users, do 1-on-1 interviews, collect feedback |
| Post-PMF, early growth | ⚠️ Cautiously | 5–10 seed ambassadors, zero KPIs, completely free |
| Stable growth | ✅ Full program | Formal ambassador system with tiers, points, events |
| Market leader | ✅ Full investment | Ecosystem network, Affiliate commissions, regional leads |

Notion's timeline: Product usable in 2016 → Database launch in 2018 → Founder Ivan starts 1-on-1 with active contributors in 2019 → Official ambassador program in 2020. Four years. Don't rush.

---

## Part 1: Community Setup SOP (7 Steps)

### Step 1: Choose Your Platform

| Platform | Best For | Notes |
|----------|----------|-------|
| **Discord** | Developer/open-source communities | Channel categorization, Bot ecosystem, real-time |
| **Slack** | International professional communities (Notion, Asana model) | Mature, efficient for ambassador channels |
| **Lark/Feishu** | Asian-market communities, product deeply bound | Official direct operation |
| **Telegram** | Fast reach, regional groups | Messages bury quickly |
| **Facebook/LinkedIn Groups** | Regional consumer communities | Easy local discovery |

If a community already exists in your space, reach out to the admin about collaborating before creating a competing group.

### Step 2: Write Your Welcome Post Template

```
👋 Welcome to [Community Name]!

[One sentence: what the brand does + why this community exists]

🔗 Official links:
- Product: [link]
- Docs/Help: [link]

📋 Community rules:
1. No unauthorized ads
2. Respect everyone — no personal attacks
3. Verify before sharing
4. [Brand-specific rule]
```

### Step 3: Set Admin Standards

Minimum viable admin:
- 3+ content posts per week (events, product news, user stories)
- Respond to questions within 24h
- Invite 10+ new members per week
- Handle rule violations promptly

### Step 4: Set Up Brand Monitoring (CRITICAL)

Notion built a **crawler that auto-detects all tweets mentioning the brand and pushes internal notifications**. You don't need a crawler on day one, but the behavior is the same: follow and respond to every single person who posts about your product. 

**Key insight from Notion ambassador Linmi:** "One ordinary user consistently posting is worth more than a KOL posting once." Official follow + repost of every brand mention is the highest-ROI social action in early community building.

Set this up now:
- [Brand24](https://brand24.com/) or [Mention.com](https://mention.com) for web monitoring
- Manual Twitter/X search for brand name daily (until you can automate)
- When you find someone posting → follow + repost + DM to invite to community

### Step 5: Build a Community Wiki

| Page | Content |
|------|---------|
| Events Calendar | Upcoming events (embed from Luma/Notion) |
| Tutorial Library | Native-language tutorials, help docs |
| Member Directory | Voluntary member database for collaboration |
| Landing Page | Public welcome page for newcomers |

### Step 6: Set Baseline Metrics

| Metric | Seed Phase Target | Growth Phase Target |
|--------|------------------|---------------------|
| Total members | 50 | 500+ |
| Weekly active rate | ≥30% | ≥20% |
| Content posts/week | ≥3 | Daily |
| Q&A response time | ≤24h | ≤4h |
| Events/month | 1 | 2–4 |

### Step 7: Distribute Everywhere on Launch

- Invite every existing user personally
- DM competitors' followers on Twitter/LinkedIn (Notion/ClickUp users = your ICP)
- Post to relevant subreddits (r/SaaS, r/productivity, r/programmingg — follow community rules)
- LinkedIn posts + targeted DMs to potential members in target industries
- Local professional forums and groups

---

## Part 2: Ambassador Program Design

### The True Nature of an Ambassador Program

From Notion ambassador Linmi's insider interview: **"Ambassadors are free outsourcing. Surface has values packaging, core is win-win."**

Ambassadors become KOLs and build monetizable businesses through spreading your product. You get community content, user education, regional penetration, and brand risk transfer. Both sides must win or it collapses.

**Ambassador motivations (ranked by actual impact from Notion data):**

1. **Product is genuinely good** — prerequisite for everything else; no amount of incentive compensates for a weak product
2. **Beta/gray release priority** — ambassadors feel like insiders, experience new features first
3. **Direct founder dialogue** — Ivan's 1-on-1 meetings with active Notion contributors in 2019 was the single most cited motivator
4. **Help ambassadors become KOLs** — official repost, community announcements, showcasing their content
5. **Official follows and reposts everything** — making every ordinary creator feel recognized

### Ambassador Entry Standards (Notion: must satisfy A AND B)

| Requirement | Description |
|-------------|-------------|
| **A: Event organization ability** | Can organize offline meetups, has local connections |
| **B: Content production ability** | Video creation OR written tutorials OR template creation (any one) |

Maintain high standards. Notion's active ambassador rate is ~25% of enrolled ambassadors — this is **normal**. Don't lower standards chasing headcount.

### The 4-Tier System

| Tier | Annual Points | Core Benefits |
|------|--------------|---------------|
| Bronze | Auto on entry | Official recognition, community badge, product news |
| Silver | ≥100 pts/year | Beta access, official social media repost |
| Gold | ≥300 pts/year | 1-on-1 with official team, invited to annual events |
| Platinum | ≥600 pts/year | Customized support, annual awards, event sponsorship |

**Points Matrix:**

| Contribution | Points | Notes |
|-------------|--------|-------|
| Twitter/X post tagging brand | 5 pts | Must @official account |
| Tutorial article | 20 pts | ≥1000 words with real steps |
| Video tutorial | 30 pts | Any platform, ≥3 min with demo |
| Community Q&A (marked best answer) | 3 pts | Quality filter |
| Valid bug report | 10 pts | Confirmed and fixed |
| Organize local event | 50 pts | Prior approval required |
| Translation of docs/UI | 15 pts | Per page, must pass review |
| Invite new active user | 5 pts | Must become active |

### Ambassador Benefits (Notion-Validated)

| Benefit | Notion Practice | Universal Template |
|---------|----------------|-------------------|
| Tool access | Free Personal Pro + Notion AI (1 year) | Pro tier access |
| Event support | $200 event fee + $150 transport | Budget-dependent subsidy |
| Founder dialogue | Ivan did 1-on-1s personally in 2019 | Regular Town Hall Q&A |
| Monetization support | Help ambassadors take Fiverr/Upwork template orders | Official recommendation + brand endorsement |
| Career endorsement | Ambassador badge + certification | LinkedIn recommendation |
| Content exposure | Announce outstanding ambassadors in community | Official multi-channel promotion |

### Ambassador Recruitment Application (Required Fields)

Design your Typeform/form with: Name, email, location, social media links, "Why do you love [brand]?", contribution types interested in, how they plan to contribute, weekly time available, event organization experience, content creation experience + links.

Reference application: https://6dxre9ihosp.typeform.com/to/CLw1pUAp

### Onboarding a New Ambassador

| Timeline | Action | Owner |
|----------|--------|-------|
| Within 3 business days | Review application | Community ops |
| On approval | Welcome email + handbook + resource links | Community ops |
| Week 1 | Invite to ambassador-exclusive channel | Community ops |
| Week 1 | 30-min 1-on-1 video call to understand goals | Ambassador lead |
| After 1-on-1 | Share product roadmap (aspirational OK, but must deliver) | Product team |
| After 1-on-1 | Assign first task matching ambassador type | Ambassador lead |
| Day 30 | Check-in: review contributions, give feedback | Community ops |

### Weekly Ambassador Engagement (Notion's "Ambassador Seminar" Pattern)

Notion's Slack has different channels where they schedule one seminar per week or two weeks. 10–20 people, no fixed topic, free exchange. They also post cats/dogs/memes to maintain atmosphere. **No fixed topic is intentional** — it keeps it feeling like community, not obligation.

### Churn Warning Signals

| Signal | Response |
|--------|----------|
| No contributions for 2 months | Private check-in message |
| Content quality declining | Share content creation resources |
| Feeling undervalued | Arrange 1-on-1 call, repost their content |

### Retention Rhythm

- Monthly: Community newsletter (product updates + ambassador spotlights)
- Quarterly: Ambassador-only online call (casual, no agenda required)
- Bi-annually: Official team personally reaches out to key ambassadors
- Annually: Ambassador gala + awards ceremony

### Annual Awards

| Award | Criteria |
|-------|----------|
| Most Active Ambassador | Highest annual points |
| Best Content Creator | Highest value content output |
| Best Localization | Highest quality translation volume |
| Best Bug Hunter | Most confirmed bugs |
| Best Community Builder | Most new members + most events |
| Best Innovation | Most impactful product suggestion adopted |

---

## Part 3: Community Event SOP

### Event Types

| Type | Scale | Frequency | Purpose |
|------|-------|-----------|---------|
| Online Workshop | 20–100 | 1–2x/month | Product education, user activation |
| AMA | Unlimited | 1x/quarter | Founder trust-building |
| User Case Sharing | 50–200 | 1x/month | Social proof, UGC |
| Ambassador Seminar | 10–20 | Weekly/bi-weekly | Ambassador peer learning |
| Local Meetup | 10–50 | As needed | Regional deep connections |
| Hackathon | Unlimited | Every 6 months | Innovation, UGC output |

### Event SOP (3 Phases)

**Phase 1 — Setup (at least 3 weeks before)**
1. Confirm date and venue (ask community members if they can host — free venue)
2. Submit event form to official team: https://bytedance.larkoffice.com/share/base/form/shrcnww1MbaxwOKngVDsEh4zQOe
3. Design poster in Canva (include: date, location, community QR code, registration link)
4. Publish to Luma/Eventbrite/Meetup/Peatix
5. Post everywhere: LinkedIn, Facebook, Twitter, community channels

**Recommended event structure (1–2 hours):**
- Warm-up (Slido poll: "How many tools in your workflow?")
- Lark/brand intro video if needed
- User case presentation (15–20 min)
- Key feature training (20–30 min)
- Group discussion (15–20 min)
- Group photo

**Phase 2 — During**
- Full rehearsal before start
- Take photos and videos throughout
- Post real-time to community + social media
- Invite all attendees to join the local community (don't skip this)

**Phase 3 — After**
- Verify attendees joined the community (the single most important post-event action)
- Post event summary + review questionnaire to community
- Edit long video → YouTube Shorts
- Post recap (photos + text) on Twitter/Facebook/LinkedIn
- Archive everything — every piece of content should be repurposed

**Event Checklist:**
- [ ] Date and venue confirmed
- [ ] Event form submitted
- [ ] Structure confirmed
- [ ] Poster designed
- [ ] Published to event platforms
- [ ] Posted link everywhere
- [ ] Social media posts scheduled
- [ ] Rehearsed
- [ ] Event recorded
- [ ] Post-event summary and social recap done
- [ ] Links shared to community channels

---

## Part 4: Content Strategy

### The Build-in-Public Post Framework

For product updates and feature announcements, structure posts with:

**For Product Previews:** What are you introducing? What's the impact? Any direction changes? CTA: Are you looking for feedback?

**For Design Previews:** What is the feature? What design choices were made and why? CTA: Which do you prefer?

**For Dev Feature Previews:** Feature name, user benefit in one sentence, GIF/video of how to use it, where to access it (insider sneak peek / testing / live).

Keep it honest and specific. "We shipped X and it helps you do Y in Z seconds" beats "We're excited to announce..."

### Content Type Weights (Data-Validated from 200 Tweets)

| Type | Priority | Notes |
|------|----------|-------|
| Long-form story/case study | ⭐⭐⭐⭐⭐ | Highest engagement and retention |
| Tutorial/how-to | ⭐⭐⭐⭐ | High bookmark rate |
| Thread (8+ points) | ⭐⭐⭐ | Use when multiple independent insights |
| User case/social proof | ⭐⭐⭐⭐ | Trust-building |
| Pure philosophy/quotes | ⭐ | Data shows consistently low performance — avoid |

### Platform Distribution Matrix

| Platform | User Type | Format |
|----------|-----------|--------|
| Twitter/X | Builders, indie devs, tech founders | Long-form, threads, real data |
| LinkedIn | Enterprise buyers, B2B | Case studies, ROI data |
| YouTube/TikTok | Broad audience | Tutorial videos, demos |
| Reddit | Developers, enthusiasts | Authentic discussion, no hard promotion |
| HackerNews | Technical builders | Only launch/Show HN — must be genuine |

---

## Part 5: PLG + CLG Growth Models

### Lovable's CLG Flywheel ($50M ARR, 6 months)

The core mechanic: **Remix**. Every free user's project is public and remixable. Every remix is a product demo. Free tier = projects must be public = every free user is an advertisement.

Key data: 100,000+ Discord members, 85% subscription retention, 67% of users have almost no programming experience, 21.22M monthly traffic vs. competitors at 5–6M.

To replicate the pattern:
1. Build a product-level viral mechanic (share, remix, fork, duplicate)
2. Free tier that requires public-facing output → fuels UGC
3. Discord/community as primary retention mechanism (social lock-in)
4. "Built with [Brand]" branding on free outputs → free distribution

### AFFiNE's Open Source Community Flywheel

- Day 1 strategy: Simultaneous posting to r/producthunt, r/SaaS, r/Entrepreneur
- 24h rule: Team members respond to every single comment within 24 hours
- 1-week follow-up: Post a recap/thank-you post that builds long-term relationship
- Result: 3–4M effective traffic from Reddit, ~5–8% Star conversion rate

### ClickUp's PLG Metrics

- CAC:LTV = 1:3 (healthy PLG benchmark)
- Daily blog posts (16 internal authors + external contributors)
- Zapier integration drove +170% growth
- Onboarding activation + monetization activation as two separate metrics

---

## Part 6: Community Health Dashboard

Track weekly/monthly:

| Category | Metric | Target |
|----------|--------|--------|
| Growth | New members / month | ≥15% MoM |
| Activity | WAU / total members | ≥20–30% |
| Content | UGC posts / week | ≥10 |
| Support | Avg response time | ≤24h |
| Events | Events / month | ≥1 |
| Ambassador | Active ambassadors (≥10 pts/month) | ≥20 |
| Ambassador | Active rate (vs enrolled) | ≥25% (Notion benchmark) |
| Ambassador | Content coverage | ≥60% of active ambassadors |

---

## Tool Stack

| Category | Tools |
|----------|-------|
| Community platform | Discord, Slack, Lark, Telegram |
| Events | Luma, Peatix, Eventbrite, Meetup |
| Live interaction | Slido |
| Design | Canva |
| Brand monitoring | Brand24, Mention |
| Affiliate | Rewardful |
| Ambassador applications | Typeform |
| Video | YouTube, TikTok, Loom, Screen Studio |
| SEO | Ahrefs |
| Ambassador monetization | Fiverr, Upwork, Udemy, Gumroad |
| Analytics | Lark Bitable, custom dashboards |

---

## Reference Files

- [`references/benchmarks.md`](references/benchmarks.md) — Deep dives: Notion, Lovable, AFFiNE, ClickUp, GitHub Stars, Asana
- [`references/templates.md`](references/templates.md) — Copy-ready templates: welcome post, application form, event checklist, newsletter format
Community Building Playbook

SKILL.md

related skills
