Community-led growth gets described as a channel, which is why most attempts fail. A channel is something you switch on and measure next month. A community is a group of people who keep turning up because they get something from each other, and your company happens to be the host. I joined the WordPress community in December 2015, have spoken at 17 WordCamps, organised eleven events and led the organising team of WordCamp Kolkata 2022. This guide is what that decade taught me about how communities grow products, where founders go wrong, and how to connect community work to revenue without ruining it. If you are still choosing your growth motion, read [product-led vs sales-led vs partner-led](/insights/product-led-vs-sales-led-vs-partner-led) first.
What is community-led growth?
Community-led growth is a go-to-market approach in which a community of users, customers and practitioners does part of the work that marketing, sales and support would otherwise do alone. Members answer each other's questions, share how they use the product, recommend it to peers and tell you what to build next.
It helps to separate three things that often get mixed up.
- An audience listens to you. A newsletter list or a LinkedIn following is an audience. Communication runs one way.
- A community talks to each other. If you stopped posting for a month, conversations would continue.
- A customer base pays you. Some customers will never join a community, and some of your most useful community members will never pay.
WordPress shows what the model can do at full scale. Volunteers translate the software, review plugins, organise meetups and WordCamps, record talks for WordPress.tv and answer support questions. Companies that sell WordPress products benefit from all of it, and the good ones put time and money back in. Your company does not need that scale. It needs the same principle: people stay because the community is useful to them, and the commercial benefit follows.
Read the transcript
You are still your own head of marketing. Marketing has a budget and agencies. Nobody senior is running it.
Every campaign waits for you. Each agency reports its own numbers. Nobody senior owns the pipeline target.
What you need is a leader, not another vendor.
Senior leadership, part time. One person owns the plan and the number. You get your time back, and marketing gets a leader.
Fractional CMO, with Rahul D Sarker. Book a call at rahuldsarker.co.
When does community beat paid acquisition, and when does it not?
Community is slow to start and hard to stop. Paid acquisition is fast to start and stops the day the budget does. The right question is which fits your buyers and your stage.
Community tends to work when these conditions hold:
- Buyers already talk to each other. Developers, marketers, founders, designers and finance teams all have existing forums, meetups and groups. You are joining a habit, not creating one.
- The product has depth. If users can get noticeably better at using it, they have something to teach and learn. A simple utility gives people little to discuss.
- Trust matters more than reach. In categories where buyers ask a peer before they ask a vendor, a recommendation inside a community outweighs an advertisement.
- You can commit for years. Communities reward consistency. A programme that changes owner every two quarters never builds trust.
It tends to fail when:
- You need pipeline this quarter. Community cannot rescue a missed target. Use paid and outbound for that, and read what to cut when runway is short before you start anything long term.
- Buyers are few and senior. If you sell to fifty chief financial officers, a private dinner series or an advisory group suits them better than an open forum.
- Nobody senior will show up. A community run entirely by a junior hire, with no founder or product presence, reads as a marketing project.
| Question | Community | Paid acquisition |
|---|---|---|
| How soon does it produce pipeline? | Slowly, and unevenly at first | Within weeks of launch |
| What happens when you stop investing? | Activity declines gradually | Leads stop at once |
| What does it cost? | Mostly people and time | Mostly media budget |
| What is it best at? | Trust, retention, product feedback, referrals | Reaching known demand quickly |
| What is the main risk? | Losing patience before it compounds | Rising costs and weak lead quality |
The four jobs a community can do
Decide which job you are hiring the community for. Trying to do all four at once is the most common reason programmes stall.
- Acquisition. Members bring peers, speak about the product at events and write about how they use it. This is the job founders want, and it is the one you can least force.
- Activation and support. New users get answers from experienced ones. This shortens time to value and reduces support load. For many software companies, this is where community pays for itself first.
- Retention and expansion. Customers who have relationships inside a community are harder to lose. They also learn about features they are not yet using.
- Product insight. A healthy community tells you what is broken and what is missing, in the users' own words. It complements structured research such as win-loss interviews.
Pick one primary job for the first year. A plugin company with heavy support tickets should start with support. A developer tool with a few passionate users should start with acquisition through those users. Write the choice down, because it decides where the community lives, who runs it and what you measure.
How to start: the first 100 members
Large communities start as small groups of people who know each other. The early work is personal and does not scale, and that is the point.
- Find the existing gathering. Before you create a space, join the ones your buyers already use: subreddits, Slack and Discord groups, meetups, LinkedIn groups, WhatsApp groups. Contribute there as a person for a few months.
- Recruit ten founding members by hand. Choose customers and practitioners who already help others. Ask each one personally. Tell them what you are building and what you want from them.
- Choose one home. A forum suits searchable, lasting answers. Slack or Discord suits quick conversation. A recurring meetup suits local trust. In India, WhatsApp groups work well for small circles and badly for anything you need to search later. Start with one.
- Create a rhythm. One recurring thing that people can rely on: a monthly call, a weekly question thread, a quarterly meetup. Rhythm matters more than volume.
- Seed the first conversations. Ask specific questions, bring a member to share a teardown, and reply to everything in the first weeks. Empty rooms stay empty.
- Write short rules and enforce them. Say what is welcome and what is not, especially self-promotion. Remove spam quickly. Members judge a community by what it tolerates.
- Hand over ownership early. Ask members to host sessions, moderate topics and welcome newcomers. The first time a conversation runs without anyone from your company, you have a community.
Running it: roles, events and recognition
Open-source communities are a useful model because nobody is paid to take part, so everything depends on motivation.
Give people real roles. WordPress has organisers, speakers, translators, reviewers and video volunteers. Each role has a clear task and a visible outcome. In a company community, the equivalents are topic moderators, event hosts, beta testers and content contributors.
Use events as anchors. In my experience, relationships formed in person carry a community through quiet periods online. A meetup does not need a budget. It needs a room, a date, one useful talk and time for people to speak to each other. Regional events matter in India: a meetup in Kolkata, Pune or Ahmedabad reaches people who will never travel to Bengaluru.
Recognise contribution publicly. Thank people by name. Feature their work. Give early access, speaking slots and references. Be careful with payment: once you pay for contributions, unpaid contributors feel foolish. Reward with access and recognition first.
Keep sales out of the room. Members will ask about your product when they are ready. If sales staff message new members the day they join, word spreads and people stop joining. Agree a rule: no outreach unless the member asks or clearly signals intent.
Staff it properly. One named owner with authority, plus scheduled time from founders, product and support. A community manager who cannot get an engineer to answer a question cannot keep members.
How to connect community to pipeline without spoiling it
You need to show the business what the community produces. You can do that without turning members into leads.
- Record community membership in the CRM. Add a field on the contact and the company for community member, event attendee, speaker or contributor. The CRM data dictionary template is a good place to define these.
- Capture it at the source. Add "How did you hear about us?" as a free-text field on demo and signup forms. Community influence rarely shows up in click tracking, because people hear about you in a conversation and then type your name into a browser. Our UTM discipline guide explains where click tracking stops being useful.
- Compare cohorts, not clicks. Look at members and non-members: win rate, sales cycle length, retention and expansion. This shows whether community customers behave differently, which is the question that matters.
- Count the work the community absorbs. Track questions answered by members and the support tickets that never had to be raised.
- Report honestly. Say "influenced" when you mean influenced. A board report that overclaims community revenue loses the trust you need to keep funding it.
Expect the numbers to be small in year one. The early evidence is qualitative: members answering each other, customers quoting community advice in sales calls, and prospects arriving already convinced.
What to measure, by stage
Measure the health of the community before you measure its revenue. A community with weak participation cannot produce pipeline, whatever the dashboard says.
| Stage | What to watch | What good looks like |
|---|---|---|
| First six months | Active members, questions asked, share of questions answered by members | Conversations happen without staff starting them |
| Six to eighteen months | Returning members, member-led sessions, new members invited by members | A core group turns up every month |
| After eighteen months | Member and non-member win rate, retention, expansion, support load | Member cohorts close faster and stay longer |
There are no universal benchmarks here. Compare your own cohorts over time.
Mistakes that kill communities
Most failed communities die of the same few causes.
- Launching the platform before the people. A new Slack workspace with nobody in it is a signal that nobody cares. Gather the first members privately, then open the doors.
- Treating members as a list. Promotional broadcasts in a community space teach members to mute it.
- Measuring it like a campaign. If the programme is judged on leads in its first quarter, it will be cut before it works.
- Depending on one person. When the only organiser leaves, the community often goes with them. Share ownership from the start.
- Ignoring moderation. One aggressive member or a wave of spam can undo a year of work.
- Taking without giving. If the company only asks for testimonials, feedback and referrals, members notice. Give access, learning and recognition first.
A first-year plan
If you decide to commit, a simple sequence helps.
- Months 1 to 3: listen. Join existing communities, interview ten customers about where they learn and whom they trust, and choose the primary job.
- Months 4 to 6: gather. Recruit founding members, choose a home, start one recurring rhythm and write the rules.
- Months 7 to 9: hand over. Give members roles, run the first member-led sessions and hold a first in-person meetup where it makes sense.
- Months 10 to 12: connect. Add CRM fields, start cohort comparisons and report the first findings to leadership.
A fractional CMO can design the programme and connect it to the revenue system, but the company's own people have to show up in it. If you want a second opinion on whether community fits your stage, a free 30-minute consultation is the quickest way to find out.
FAQ
Expect a year before the community runs without constant prompting, and longer before it shows clearly in revenue. Early signs come sooner: members answering each other, repeat attendance and customers mentioning the community in sales calls.
You need one named owner, though it can be a founder or an early team member for the first months. Hire a dedicated manager once there is a regular rhythm and more activity than one person can handle part time.
Open communities grow faster and help acquisition. Customer-only communities suit support, retention and sensitive topics. Many companies run an open space for the topic and a private one for customers.
Use the one your members already open every day. Forums keep answers searchable, chat tools are better for quick conversation and events build trust. Choose one home first and add others only when members ask.
Yes, but it will look like a customer circle, not a public forum: a quarterly call, a private group and an annual meet-up. With few customers, depth of relationship matters more than member count.