Latest / Community Marketing with Fexingo: Discord, Slack Groups, and Brand Communities / How a Brand Community Became a Market Research Machine
Transcript
- Lucas: So there's this B2B software company called Grain — they make a tool for recording and transcribing sales calls. About 18 months ago they had a classic early-stage problem: they needed to understand their customers' workflows better, but they didn't have the budget for a dedicated market research team. Luna: Right, that's a common pain point. So they turned to their community? Lucas: Exactly. They had a Slack community of about 150 power users — mostly sales ops managers and revenue leaders. And the community manager, a woman named Jess, decided to turn that group into an ad hoc market research machine. Not by asking vague questions like 'what do you want?' but by building a pretty systematic process. Luna: Okay, I'm curious about the system. What was the first step? Lucas: She started with what she called 'hot take' threads. Every Monday she'd post one specific question about a feature or a workflow — like 'how many of you are still using spreadsheets to track deal stages?' or 'when you lose a deal in the final round, what's the number one reason?' The key was that the question was super narrow. Not 'tell me about your sales process' but 'give me one data point about this specific thing.' Luna: And people actually responded? Because that kind of thing can feel like homework. Lucas: That's the clever part. Jess made the threads time-boxed — responses only open for 24 hours. And she'd share the aggregated results in a follow-up post within 48 hours. So participants got immediate value from seeing what their peers said. The response rate was consistently over 40 percent, which is insane for unsolicited community engagement. Luna: Forty percent? That's better than most internal employee surveys. Lucas: Right. And then she added a second layer: a private channel called '#competitive-intel' where community members could anonymously share what they were seeing from competitors. The rule was no direct naming of other products in public channels, but in that private channel, anything goes. That channel alone generated something like 80 actionable competitive insights in the first quarter. Luna: So the community became a kind of early warning system. I can see how that would feed directly into product and marketing decisions. Lucas: It did. The product team started attending the weekly insight reviews. And here's the concrete result: Grain's product-market fit score, measured by Sean Ellis's standard survey, went from 32 percent to 44 percent over six months. That's a 12-point jump. The company attributes about half of that improvement to decisions directly informed by community research. Luna: That's a dramatic shift. But I wonder — does this only work for a certain type of community? Grain's users are sales professionals, who are already analytical and used to sharing data. Would this work for, say, a consumer brand's Instagram community? Lucas: Fair question. I think the principle scales, but the tactics need to match the platform. On Instagram, you're not going to get a 40 percent response rate to a text thread. But you could run weekly polls in Stories and get similar breadth, if not depth. The core idea is the same: ask one narrow question, share results fast, give people a reason to participate. Luna: So the community becomes a research panel that's also a retention engine. That's a powerful combo. Lucas: Exactly. But there's a hidden cost I want to flag. Jess told me that after about six months, she started noticing a dip in engagement on the hot take threads. Some members complained they felt 'over-surveyed.' The novelty wore off. So she had to pull back to every other week, and she introduced a quarterly 'deep dive' survey that replaced the weekly threads for that month. The deep dive got a 70 percent response rate because it felt more substantial. Luna: That's a good lesson. You can't just keep pulling from the well without giving back. The community members need to feel like they're getting value, not just being mined for data. Lucas: Right. And Grain's approach to giving back was pretty smart. They started offering early access to new features to anyone who participated in three or more hot take threads. That created a status reward — you got to see things before the general user base. It wasn't financial, but it was meaningful to the power users. Luna: So the research loop became a loyalty loop. Participate, get access, feel special, participate more. Lucas: Exactly. And the data they got from those early access previews was even more valuable. Because now they weren't just asking about hypotheticals — they were watching people actually use the feature and hearing feedback in real time. That closed the loop completely. Luna: Okay, I want to ask about the limits. You mentioned this works for a 150-person community. What if your community is 10,000 people? Does the same system break? Lucas: It probably does. At scale, you'd need to segment. Maybe you have a 'research council' of 200 highly engaged users who opt into the deeper work, and then you use broader polls for the rest. The hot take thread format would get noisy in a huge channel. But the principle of narrow questions and fast feedback cycles still holds. Luna: I'm also thinking about the quality of insights. With a small, self-selected group, you risk hearing from the loudest voices, not the most representative ones. Lucas: That's a real risk. Grain mitigated it by comparing community survey results to their broader customer base via email surveys every quarter. They found that the community responses were actually directionally aligned — just more detailed. The community wasn't representative of the entire user base, but it was representative of their most engaged segment, which is often the segment you want to learn from first. Luna: That makes sense. If you're building for power users, ask power users. If you're building for the mainstream, you need a different panel. Lucas: Exactly. And that's the strategic choice: know who your community represents and use their insights accordingly. Grain's community skewed toward early adopters and high-usage accounts, which was perfect for product development. For marketing messaging, they supplemented with broader surveys. Luna: So the community became one input among many, but a uniquely fast and rich one. Lucas: Precisely. And the cost comparison is striking. A typical market research project with an agency — let's say a custom survey of 200 B2B buyers — runs anywhere from $15,000 to $30,000 and takes 6 to 8 weeks. Grain's hot take threads cost essentially zero incremental dollars and delivered insights in 48 hours. Over a year, they effectively replaced three to four agency projects. Luna: That's a huge ROI, especially for a startup. But I imagine the community manager's time isn't free. Jess probably spent 5 to 10 hours a week on this. Lucas: She estimated about 6 hours per week — writing the questions, monitoring responses, compiling results, and running the deep dive survey. So call it a quarter-time role. Compare that to a full-time market research analyst salary, and you're still way ahead. Plus, the community manager is already in the channels, so there's no onboarding cost. Luna: I want to try something like this with my own community. But I think the hardest part is coming up with good questions. You can't just ask 'what do you think?' every week. Lucas: Totally. The question design is the skill. Jess had a simple framework: each question had to pass three tests. One, it's about a specific behavior, not an opinion — 'when did you last X' not 'how do you feel about X.' Two, the answer can be summarized in a single chart or top-three list. Three, the result would be useful even if only ten people respond. That last test prevents you from asking something that requires a big sample to be meaningful. Luna: That's a great heuristic. I'm going to steal that. Lucas: You should. And honestly, if this episode sparked an idea you've actually used in your own community or business, that's the kind of thing that keeps this show ad-free. We don't run sponsors, we don't do mid-rolls. The whole thing stays independent because of listeners who find value in it. If today's conversation was worth a coffee to you, that's the link — buy me a coffee dot com slash fexingo. Luna: Yeah, it's a small way to keep the conversations coming. No pressure, just if it felt useful. Lucas: Anyway, back to the question design — one thing Jess emphasized was that the best questions often came from product team debates. If the product managers were arguing about whether to build feature A or feature B, she'd turn that into a hot take thread. The community's response didn't decide the roadmap, but it often broke the tie. Luna: So the community became a tiebreaker for internal disagreements. That's a pretty high-impact role for a 150-person Slack group. Lucas: Exactly. And that's the through line of this whole episode: a brand community, when structured with intentional research practices, can punch way above its weight. It's not just a place for chit-chat or support. It can be a strategic asset for understanding your market, testing ideas, and even shaping your product. Luna: I think the key takeaway for me is that it's not about the size of the community — it's about the discipline of the process. Narrow questions, fast results, and a clear feedback loop. Lucas: Right. And knowing when to pull back so you don't exhaust your most valuable members. That balance is everything. Luna: So for anyone listening: if you have a community, even a small one, you probably have a market research machine sitting idle. You just need to turn it on. Lucas: And maybe start with one hot take thread this week. See what happens. I'd love to hear from anyone who tries it. Luna: Agreed. That's it for this episode of Community Marketing with Fexingo. We'll see you next time.