The First Ten Members: Why Who You Invite First Decides Everything
Every founder spends time thinking about what their community will eventually become. Fewer spend any real time thinking about who the first ten people in it will be, and that's a strange gap, because those ten people do more to determine what the community eventually becomes than almost any decision that comes after. A rule you write in month six can be rewritten. A feature you add in month nine can be removed. The tone set by your first ten members, though, calcifies faster than founders expect, and it calcifies in ways that are extremely difficult to reverse once a hundred more people have joined and absorbed it as "how this place is."
This isn't a mystical claim about community magic. It's a fairly mechanical consequence of how new members orient themselves in an unfamiliar space. Nobody reads your rules page as carefully as they read the actual behavior happening in front of them. A newcomer scrolling through your general channel isn't parsing your carefully worded code of conduct — they're pattern-matching against the last twenty messages they can see. If those messages are warm, curious, and generous, the newcomer calibrates toward warmth, curiosity, and generosity. If those messages are terse, sarcastic, or cliquish, the newcomer calibrates toward that instead, often without consciously noticing they're doing it. The first ten members aren't just early adopters. They're the training data for everyone who comes after them, and a training set that size is disproportionately powerful precisely because there's so little else to compete with it yet.
The instinct to invite everyone you know, and why it backfires
The most common approach founders take is the path of least resistance: post the invite link everywhere you can think of, DM everyone in your contacts who might plausibly care, and let whoever shows up, show up. This feels efficient. It is almost never the right move, and the reason comes down to a mismatch between what "more people" gets you and what a fragile new community actually needs.
A brand-new space needs a small number of people who will reliably do three things: post first, respond quickly when someone else posts, and model the tone you actually want the place to have. An indiscriminate blast invite optimizes for none of these. It optimizes for headcount, and headcount without engagement is worse than no headcount at all, because a member list showing forty names next to a general channel with three messages tells every visitor exactly the wrong story — that the place is dead, that nobody here actually talks, that joining would mean shouting into an empty room. You'd genuinely be better off with six people who post daily than sixty people who joined once and never opened the app again, because the six create a texture of activity that a newcomer can walk into and immediately understand, while the sixty create exactly the silence that kills new communities in their first month.
There's also a subtler cost to the blast-invite approach: it front-loads people who have no particular stake in whether the community succeeds. Someone who joins because a friend happened to share a link in a group chat has approximately zero investment in whether the space develops a healthy culture. They'll lurk, or leave, or occasionally post something low-effort, and none of that is malicious — it's just what happens when the barrier to joining was near-zero and the person's actual interest in the topic was moderate at best. Compare that to someone you deliberately reached out to because you know they care about the exact thing your community is about. That person joins with intent already baked in. They're far more likely to post something substantive in week one, and far more likely to still be around in month six, because they didn't wander in — they were invited for a reason, and reasons tend to produce follow-through in a way that passive discovery doesn't.
What you're actually looking for in a founding member
Enthusiasm for the topic is necessary but nowhere near sufficient. Plenty of people who are genuinely excited about a subject are terrible founding members, because excitement about a topic and willingness to post first in an empty room are two entirely different traits, and the second one is the one that actually matters in the earliest days. The person you want is someone who has, in other contexts, demonstrated a specific and somewhat rare behavior: they start conversations without needing an existing conversation to reply to. Watch how someone behaves in group chats you already share with them. Do they ever send the first message of the day, or do they only ever reply to something someone else opened? Do they ask questions of the group, or only answer questions when asked directly? The people who initiate are disproportionately valuable in a founding cohort, because initiating is exactly the skill an empty community needs most and has the least natural supply of.
Generosity of response matters just as much as initiation. A founding member who reliably replies — with something more substantial than a one-word acknowledgment — to whatever anyone else posts is doing an enormous amount of invisible labor. Every post that gets a thoughtful reply within the first hour teaches the poster, and everyone who later reads that thread, that this is a place where speaking up gets you engagement rather than silence. Silence is the single biggest killer of new communities, more than bad rules, more than the wrong platform, more than a founder who's occasionally slow to respond. A founding cohort of even three or four people who've committed to responding to new posts quickly can single-handedly prevent that silence from ever taking hold, buying enough time for organic replies from other members to start happening on their own.
Tone-setting is the third quality, and it's the hardest to screen for because it's the least visible until it's already a problem. Some people are naturally warm in how they communicate — quick to encourage, generous in reading intent charitably, comfortable admitting when they don't know something. Others default to a more clipped, competitive, or sarcastic register, which can read as perfectly normal one-on-one but sets a very different tone when it's one of only three visible voices in a brand-new space. Neither register is a moral failing. But if your goal is a community that feels welcoming to strangers, you want your founding cohort skewed toward the warmer register, because their default mode of communication is what a newcomer will assume the entire community's default mode is, at least until enough other evidence accumulates to update that impression.
The right number is smaller than you think
Founders often imagine that the pre-launch phase should involve as many people as possible, on the theory that a bigger initial base means more momentum. In practice, somewhere between five and fifteen deliberately chosen people produces far better results than fifty loosely interested ones, for reasons that come down to coordination and visibility. With five to fifteen people, you can actually reach every one of them personally — a real message, not a mass blast — explaining what you're building and why you specifically thought of them. That personal outreach does two things simultaneously: it filters out anyone who isn't genuinely interested (because a personal message invites a real yes-or-no response in a way a public link doesn't), and it creates a sense of obligation that a public invite never generates. People who were personally asked show up differently than people who self-selected off a shared link, and that difference persists for months.
There's a coordination benefit too. With a small founding group, you can actually talk to all of them at once — in a separate side channel, a group chat, a call — and get real alignment on what the first few weeks should look like: who's going to seed which topics, who's on point for replying quickly during which hours, what the unwritten tone should be. Try that coordination with fifty people and it collapses into noise; nobody reads a fifty-person group announcement carefully, and nobody feels personally responsible for anything when responsibility is diffused across that many names. Small groups create accountability. Large groups dissolve it.
The other reason smaller is better: your new space needs to look proportionate to its size, not undersized for an imagined future size. A member count of nine sitting next to an active-feeling general channel reads as a cozy, real thing that a curious visitor might want to be part of. A member count of ninety sitting next to the same three messages reads as a graveyard. Undersizing your ambitions for the first month, on purpose, is one of the more counterintuitive but reliable pieces of advice for new founders — you can always expand the invite list later once there's something worth joining, but you can't easily undo the impression left by a big number attached to nothing happening.
How to actually make the ask
The message you send to a prospective founding member matters more than founders tend to assume, because it's doing real persuasive work, not just logistical work. A generic "hey, check out this thing I made" undersells both the opportunity and the ask. What actually works is being specific about two things: why you thought of this particular person, and what you're specifically hoping they'll do, not just that you'd like them to join.
Being specific about why you thought of them does something important — it signals that this isn't a mass invite dressed up as a personal one. "I'm starting a small space for people who actually finish their side projects instead of just talking about starting them, and you're one of maybe three people I know who's actually shipped something in the last year" is a completely different message than "hey come join my new community," even though both are technically invitations to the same place. The first version tells the recipient they were chosen for a reason connected to who they specifically are. That distinction changes how seriously people take the invitation and how much effort they put into their first few posts once they've joined.
Being specific about the ask matters just as much. Don't just ask someone to join — ask them to do something concrete in the first week. "Would you be up for posting something about what you're currently working on sometime in the first few days, just so there's something for people to react to?" gives a prospective founding member a clear, low-friction first action, rather than leaving them to figure out on their own what an appropriate first post even looks like in a space with no existing posts to reference. Most people, left to their own devices in a new empty community, default to lurking, not because they don't want to participate but because the first move in an empty room is genuinely the hardest one, and an explicit, low-stakes suggestion removes that friction almost entirely.
Seeding the first conversations before anyone else arrives
Even with a strong founding cohort assembled, the founder still carries most of the weight in the earliest days, and one of the highest-leverage things a founder can do is post real content before asking anyone else to. Not a generic welcome message — genuine, substantive posts that demonstrate exactly the kind of contribution you're hoping to see from others. If your community is about a hobby, post your own detailed project update, complete with photos and the specific problems you ran into, not a vague "excited to be here." If it's about a shared interest, post a genuinely interesting take, a question you've actually been wrestling with, something that invites a real response rather than a polite acknowledgment.
This matters for two reasons. First, it gives your founding cohort something concrete to react to, which is far easier than generating original content into a void — replying is always lower friction than initiating, so a strong first post from the founder unlocks a wave of easier follow-on engagement from everyone else. Second, and less obviously, it establishes a template. The very first few posts in any community become the implicit standard for what "a normal post here" looks like, in the same way the first few employees at a company set an implicit standard for what "normal work" looks like there long after the company has grown far past them. If your first post is thoughtful, specific, and a little vulnerable, you're quietly setting the expectation that posts here should be thoughtful, specific, and a little vulnerable. If your first post is a one-line placeholder, you're setting the opposite expectation, whether you intend to or not.
A useful practice in the first two weeks is to seed one substantive post per day yourself, spread across different angles of your topic, so that a newcomer arriving on any given day finds more than a single thread to explore. This is real work, and it's the part of founding a community that looks the least like the fun, social parts founders imagine when they first get the idea. But it's the work that determines whether the space still exists in month three, and there's no way around doing it personally in the earliest stretch, because nobody else has the standing yet to do it for you.
What to do about the well-meaning wrong invite
Sometimes the mismatch isn't malicious — it's just a case of a genuinely nice person who happens to be wrong for a founding cohort. Maybe they're interested in the topic but communicate in a way that reads as combative even when they don't mean it to. Maybe they're the kind of person who only ever posts once every few weeks, which is fine in an established community with dozens of other voices but corrosive in a founding cohort of five, where every silence is conspicuous. Founders often feel obligated to invite these people anyway, out of loyalty or guilt, and then feel stuck when the resulting dynamic doesn't work.
The honest answer is that you don't owe anyone a spot in your founding cohort, and being thoughtful about who's in it isn't exclusionary in any meaningful sense — the community isn't closed, it's just sequenced. Someone who isn't a fit for the first ten people can absolutely be a wonderful member number forty, once there's enough existing culture and activity that their particular communication style gets absorbed into a bigger, more varied whole rather than defining the whole tone on its own. If you're worried about hurt feelings, the honest move is simply not overselling the founding invite as more exclusive or significant than a normal invite — most people don't actually track whether they were member three or member thirty, and the ones who do generally aren't the ones you needed to worry about in the first place.
Watching the tone take shape, and correcting early
Even with careful selection, tone doesn't always land exactly where you intended, and the earliest days are also the cheapest time to correct it, because there's so little inertia yet to fight against. If you notice, in the first couple of weeks, that the register of conversation is skewing more combative or cliquish than you wanted — inside jokes forming that exclude newcomers, a slightly dismissive tone toward questions that read as basic — it's worth naming that directly and quickly, rather than hoping it self-corrects. A quiet, friendly note in your side channel with the founding cohort ("hey, I want to make sure new people feel like they can ask beginner questions without it feeling like an interrogation — can we all be a little more deliberate about welcoming those?") costs almost nothing to say and can meaningfully shift the trajectory while the group is still small enough that everyone actually reads what you post.
Waiting until the tone has fully calcified across fifty or a hundred members is a much harder position to correct from, both because there are more people whose existing habits you'd be asking to change, and because by then there's a real community identity wrapped up in "how we talk to each other here" that people will resist having named as a problem, even gently. The first two weeks are uniquely cheap to steer. Every week after that, steering gets a little more expensive, and by month three or four, in a community that's grown past its founding cohort, steering tone is closer to a slow cultural project than a quick correction. Use the cheap window while you have it.
What the first ten members teach you about your own idea
There's a diagnostic benefit to being deliberate about your founding cohort that founders rarely anticipate going in: watching how ten thoughtfully chosen people actually respond to your concept tells you, with far more honesty than any amount of solo planning could, whether the idea has real legs. If you personally reach out to twelve people you'd specifically want in a founding cohort and only three say yes with any enthusiasm, that's genuinely useful information, delivered a lot more cheaply than discovering the same thing after building out an elaborate structure and blasting an invite link into the void. It might mean the concept needs sharpening. It might mean you're pitching it wrong. It might mean the timing is off. Whatever it means, you get to find out before you've sunk weeks into infrastructure nobody asked for, and that's a genuinely valuable trade even setting aside everything else the deliberate approach gets you.
The inverse is true too. If ten people you personally respect and personally selected for their engagement habits all say yes quickly and enthusiastically, that's a much stronger signal about the health of your idea than any number of anonymous joins off a public link ever could be, because you know these are people who initiate, respond, and set a good tone — which means you're not just hearing "yes, this sounds interesting," you're hearing it from exactly the people whose engagement will determine whether the thing actually works. That's a signal worth paying attention to, and it's one that only becomes available to founders willing to do the slower, more deliberate work of choosing their first ten people instead of skipping straight to the announcement.
A short list of what actually matters, distilled
Choose people who initiate conversations unprompted in contexts you've already seen them in, not just people who claim to be interested in your topic. Prioritize a small, personally reached-out-to group over a large, passively acquired one — five to fifteen real people beats fifty half-interested ones, every time, in the earliest weeks. Make the ask specific: explain why you thought of this person, and give them something concrete to do in week one rather than leaving the first move up to their own imagination. Post real, substantive content yourself before asking anyone else to, because the founder's first posts set the implicit template for what a normal contribution looks like. Watch tone closely in the first two weeks, while correcting it is still cheap, and say something directly the moment it starts skewing away from what you want, rather than hoping it resolves on its own. And treat the response you get from your founding outreach as real information about your idea, not just a logistics step to get through on the way to the "real" launch — because in a very real sense, this quiet, unglamorous outreach phase is the real launch, and everything after it is just what that launch grows into.
None of this guarantees a thriving community six months out. Plenty of variables sit outside a founder's control no matter how carefully the first ten members are chosen — timing, platform shifts, plain bad luck. But of every lever available to a founder in the earliest days, this is the one that costs the least and moves the outcome the most, and it's also the one that's easiest to skip past in the excitement of finally getting to build the thing you've been imagining. Slow down for it. The community you end up with in a year is, more than founders like to admit, downstream of the ten people who were in it during the first week.