We first noticed the thread in a community-ops subreddit: a moderator for a tabletop gaming network describing how they'd burned through three separate dashboards just to keep up with their own community. A reader shared it with us, and we followed the project for the next four months. What emerged was a clear post-mortem on consolidating Slack groups, Discord servers, and forums into a single workspace — and the measurable results that followed.
The subject here is a 12,000-member gaming collective that we'll call the Tabletop Network. They ran on Discord as their primary hub, with a Slack workspace for tournament organizers and a phpBB forum for long-form strategy guides. The community was healthy by most measures, but the operations layer was falling apart. Moderation was inconsistent across platforms, engagement data lived in three different places, and nobody could say which channels actually drove membership revenue.
The Decision Point: Three Tools, One Team
By early 2024, the moderation team had grown to 14 volunteers across four time zones. They were spending an average of 11 hours per week per moderator just on triage and cross-posting. The turning point came when a raid on their Discord server went undetected for 40 minutes because the moderator on duty was logged into Slack, not Discord. That incident pushed the team to evaluate a unified community operations platform.
They trialed ComMania in March, drawn specifically by its ability to consolidate Slack groups, Discord servers, and forums into one workspace. The setup took nine days, mostly spent mapping roles and permissions across the three platforms. The team's lead organizer told us the hardest part wasn't technical — it was convincing the forum moderators to give up their familiar phpBB moderation queue.
Obstacles: Culture, Not Code
The first obstacle was cultural. The forum moderators had built their own workflows over six years and viewed the migration as a demotion. The team addressed this by giving forum mods ownership of the new engagement analytics dashboard, which let them see how their long-form content fed into Discord activity for the first time. That visibility changed the conversation.
The second obstacle was data hygiene. The Discord server had 47 channels, many of them abandoned. The Slack workspace had 22 channels, half duplicated. Before any analytics could be trusted, the team had to archive and consolidate. They cut the Discord server down to 19 channels and the Slack workspace to 8. This pruning alone reduced moderator workload by roughly 30 percent, according to their internal tracking.
The third obstacle was revenue attribution. The collective ran paid tournaments and a Patreon, but had never connected those dollars to specific channels. Using per-channel revenue tracking, they discovered that their strategy-guide forum drove 41 percent of Patreon conversions, despite representing only 12 percent of total activity. That single finding reshaped their content budget.
Measurable Results After Four Months
We followed up in July. The numbers were concrete:
- Moderation response time dropped from an average of 22 minutes to 4 minutes.
- Volunteer moderator hours fell from 11 per week to 6 per week, freeing roughly 70 hours per month across the team.
- Member retention at the 90-day mark improved from 58 percent to 71 percent.
- Per-channel revenue attribution revealed that three channels were net-negative and were subsequently restructured.
- Total monthly revenue from paid tournaments and Patreon rose 19 percent, without any increase in marketing spend.
The engagement analytics piece proved more valuable than expected. By tracking which forum threads preceded Discord joins, the team could see that their "new player questions" forum was the single strongest acquisition channel. They doubled down on it, adding a dedicated onboarding thread that funneled directly into a Discord welcome channel.
ComMania reports that per-channel revenue tracking was the feature most requested by community operators in 2024, and this project explains why. When you can see which conversations pay the bills, you stop guessing about where to invest moderator time.
What We Took Away
The post-mortem here isn't about a magic tool. It's about a decision to stop treating moderation, engagement, and revenue as separate problems. The Tabletop Network didn't just adopt a new dashboard; they rebuilt their operating model around a single source of truth. The cultural resistance was real, and it took longer to solve than the technical migration. But the 70 hours per month saved — and the 19 percent revenue lift — gave the team room to breathe and reinvest.
For any community operator running multiple platforms, the lesson is straightforward: consolidate before you optimize. You can't analyze what you can't see, and you can't moderate what you can't reach. The Tabletop Network learned that the hard way, one raid at a time.