-
1
Define the single purpose the community exists to deliver
Communities drift and die when they try to be everything to everyone. Pick one of four purposes and write it down in a single sentence before anything else: peer support (customers help each other solve product problems), networking (buyers meet other buyers in the same role), advocacy (power users amplify the brand and feed references), or learning (members level up a shared craft). The purpose decides the content, the rituals, the invite list, and the metric the program will be judged on. A support community is measured on question-response time; a networking community is measured on member-to-member connections; an advocacy community is measured on references and reviews sourced; a learning community is measured on content consumed and skills built. Research from CMX and Pavilion consistently finds that the healthiest B2B communities have one purpose named out loud and defended, not three.
- Name the single purpose in one sentence (support, networking, advocacy, or learning)
- Write the one metric the community will be judged on at the end of year one
- List the three topics or activities that are off-charter so moderators have a clear no
Tip: If the purpose statement could describe any other vendor's community, it is not sharp enough yet. Narrow until it only fits yours.
-
2
Pick the platform that fits the audience, not the roadmap
Platform choice is a two-year commitment that is painful to reverse, so match the tool to where the audience already works. Slack suits buyer-practitioner communities whose members live in Slack all day for their day job and want threaded support plus DMs. Discord fits developer, creator, and prosumer audiences that expect voice channels, roles, and higher message velocity. A dedicated community platform (research from Circle, Bevy, and Discourse covers the trade-offs well) wins when searchable long-form content, events, and SSO with the product matter more than real-time chat. Avoid the trap of picking the platform the team already uses internally; pick the one the members will show up on without being nagged. Document the choice, the rationale, and the migration cost so the next executive who proposes switching has to meet the same bar.
- Interview five target members on where they already spend community time
- Score platforms on search, threading, events, roles, SSO, and moderation tooling
- Pick one and commit for at least a year; cross-posting splits attention and kills habit
Tip: The best platform is the one the members will log into without a reminder. If the invite needs a sales pitch, it is the wrong platform.
-
3
Establish the weekly, monthly, and quarterly rituals
Rituals are what turn a channel into a community. Pick three recurring moments and run them without exception for the first ninety days. A weekly thread (a recurring prompt on a fixed day, like a Monday wins thread or a Thursday ask-me-anything) gives members a reason to open the app every week. A monthly event (a live roundtable, office hours, or members-only AMA) builds relationships that chat cannot. A quarterly research moment (a member survey, a published benchmark, or a council readout) gives the community a shared artifact and a reason for members to invite their peers. HBR's community research on belonging and B2B research from Commsor both land on the same point: a predictable cadence of small rituals beats one annual conference every time.
- Pick a weekly recurring thread on a fixed day and assign a named owner
- Schedule a monthly event with a confirmed host, time, and promotion plan for the next quarter
- Pre-book the quarterly research moment (survey, benchmark, or council) into the editorial calendar
Tip: Skipping a ritual week trains members to tune the space out. Shrink the ritual before you skip it.
-
4
Seed with 30-50 members who already know the brand
A quiet seed launch to warm names is the single best protection against a community that feels empty. Build the first invite list from the CRM: existing customers who are power users, warm prospects who have asked for peer intros, advisors who already give feedback, and five to ten internal teammates who will keep the channels alive during low-traffic weeks. Send each invite as a personal note, not a bulk blast, and ask every new member a single onboarding question they have to answer in their first message. The question doubles as an icebreaker and as the first data point for later segmentation. Resist the urge to open public signups until the first ritual has run three times; a community that is loud with thirty warm members is a community strangers will join, and an echoey one with three hundred cold ones is one they will leave.
- Pull the seed list from CRM: top accounts, warm prospects, advisors, and internal power users
- Send personal, one-to-one invites with a specific reason each person was picked
- Ask every new member a single intro question they answer in their first message
Tip: Thirty engaged members beat three hundred lurkers. Protect density early and width will take care of itself.
-
5
Launch with purpose-driven onboarding, not a welcome tour
The first ten minutes a member spends in the space decide whether they come back. Build an onboarding flow that forces one meaningful action tied to the stated purpose: in a support community, that is posting a real question; in a networking community, it is naming the one peer they want to meet; in an advocacy community, it is sharing one win worth amplifying; in a learning community, it is picking a track and committing to one artifact. Replace the usual list-of-channels welcome with a short, direct note from the community lead that restates the purpose, names the three rituals, and asks for the first action. Pin the welcome at the top of the primary channel and refresh it quarterly so new members hitting the space on day ninety see the same clarity the day-one members saw.
- Replace generic welcomes with a purpose-first intro from a named human
- Force one meaningful action in the first session (question, intro, win, or commitment)
- Pin the welcome and refresh it quarterly so late joiners get the same clarity as day one
Tip: A welcome tour is a corporate reflex. A single first action is a community reflex. Pick the second one.
-
6
Run a 90-day engagement cadence with a named owner
The first ninety days decide whether the community has legs. Run a tight weekly operating cadence with one named owner, not a committee. The owner posts the recurring thread on day one of the week, hosts or confirms the monthly event, answers every DM within one business day, and publishes a short internal retro every Friday with three numbers: new members this week, active posters this week, and the single best thread of the week. The retro is for the executive sponsor and for the owner's own future self; a founder who sees a four-week trend of declining active posters can intervene before the ritual collapses. Protect the owner's calendar: community work bleeds into every other role if the hours are not blocked.
- Assign one named owner for the first ninety days with a protected weekly time block
- Publish a short Friday retro with new members, active posters, and the best thread of the week
- Guarantee a one-business-day response on every DM, question, and new-member intro
Tip: A community without one named owner is a community that is slowly becoming no one's job. Name the owner before the invite goes out.
-
7
Measure DAU, question-response, and member-sourced pipeline
Most community dashboards count total members and call it a day, which tells leadership almost nothing. Track three signals that actually predict health. Daily or weekly active users (DAU or WAU) show whether the rituals are working; a healthy B2B community lands between 15% and 30% WAU, with Commsor and CMX research both landing in that band. Question-response time (how long before a new question gets a substantive reply) is the single clearest signal of a support community's health; under four business hours is strong, over twenty-four is a warning. Member-sourced pipeline (opportunities where a community member is the first-touch or referrer) is the one number that lets the community defend its budget to the CFO. Report the three on a monthly cadence and resist the urge to add a fourth before the first three are trusted.
- Instrument WAU and active-poster counts in the platform's analytics or a lightweight dashboard
- Measure median question-response time weekly and alert when it crosses four business hours
- Tag opportunities in the CRM with a community-sourced flag so pipeline attribution is defensible
Tip: Total member count is the vanity metric that will survive every reorg. Replace it with WAU in the first exec readout and never go back.
-
8
Iterate quarterly against reader themes and member feedback
The community a team launches and the community members ask for will drift apart within two quarters. Protect the compounding by running a thirty-minute quarterly retro. Pull the top ten threads by replies, the top five by reactions, the top five unanswered questions, and the raw text of every member survey response from the last ninety days. Tag themes and let the next quarter's ritual calendar reflect what members actually asked for, not what the original launch doc promised. Kill one ritual that is not working; adding a new one on top of an underperforming one is how community calendars silently become unreadable. Share the retro back with members in a short public post so the community sees the loop close; HBR's community research is clear that visible iteration is one of the strongest signals of belonging a community can send.
- Pull the top threads, top unanswered questions, and raw survey text each quarter
- Rewrite the next quarter's ritual calendar against the themes the members surfaced
- Publicly share one thing changing and one thing being killed based on member input
Tip: The point of iteration is not more rituals, it is better ones. Cut before you add.
