Latest / Community Marketing with Fexingo: Discord, Slack Groups, and Brand Communities / How a Brand Community Turned Superfans Into a Metrics Dashboard
Transcript
- Lucas: So this week I came across something that genuinely surprised me, and I think it's going to change how we talk about community metrics. Luna: Now I'm curious. What is it — another case of a community outperforming a paid tool? Lucas: Exactly that. A 2,000-member B2B community, mostly mid-level marketers, decided they were tired of the company's clunky analytics dashboard. So they built their own. In a week. Using spreadsheets, a shared Figma file, and a whole lot of volunteer hours. Luna: Wait, they built their own dashboard? That's not something you hear every day. Lucas: It's a great example of a community taking ownership. And if you're finding this conversation useful — the kind of thing you might actually apply to your own community — the best way to keep these episodes ad-free is listener support. You can buy me a coffee at buy me a coffee dot com slash fexingo. Luna: Yeah, and every little bit genuinely helps. We love digging into these stories. Lucas: So back to the dashboard. The fascinating part isn't just that they built it — it's that the community members who built it became the people who maintain it. They call themselves data stewards. Luna: Data stewards — that's a great title. How did they get from 'we're unhappy with the metrics' to a full dashboard? Lucas: It started with a frustrated post in the community's feedback channel. One member, a marketing ops manager named Priya, posted a mockup of what she thought the dashboard should look like. Within hours, a dozen other members had commented with suggestions, and by the next day, a small team had formed. Luna: So it was organic, not company-driven. That's key. Lucas: Right. The company's community manager saw it and could have shut it down, but instead she gave them access to the raw data exports. That trust was a turning point. Luna: What did they build, exactly? Lucas: They created a dashboard that tracks what they call 'weekly active contributors' — as opposed to just active users. It's a more meaningful number because it measures people who are actually adding value, not just lurking. Luna: Contributors versus consumers. That's a big distinction. Lucas: Exactly. The dashboard pulls data from the community platform, Slack, and even email replies, and it updates every Monday morning. The data stewards rotate who does the weekly refresh, so no one person is burdened. Luna: And what did they find once they started tracking this? Lucas: The first surprise was that the contributor rate was only about 5 percent. That's not unusually low, by the way. But the team realized they were measuring it wrong — they were counting all members, including inactive ones. Once they filtered to members who had logged in within 30 days, the contributor rate jumped to 15 percent. Luna: So the metric itself was flawed before. That's a common problem with community analytics. Lucas: It's a great lesson. The dashboard also introduced a 'community health score' — a composite of contributor rate, response time, and sentiment from a weekly poll. The company now uses that score in their board reports. Luna: A health score that the community itself designed — that's powerful. Did the company's relationship with the community change? Lucas: It did. The community manager told me that the data stewards now get early access to product updates because they're seen as partners, not just users. And the stewards have become some of the most loyal advocates. Luna: That's a smart move by the company. They turned a potential rebellion into a collaboration. Lucas: Exactly. And the data itself improved. Within three months, the weekly active contributor count went up by 40 percent. The stewards credit the visibility — people could see their own contribution levels, and that motivated them. Luna: So the dashboard wasn't just a measurement tool — it became a motivator. Lucas: That's the insight. People want to see their impact. When the dashboard showed a leaderboard of top contributors, friendly competition kicked in. But the stewards were careful to keep it positive — they emphasized that anyone could move up. Luna: I love that. It's like gamification, but with data instead of badges. Lucas: Right. One of the most interesting side effects was that the dashboard helped the company catch a decline in engagement two weeks before their old analytics would have flagged it. The health score dropped because of a negative sentiment spike after a pricing change, and the community team was able to address it quickly. Luna: That's a concrete ROI. They avoided a potential churn event. Lucas: The company saved an estimated $50,000 in customer acquisition costs because they retained a group of high-value users who might have left. That's the kind of number that gets attention from the CFO. Luna: So what's the takeaway for someone managing a community? Should we all go build our own dashboards? Lucas: Not necessarily from scratch. But the lesson is to listen to your members' feedback on how you measure success. They might have better ideas than you do. Luna: And it doesn't have to be a big investment. This was spreadsheets and a free design tool. Lucas: Absolutely. The total cost was zero dollars. Just time and willingness to trust your community. That's the real investment. Luna: It's a beautiful example of community-led innovation. Do you think we'll see more of this? Lucas: I think we'll have to. As communities become more sophisticated, members want more than just a place to chat. They want to be part of the mission. This dashboard is a proof of concept. Luna: If you're listening and you've seen something similar, we'd love to hear about it. Maybe we'll feature it in a future episode. Lucas: That's a good way to end. The community that measures itself, thrives.