Community-Led Growth: When It Prints Money and When You're Just Burning It

Here's the uncomfortable truth about community-led growth: most companies are doing it because everyone else is, not because it makes money. The narrative sounds great—turn users into evangelists, watch them recruit other users, benefit from organic word-of-mouth that costs nothing. But Kyle Poyar, former Operating Partner at OpenView, cuts through the hype with a warning that should be tattooed on every CMO's vision board: "Folks shouldn't build community on the basis of what KPIs it's going to improve for you. You need to build a community with and for your users or your audience. And so if it's really explicitly about your own objectives, the kind of counterintuitive finding is that you're probably never actually going to meet your objectives because it needs to be actually community driven."

That paradox—build it for them, not you, or it won't work for you—is the central tension in community-led growth. Some companies crack the code and watch community become their most efficient acquisition channel. Others pour six figures into Slack channels and conferences that generate nothing but feel-good vibes. The difference comes down to understanding when community is a growth engine and when it's just expensive theater.

The product-led precondition nobody talks about

Community doesn't fix a mediocre product. It amplifies a great one. Poyar frames community as the natural evolution of product-led growth, not a replacement for it: "It's really like the story of PLG playing out to its natural conclusion. And community is not a new thing...if you build a community, you won't become a commodity. You'll constantly get those raving fans who give you the feedback to make your product better."

Mallory Contois, VP of Growth at Maven and former Head of Community at Mercury, saw this firsthand at Pinterest when she joined as one of the first 100 employees. The platform wasn't positioned as social media—it was a visual discovery engine built for the user, not for performance. "What I loved about Pinterest was that my own organic usage, even before I started working there...it felt so clearly like it was for me, not for everyone else," Contois says. That core positioning created genuine word-of-mouth because users weren't performing—they were solving a real problem. "My first time experiencing being on the receiving end of that, of seeing users talk about it that way and for us to grow that way...I credit so much of Pinterest growth to that."

The lesson: community amplifies signal. If your product is noise, community just makes it louder noise. Contois puts it bluntly: "That really genuine, like, oh my God, this thing has never existed before and now it's in my hands and I love it so much and I'm going to tell everybody I know about it...it's one of my favorite memories, just telling people that I worked at Pinterest. I almost didn't want to tell people sometimes because it was like I wasn't leaving that conversation for 30 minutes after."

Compare that to the typical SaaS playbook: build community as a lead-gen tactic, measure it by MQLs, kill it when the CAC doesn't pencil out in quarter two. That's not community-led growth. That's community-flavored marketing.

When community actually converts: the Clay billboard test

Bruno Estrella, Head of Growth Marketing at Clay, ran an experiment that clarifies when community crosses from brand exercise to revenue driver. Clay spent low hundreds of thousands on billboards in San Francisco—not a scattershot campaign, but strategically timed to Dreamforce when every go-to-market executive flies into the city. "We actually try to mitigate as much as possible...we remapped out all of the touch points that people that are coming to San Francisco would land. It's like SFO Airport, 101 as they take, as they leave, and then downtown San Francisco as they're walking around," Estrella explains.

The anxiety was real. "I'm spending a ton of money here. How do I actually prove your ROI?" Estrella admits. But the strategy worked because Clay wasn't just buying awareness—they were activating an existing community of users who were already talking about the product. The billboards gave those users something to photograph, share, and rally around. "A lot of cost, like people that have open opportunities reaching out, a lot of like high profile CEOs commenting about it because we were, we did a kind of like a creative way of to do this campaign."

The campaign worked because Clay already had product-market fit with GTM leaders and users who loved the tool enough to build workflows around it. The billboards didn't create community—they gave the community a reason to get louder. That's the difference between community-led growth and growth-theater-with-a-Slack-channel.

The Mercury doctrine: organic growth on almost no budget

Contois offers the counterpoint to big-budget community plays. At Mercury, she ran "the lowest budget team" with a singular focus: "How far can we get on almost no money? What can we do by showing up as human beings in this ecosystem who understand our users and understand what founders are going through and show up for them in a way that's actually useful, not like buying them drinks and like taking them to Knicks games."

This is where the philosophy splits. Estrella at Clay invested hundreds of thousands in a two-month billboard blitz. Contois at Mercury spent almost nothing and built community by showing up authentically in founder circles. Both worked—but for different reasons tied to their respective business models and customer profiles. Clay needed to break through the noise in a crowded data enrichment market and establish legitimacy with enterprise buyers. Mercury needed to build trust with early-stage founders who are allergic to corporate BS.

Contois is explicit about her thesis: "I don't philosophically buy into the more money you spend on events and things like that, the more people will talk about them. I just, I think that's just not true." She built Mercury's community through genuine presence, not budget: understanding what founders need, showing up where they already are, and solving problems without expecting immediate ROI.

