The first meaningful community milestone is not 10,000 followers, 5,000 Discord members, or a trending announcement.

It is 100 people who understand why the project matters and repeatedly choose to participate.

That number is small enough for a team to know many members directly and large enough for useful patterns, peer relationships, and early culture to emerge. It forces the company to learn why people return before paying to acquire thousands who do not.

Define "cares" as behavior

Do not define an active member as someone who joined a server or reacted to an announcement.

For the first 100, require one or more meaningful behaviors:

  • attended two sessions;

  • answered another member's question;

  • tested the product and submitted useful feedback;

  • created a resource, integration, or piece of content;

  • introduced a relevant participant;

  • returned in multiple weeks;

  • completed an economically or commercially valuable action.

The definition should reflect what makes the product or network stronger.

Recruit from a narrow shared problem

Broad communities struggle because members have little reason to recognize one another.

"People interested in Web3" is not a useful initial group. "Treasury leaders at crypto companies evaluating stablecoin yield and counterparty risk" is. Narrowness increases the probability that one member's question is valuable to another.

Begin with a member thesis:

We are assembling [specific people] who are actively trying to [specific outcome] and can help one another by [specific exchange].

This is more compelling than asking strangers to join a company server.

Build the first cohort manually

The founding team should recruit the first 25 to 40 members through direct relationships and high-context outreach.

Look across:

  • existing customer and prospect conversations;

  • former colleagues and collaborators;

  • public contributors in adjacent communities;

  • thoughtful replies to relevant social posts;

  • event participants;

  • newsletter readers who consistently respond;

  • developers or creators already solving related problems.

The invitation should explain why that person specifically belongs, who else will participate, and what the first experience will deliver. Exclusivity without relevance is vanity. Relevance creates the feeling of being in the right room.

Start with a recurring small-group ritual

Do not launch with twenty empty channels. Launch with one repeatable reason to gather.

Examples include:

  • a weekly product teardown;

  • a private market-signal briefing;

  • a founder problem-solving session;

  • an integration clinic for developers;

  • a rotating member case study;

  • a research exchange around a narrow market.

The ritual should make members useful to one another. Collect the best questions, decisions, and resources, then return them to the group as a growing knowledge base.

Give members consequential roles

Early members should be able to influence something real.

They might test a feature, shape documentation, help select speakers, lead a working group, nominate future members, or contribute to a public guide. The role must have a visible effect. Decorative councils and meaningless badges teach people that participation is theater.

Recognition should follow contribution. Highlight the member who solved a difficult problem, introduced two collaborators, or produced a resource-not merely the person who posted most frequently.

Create a weekly member-health review

For every new member, track:

  • source of introduction;

  • reason for joining;

  • first meaningful action;

  • relationships formed;

  • contributions made;

  • last meaningful participation;

  • likely next role.

Each week, identify five members who need a better introduction, a clearer invitation, or a direct conversation. Early community operations are closer to relationship management than mass social media.

Grow through member density

Invite the next cohort only when the first group is receiving consistent value. Ask active members whom they know with the same problem and what expertise is missing from the room.

This creates density: a higher probability that any member can find a relevant conversation, collaborator, or answer. Density matters more than raw size because it produces the experiences people describe to others.

The first 100 members establish norms the next 1,000 will inherit. If the initial culture rewards speculation, extraction, and staff dependence, scale will amplify those behaviors. If it rewards useful contribution, informed disagreement, and peer support, growth has something worth multiplying.

lowob takeaway: Do not ask how to make a community look large. Ask what would make 100 specific people return without being chased.