Most founders bolt a Slack workspace onto their product, call it a "community," and wonder six months later why it feels like a graveyard with three power users answering support tickets nobody assigned them. A real community program is a distinct function with its own strategy, staffing, metrics, and operating cadence. Done right, it compounds retention, shortens sales cycles, and turns customers into your best product managers.
A community is a persistent, member-owned space where your customers get value from each other — not just from you. It is not a marketing channel, a support queue, or a user conference in Slack form. If members only show up when your team posts, you don't have a community; you have a broadcast list.
Three tests: (1) member-to-member messages outnumber team-to-member messages, (2) members return without a team prompt, (3) members refer new members without incentive.
Start when you have 100+ active customers who share a job-to-be-done specific enough that peer advice is more valuable than a Google search. Before that, invest in 1:1 customer development. A community with 20 people is a group chat; a community with 200 strangers and no shared context is a spam target.
Slack: fast to launch, familiar, weak search, poor SEO, no thread persistence past free-tier limits.
Discord: strong for developer and consumer audiences, voice-native, unfamiliar to enterprise buyers.
Circle / Bettermode / Discourse: SEO-friendly, structured, better for long-form and searchable knowledge.
Rule: match the platform to where your members already spend their day. A CFO community on Discord will die. A game-dev community on Circle will feel corporate.
The single biggest failure mode is treating community as a side project for someone in marketing. Hire a dedicated Community Lead by the time you have 500 members. Their job is not to post — it is to make members post. Expect a ratio of one full-time community manager per ~2,500 active members, plus a rotating pod of engineers and PMs for weekly AMAs.
Days 0–30: Seed with 25 hand-picked members you already know. Every one gets a personal onboarding call. Publish a member directory, a code of conduct, and three starter threads.
Days 31–60: Run one live event per week (office hours, teardown, workshop). Ship a weekly digest email — this is your retention engine, not the platform itself.
Days 61–90: Recruit 10 member-moderators. Give them a private channel, early product access, and a title. Their status is the payment.
Daily: Community Lead does a 20-minute sweep — welcomes new members by name, answers unanswered questions, resurfaces buried gems.
Weekly: Digest email, one live event, one long-form member spotlight.
Monthly: Cohort report to product and CS with the top 10 threads, top 5 feature requests, and top 3 at-risk accounts identified by sentiment.
Quarterly: Member survey (NPS + open-ended), moderator dinner, roadmap AMA with the CEO.
Stop measuring member count. It is a vanity number that goes up when you spam signup forms. Measure:
L28 active member ratio — members who posted or reacted in the last 28 days divided by total members. Healthy: >20%. Great: >35%.
Time to first reply — median minutes between a new question and its first substantive reply. Target: 5:1.
Community-attributed retention lift — 12-month retention of active community members vs. matched non-members. This is the number that justifies headcount to the CFO.
Community-sourced pipeline — opportunities where the first touch or a documented influence event came from the community.
Publish a weekly "state of the community" thread. Pin three evergreen resources: a getting-started guide, a member directory, and a searchable FAQ. Everything else should be generated by members with light editorial nudging.
Publish the code of conduct on day one. Enforce it on day two. The first time you fail to remove a bad actor, half your best members go quiet. Ban decisions are made by the Community Lead, documented in a private log, and never litigated in public.
Do not gate the community behind a paid tier in the first year — you starve the network effect. Do not run sponsored posts from vendors — you rent your credibility. Do not let sales reps pitch in public channels — you convert a community into a lead list and lose both.
A community that hits critical mass becomes the single hardest thing for a competitor to copy. Product features get cloned in a quarter. Pricing gets matched in a week. Ten thousand customers who trust each other and answer each other's questions at 11 p.m. on a Tuesday cannot be replicated with a budget.
Build it as a program, not a channel. Staff it like a product. Measure it like a revenue line. Then leave it alone long enough to compound.
