Latest / Community Marketing with Fexingo: Discord, Slack Groups, and Brand Communities / How a Brand Community Becomes a Product R&D Engine
Transcript
- Lucas: You know the phrase 'the customer is always right'? I think a more useful version for marketers is 'the customer always has something to teach you' — if you set up the right system to let them teach you at scale. Luna: And 'at scale' is the key. One-on-one calls with customers are great, but they don't scale. A community can. Lucas: Exactly. So today I want to look at a B2B SaaS company — we'll call them WorkflowPro, name changed — that essentially replaced their entire product research function with a 200-person Discord server. Luna: Two hundred people replacing a whole department? That sounds both impressive and a little terrifying for the researchers. Lucas: Well, the researchers were actually external agencies they were paying two hundred thousand dollars a year to run focus groups and usability studies. And the community didn't just replace that — it made the feedback faster and more actionable. Luna: Okay, so how did they set it up? I imagine it wasn't just 'create a Discord and hope people talk.' Lucas: Right, there were three specific mechanics. First, a weekly feedback thread every Wednesday at noon Eastern — a pinned post where any member could share a pain point or a feature idea. Second, a voting bot where users could upvote feature requests, and the top five each month went straight onto the product team's radar. Luna: So the community essentially became a prioritization engine. Lucas: Exactly. But the third mechanic was the most powerful: a private alpha channel. They invited about thirty of their most engaged — and most demanding — customers to test new builds before anyone else saw them. These were power users who weren't afraid to say 'this button is in the wrong place' or 'the loading time increased by two seconds.' Luna: And those are the kinds of insights you'd pay a usability lab hundreds of dollars per session to get. Lucas: Yeah. The company estimated that each alpha test — with maybe ten participants — saved them about five thousand dollars in agency fees. And they were running two or three of these a month. Luna: So that's roughly fifteen thousand a month in savings, or a hundred and eighty thousand a year — just from the alpha channel. Lucas: Plus the feedback threads and voting data meant the product team never had to guess what customers actually wanted. They had a ranked list, updated in real time, from their most valuable users. Luna: There's a risk though, right? The loudest voices in a Discord might not represent the broader customer base. You could end up building features for a vocal minority. Lucas: That's the classic trap. And WorkflowPro almost fell into it. In month three, the voting bot showed a feature about bulk CSV export as the number one request. The product team spent three weeks building it. When they shipped it, usage data showed fewer than five percent of customers actually used it. Luna: Ouch. So what did they change? Lucas: They added a simple check: before any top-voted feature got built, they'd post a mockup in the feedback thread and ask the broader community — not just the voters — 'Would this solve a problem for you? How often?' That filter saved them from building at least two more features that would have been duds. Luna: So the community is the idea engine, but you still need a validation layer. That's smart. Lucas: And it's still faster and cheaper than a traditional focus group. You go from idea to validated mockup in about a week, instead of a month-long agency study. Luna: I think the other thing that's interesting is the emotional dynamic. The alpha testers felt like insiders. They weren't just giving feedback — they were part of the product's evolution. That's a retention driver in itself. Lucas: Yeah, WorkflowPro saw their churn rate among alpha participants drop to nearly zero. Those customers were invested. Some of them even started answering other users' questions in the general channel, reducing support tickets too. Luna: So the community started pulling double duty — R&D and customer support. Lucas: Exactly. And this is the part that I think a lot of marketers underestimate: the conversation itself is the product. When you have users talking to each other about your tool, you get organic FAQs, workarounds, and feature requests all in one place. You just have to listen. Luna: Listening is the easy part. The hard part is acting on it without being overwhelmed. WorkflowPro had a dedicated community manager who spent about ten hours a week just curating the feedback and passing it to product. Lucas: Ten hours a week to replace a two-hundred-thousand-dollar agency retainer. That's a return on investment that's hard to beat. Luna: It makes me wonder how many companies are sitting on a goldmine of customer insight in their support tickets or social media mentions, but they just don't have a structured way to mine it. Lucas: And the community is that structure. It's not just a place to post announcements. It's a research lab that pays for itself. Luna: Alright, so for someone listening who wants to start something like this — what's the minimum viable version? Do you need a full Discord with voting bots and alpha channels? Lucas: Not at all. You could start with a simple private Slack group or even a WhatsApp chat with your top twenty customers. The key is the routine: a regular time each week when you ask a specific question, and a way to track which ideas get the most support. Even a Google Form shared in a group can work. Luna: It's the consistency that builds the habit — for both the company and the customers. Lucas: Yeah. And honestly, if these marketing conversations have sparked something you've actually used in your own work, that's exactly the kind of signal we love hearing about. A handful of listeners chip in monthly through buy me a coffee dot com slash fexingo, and that literally helps fund making this many of these episodes — keeps it ad-free, keeps it focused on what's actually working. Luna: Yeah, it's a small group, but it makes a real difference. And it's not about perks or anything — just people who find value and want others to find it too. Lucas: Exactly. And back to the community as R&D engine — one last stat that stuck with me. WorkflowPro's time from feature idea to shipping dropped from about six weeks to under two weeks once the community system was fully running. Luna: Six weeks to two weeks. That's a competitive advantage in any market. Lucas: And it all came from two hundred people in a Discord server — people who already wanted the product to be better. You just had to give them a way to tell you how.