Latest / Community Marketing with Fexingo: Discord, Slack Groups, and Brand Communities / How a Brand Community Beat Its Own Churn Problem
Transcript
- Lucas: So we talk a lot on this show about growing a community — bringing people in, getting them engaged, turning them into advocates. But what about the flip side? What do you do when members start drifting away? Luna: That's the churn problem. And it's one most communities avoid talking about until it's too late. Lucas: Exactly. And today I want to get into a tactic that I've seen work surprisingly well, and it's not what you'd expect. It's not a better email sequence, it's not a discount offer. It's using your most loyal members to personally reach out to the ones who are about to leave. Luna: Oh, like a save squad? I've heard of that in a customer success context. Lucas: Yeah, save squad is exactly the term. And I first saw this done really well at a B2B SaaS company — I'm not going to name them because the details are a little fuzzy, but the story is solid. They had about two thousand paying customers, and their churn was running at roughly 2.5 percent per month. That's not catastrophic, but it's the kind of number that keeps a CFO up at night. Luna: Two and a half percent monthly is like twenty-six percent annualized. That's brutal. Lucas: Right. And they'd tried the usual stuff — automated win-back emails, a pop-up modal when you hit the cancel button, even a retention discount. The discount worked a little, but it was expensive and it trained people to threaten to cancel to get a better price. Luna: Classic. So they needed something that didn't feel transactional. Lucas: Exactly. So they built a save squad. They recruited twelve of their most active, most enthusiastic customers — the ones who were in the community every day, answering questions, evangelizing the product. They asked them if they'd be willing to reach out to customers who had shown signs of disengagement and just... talk to them. No scripts, no sales pitch, just a conversation. Luna: And those twelve said yes? What did they get in return? Lucas: That's the interesting part. They got nothing material. No discounts, no swag, no recognition badges. They did it because they genuinely loved the product and hated seeing other users struggle and quit. A couple of them even said it felt like helping a friend stick with a hobby. Luna: That's incredibly generous. But how do you even identify who's at risk? You can't just look at who hasn't logged in for a week — that could be a vacation. Lucas: Right, they looked at a composite of signals. They built a simple score based on login frequency dropping off, fewer feature usage, less engagement in the community, and, importantly, whether the person had recently hit a support ticket that went unresolved or angry. That last one was a big predictor. If someone had a bad support experience, their churn risk spiked. Luna: So it's not just inactivity — it's frustration. Lucas: Exactly. Frustration is a much stronger signal than simple laziness. So they had a weekly list of maybe twenty or thirty at-risk customers, and they'd assign them to save squad members based on time zone and, loosely, industry. The squad member would send a short, personal message — usually through the community's direct message system or email — something like: 'I saw you've been using us a lot less lately. I'm a fan of the product and I'm curious — is there anything I can help with? What's been going on?' Luna: And people actually responded to that? I'd probably assume it was a bot. Lucas: That's the thing — it wasn't a bot, and it didn't read like one. The messages were filled with personal quirks, emojis, references to their own usage. And because the squad members were real users, they could talk about the product in a way no support rep could. They'd say things like, 'I know the reporting dashboard is a pain, but I found a workaround that works for me — let me show you.' That kind of peer to peer advice is gold. Luna: So it's almost like a mini onboarding session, but from a friend. Lucas: Yeah. And the results were pretty striking. After two months, they saw their monthly churn drop from 2.5 percent to about 2 percent. That's a 20 percent relative reduction in churn. And when they dug into the numbers, they found that customers who received a save squad message and actually replied were about forty percent less likely to cancel in the following month. Luna: Forty percent — that's huge. But I'm wondering, is this something that only works when you have a few hundred customers? Twelve volunteers can't reach out to thousands of at-risk accounts every week. Lucas: That's a fair point. This particular company had two thousand customers, so twelve volunteers could handle the twenty or thirty at-risk accounts each week. But what happens when you scale to twenty thousand? Then you need a hundred volunteers, and you run into issues of quality control and volunteer burnout. Luna: And not every community has a hundred superfans willing to do that. So is this a niche tactic? Lucas: I'd say it's a tactic that works best in the early to mid-stage of a company, when you have a tight-knit community and you can still pick out your most passionate members by name. But the underlying principle — that peer support beats corporate outreach — scales even if the specific save squad doesn't. Lucas: You can formalize it into a peer support network, you can build a 'customer circle' where at-risk users get matched with a more experienced user for a month. The spirit is the same: a human connection that says, 'We see you, and we want you to stick around.' Luna: And honestly, this whole conversation is a good example of why we do this show. We dig into real tactics that you can actually apply, not just theory. Lucas: Yeah, and if today was actually useful to you, the way these episodes stay ad-free is listener support. You can buy me a coffee dot com slash fexingo — it's a small gesture that keeps the lights on and keeps us going deep on these topics. Luna: And every coffee genuinely helps. Now, back to the save squad — I want to push back a little more on the scalability thing. Lucas: Go ahead. Luna: Even with a small community, how do you make sure the save squad members don't feel taken advantage of? They're doing free work for a company they pay to use. That could breed resentment. Lucas: That's a real risk. The company was careful to make it opt-in, and they emphasized that it was entirely voluntary and that they could quit anytime. They also set expectations that it was a low-time commitment — maybe an hour a week. But they didn't track it too closely, which I think helped. They didn't turn it into a formal program with KPIs for the volunteers. That would have made it feel like a job. Luna: So you're saying the magic is in keeping it casual and human. The moment you systematize it too much, you lose the authenticity. Lucas: Exactly. And there's another layer to this. The save squad members often learned so much from their conversations that they became even more loyal advocates. They saw the struggles other users faced, and they felt like they were part of the solution. A couple of them even started volunteering in the support forum. Luna: That's a virtuous cycle. It's almost like the community becomes a self-healing organism. Lucas: That's a nice way to put it. But it's not all rosy. There's a dark side to this tactic, and I want to be honest about it. If you're not careful, a save squad can turn into a clique. The same twelve people get all the attention, and they might start to see themselves as gatekeepers. Luna: Whoa, I hadn't thought of that. How do you avoid that? Lucas: The company rotated the list. They made sure the save squad wasn't the same group every month. They recruited new members periodically and let others step back. They also encouraged the squad to report back what they were hearing, which gave them a sense of purpose beyond just 'saving' someone. Luna: So it's not just about churn — it's also about community health. Lucas: Right. And the other risk is that this could feel like a guilt trip. If a customer is on the fence and then gets a personal message from a peer, they might feel pressured to stay, even if the product genuinely isn't a fit. That could create resentment that comes out later. Luna: So the save squad's message has to be genuinely supportive, not manipulative. Lucas: Which is why the company didn't give them a script. They gave them guardrails, like 'Don't offer discounts' and 'Don't badmouth competitors' — but otherwise, they trusted them to be human. And that trust paid off, because the conversations were naturally empathetic. Luna: So what would you say is the one concrete takeaway someone listening today could apply to their own community? Lucas: I'd say this: before you invest in another automated win-back campaign, look at your community and see if there are a handful of people who love your product enough to have a genuine conversation with a struggling user. If you can find even three people willing to do that, you're on your way. It's low-cost, high-trust, and it might just be the most effective retention tool you'll ever build. Luna: And it turns your most loyal customers into your best retention asset. I love that. Thanks, Lucas. Lucas: Thanks, Luna. And to everyone listening — if you try this, let us know how it goes. We're curious.