Latest / Community Marketing with Fexingo: Discord, Slack Groups, and Brand Communities / How a Brand Community Replaced a Full Product R&D Engine
Transcript
- Lucas: So earlier this week I was looking at a company called Sparkplug — it's a B2B SaaS platform for sales teams, about 500 employees, and they've got a Discord server with roughly 300 active members. Luna: Three hundred doesn't sound huge. Most B2B communities I see are aiming for thousands. Lucas: Right, but Sparkplug isn't using that server for marketing or support in the traditional sense. They're using it as their primary product research and development engine. I'm talking about replacing a full product research team — the kind that costs half a million a year in salaries alone — with a well-run Discord. Luna: Okay, that's a big claim. How do they actually pull that off? Lucas: So they structure the server around what they call 'Feedback Fridays.' Every Friday, they post a thread with a specific product question — it could be about a new feature mockup, a pricing change, or even a strategic direction. The community responds with their thoughts, and the product team reviews every single comment. Luna: And that replaces formal user interviews? I've run user research programs — they're structured, you recruit participants, you pay incentives... Lucas: Exactly. Sparkplug used to do all that. But they found that their community members — who are already paying customers — are more than willing to share feedback for free, because they have a direct stake in the product improving. Plus, the feedback is more authentic since it's in a group setting where people build on each other's ideas. Luna: It's like a focus group that never ends and recruits itself. Lucas: That's exactly it. And the results are tangible. Last year, one of their Feedback Friday threads led to a feature request that became their highest-converting add-on — it generated two million dollars in new annual recurring revenue within six months. Luna: That's the kind of story that makes you wonder why more companies don't do this. Lucas: And you know, if these marketing conversations have sparked something you've actually used — maybe a new way of thinking about your own community — that's exactly what listener support helps us keep doing. No ads, no sponsors, just the show and the people who find it useful. If you ever feel like chipping in, you can at buy me a coffee dot com slash fexingo. Luna: It's a small way to keep this going. Anyway, back to Sparkplug — how do they avoid the community just becoming a complaint forum? Lucas: Great question. They have a dedicated community manager who sets the tone. The key is that Feedback Fridays are framed as collaborative problem-solving, not just venting. They also have a 'feature voting' channel where members can upvote ideas — but only after they've been discussed in a thread. That prevents pile-on voting without context. Luna: So there's structure. It's not just a free-for-all. Lucas: Right. And they've also built a direct pipeline to the product roadmap. Every month, the product team publishes a 'community impact report' — basically a summary of which community ideas made it into the next sprint, and why. That transparency loop keeps members engaged and feeling heard. Luna: That's smart because it closes the feedback loop. Most companies collect feedback and then it disappears into a black hole. Lucas: Exactly. And the numbers back it up. Sparkplug estimates that this community-driven R&D saves them about four hundred thousand dollars a year compared to the old way of doing things — that's the cost of two full-time product researchers plus external user research vendors. Luna: But what about the bias? The people in the Discord are already customers — they're probably more engaged and more positive than the average user. Lucas: That's a valid concern. Sparkplug addresses it by occasionally running blind surveys to a broader customer base and comparing results. They've found that the Discord feedback actually correlates pretty well with the broader base, but they also acknowledge that the community is more tech-savvy and more willing to try new features. So they treat the community as an early signal, not the final word. Luna: So it's more of a rapid prototyping sandbox than a full market research replacement. Lucas: Exactly. And that's a healthier framing. The community helps them prioritize what to build next, but they still validate with quantitative data and broader market analysis before going all-in. Luna: I'm curious — how do they handle the operational side? Who's actually running the Discord day-to-day? Lucas: They have one full-time community manager, who reports to the head of product. That person costs about seventy thousand a year. So even with that salary, the net savings versus a full product research team are substantial. Luna: And the community manager isn't just a babysitter — they're actively synthesizing feedback and feeding it into the product process. Lucas: Right. They write weekly summaries that go straight to the product team. And they also run 'office hours' on the server twice a week where product managers drop in to answer questions directly. That's another layer of engagement that builds trust. Luna: It sounds like they've turned their most engaged users into an unpaid, highly motivated advisory board. Lucas: That's a great way to put it. And the members benefit too — they get early access to features, direct influence over the product, and a sense of belonging. It's a genuine two-way value exchange. Luna: So what's the takeaway for companies that want to try this? You can't just spin up a Discord and expect magic. Lucas: No, definitely not. There are three prerequisites. First, you need a product that people are passionate enough about to discuss in their free time. Second, you need a community manager who understands both product and community dynamics. And third, you need executive buy-in to actually act on the feedback — otherwise people will stop participating. Luna: So it's not a shortcut. It's a different way of working. Lucas: Exactly. It requires discipline and transparency. But for companies that get it right, the payoff is huge — faster iteration, lower R&D costs, and a product that's more closely aligned with what customers actually want. Luna: I'm thinking about whether this model works for consumer products too. Like a fitness app or a food brand — would people be as engaged? Lucas: It can work, but the dynamics are different. For B2B, the motivation is often professional — people want to be better at their jobs. For B2C, you need to tap into identity or passion. But there are examples. Peloton's community has influenced product features, for instance. Luna: I'd love to dig into a B2C example in a future episode. Lucas: Noted. For now, I think Sparkplug's case is a really concrete blueprint for any B2B company sitting on an existing user base. You might already have the raw material for a product R&D engine — you just need to structure it. Luna: And maybe save a few hundred thousand dollars in the process. Lucas: That certainly doesn't hurt.