Community-led growth: when it works, the operating model and the metrics

Community-led growth is a go-to-market model in which users who help each other become the reason new users arrive, activate and stay. The company hosts the space and seeds the first conversations, then members answer questions and vouch for the product. dbt Labs built a 100,000-member community that Community Inc. reported generates 80% of its inbound leads. This guide covers when it works, a 90-day plan and the metrics to report.

What is community-led growth?

Community-led growth is a go-to-market model in which users who help each other become the reason new users arrive, activate and stay. The company hosts the space and seeds the first conversations. Members then do much of the work: answering questions, sharing working patterns and vouching for the product in public.

Three figures show what the model can do and how thinly it is often staffed. dbt Labs built a 100,000 member-strong community, and Community Inc. reported that the community generates 80% of its inbound leads. Census grew the Operational Analytics Club to more than 7,500 data practitioners in just two years. Yet in CMX's 2025 survey, 17% of respondents said they don't have anyone working full time on community.

How it differs from product-led growth

In product-led growth, the product carries acquisition and onboarding. In community-led growth, peers carry part of that load. dbt Labs runs both: over 30,000 companies use dbt, with 3,800 paying customers, so under 13% of users pay. In our reading, the community is what keeps that large free base moving toward paid.

Stage	What members do	Example from the sources	What to track (our reading)
Arrive	Bring peers in	The dbt community doubled in size every year it has existed	New members per month and where they heard of you
Activate	Answer first questions	dbt's founders spent early time answering their questions in Slack	Time from join to first reply received
Stay	Keep showing up	Census tracks the 28-day rolling average of active members	Active members as a share of total, by cohort

A community is not an audience

Both examples are communities of practice, built around the job rather than the vendor. Census chose not to assign any specific revenue targets to the community. We think that restraint is part of why members trust the space enough to bring colleagues.

The measurement still has to reach the business. CMX found that teams with CRM-integrated community data are over twice as likely to rate their impact as 'extremely successful'. CRM stands for customer relationship management.

A step for this week: add one field to your CRM recording whether a contact is a community member. Then compare their activation and retention with non-members over the next quarter. That comparison tells you whether your community is doing the arrive, activate and stay work, or only collecting members.

When a community drives growth and when it is a cost center

Community spending has a long history of landing in the wrong column. CMX, a community professionals' organization, puts it plainly: community was historically seen as a cost center. Whether yours turns into a growth channel depends on two conditions you can check before you hire anyone or open a Slack workspace.

Condition one: members answer each other

In a support community, CMX says, members answer questions and solve problems for each other to cut support costs. When only staff answer, you have a support desk with extra steps. CMX lists the number or percentage of answered questions as a common metric, and we would split it by who answered.

Here is a worked example, not a benchmark. Of 100 questions posted in a month, members answered 50 without staff help, so your peer answer rate is 50%. We read a rising peer share as the signal that matters. A flat one means the founders are still doing the work.

Webflow tracked something close to this. Matthew Munger, its community lead, decided responsiveness was key for him to track so that questions got addressed quickly.

Condition two: the product has a craft

People keep talking when there is a skill to get better at. In March 2018, dbt's Slack was 350 members strong. In it, people with roles like data analyst, data engineer, and data scientist all sit around the same table, and discussion ran from performance tuning on Redshift to style guides for SQL. None of that is a product question. It is people trading how they do their jobs.

A craft also creates a path for members to grow. Munger was a freelance web developer who joined the Webflow community to learn from and help others. The company then offered him a role as a community moderator, then a quality analyst, and later he became a senior product expert.

The ten-minute checklist

Answer yes or no to each. Use your own data where you have it.

1. Do users already ask each other for help somewhere: a forum, a subreddit, a GitHub issue thread?
2. In the last month, did a non-employee answer at least one question before your team did?
3. Is there a skill around your product that people put on a resume or a job post?
4. Do users share artifacts with each other: templates, code, style guides, configs?
5. Could you name three users who would explain your product to a stranger without being asked?
6. Will someone on the team own a weekly count of answered questions and who answered them?

