Chit-Chat Won't Keep Them Around

01 /The Concept

Root declares that "the era of real tools for real communities has arrived" – naturally implying that this era only begins for communities whose admins switch to Root.

The platform looks, at first glance, like Slack – a set of channels with chat. But the key difference is in the sidebar: alongside the channel list and navigation links, there's now a list of apps that community members can use directly inside the platform.

For historical reasons, Root built its initial feature set for gaming communities. Three apps are currently available.

The first, Task Tracker, lets community members plan shared objectives – setting goals, assigning owners, breaking work into checklists, and tracking completion.

The second, Raid Planner, helps organize in-game raids and events – assigning each participant a role, and overlaying the preparation and execution timeline onto a shared calendar.

The third, Sticker Wall, works like the front of a fridge. It's a shared board where community members can post stickers – to celebrate something, mark a shared win, express feelings, or just say hello. Multiple boards can coexist inside a community, each serving a different purpose or tone.

Critically, these apps can be built by community members or external developers using JavaScript and the platform's API. Any functionality is possible; the API allows apps to connect with the community's underlying data. Admins can install apps and bots from a built-in marketplace.

The platform isn't publicly available yet – a closed beta is coming soon. Despite that early stage, Root raised $9M in seed funding.

02 /Why It Matters

As Root's founder puts it: "Every community is different, with its own goals and objectives. But look at today's popular community platforms – Discord, for example – and what you find is that they offer only basic chat functionality to help communities achieve those goals. I believe every community needs its own tools."

For gaming communities specifically, what's needed is the ability to organize raids, maintain a game knowledge base, manage teams, and coordinate across time zones. Right now, admins literally duct-tape their communities together using Google Sheets and links to external apps – a setup that's clunky at best and breaks down under load.

Good communities also evolve, which means their needs evolve too. A platform must not only be customizable at a point in time but capable of growing alongside the community itself.

The lead investor from Headline Ventures put it more dramatically, calling Root "a paradigm shift that comes along rarely – not an improved community platform, but a complete rethink of how communities should self-organize and develop." They see the investment as a chance to participate in reshaping the digital spaces where online communities will live.

The actual paradigm shift is this: Root is not built for communication within communities – it's built for action.

Here's the problem with pure communication as a community foundation. People gather, they talk, old topics run dry, new ones don't naturally appear – and the community starts to fade. Or it turns into a one-person show: the founder burns out trying to generate topics, posting constantly to fill the silence, and eventually that stops too.

Communities that last are built around shared activities – planning them, executing them, and debriefing on them generates the conversation naturally. Discussion is the byproduct of action. No action, no discussion.

But doing shared things requires the right tools. And most community platforms don't have those tools. Linking to external ones adds friction – exactly the friction Root is trying to eliminate.

03 /Opportunities

Building a community is a popular aspiration. Almost every product creator wants one for their users; every online creator wants one for their audience.

The goal is obvious – a community should improve retention. But only a live community does that. A dead one is just additional work for its creator, who ends up flogging a dead horse.

Two directions emerge from this. For community builders – stop trying to engineer conversation artificially. Design regular activities that members will want to participate in; the conversation starts itself once those activities exist. The more interesting product question is what those activities could be for your specific community.

For platform builders – the structural insight points toward action-first community platforms rather than chat-first ones.

The practical advice here is to start specific – platforms built for a particular type of activity within a particular type of community. Generic "all-purpose" community tools that theoretically work for anyone tend to work well for no one in practice. Root went narrow with gaming communities first, and that's the right call.

Start with a community type you know from the inside – gaming, fitness, professional development, creator networks – and map the specific coordination tasks members currently handle through Google Sheets and external links. That friction is the exact product spec.