Skip to content

Community Growth Strategies: How to Grow Participation, Not Just Member Counts

Member counts hide what matters. How to grow participation instead of signups, get the first hundred members, and turn lurkers into contributors.

August 4, 2026 · Eugene Suslov

Key takeaways:

  • Member count is the wrong target. In most online communities 90% of people never post, 9% contribute occasionally, and 1% produce nearly all the activity.
  • The same distribution means 5,000 members yields roughly 50 real contributors and 200 members yields two, so critical mass matters more than reach.
  • The first hundred members decide the norms, so recruit them individually rather than announcing a launch.
  • Retention is the growth strategy, because a community that keeps people compounds and one that leaks needs constant recruitment.

Most community growth strategies are really recruitment strategies. Run a launch campaign, add a signup link, cross-promote, offer an incentive. All of it moves the member number, and none of it addresses the thing that determines whether a community survives, which is whether anyone talks.

I have watched several companies launch a community, hit a thousand members inside two months, and quietly archive it a year later. In every case the member count looked healthy the whole way down. The number that was dying was invisible on the dashboard.

This covers how community growth actually works, what to target instead of signups, how to get the first hundred people, how to convert lurkers into contributors, and when the honest answer is not to build one at all.

What growth actually means here

A community has two populations and they behave nothing alike.

Members have joined. They occupy a row in a database and they cost you nothing except the illusion of progress.

Participants post, reply, answer questions and show up unprompted. They are the community in any meaningful sense, and every valuable thing a community produces comes from them.

Community growth strategies that target members and those that target participants look completely different. The first optimizes for reach and friction removal. The second optimizes for the experience of the twentieth visit rather than the first.

The practical consequence is that most community metrics are misleading by design. If your dashboard leads with total members, it will tell you things are going well right up until the point where the last regular contributor stops posting.

The 90-9-1 problem

There is a well-established pattern here, and understanding it changes what you plan for.

Nielsen Norman Group's analysis of participation inequality describes the distribution that recurs across large online communities: roughly 90% of users are lurkers who never contribute, 9% contribute occasionally, and 1% account for almost all the activity. The specific split varies, but the shape is remarkably consistent, and it has held since the pattern was first studied in the early 1990s.

Run the arithmetic on that and most community growth strategies write themselves. A community of 5,000 members produces around 50 people doing nearly all the talking. A community of 200 produces two, which is not enough to sustain a conversation and is why small communities feel dead even when the members are genuinely interested.

The same rule applied at two scales is what makes critical mass a real threshold.

Community growth arithmetic: 5,000 members yields 50 contributors, 200 yields two.

Two conclusions follow. First, you need a critical mass before a community becomes self-sustaining, and below it you have to manufacture the activity yourself. Second, the work with the most upside is not recruiting more lurkers, it is moving people from the 90 into the 9, because that is where the ratio actually improves.

Most branded communities never attempt the second thing.

Why most branded communities die

Four failure patterns account for nearly all of them.

The first is launching to nobody. A community opens with an announcement, a hundred people join out of curiosity, find an empty space, and never return. Emptiness is self-reinforcing.

The second is being a support queue in disguise. If the only reason to post is that something is broken, every thread is a complaint and nobody visits for pleasure.

The third is the company doing all the talking. A space where the brand posts announcements and members occasionally react is a newsletter with extra steps.

The fourth, and the most common, is that the community was built for the company's benefit rather than the members'. People can tell within one visit, and the tell is what happens when someone asks a question the product does not answer.

Choosing where it lives

Platform choice is less important than people think and more consequential than they expect, mostly because it determines who can find you and what you keep.

Where

Best for

Real cost

What you give up

Slack or Discord

Fast-moving peer conversation, developer audiences

High moderation load

Searchability; history disappears

Owned forum platform

Compounding, searchable knowledge

Platform fees and slow start

Convenience; people must choose to visit

LinkedIn or Facebook group

Borrowing an audience that already exists

Low, but reach is rented

Ownership, data, and control

Subreddit

Public discovery and genuine reach

Moderation and community scrutiny

Control over norms and tone

Circle, Bettermode or similar

A structured space with events and courses

Subscription plus setup

Some of the informality

The question underneath is whether you need conversation or knowledge. Chat platforms produce conversation and destroy knowledge, since a great answer in Slack is unfindable within a fortnight. Forums produce knowledge and start slower.

Every option on that list buys something and quietly bills you for something else.

Five community platforms listed against what each one costs you in return.