In our reading, four or more yeses justify a one-quarter test. With fewer, treat community as a support cost and budget for it that way. Spend the growth quarter on a growth loop you can measure.

Pick one business goal with the SPACES model

Once you know a community can pay its way, the next decision is what it is for. CMX's SPACES model gives six answers: Support, Product, Acquisition, Content, Engagement and Success. Each one points members at a different behavior and a different number.

In CMX's 2025 Community Industry Report summary, the most common top objectives were support at 24%, success at 22% and acquisition at 20%. The same summary found that only 24% of respondents could confidently quantify their community's value. In our reading, that gap comes from teams spreading effort across too many goals to measure any one of them well.

Goal	What members do	Metric it moves	Fit for one community lead (our reading)
Support	Peer answers, covered above	Case deflection, reduced support calls	Good if support tickets are a real cost
Product	Share ideas and feedback that shape the product	Product ideas, feature adoption	Good if a product manager will act on the input
Acquisition	Act as ambassadors and advocates	New customers, new member signups	Good when a sales or marketing owner tracks sourced leads
Content	Create content that makes up the product or other assets	New user-generated content	Weak unless the product already runs on contributions
Engagement	Gather around a shared interest tied to the brand	Active engagement, conversation engagement	Weak as a primary goal: activity is hard to tie to revenue
Success	Share best practices and help each other adopt the product	Customer retention, Net Promoter Score (NPS)	Good once you have paying customers to retain

The member behaviors and metrics come from CMX's model page. The fit column is ours.

Pick and commit

CMX's own advice is to limit scope: "One or two is more than enough to start." Its suggested routine is to choose one or two pillars, pick one metric for each, track it consistently and send stakeholders a monthly update.

Our rule is a little tighter. Choose one primary goal and at most one secondary goal. The primary goal gets most of the lead's week and the headline number in the monthly update. The secondary goal gets one metric and no dedicated programs.

Here is a one-line template to put at the top of your community plan:

• Out of scope this quarter: Content, Engagement, Acquisition, Support.

Writing the out-of-scope line matters as much as the goals. It tells the team which requests the community lead can turn down.

How dbt, Figma and Notion built their communities

Each ends with the one mechanism we think a startup can copy this quarter.

dbt: grow the Slack, then add structure to it

The earlier sections covered how dbt's Slack started small, with the founders answering questions. By mid-2020, dbt Labs reported more than 2,100 companies actively using dbt. Its Slack group had tripled in a year, from roughly 2,000 to roughly 6,000 members.

Growth then forced structure. The team built an onboarding flow that forces participants to accept the community guidelines prior to joining. It also trained over 200 people through dbt Learn and recorded over 30 community contributions to its documentation. It then said it planned to moderate the growth of the dbt Slack group.

Mechanism to copy: a gated onboarding step and a training path that turn new members into people who answer questions.

Figma: make the product file the thing people share

It was described as a space to publish Figma files for anyone to inspect, reuse, and remix. Before that, thousands of creators signed up for the beta.

Mechanism to copy: the shared asset is a working product file, so every reuse starts inside the product. See growth loops explained.

Notion: ambassadors, capped and selected

Notion's community feeds a B2C2B (business-to-consumer-to-business) go-to-market, and more than 80% of its users are outside the US. Its ambassador program started back in 2019 with just 20 people, chosen after the team got 400 applications. It later capped new ambassadors to 20 per month and kept a deliberately long application form.

Mechanism to copy: a small, selective cohort that grows at a rate the team can onboard properly.

This week, pick the one row that matches your SPACES goal and write the single rule you will enforce: a joining step, a publishable asset, or an intake cap.

Should your community live on Slack, Discord or a forum?

The platform decides who can find your community's answers, who keeps them and how many hours a week you spend moderating. The table below is our reading of the trade-offs, not a ranking. Each option suits a different audience.

