Most community launches fail the same way. The organization announces it broadly, hundreds of people sign up, the space feels empty because nobody knows anyone, and within a month it is quiet. The people who built it conclude that “our members just don’t engage.”
The problem is the launch, not the members. This playbook describes the approach that works: a specific purpose, a hand-recruited founding group, a small private space, and a host who seeds activity until members take over.
Step 1: Define the purpose and the people
Write one sentence: “This is a community for [specific people] who want to [specific outcome].”
Specificity is the whole game. Compare:
- “A community for marketers” — nobody knows if they belong.
- “A private community for heads of marketing at B2B software companies under $50M in revenue who want candid peer advice on team, budget, and pipeline” — the right person reads that and thinks finally.
The narrower the definition, the faster the community forms, because members immediately recognize each other. You can widen later. You cannot easily narrow.
Then list what members will get in the first 30 days. If you cannot name three concrete things (a peer they will meet, a question they will get answered, a resource they will receive), the promise is not ready.
Step 2: Recruit founding members by hand
Before opening the doors, recruit 10 to 30 founding members individually. Not with a signup form; with a personal message or call. Explain the purpose, say why you are asking them specifically, and ask for a commitment: show up for the first 90 days and contribute.
Choose founding members for three qualities:
- They match the definition. Exactly the people the community is for.
- They are generous. People known for helping others in their field.
- They are respected. Others will join partly because of who is already there.
Give founding members something in return: a permanent designation, a say in the norms, early pricing, or simply the status of having built the thing. Many communities still display “Founding Member” badges years later.
This step also tests the promise. If you cannot get 10 relevant people to say yes, the purpose or the audience needs rethinking before you build anything.
Step 3: Decide the model and the rules
Three decisions to make before launch:
Access. Open, application-based, invite-only, or paid? Professional communities almost always do better private, with some vetting, because candor depends on knowing who is in the room.
Price. Free (supported by another revenue line), paid, or tiered? Charging filters for commitment. If you charge, keep the early price simple and honor it for founding members.
Norms. Write three to six guidelines in plain language. See Community Moderation and Guidelines. Have founding members review them; they will enforce norms they helped write.
Step 4: Choose the platform (now, not earlier)
Platform decisions made before the purpose is clear are usually wrong. Now that you know who the members are, what they will do, and whether the community is private and paid, you can evaluate tools against real needs: privacy and access control, member directories and profiles, discussion and Q&A, events, payments, branding, and how much the host wants to own versus rent.
See How to Choose a Community Platform for criteria. The short version: pick for the needs of the first year, make sure you can export your data, and do not let the tool dictate the design.
Step 5: Seed before you open
An empty community is the most common reason newcomers leave. Before any wider invitation:
- Post 10 to 20 real conversations, started by founding members and the host: introductions, questions, resources, debates.
- Make sure every one of them has replies.
- Set up the first two or three rituals and run one cycle. See Community Engagement Best Practices.
- Fill in the member directory. New members look at who is there before anything else.
The goal is that the first person through the door after the founding group sees a living room, not an empty hall.
Step 6: Open in waves
Invite in waves of 20 to 50, not all at once. Each wave gets a personal welcome, introductions to relevant founding members, and time to settle before the next. Waves keep the ratio of active to new members healthy and let onboarding keep up. See Community Onboarding Best Practices.
Prioritize referrals from existing members over broad promotion. Referred members arrive with trust and context.
Step 7: The first 90 days
The host’s job in the first 90 days is to seed activity and hand it over.
Weeks 1 to 4. Post daily. Reply to everything. Welcome everyone personally. Make at least five introductions a week. Run the rituals exactly on schedule. Fix anything confusing in onboarding immediately.
Weeks 5 to 8. Shift from posting to prompting. Ask founding members to start threads. Identify the members who are naturally helpful and give them small roles: welcoming, hosting a call, moderating a space. Hold the first live gathering if you have not already.
Weeks 9 to 13. Measure. What share of activity comes from members rather than the host? What percentage of new members made a first contribution? Which rituals have attendance and which do not? Cut what is not working, double what is. Ask members, in a short survey, what the community has done for them so far; their answers become your marketing.
By the end of 90 days, a healthy launch shows most activity coming from members, a recognizable weekly rhythm, and at least a handful of member-to-member relationships that exist without the host.
What not to do
- Do not launch with a broadcast. A mass announcement produces passive signups and an empty space.
- Do not build twelve channels. Start with three. Add spaces only when a conversation outgrows its home.
- Do not wait for members to engage. Early on, the host creates the activity. That is not a failure; it is the job.
- Do not optimize the platform before the purpose. Features do not create belonging.
- Do not skip founding members. This is the step that organizations most often cut and most often regret.
A launch checklist
- One-sentence purpose with a specific audience
- Three concrete things members get in 30 days
- 10 to 30 founding members personally committed
- Access, pricing, and guidelines decided
- Platform chosen against real needs, with data export confirmed
- 10 to 20 seeded conversations, all with replies
- Two or three rituals scheduled
- Onboarding sequence and welcome owner assigned
- Wave-based invitation plan
- A 90-day review with the metrics in Community Metrics and KPIs
Next: Community Strategy and Frameworks.
Frequently asked questions
How many members do you need to launch a community?
Fewer than most people think. A community can launch with 10 to 30 committed founding members and feel alive, because activity per member is high when the group is small and known. Launching with hundreds of passive signups usually produces a quiet space that is hard to revive.
What is a founding member?
A founding member is one of the first members recruited personally before a community opens more widely. Founding members shape the norms, seed early conversations, and often receive recognition or benefits in return, such as a permanent badge, lifetime pricing, or a role in governance.
Should a new community be free or paid?
It depends on the model. Paid membership filters for commitment and funds the work, and professional communities often charge from day one. Free works when the community supports another revenue source, such as an association's dues or a product. Either way, be clear about the promise and the expectations.
How long does it take to build a community?
Expect three months to establish rhythm with founding members, six to twelve months to reach self-sustaining member-to-member activity, and one to two years for a mature community with member leaders and visible business value.