Latest / Community Marketing with Fexingo: Discord, Slack Groups, and Brand Communities / How a SaaS Community Cut Churn by 30 Percent
Transcript
- Lucas: So there's a B2B SaaS company called TaskFlow — they make project management software for mid-sized teams. About a year ago, they had a churn problem. Twenty-eight percent of paying customers were leaving within the first six months. That's almost a third of their new business bleeding out before they even recouped the acquisition cost. Luna: Ouch. And I'm guessing they tried the usual stuff — better onboarding emails, a customer success team, maybe a discount for annual plans. Lucas: Exactly. They did all of that. Onboarding NPS went up, but churn barely budged. So the head of customer success decided to try something different. They already had a public Slack community for product announcements, but it was basically a broadcast channel — a couple hundred members, mostly lurkers, very little conversation. She asked the community team to turn it into a retention engine. Luna: She wanted to move from broadcasting to actually engaging people. So what were the specific changes? Lucas: Three big moves. First, they created a dedicated onboarding channel. Every new customer was invited to join that channel on day one, and they assigned a power user — not a support rep — as a mentor. The mentor would answer questions, share workflows, and just check in. No sales pitch, no product tour, just peer guidance. Luna: That's smart. It turns the community into a relationship seat rather than a complaint desk. Did they measure the impact on activation? Lucas: They did. Customers who joined the onboarding channel and posted at least twice in the first week had a 90 percent activation rate — meaning they completed the core 'create a project and invite a teammate' action. The control group, who didn't join Slack at all, had a 62 percent activation rate. That's a huge gap. Luna: And activation is a leading indicator for retention. If you get someone to that aha moment early, they're less likely to churn. Lucas: Right. But the onboarding channel was just step one. The second move was adding a channel called 'help wanted' — specifically for bug reports and feature requests. The community team promised to respond to every thread within four hours, even if the response was just 'we're looking into it.' That built trust. Luna: I can see that. Nothing kills a community faster than posting a legitimate issue and getting radio silence. Trust is the currency. Lucas: Exactly. And the third move was the most impactful: a monthly feature vote. They'd pick five features from the 'help wanted' channel, let the community upvote, and then publicly commit to building the winner within the next sprint. No fine print, no 'we'll consider it.' They built it and shipped it. Luna: So they gave power users a real seat at the roadmap table. That's a retention loop — the more you invest in the product through voting, the more you want to stay to see your ideas come to life. Lucas: That's exactly the dynamic. After six months, TaskFlow's six-month churn dropped from 28 percent to 19.6 percent — a 30 percent relative reduction. And the community grew from about 200 active members to over 800. Luna: An 800-person community for a B2B SaaS with maybe a few thousand customers — that's a pretty high engagement rate. But here's what I'm wondering: did they see any downside? Like, did vocal power users start demanding too much, pulling the roadmap in a niche direction? Lucas: Actually, that didn't happen because the feature vote was limited to five options, and they always included at least one 'quick win' that appealed to the broader user base. But the more interesting downside was something else entirely. Luna: I'm listening. Lucas: They found that customers who joined the community but never posted — lurkers — actually had higher churn than customers who never joined at all. By about 5 percentage points. It's counterintuitive. You'd think any community touch would help, but passive membership seemed to amplify dissatisfaction. Luna: Wow. So lurkers were seeing other users complain or request features that weren't built yet, and they internalised that as 'this product isn't good enough' instead of feeling part of the solution. Lucas: That's the theory. The community team actually started a small experiment where they'd DM lurkers two weeks after they joined, just asking 'how's it going?' and offering a one-on-one demo. That alone pulled their churn back down to the level of non-members. Luna: Proactive outreach to the silent majority. That's a great takeaway. So if I'm a community manager at a similar company, the lesson is: don't just open the doors — make sure every member has a reason to participate, even a small one. Lucas: Yeah, and build in mechanisms that give lurkers a low-friction way to engage. A simple thumbs-up reaction, a 'quick tip' thread, anything that breaks the ice. TaskFlow's experiment proved that a single personal message could make a difference. Luna: Before we get deeper into the lurking problem, I want to zoom out for a second. You know, this episode made me think about something. We talk a lot on this show about tactics — and I love that — but if these marketing conversations have sparked something you've actually used in your own community, whether it's an onboarding channel or a feature vote or a lurker outreach script, and you found it valuable, there's a way to support the work we do behind the scenes. This show is ad-free by design, and listener support is what keeps it that way. People can contribute at buy me a coffee dot com slash fexingo. It's a small gesture that adds up. Lucas: Totally. And no pressure — we're not going anywhere. But if the show has ever saved you from a community mistake or given you an idea that paid off, that's where you can make sure we keep doing deep dives like this one. Luna: Exactly. Alright, back to the data. So the churn reduction is impressive, but does it scale? TaskFlow is a B2B tool with a clear use case, and users are already in Slack because of work. What about a consumer brand that uses Discord for a gaming community? Lucas: Great question. The principles are the same, but the execution differs. Consumer communities usually have much larger member counts and lower average time invested per person. You can't assign a personal mentor to every new member. But you can still create structured channels, use bots for onboarding, and run feature polls. The scale just means you need more automation and community moderation. Luna: So the core idea — turning passive members into active contributors through low-friction prompts — applies across verticals. But the specific tactics need to match the platform and the audience. Lucas: Exactly. For TaskFlow, the Slack community worked because their customers are already in Slack. For a consumer brand, you'd probably overlay the community on top of a platform people already use, like Discord for gamers or a dedicated app for a fitness brand. The hardest part is the initial invite and the first interaction. Luna: Speaking of first interactions, TaskFlow also found that the timing of the community invite mattered. They used to send the invite after purchase confirmation, but they moved it to the moment a user completed their first project. That one change increased invite acceptance by 40 percent. Lucas: Right, because at that point the user has already experienced value. They have context. A cold invite before they've even logged in is just noise. So there's a real lesson here about mapping community touchpoints to the customer journey. Luna: And the last number I want to highlight: TaskFlow's customer lifetime value for community-active users was 2.3 times higher than for non-community users. That's not just churn — it's expansion revenue too, because active members upgraded to higher tiers more often. Lucas: That's the hidden multiplier. Community doesn't just reduce churn, it increases willingness to pay. When you feel like you're co-creating the product, you're more likely to buy the premium version. TaskFlow's community members were also the top source of referrals. Luna: So the ROI on community goes way beyond retention. But I'd argue you need to nail retention first, because a leaking bucket is hard to fill. TaskFlow proved that a focused, intentional community strategy can patch that leak. Lucas: Absolutely. And they did it without a huge budget — just a Slack workspace, two community managers, and a commitment to respond within four hours. That's the encouraging part. You don't need a custom platform. You just need a strategy that treats the community as a core retention lever, not an afterthought. Luna: One question that lingers for me: what happened to the lurkers after the proactive DM experiment? Did they become active members, or did they just stay passive but feel more valued? Lucas: Great question. About 30 percent of the DMs converted into a reply, and of those, about half went on to post in a public channel within the next month. So the DM didn't magically turn everyone into a power user, but it did lower the barrier. The real win was the churn reduction — those lurkers stopped leaving at a higher rate. Luna: So the metric that matters most isn't post count. It's retention. That's a reframe a lot of community teams need to hear. Lucas: One hundred percent. And it's a good note to end on. If you're building a community, think about what behavior correlates with staying longer, not just posting more.