Latest / Community Marketing with Fexingo: Discord, Slack Groups, and Brand Communities / How 100 Community Members Generated 40 Percent of New Revenue
Transcript
- Lucas: There's a B2B SaaS company — I'm not naming it because the story is more useful than the brand — that generated 40 percent of its new revenue in 2025 from a community of just 100 people. Luna: Forty percent from a hundred people? That sounds almost too neat. What were they selling? Lucas: A project management tool aimed at mid-market creative teams. Price point was around $30 per user per month, typical annual contract value in the five figures. The community was invite-only, mostly power users and early customers who'd been around for a couple of years. Luna: So these were already engaged users. But 40 percent of new revenue — that's not just retention, that's acquisition. Lucas: Exactly. The community became a structured acquisition channel. They did three things that I think are replicable. First, they ran a private beta preview program. Before any public launch of a feature, they'd give the community early access and ask them to test it with their teams. Luna: And those teams became new accounts? Lucas: Often yes. A community member at a design agency would get early access to a new workflow feature, show it to their colleagues, and the agency would expand from five seats to twenty. The company tracked this with unique invite codes tied to each community member's account. Luna: That's smart because the attribution is clean. It's not a vague 'community drove awareness' metric. Lucas: Right. Second thing: they built a referral tier that actually paid out. Not the usual 'give your friend 20 percent off' — the community member got a 10 percent commission on the first year of any new account they referred. It was structured like an affiliate program but only open to the community. Luna: Ten percent of a five-figure ACV — that's real money. Did it change the dynamic in the community? Lucas: It did. Some members started treating referrals almost like a side hustle. The company had to put in a cap — one person referred 12 accounts in six months, which was about $15,000 in commissions. But the company was comfortable with that because the cost per acquisition was still half of what they paid for paid search. Luna: What was the third thing? Lucas: Community-generated content. They didn't run a formal case study program. Instead, they had a channel called 'wins' where members posted what they'd built or accomplished using the tool. The marketing team would ask permission to turn those posts into blog posts or social proof slides. Members loved the visibility. Luna: That's the kind of content that actually converts, because it's not scripted. A prospect reads 'another project manager like me solved this problem' and it carries more weight than any testimonial the company writes. Lucas: The numbers back that up. The company told me that leads sourced from the community — either through referral links or content attribution — had a 3.5 times higher conversion rate than outbound leads. And the sales cycle was about 60 percent shorter. Luna: Sixty percent shorter makes sense. The prospect already trusts the brand because they trust the community member who referred them. You're skipping the entire awareness and consideration phase. Lucas: Right. A typical outbound lead might take 90 days from first touch to close. A community-referred lead averaged 35 days. The trust was preloaded. Luna: So the community is basically a demand gen engine that pays for itself through reduced CAC. But I wonder — does this only work for a small, curated community? If they scaled to 1,000 members, would the referral program still feel organic? Lucas: That's the tension. The company deliberately kept the community at around 100 people. They had a waitlist. They wanted members who were already advocates, not just users looking for a discount. If you open it up too broadly, the sense of exclusivity erodes and the referral behavior might become transactional. Luna: Transactional in a bad way? Or just less authentic? Lucas: Both. If someone joins only because they heard they can make commission, they're not going to produce the kind of authentic content that drives trust. The company was very careful about who they let in. They'd look at product usage data, support ticket history, even social media presence. They wanted people who were already talking about the tool organically. Luna: So it's less about the size of the community and more about the selection criteria. A hundred people who are genuinely enthusiastic can outperform a thousand who are passive. Lucas: Exactly. And this ties back to something we've talked about before — communities as a quality filter, not a quantity play. The revenue numbers reflect that. Forty percent of new revenue from 0.1 percent of the total user base. Luna: I want to push on one thing though. If a community member is earning commissions, does that change how other members perceive their recommendations? Does it create skepticism? Lucas: The company worried about that too. So they required all referral posts to include a clear disclosure. The community channel had a pinned note: 'Members may earn commissions on referrals. Always do your own evaluation.' They also capped commissions at $2,000 per member per quarter to keep it from becoming the primary motivation. Luna: That seems reasonable. It's transparent, and the cap prevents anyone from gaming the system. But it also means the company is leaving some money on the table — if someone could refer 20 accounts, they're only paying for 10. Lucas: They decided that was worth it to preserve trust. And it worked — I didn't see any backlash in the community. In fact, some members said they appreciated that the program felt like a genuine thank-you rather than a sales incentive. Luna: So what's the takeaway for someone listening who wants to try this with their own community? Where do you start? Lucas: I'd say start with the content piece. It's the lowest friction and the least likely to feel transactional. Identify your most active community members and ask them if you can share their success stories. Most will say yes. Then track whether those stories generate inbound leads. Luna: And if you see a signal, then you can layer in a referral program. Lucas: Yes. And don't start with a commission. Start with simple incentives — a gift card, a free month of service, a branded hoodie. See if the behavior changes. Only move to cash if the volume justifies it. Luna: It's interesting — this episode is essentially about monetizing community trust without breaking it. That's a fine line. Lucas: It is. And the companies that do it well treat the community not as a channel to extract value from, but as a partnership. The revenue is a byproduct of genuine advocacy, not the goal itself. Luna: Speaking of value — we keep this show ad-free because we believe the conversations themselves should be the value. If these episodes have helped you think differently about your community, and you'd like to support that approach, we have a simple link: buy me a coffee dot com slash fexingo. No pressure, just an option. Lucas: Yeah, it's a small way to keep this independent and free of sponsor noise. Appreciate anyone who finds that useful. Luna: Alright, back to the numbers. Lucas, you mentioned the sales cycle was 60 percent shorter. Was the company able to quantify the actual dollar value of that acceleration? Lucas: They did. They calculated that shaving 55 days off the average sales cycle meant they could close deals faster and reduce the working capital tied up in sales operations. Rough estimate: about $200,000 in freed-up cash flow annually for a company of that size. Luna: That's not trivial. And it's a metric most community teams don't even think to measure. Lucas: Right. The standard community metrics are engagement, retention, NPS. But revenue attribution — especially acceleration — is still rare. This company built a simple model: they compared the close date of community-referred deals to the average close date of all other deals, and multiplied by the number of community-sourced opportunities per quarter. Luna: So any community team could do that. You just need CRM data and a referral source field. Lucas: Exactly. It's not complex analytics. It's discipline in tagging leads at the point of entry. Luna: One more question — did they ever have a situation where a community member referred a company that turned out to be a bad fit? High churn, lots of support tickets? Lucas: Yes, it happened a few times. The company had a policy that if a referred customer churned within six months, the commission was clawed back. That kept members honest. They didn't want to refer just anyone — they referred people they believed would actually benefit. Luna: That's a smart guardrail. It aligns incentives with quality, not just volume. Lucas: And it preserved the community's reputation. If a bad referral had been left unchecked, other members would have started questioning the program's integrity. Luna: So the whole system — the preview program, the referral tier, the content engine, the clawback — it's all designed to reinforce trust. That's the thread. Lucas: That's the thread. And I think that's the lesson for any brand thinking about turning their community into a revenue channel. If the design prioritizes trust over short-term revenue, the revenue will follow. If you optimize for revenue first, you'll break the trust and lose both. Luna: A hundred people, forty percent of new revenue. It's a reminder that the size of the community matters less than the depth of the relationship. Lucas: Absolutely. And maybe that's the question every community manager should ask themselves: if you could only keep a hundred members, which hundred would you choose?