Teams that need both usually run a chat space for the regulars and publish the good answers somewhere permanent, which is an editorial job rather than a community one.

Whichever you choose, model what the community would need to be worth in retained revenue or deflected support before you commit a year of somebody's time, which is the arithmetic my free calculators are built for.

Member counts grow on their own. Participation does not.

A community with no owner becomes a feed nobody posts in. Somebody has to seed, answer, moderate and decide what it is for, every week, for months.

30 minutes. If a fractional Head of Content is not the right move, I will say so.

The first hundred members

Everything afterward is shaped by this phase, and none of it can be automated.

Recruit them one at a time, by direct invitation, from people you already know are interested. Not a launch announcement. Individual messages explaining why you thought of that specific person, which is slow and is the reason it works.

Choose them for propensity to talk rather than seniority. Ten opinionated practitioners will build a better community than a hundred VPs who joined to be polite. Seed the space with genuine questions before you open it, so early arrivals find a conversation in progress rather than a blank room.

Then, for the first three months, treat it as your job to reply to everything. Every post gets a substantive response quickly, because the strongest signal a new community can send is that posting is worth it.

Understanding what those early members actually want out of it is worth doing properly rather than assuming, and it is the same discipline as a content marketing audit: ask what people came for before deciding what to give them.

Turning lurkers into contributors

This is the work that changes the 90-9-1 ratio, and it is mostly about lowering the cost of a first post.

Ask questions only a member can answer

Broad questions get no answers because nobody feels qualified. Specific ones aimed at experience get replies: "what did you use before this, and what made you switch" invites anyone to contribute.

Make the first contribution trivially small

A poll, a one-word answer, a reaction. The gap between never having posted and having posted once is much larger than the gap between one post and ten.

Invite named people directly

"You mentioned you had solved this, would you be willing to share how" converts far better than any general prompt. It is not scalable and it does not need to be, because you are trying to create the 9%, not the 90%.

Make contributors visible

Recognition is the cheapest currency you have. Highlight good answers, credit people by name, and let the regulars become identifiable to each other. A community where the same six names are recognizable is one people return to.

Norms and moderation

Communities are governed by what gets tolerated, not by what the rules page says.

Set the norms early and enforce them visibly while the group is small enough for that to be easy. The three that matter most are how self-promotion is handled, how disagreement is handled, and whether the company gets special treatment.

That third one is worth deliberate thought. A community where the brand's word ends every argument is not a community. Letting a customer publicly disagree with you, and responding well, does more for credibility than any amount of content.

Moderation load scales with activity, not membership, which is another reason participation-focused growth needs planning. Ten thousand silent members cost nothing to moderate. Three hundred active ones is a real job.

The variable that drives the workload is not the one on the dashboard.

Moderation load scales with community activity rather than membership count.

That load is also why community is one of the first things companies try to outsource and one of the last things that survives being outsourced, a tension worth weighing before briefing any of the B2B content marketing agencies on it.

Retention is the growth strategy

Every community leaks. The question is whether it leaks faster than it fills, and this is where most growth plans quietly fail.

A bibliometric review of customer loyalty and retention in digital environments found that organizations able to retain customers gain greater capacity for expansion, financial stability and long-term planning, and identified emotional connection as a recurring driver of loyalty across the literature.

That translates directly. People stay in communities where they have relationships, not where they have access to information. Information is available everywhere; the specific group of people who recognize your username is not.

The practical version is that retention work looks like introductions, recurring rituals and recognition rather than content. A monthly call where regulars actually speak does more for retention than a resource library nobody opens.

Recognition is the lever most teams under-invest in first, and reversing that is what turned several of the programs in the case studies around: what compounded was a reason to come back, not a bigger push to arrive. Transkriptor is a busyless client where the same principle applied to content did the work: 27,000 new visitors arrived because there was a genuine reason to come back, not because a campaign pushed them once.

Community is one of the two or three, or it is nothing.

Run it as a side project and it dies quietly. I would rather tell you it is the wrong channel for you than watch it become another dormant account.

Weekly working sessions, one monthly report, and a quarterly kill of what did not move.

What to measure

Replace the member count with numbers that describe participation.

Metric

What it tells you

Healthy direction

Active contributors per month

The real size of your community

Growing faster than membership

Percentage of members who ever post

Your position against 90-9-1

Above 10% is good

Replies per thread

Whether conversation happens or posts sit alone

Above two

Time to first reply

Whether posting feels worthwhile

Under a few hours

Share of threads started by members

Whether it is yours or theirs

Rising over time

Returning contributors