Option	Searchability (our reading)	Who holds the content (our reading)	Moderation load (our reading)	Fit for practitioners (our reading)	Fit for consumers (our reading)
Slack	Search works inside the workspace, but answers stay out of public search	The platform hosts it, and you run the workspace	High: live chat needs daily coverage	Strong where members already work in Slack	Weak: most consumers do not keep Slack open
Discord	Search works inside the server, but answers stay out of public search	The platform hosts it, and you run the server	High: real-time channels and voice need moderators	Mixed: depends on the audience's habits	Strong where the audience already uses Discord
Forum you host	Threads can be found through public search	You host it and control the archive	Lower per post, slower pace	Good for long technical answers	Good for how-to questions
Forums run by users	Varies by host	The community organizers	None for you	Depends on the organizer	Good for broad user bases

What companies did

Census built its practitioner community on Slack. Its team described the early manual work as including setting up Slack as their community gathering place. By the time of that account, the club had roughly 2,000 members in Slack, where the OA Club’s innermost circle is hosted. Census handled part of the moderation load by having its Data Champions assist in moderating channels.

dbt also started on Slack. When dbt turned two in March 2018, its Slack community was 350 members strong, with analysts, engineers and scientists in the same channels.

Notion took a different route for its broad user base. It points users to community forums that are not hosted, sponsored, or moderated by Notion. Its ambassador and champion programs still get a private Slack group.

A check to run this week

Chat platforms have a known leak. Census noted that a new member often joins to ask a specific question, then disappear once they’ve received an answer. Its team tracked a 28-day rolling average of active members and total membership.

Run the same check yourself. In this example, not a benchmark, a workspace with 1000 members and 100 active in the last 28 days has 10% of members active. If your members keep returning to the same questions and that share stays low, we think the community needs a searchable archive more than a busier chat. Measure it against your retention by cohort.

The 90-day plan for a startup with one community lead

In that report, 17% of respondents had no one working full time on community. So the plan is built for one person who shares the work with a founder and the first members.

Days 1 to 30: hand-recruit and answer everything

The community lead and a founder invite the first 50 practitioners by name, from customer calls, support tickets and signup lists. Every question gets an answer within one business day, from the lead or a founder.

Track response time from day one. Webflow's Matthew Munger decided responsiveness was key to track.

Days 31 to 60: weekly rituals and first member experts

The lead runs two fixed weekly rituals, for example a Monday question thread and a Thursday office hour. The goal of this phase is to find members who answer other members.

Webflow's path is the model. Munger joined as a member, and the company offered him a role as a community moderator, then a quality analyst. Your version is smaller: give your most helpful members a title, early product access and moderation rights.

Worked example, not a benchmark: if 10 of your first 50 members answer another member's question this month, that is a 20% contributor share. Pick a target before the phase starts.

Days 61 to 90: connect community data to signups and revenue

The lead and whoever owns your customer relationship management (CRM) system match community members to accounts, then compare signups, activation and revenue for members against non-members by cohort. CMX found teams with CRM-integrated community data were over twice as likely to rate their impact as extremely successful. That is a correlation, and we read it as a reason to do this step early.

AI tools can absorb some of the load: 81% of respondents already used them, mostly for content creation, reporting and moderation.

Phase	Who does the work	What it produces	How to know it worked (our reading)
Days 1 to 30	Community lead, founder	50 hand-picked members, a response-time log	Every question answered within one business day
Days 31 to 60	Community lead, first member experts	Two weekly rituals, named moderators	Members answer questions before staff do
Days 61 to 90	Community lead, CRM owner	Member-tagged accounts, a cohort comparison	You can show signups and revenue from members

Log each ritual and outreach idea in the growth experiment backlog template so the next quarter starts from evidence.

Community metrics a founder can defend

Proving value is where most community programs stall. In the 2025 report, CMX found that proving ROI "remained one of the top frustrations," and only 24% of respondents said they could confidently quantify their community's value. The fix is a short metric set in three tiers, reported the same way every month.

