Latest / Community Marketing with Fexingo: Discord, Slack Groups, and Brand Communities / Why Discord Servers Beat Email Lists for Community
Transcript
- Lucas: So there's this number that's been sticking with me all week. A friend of mine runs community at a mid-size SaaS company, about forty thousand members in their Discord server, and they just compared that to their email list of a hundred and twenty thousand. The Discord server drives three times the weekly active engagement per member than the email list does. Luna: Three times? That's a big gap. But I guess it makes sense — email is push, Discord is pull. People have to actually show up. Lucas: Exactly. And it's not just about open rates. They measured something they call 'meaningful actions' — posting a message, reacting, helping another member, clicking a product link. Per active member, the Discord server produced three times as many of those actions per week as the email list produced per subscriber. And the email list had three times the raw number of people. Luna: So the raw volume is similar, but the density of engagement is way higher on Discord. That's the real story. Lucas: Right. And it changes how you think about community. For years, the playbook was 'build your list, email it weekly, hope for a two percent click-through.' But a Discord server is a different animal — it's a persistent space where your most engaged users are hanging out all day. The question is whether that depth of engagement actually moves the business metrics. Luna: And does it? What did they see in terms of retention or revenue? Lucas: They tracked a cohort of customers who joined the Discord server within their first week of signing up, versus those who didn't. The Discord joiners had a thirty-day retention rate that was twenty-two percentage points higher. And their net revenue retention after six months was about fifteen percent better. Now, correlation isn't causation, but they controlled for signup source and plan size, and the effect held. Luna: Twenty-two percentage points on retention is huge. That's not a rounding error. So what's actually driving that? Is it the support they get from other members, or the feeling of being part of something? Lucas: I think it's both, but the support angle is underrated. In their server, there's a dedicated help channel where power users answer questions faster than their support team does. The median first response time in the Discord help channel is under four minutes. Their email support ticket median is around six hours. So if you're stuck at nine p.m., you post in Discord and you get an answer before you finish your coffee. Luna: That's the kind of thing that makes someone stick around. But managing a forty-thousand-member server has to be a full-time job — or three. Lucas: It is. They have two full-time community managers and a rotating crew of about twenty volunteer moderators. The volunteers get a free premium plan and a private mod lounge. That's it. And honestly, that's the part that surprises me about the economics — the cost of running that server is way lower than the cost of scaling email marketing automation, at least in terms of human attention. Luna: But email is cheap to send. Discord requires a constant human presence. That's a different kind of cost — it's not linear, it's a step function. You need a critical mass of mods to keep it from turning into a swamp. Lucas: Yeah, and that's why a lot of brands are scared of it. They see the moderation horror stories — the toxic servers, the ones that become echo chambers. But the flip side is that a well-moderated server can be one of the most trusted spaces on the internet. And that trust transfers to the brand. Luna: Speaking of trust, I've noticed that a lot of the community members in these servers are more likely to defend the brand in public. It's like they have a stake in it. Lucas: That's a real phenomenon. My friend shared a case where a member posted a complaint about a bug in the product, and within an hour, two other members had replied with workarounds, and a third had tagged the product manager. The original poster ended up thanking the community and saying they were more impressed by the response than if they'd just gotten a support ticket. That's the kind of organic advocacy you can't buy with email. Luna: So the community becomes a self-sustaining support layer. But not every brand should jump into Discord. When is it the wrong tool? Lucas: Good question. If your audience is primarily over forty-five and not technically inclined, a Discord server might be a ghost town. Also, if your product is low-engagement by nature — say, a utility like a bill-pay app — people aren't going to hang out in a server about it. The sweet spot seems to be products that people use daily or weekly and where they have questions, tips, or a sense of identity. Luna: And the size of the community matters too. A server with two hundred members can feel dead, but a server with two thousand feels alive. There's a threshold. Lucas: Right. My friend's server crossed that threshold around five hundred active weekly members. Below that, you have to work hard to seed conversations. Above it, the community starts generating its own energy. And they actually used a structured onboarding program to get people there — they had a week one challenge that got new members to introduce themselves and ask one question. That's a detail I love. Luna: That sounds like something we covered in an earlier episode, actually. But it's a good reminder that the mechanics matter, not just the platform. Lucas: You know, we talk a lot about the mechanics of community building on this show, and I love that we can do it without a sponsor breathing down our necks. We don't run ads on any of the Fexingo shows, and that's a choice we make deliberately. If you want to support that choice, the link is buy me a coffee dot com slash fexingo. Luna: Yeah, it's a small way to keep the podcast ad-free and keep these conversations independent. And we appreciate it — it's not a big ask, but it does matter. Lucas: Anyway, back to the numbers. The other thing that surprised me was how the Discord server affected their product development. They have a dedicated feedback channel where members upvote feature requests, and the community managers compile a weekly digest for the product team. In the last quarter, they shipped four features that originated directly from community suggestions. Luna: That's a direct line from community to roadmap. And it makes members feel like they're part of something bigger than just a product. Lucas: Exactly. And that's the thing — email lists are a broadcast medium. You send a message, and you hope people read it. A Discord server is a two-way street. You get real-time feedback, you see the pain points, you watch the conversations unfold. For a product-led company, that's gold. Luna: But there's a risk of over-reliance on Discord. If the platform changes its policies or the audience migrates elsewhere, you're stuck. Did they have a plan for that? Lucas: They did, actually. They use Discord as the primary community hub, but they cross-post key announcements to a mailing list and they have a read-only forum on their website. So they're not putting all their eggs in one basket. But the real conversations happen in the server, and they're okay with that because that's where the energy is. Luna: So the email list becomes more of a backup, a way to reach the less engaged people who might not check Discord. That's a smart split. Lucas: And it's actually a lesson in prioritization. Instead of trying to force everyone into one channel, you're meeting people where they are. The hardcore fans get the real-time community, the casual users get the occasional email. And the community managers are trained to gently nudge email subscribers toward the server without being pushy about it. Luna: I like that. What about the metrics they use to track success? Is it just active users, or are they looking at something deeper? Lucas: They track a few things. Weekly active members, of course, but also 'helpful reactions' — things like a message marked as a solution or a 'thanks' emoji. They also track the ratio of questions asked to questions answered within a few hours. And they look at the retention cohorts I mentioned. The key is that they're not just counting messages; they're measuring whether the community is actually helping people get value from the product. Luna: That's the difference between a vanity metric and a real one. It's easy to celebrate a hundred thousand members, but if they're all lurking and not getting value, what's the point? Lucas: Exactly. And that's why I think the 'community as a retention lever' story is so compelling. It's not about the number of members; it's about the depth of the relationships and the speed of the support. My friend's data shows that a member who's active in the Discord server is worth, on average, about two and a half times more in annual revenue than a member who only gets emails. Luna: Two and a half times. That's the kind of number that would make any CFO pay attention. Lucas: Yeah, and I think that's the real takeaway. We've been talking about community as a 'nice to have' for years, but the data is increasingly showing that it's a business driver. The challenge is that it requires a different kind of investment — not just a budget line item, but a cultural commitment to listening and engaging. Luna: So what would you say to a marketing manager who's thinking about starting a Discord server but is worried about the time and moderation? What's the first step? Lucas: Start small and be honest about the commitment. Don't launch a server and then walk away. Set a clear purpose — is it for support, for product feedback, for community building? Recruit a few trusted power users as early mods. And set expectations with your team that this is a long game. The ROI doesn't come in a month; it comes in a quarter or two. But as my friend's case shows, when it works, it works in ways that email never could. Luna: That's a solid blueprint. And a good note to end on — community isn't a side project anymore, it's a strategy. Lucas: Couldn't agree more. And next time we'll dig into how to measure the ROI of community even when the numbers aren't as clean. Until then, keep building.