How to Recruit Founding Members
# Format: Playbooks
# Community
How to identify, personally invite, and support the small group of people who set the tone for a new community.
July 27, 2026
Joshua Zerkel
At a glance
- Define what makes someone a good founding member before you start reaching out.
- Look for relevant experience, a genuine reason to participate, curiosity, and generosity.
- Recruit personally. A broad announcement won't produce real founding members.
- Explain why each person was invited and what kind of participation would help.
- Make the ask specific: an introduction post, an event, feedback, or answering peer questions.
- Offer something real in return, and keep the group small enough to support directly.
Introduction
Every community has a founding group whether or not anyone planned for one. The first 10 or 15 people who actually post set the tone that everyone after them inherits, whether that's generous and curious or quiet and transactional. I've seen teams treat this stage as a numbers exercise, invite as many customers as possible and hope a few turn into regulars. That approach produces a list, not a founding group.
Recruiting founding members is closer to casting than broadcasting. You're choosing specific people for specific reasons, and you're asking something of each of them personally. Done well, the group is small, engaged, and already modeling the kind of participation you want to see at scale. Done as a mass invite, most people accept and never show up, and the space you eventually launch to a broader audience still looks empty.
This guide covers who to look for, how to make a personal and specific ask, and what to offer people in return for showing up early.
When this matters
This work matters most in the run-up to a launch, right after you've settled on purpose, audience, and launch shape, but before any broader invite goes out. It also matters when an existing community has plateaued and needs a fresh group of engaged people to reset the tone, or when a new segment, program, or sub-space opens inside a community that already exists.
Any time a space is about to open to more people than you can personally support, the question of who goes in first, and why, needs an answer before the invite does.
What matters most
Define the profile before you start recruiting
A founding member is defined by what they'll actually do in the first weeks: post, answer questions, and set an example for people who join later. Before recruiting anyone, get specific about the profile you're looking for, rather than defaulting to "anyone who says yes." I look for a mix of relevant experience, a genuine reason to be there, curiosity about what the community could become, and some natural generosity, the willingness to answer a peer's question without being asked twice. Not every founding member needs all four, but someone with none of them rarely turns into a real contributor no matter how enthusiastically they accept the invite.
The ask has to be personal
A broad announcement to a list produces acceptances more often than participation. People say yes to an invite and then never post, because nothing about a generic message asked anything specific of them. I reach out to founding members directly, by name, and tell them why I thought of them specifically. That single sentence, here's why I invited you, does more to convert an acceptance into an actual first post than anything else in the recruiting process.
Make the ask specific enough to act on
"Be active" is not an ask anyone can act on immediately. A specific ask is: post an introduction this week, come to the launch event, share one thing that's worked for you, or answer a question in your area of expertise. Specific asks convert into action because they remove the guesswork about what a good first move looks like. I'll usually give each founding member one concrete thing to do in their first week, not a general invitation to participate whenever they feel like it.
Offer something real in return
Recruiting shouldn't feel one-sided. Founding members are doing real work, whether that's writing the first posts, answering questions with no community around them yet, or bringing credibility to a space that doesn't have any yet. What I offer back varies by person: early access to something, visibility with a product or leadership team, more influence over how the community develops, or simply a genuine connection to people solving similar problems. Figure out what each person actually values before assuming the invite itself is the reward.
Keep the group small enough to actually support
The instinct to recruit broadly, on the theory that more people means more content and more safety in numbers, works against you here. A founding group of 30 you can't personally track is worse than one of 10 you know well enough to notice who's struggling, who's thriving, and who needs a nudge. I've never regretted starting smaller than felt comfortable. I have regretted recruiting a group large enough that half of it became invisible to me.
Be honest about what the role actually asks
Founding members are taking on real work, even when the ask feels small, and treating the invite as if it were purely an honor undersells what you're asking of someone. Tell people plainly that this stage will ask more of them than being a regular member later will, roughly how long that heavier lift is likely to last, and what changes once a broader group arrives. People are usually more willing to commit to a demanding early role when it has a clear shape and an end point, rather than being asked to sustain founding-member energy indefinitely without ever being told when that stops being the expectation.
Putting it into practice
1. Write the founding member profile.
Decide what mix of experience, reason to participate, curiosity, and generosity you're looking for before reaching out to anyone. Output: a short profile you can use to evaluate candidates.
2. Build a candidate list from real sources.
Pull names from customer success, sales, support, existing community activity, and your own network, not just a marketing list. Output: a list of 20 to 30 candidates for a founding group of 10 to 15.
3. Reach out personally to each one.
Contact each candidate by name and explain specifically why you thought of them. A form invite undermines the personal recruiting this stage depends on. Output: a personal message sent to each candidate.
4. Give each person one specific ask.
Tell each founding member exactly what a good first action looks like: an introduction, a specific question to answer, or an event to attend. Output: a documented first ask for every confirmed member.
5. Confirm what you're offering in return.
Decide what each person actually values, access, visibility, influence, or connection, and make sure it's real before you promise it. Output: a clear value exchange for each founding member.
6. Set a support cadence for the group.
Plan how you'll check in with founding members individually during the first weeks, not just as a group. Output: a simple schedule for personal follow-up.
7. Tell people how long the founding phase lasts.
Let each founding member know roughly when the group opens up more broadly and what changes for them at that point. Output: a clear timeline shared with the founding group.
Where teams get stuck
The most common obstacle is defaulting to a mass invite because personal recruiting feels slow when there's already a launch date set. I'd resist this. A rushed founding group that never posts costs more time later than a few extra days spent reaching out individually now, since a founding group with no real participation still has to be reset before a broader launch can succeed.
A second obstacle is recruiting people who look right on paper, active customers, engaged accounts, but don't actually have a reason to participate beyond being asked. Ask directly what they'd get out of it before assuming enthusiasm from a sales or CS relationship translates into community participation.
A third obstacle is treating the founding group as a one-time recruiting task instead of an ongoing relationship. People who agreed to help six weeks ago need a reason to still be showing up in week three. A quick, specific personal check-in, one that references something they actually posted, usually does more than a broadcast reminder asking the whole group to stay engaged.
Before you move on
- A founding member profile is defined, not just a headcount target.
- Candidates are pulled from real sources, not just a marketing list.
- Each candidate has been contacted personally, by name.
- Every confirmed member has one specific first ask.
- What you're offering each person in return is real and specific.
- The group is small enough to support and check in with directly.
What good looks like
Here's what a founding member recruiting plan might look like once each piece has an answer:
Recruiting element | Example output |
|---|---|
Founding member profile | Existing customers with six or more months of product use and a documented workflow challenge |
Candidate source | 25 names from customer success and support ticket history |
Personal outreach | Individual message naming the specific reason each person was invited |
Specific ask | Post one introduction and answer one peer question in week one |
Value exchange | Early access to a new feature and direct input on the community roadmap |
How to know it's working
Watch the gap between who accepts the invite and who actually posts in the first two weeks. A wide gap usually means the ask wasn't specific enough, or the person didn't have a real reason to participate beyond agreeing to help. This gap is often the single most useful number to track early on, since it isolates whether the recruiting itself or the follow-through afterward is the weaker link. Track how many founding members post more than once without being prompted again, since a single obligatory post says less about real engagement than a second one that nobody asked for.
Qualitatively, notice whether founding members are referencing each other's posts, welcoming new people themselves, or answering questions before you do. That's a sign the group is starting to function as a community rather than a set of individual relationships with you.
On the business side, look at whether founding members are becoming more visible advocates elsewhere, in reviews or renewal conversations, though this is a slower-moving signal than activity metrics. It usually shows up later than the first 30 days, so treat it as something to revisit at the 90-day mark rather than an immediate return.
Key takeaways
- Define the founding member profile before recruiting anyone.
- Recruit personally. A broad announcement won't produce real participation.
- Make the ask specific enough that people know exactly what to do first.
- Offer something real in return, matched to what each person actually values.
- Keep the group small enough to support and notice individually.
Common questions
How many founding members should we recruit?
Somewhere between 10 and 20 is usually enough to create real momentum without becoming too large to support personally. The right number depends more on how much individual attention you can give than on any fixed target.
What if someone accepts but never actually participates?
Follow up once, personally, and ask if the specific ask still makes sense for them. If they still don't engage after that, it's fine to let them stay quiet in the group rather than pushing further. Not everyone who accepts an invite turns into an active contributor, and that's expected.
Should founding members be customers, internal experts, or both?
Both, usually. Customers bring credibility and real problems. Internal experts bring answers and consistency in the early days. A mix of both tends to produce more useful early activity than either group alone.
Like
Comments (0)
Popular
ďťż
Dive in
Related
Resource
Playbook: How to Prepare Members for a Community Migration
By Patricia Feitosa â˘Â May 26th, 2026 ⢠Views 48
Resource
Playbook: Supporting Members After A Community Migration
By Ryan Paredez â˘Â Feb 27th, 2026 ⢠Views 25
Resource
Building Advocacy Funnels: From Community Members to Champions
By Joshua Zerkel â˘Â Dec 4th, 2025 ⢠Views 19
33:07
Video
Event Replay: Context First: Helping Members Build New Habits During a Migration
By Patricia Feitosa â˘Â Apr 10th, 2026 ⢠Views 25
Resource
Playbook: How to Prepare Members for a Community Migration
By Patricia Feitosa â˘Â May 26th, 2026 ⢠Views 48
Resource
Building Advocacy Funnels: From Community Members to Champions
By Joshua Zerkel â˘Â Dec 4th, 2025 ⢠Views 19
33:07
Video
Event Replay: Context First: Helping Members Build New Habits During a Migration
By Patricia Feitosa â˘Â Apr 10th, 2026 ⢠Views 25
Resource
Playbook: Supporting Members After A Community Migration
By Ryan Paredez â˘Â Feb 27th, 2026 ⢠Views 25