Tier	Metric	How to measure it	What it tells a finance lead (our reading)
Engagement	Weekly active members	Members who posted, replied or reacted in the last 7 days	The space is alive, not just large
Engagement	Share of questions answered by members	Questions with a non-staff reply, divided by all questions	Support load is shifting to members
Contribution	Member-created answers, templates, events	Count per month, tagged by author	Members are producing assets you would otherwise pay for
Business	Community-influenced signups	Signups whose email matched a community member before signup, plus signup survey answers	Community is feeding the funnel

Census ran its program with this tiered view in mind. It also tracked business results, such as contribution to open pipeline, deals won, and faster time to close. Census also chose not to assign any specific revenue targets to the community. We read that as a useful split: measure business impact, but do not hand the community lead a quota. Asana and Common Room presented the same idea as a data-driven approach to measuring and communicating the impact of community.

A worked ROI example

These are round example inputs, not benchmarks.

• A community has 1,000 members, and 100 are active weekly, so weekly active members are 10% of the total.
• Members ask 50 questions a week, and members answer 20 of them, so the member answer share is 40%.
• The community produces 90 influenced signups a month. Of those, 10 become paid, a 11.1% free-to-paid rate for that cohort.
• Program spend on tools and events is 1,000 a month. Spread across 10 paid customers, that is 100 to acquire each one.
• Each customer brings 50 a month in gross margin, so a 100 acquisition cost pays back in 2 months.

This example counts program spend only. Add the community lead's salary to the cost line before you show it to anyone. Then compare the payback period with your paid channels. Plug your own inputs into the growth model template, and track influenced signups by cohort so you can check whether they hold up on retention.

Why community-led growth fails

In our reading, most community programs that stall fail in one of five ways. In our reading, each one shows up in the data weeks before anyone admits it, so the work is spotting the signal early and acting on it.

Failure mode	Early warning sign (our reading)	Fix (our reading)
No full-time owner	Replies to members slow down when the part-time owner has a launch or a quarter-end	Name one owner with a written weekly time block, and pick one goal they report on
Budget cut before value shows	Leadership asks what community does and nobody has a number ready	Agree on one leading metric and one business metric before the first spend
Vanity member counts	The headline number rises while posts per week stay flat	Report active members and answered questions, not total sign-ups
Staff-only posting	Employees write most threads and most replies	Recruit a few members to host recurring threads and answer first
Decentralized drift	Member-run spaces grow, but product feedback stops reaching the team	Give leaders early access in exchange for a feedback channel

Ownership and budget

In our reading, the owner problem is getting harder to staff from inside. In the 2025 CMX survey, another 15% identified as consultants or freelancers. An outside contractor can run events, but we think the goal and the metric should sit with someone on staff.

Budgets move fast and often out of sight. The same report found that only 26% of respondents saw budget increases this year, while 18% faced cuts, and a full quarter said they didn’t know how their budget changed. If you do not know your budget, you cannot defend it. Ask finance for the line item this week.

Member counts and staff-only spaces

Here is an example, not a benchmark. If 50 of 1,000 members posted last month, the active share is 5%. That 5% is the number to grow. The 1,000 mostly tells you how good your sign-up form is.

The staff-only space is the same problem seen from the other side. Count the last 20 threads. If staff started 10 of them, half your community is your own team.

The control tradeoff of a decentralized model

Notion shows what you give up when members own the spaces. At Notion, two ambassadors run the 300k+ member /r/notion subreddit, and one team member put the stance plainly: "We don't direct them because that's not the point of the community."

That buys reach and gives up message control. In our reading, Notion's counterweight is access: Ambassadors are given early access to new features, which keeps a feedback line open to the team. If you go decentralized, set that exchange up first, then let go of the rest. To check whether members stick around, read your cohort retention curves.

What this page does not cover

This page does not compare or recommend community platforms, tools or agencies, and it does not cover hiring or paying a community lead. The worked numbers are examples, not benchmarks, and nothing here is financial or legal advice.

Related on Race to Scale: Reddit Marketing Strategy for Startups: What Gets Removed, What Gets Upvoted and How to Measure It; Referral program examples that worked, and the mechanics behind them; Waitlist launch strategy: how the referral queue and the gated waitlist work, what converts, and when a waitlist backf.