The divergence here isn't about right or wrong. It's about diagnosing when community needs fuel (budget, events, activation) versus when it needs space (authenticity, trust, time). Enterprise buyers respond to signals of legitimacy—billboards, conferences, brand presence. Early-stage founders respond to humans who actually get their problems.

The metrics trap: what actually predicts revenue

Poyar lays out the metrics that matter when community works: "Your users go help recruit new users. They share your product with other people, bring folks in to hear about your brand and all the great things they can do with your product...they build templates, they share how they see value in their products...you're actually creating a lot of user-generated content that helps your product get found by folks outside of the community through SEO, through organic search."

Three metrics emerge as predictive: user-generated content volume (templates, setups, shared workflows), support deflection (users helping users instead of tickets to your team), and time-to-value acceleration (new users copying existing playbooks instead of starting from scratch). Poyar points to Airtable, Notion, and Webflow as canonical examples where community creates these flywheels: "If you have someone that you trust has a setup or has a kind of template or has a playbook that really motivates you, all of a sudden you've been able to copy that playbook as opposed to starting it all from scratch. So you get to value a lot faster."

But these metrics only materialize when the product invites customization, sharing, and showcasing. Notion users share their setups on Twitter because Notion makes beautiful, shareable workspaces. Clay users share enrichment workflows because the tool's flexibility creates infinite use cases worth teaching. The product architecture has to support community behavior, or community becomes a Slack channel where people ask the same questions on repeat.

Where community becomes a distraction (and an expensive one)

Not every business model supports community-led growth, and the failure mode is expensive. Thiago Goularte, Director of Monetization at Rappi Brazil, comes from the world of agencies, ad tech, and marketplaces—businesses where community matters less than transaction volume and operational efficiency. His career spans Whirlpool, ad agencies, and building a MarTech that measured creative performance algorithmically. Community never enters the equation because the business models don't reward it.

Goularte's experience building Livecom—an algorithm that measured ad creative performance back in 2013—illustrates a different growth motion entirely. "We started to scale the business very quickly because it was a novelty very strong in the market," he recalls. The growth came from solving a clear problem (performance measurement) for a defined buyer (agencies and advertisers) in a market with budget (corporate marketing). Community would have been a distraction. The sale was technical, the buyer was sophisticated, and the value was quantifiable ROI.

This is the blind spot in the community-led growth conversation: some products sell on ROI, compliance, integration depth, or enterprise features—and in those markets, community is often a mirage. CFOs don't join Slack channels. Procurement teams don't share templates on Twitter. If your ICP is a budget owner managing vendor consolidation, community-led growth is probably the wrong motion.

Even in product-led businesses, community can become a vanity project. Slack channels with thousands of members but zero activation. Discord servers that generate memes but not revenue. Conferences that feel great but produce no pipeline. Contois is clear about the temptation: you can't build community explicitly for your KPIs and expect it to work. But you also can't ignore KPIs entirely, or you're just running an expensive hobby.

The honest playbook: when to invest and when to walk away

So when does community-led growth actually make sense? The pattern across these five leaders suggests three preconditions:

First, your product must invite users to build, customize, or create. Notion, Airtable, Clay, Webflow—these tools let users make something they're proud of and want to share. If your product is a black box that just works, community has nothing to rally around. Poyar's framing is direct: users need to feel like "they had a hand in developing" the product, which makes them "go to bat for the products they love."

Second, your go-to-market motion must allow for bottom-up adoption. Community works when users discover, adopt, and expand without sales involvement. Estrella describes this as the foundation of Clay's growth: end users find the tool, build workflows, then bring it into their organizations. If your sales cycle requires an RFP, a procurement review, and a six-month pilot, community won't compress that timeline—traditional enterprise sales will.

Third, you need to invest in activation, not just congregation. The Mercury model (low budget, high authenticity) works when your community is small and engaged. The Clay model (high budget, strategic activation) works when you need to break through noise and reach a specific audience at a specific moment. What doesn't work is the middle ground: moderate spend on generic community tactics that lack both authenticity and activation strategy.

Contois offers a test for whether community is right for your business: "If it's really explicitly about your own objectives, the kind of counterintuitive finding is that you're probably never actually going to meet your objectives because it needs to be actually community driven." Translation: if you're building community to hit a lead target, you've already lost. If you're building community because your users are already gathering and you want to support them, you might be onto something.

The brutal reality is that most companies fall into the distraction camp. They see Notion's Twitter presence or Figma's conference energy and think "we need that" without asking whether their product, customer, or business model supports it. Community-led growth works spectacularly well for a narrow set of products—and it's an expensive distraction for everyone else. The smartest operators know which camp they're in and resist the FOMO accordingly.