Pular para o conteúdo
← Back to the blog

November 17, 2026 · 5 min read

Slack community: what we learned looking inside Granola's

By Amílcar GomesCommunity Management & Growth · Community Org

A lot of people think Slack is only for internal teams to talk. But many software companies use Slack as a user community, and some do it very well. Granola is one of those cases: it has almost 2,800 members in an open workspace, and almost nothing public talks about how this community works.

We took a look inside. This case study shows the structure, the numbers and the decisions that make the community work (and also what could be better). The numbers are our own measurement, taken in November 2026, when we looked at the public channels over the previous 90 days. They are not official Granola data.

What Granola is

Granola is an AI notepad for meetings, created in London in 2023. The product launched in May 2024 and grew mainly through word of mouth inside companies: one person starts using it, shows it to the team, and the team brings it to the company. In March 2026, the company raised a US$ 125 million Series C.

B2B or B2C? Neither, purely

Last week we wrote about what changes between a B2B and a B2C community. Granola sits in between:

  • The entry is B2C: the person joins on their own, often on the free plan.
  • The motivation is B2B: they want to solve a work problem (meetings, notes, integrations).
  • The rhythm is B2B: weekdays, long and technical questions.

That is why Slack works here. The member already spends the day in it, so the community fits into their routine without any extra effort.

The structure: 12 channels, a lean core

The public channels fall into four groups:

  • Core: #general, #product-announcements, #granola-feedback and #bugs-and-errors. Almost every member is in all four.
  • Testing programs: one channel for each beta (iOS, Windows, the beta program and previews), each with the download link in the channel topic.
  • Niches: channels for advanced uses and clubs, with a few dozen members.
  • Operations: a channel with the status bot, which posts incidents.

Two details stand out. First, the community was born before the public product: the channels were created three weeks before launch. Second, the core is small and the names are self-explanatory. Nobody gets lost in a maze of channels.

What the 90-day numbers show

  • Low volume for its size: about 2 posts a day for almost 2,800 members. The people who post are a minority, the 90-9-1 pattern. In a work community, that is not a problem: one good conversation is worth more than volume.
  • High response rate: between 62% and 81% of posts get a reply. In #bugs-and-errors, 8 out of 10 reports get an answer.
  • The beta is the richest channel: 4.6 replies per post. People who test early talk more.
  • Four silent channels: no posts in 90 days, including the announcements channel, with about 2,770 members. Announcements go out through other paths (app, email, social media) and the channel went quiet.

How the team responds

We looked at a sample of 20 recent conversations. The team's pattern:

  • Calls people by name and thanks them for the feedback.
  • Asks for detail: screen recording, app logs.
  • Explains the why behind decisions, even when the answer is "not yet".
  • Solves account issues fast: a plan upgrade made by mistake was reversed in 20 minutes.

When it gets it right, the first reply comes in under an hour. In other cases, it took 10 to 35 hours, and some questions got no reply.

Another strong point: a launch becomes product research. The new voice dictation feature sparked the longest conversation of the period, full of comparisons with competitors. The community became the place where the team hears how the product stacks up against the market.

What could be better

  1. The same question in three channels. There is no pinned guidance on "where to post what".
  2. #general turned into a support desk: email, plan, billing, login. Account issues should go to a private channel or to email.
  3. Channels created and abandoned. A new channel without a ritual dies.
  4. Status in the wrong place. The bot posts incidents in a channel of 16 people, while bug reports arrive in the channel of 2,680.
  5. Unanswered questions in a public channel are visible to every other member.

7 lessons for building a community on Slack

  1. Slack is for work products. If your member lives in Slack, the community fits into their routine for free.
  2. Start before launch. The first users become the first members.
  3. Small core, clear names. General, announcements, feedback and bugs cover almost everything.
  4. Public feedback is an open roadmap. Replying by name and explaining decisions builds trust.
  5. One channel per beta. The people who join are the ones who most want to talk.
  6. Measure two things: % of posts with a reply and time to first reply.
  7. Close the leaks: a pinned "where to post" channel, account support out of public view, no channel without a ritual, and status where people already are.

When NOT to use Slack

Slack pays off when the audience is already in it. It usually fails when:

  • the audience is consumers who don't use Slack at work;
  • the community is large and open, and the free plan's limited history erases the best answers;
  • Slack becomes "one more app" the member has to remember to open.

In those cases, Discord, WhatsApp or your own forum tend to work better.

Community Org builds and runs communities on Slack, Discord and WhatsApp, from channel structure to response metrics. If you want to run the same diagnosis on yours, Talk to us.

Written by

Amílcar Gomes

Community Management & Growth · Community Org

Follow on LinkedIn →

Ready to grow with an engaged community?

Community Org builds and manages communities on WhatsApp, Discord, Telegram and social media for brands.

Book a call

Keep reading

Get community insights

Practical ideas on engagement and community management in your inbox. No spam, unsubscribe anytime.

By subscribing, you agree to our Privacy Policy.