Retention, the one that predicts survival

Flat or rising

Time to first reply is the one I would watch above all others in year one. It is the clearest signal a new member gets about whether this place is worth their attention, and it is entirely within your control.

Wiring these into something that refreshes on its own, rather than assembling them by hand each month, is the same job as any other reporting layer and belongs in the same place as your customer journey optimization tracking.

Community-led growth for B2B SaaS

For software companies specifically, a community earns its budget through three mechanisms rather than lead generation.

Support deflection is the easiest to measure: members answering each other reduces ticket volume, and the answers are often better because they come from people running the same setup.

Product signal is the most valuable and the least tracked. A community surfaces what people are actually struggling with, in their own words, months before it appears in a survey. That material is also the best possible input for content, which is why a community and an editorial program feed each other so well and why content engineering treats them as one system.

Retention and expansion are the commercial payoff. Customers with peer relationships attached to your product churn less, and the effect is larger for products with a learning curve.

Three mechanisms carry the budget, and the fourth one everybody expects is not among them.

Three ways a B2B SaaS community pays, with new logo acquisition ruled out.

Notice that none of those is new logo acquisition. Communities do produce it, slowly and unpredictably, and building one on that promise is how they end up canceled at the twelve-month review.

When not to build one

Sometimes the answer is no, and it is worth saying so.

Do not build one if your customers have nothing to say to each other, which is common for products bought once and used alone. Do not build one if you cannot commit a named person for at least an hour a day for six months, because an unattended community is worse than none. And do not build one to generate leads, because it is a poor instrument for that and the incentives it creates will make it unpleasant.

The hour-a-day test is the one that disqualifies most plans, and it is worth applying honestly before anything is announced. A community is a standing commitment rather than a campaign, so the question is not whether you can launch it but whether you will still be answering posts in month nine, when the novelty has gone and the results have not yet arrived.

If your buyers already gather somewhere, participating there is usually the better move. Understanding where those conversations already happen is ordinary research and overlaps heavily with competitive intelligence: find the room before you build one.

Choosing not to run a community is a legitimate strategic decision. Running one badly is not a neutral outcome, because an abandoned space is public evidence that you started something and stopped.

Where this leaves you

Community growth strategies fail because they solve a recruitment problem the community did not have. Participation is the real constraint, which is why so much effort goes into signups and so little into the twentieth visit.

Target contributors instead of members, get the first hundred people by hand, spend the first quarter making posting feel worthwhile, and measure whether people come back. The member count will follow, and it will mean something when it does.

Not every audience wants a community, and finding that out early costs almost nothing. Book a call and I will pressure-test whether yours would turn up before anyone builds anything.

FAQ

Frequently asked

  • What are the most effective community growth strategies?
    Recruit the first hundred members individually rather than announcing a launch, seed genuine conversation before opening the space, reply substantively to everything for the first three months, and invite named people to answer questions they are qualified for. After that, the highest-return work is converting lurkers into occasional contributors, since participation rather than membership determines whether a community survives.
  • How do you grow an online community from nothing?
    Start with people you already know are interested and message them one at a time, explaining why you thought of them specifically. Aim for people likely to talk rather than impressive job titles. Populate the space with real questions before anyone arrives so it does not look empty, then treat replying quickly as your main job for the first quarter. Growth compounds only after there are enough regulars to sustain conversation without you.
  • What is community-led growth for B2B SaaS?
    It is using a customer community as a growth mechanism, primarily through support deflection, product signal and retention rather than new customer acquisition. Members answer each other's questions, which reduces tickets and often produces better answers; their conversations reveal real problems long before surveys do; and customers with peer relationships around a product churn less. It is a poor lead generation channel and communities built on that promise usually get canceled.
  • How many members does a community need to be self-sustaining?
    Enough that roughly 1% of them being highly active is still a viable number of people. Since participation typically follows a 90-9-1 pattern, a few hundred members produces only a handful of regular contributors, which is generally too few for conversation to continue without prompting. Most communities need to manufacture activity deliberately until the active contributor count reaches a few dozen.
  • How do you measure community growth properly?
    Track active contributors per month, the share of members who have ever posted, replies per thread, time to first reply, and how many threads members start rather than the company. Time to first reply is the most useful early signal, because it tells a new member whether posting is worth the effort. Total membership is the least useful number and the one most dashboards lead with.

Written by

Eugene Suslov

Eugene Suslov

Fractional Head of Content for B2B SaaS | Strategy + custom AI automation that drives pipeline (without a full-time hire)