Latest / Community Marketing with Fexingo: Discord, Slack Groups, and Brand Communities / How a 400-Person Discord Replaced a Full CRM Team
Transcript
- Lucas: So there's a B2B SaaS company — I'm not going to name them because they're still private and they haven't gone public with this yet — but they made a decision about two years ago that sounds kind of crazy if you work in traditional marketing. Luna: I'm already curious. What'd they do? Lucas: They fired their entire CRM and email marketing team. Not laid off, not restructured — they replaced the whole function with a Discord server. A 400-person Discord server. Luna: Wait, how does that even work? CRM is like the backbone of B2B sales. You're telling me a chat app replaced that? Lucas: That's what I thought when I first heard about it. And if these conversations have sparked something you've actually used in your own work, listener support is what keeps this show ad-free and independent. You can find us at buy me a coffee dot com slash fexingo. But yeah, let me walk through how they pulled it off. Luna: Yeah, let's dig in. I need to hear the numbers. Lucas: So the company is a B2B analytics platform — think something like Mixpanel or Amplitude, but more niche. They had about 2,000 customers, mostly mid-market. And their CRM team was four people: two email marketers, one CRM manager, and one sales ops person. Total cost including software was about $350,000 a year. Luna: And they just... stopped? No more emails? Lucas: No, they still send emails. But the community generates and manages them. Here's the key structure: they set up a Discord server with a few core channels. An announcements channel that works like a broadcast list — every product update, every webinar, every case study goes there. Then they have an onboarding channel where new members get a welcome DM with a link to the server rules and a short survey. Luna: So that welcome DM is basically a drip campaign. What's the open rate like? Lucas: They tracked it — 92 percent of new members read the welcome message within 24 hours. Compare that to a typical email onboarding sequence, which might get 40 to 50 percent open rates after the first email. The difference is that on Discord, the message pops up as a notification if the user has the app on their phone. It's immediate. Luna: Okay, that's clever. But what about segmentation? CRM teams spend all their time tagging users by industry, by product usage, by lifecycle stage. How does a chat room do that? Lucas: They use Discord roles. When someone joins, they pick their role from a list: product manager, data analyst, engineer, executive. Then they pick their industry. Once they have those roles, the server automatically gives them access to private channels for their role and industry. So a product manager in fintech sees completely different content than an engineer in healthcare. Luna: So the roles are acting like CRM segments. And the content in those channels is like the email copy. But who writes it? Before they had professional marketers. Lucas: The community managers write some, but a lot of it is user-generated. When a customer posts a question in a channel, other customers answer it. The company then takes the best answers and pins them or makes a post in announcements. They told me that about 60 percent of their knowledge base content now comes from community threads. The community managers just clean it up. Luna: That's smart, but I'm wondering about support. One of the biggest functions CRM teams handle is customer support routing. How does Discord replace a ticketing system? Lucas: They use threads. If someone has a problem, they post in a support channel, and the thread is created. The community managers monitor the threads, but often power users answer before the team even sees it. They told me their average first-response time went from four hours with email to about 12 minutes on Discord. And their CSAT scores actually went up. Luna: That's impressive. But I have to push back on something — this sounds great for a community of 400. But what about when you have 4,000 customers? Or 40,000? Does this scale? Lucas: That's the question I asked them. And their answer was honest: they think it could scale to maybe 2,000 to 3,000 active members before the signal to noise ratio gets too bad. But they also said that for their business, 400 active members covers about 80 percent of their revenue. The whales are in the server. The rest of their customers get a lightweight email newsletter once a month, but the real marketing and support happens in Discord. Luna: So it's not a total replacement for every customer — it's a replacement for the high-value segment. That makes more sense. Lucas: Exactly. And the CFO was convinced by one metric: customer lifetime value. Members who joined the Discord had a 40 percent higher retention rate and a 25 percent higher expansion revenue compared to non-members. When you do the math, the $350,000 they saved in team costs plus the revenue lift, it was a no-brainer. Luna: Let's talk about what they lost. What did they give up by not having a dedicated CRM team? Lucas: A few things. One, they lost the ability to do sophisticated A/B testing on emails. Their email now is basically one version sent to everyone, because the community managers don't have time to run multivariate tests. Two, they lost the ability to do triggered emails based on product behavior — like if a user hasn't logged in for 14 days, send a re-engagement email. On Discord, they can see activity, but they don't have automatic triggers. Luna: So they traded personalization for immediacy and user-generated content. For a certain kind of company, that trade might be worth it. Lucas: I think it works best when your product is complex enough that users need to talk to each other. If you're selling something simple, like a project management tool that's easy to use, a community might not add that much value. But if your product has a learning curve, or if there are multiple ways to use it, then the community becomes a distribution channel for expertise. Luna: What about the community managers? They're now doing the work of a four-person team. How many people run this Discord? Lucas: Two community managers. One full-time, one part-time. And they're not marketers — one used to be a customer support rep, the other was a product manager. They know the product inside out. The company says the key is hiring people who genuinely enjoy talking to customers, not people who are experts in email automation. Luna: That's a different skill set. So the hiring bar shifts from technical marketing skills to communication and empathy. Lucas: Completely. And the company also spends about $500 a month on Discord bots for automation — things like auto-assigning roles, scheduling announcements, and tracking engagement. So the tech stack is much cheaper than a CRM plus email platform, which was costing them about $2,000 a month. Luna: Let's talk about the actual results. You mentioned retention and expansion. What about acquisition? Did they see any impact on new customer acquisition? Lucas: Indirectly, yes. The public channels on their server are visible even to people who haven't bought yet. So prospects can lurk and see how helpful the community is. They said about 15 percent of new deals in the last quarter mentioned the community as a factor in their decision to buy. That's basically a free sales demo running 24/7. Luna: So it's also a lead generation engine. That's a pretty powerful stack for $500 a month and two salaries. Lucas: Right. The total cost is probably around $150,000 a year for the two community managers plus the bot subscriptions. Compare that to $350,000 for the CRM team. They saved $200,000 a year and got better results on the metrics that matter. Luna: I want to play devil's advocate for a second. One risk I see is that if the community goes quiet, you have no marketing. With email, you can always send a blast. But if people stop checking Discord, your entire funnel dries up. Lucas: That's a real risk. And they've had moments where engagement dipped. But they have a few tactics to keep it active. One, they run weekly 'ask me anything' sessions with the product team. Two, they have a 'community spotlight' where they feature a customer's use case every week. Three, they encourage off-topic channels — pets, hobbies, whatever — so the server feels like a community, not just a support forum. Luna: So they're actively managing the culture. That's not something you can automate. Lucas: Exactly. And that's the fundamental shift. A CRM team runs campaigns. A community team runs conversations. The output of a campaign is an email send. The output of a conversation is trust. And trust drives retention more than any email ever could. Luna: I think the most interesting takeaway here is that this model doesn't require a big budget or a huge team. It's accessible to almost any B2B company with a passionate user base. Lucas: Right. You don't need to be a unicorn startup. This company had about 2,000 customers and maybe 10 million in ARR. They just had the guts to try something different. And it worked. Luna: So if someone listening wants to try this, what's the first step? What should they do tomorrow? Lucas: Start with a small server. Invite your top 50 customers manually. Don't announce it broadly. See if they engage. If they do, open it up to the next tier. And don't kill your email yet — run it in parallel for three months. Measure engagement, retention, and revenue. Then decide. Luna: That's the kind of measured approach I like. Not just 'burn the CRM down' but test and learn. Lucas: Exactly. And if it works, you might end up like this company — with a marketing machine that costs less, runs itself, and actually builds relationships instead of just sending messages. Luna: I think that's a powerful vision for what community marketing can be. Not just a channel, but the whole engine. Lucas: It's a bet on people over software. And for now, it's paying off.