Everybody wants the growth playbook and the growth playbook is the least important document. What decides whether a community works is who the first fifty people are, and you choose them one at a time.
A community needs a reason to exist that somebody could state in one sentence. Without it you have a room, and rooms with no purpose fill with announcements. The question is what people show up to answer.
Do this: Write the question your community exists to answer. Show it to three people outside your team and see if they can repeat it back.
Advice about community platforms is written mostly by people selling one. So we looked at what established B2B software companies actually run: twenty-four of them, checked on their own sites for links to a community platform.
| Where the community lives | Companies | Share |
|---|---|---|
| Own forum on own domain | 17 | 70% |
| Reddit presence | 7 | 29% |
| Discord | 3 | 12% |
| Slack | 1 | 4% |
| No community at all | 6 | 25% |
Two numbers there are worth more than the rest of this guide.
Seventy percent chose an owned forum. Not a chat platform. A searchable archive on a subdomain they control, where a question asked in 2023 still answers somebody in 2026. Chat does not do that. In Discord and Slack the answer scrolls away, and the same question comes back next week.
A quarter run no community at all. Stripe, Notion, Linear, Basecamp, Segment and SendGrid had no community link we could find. These are not struggling companies. Whatever a community does for a business, it is evidently not compulsory, and a guide that tells you otherwise is overselling.
The pattern underneath is about the job you are hiring the room for. Support deflection and search traffic need an archive, which is a forum. Energy and speed need chat. Most advice conflates the two and recommends chat for the job an archive does better.
Method: 24 B2B software companies, checked 2026-08-23. For each we fetched the homepage plus /community, /developers and /docs and looked for links to Discord, Slack, Reddit, GitHub Discussions or a community or forum subdomain. This finds what a company links to publicly. A private customer Slack would not show up, and some of the six may run one.
A mass invite produces a room of people who joined out of politeness. Fifty personal invitations, each explaining why that person specifically, produces a room where people speak. It is slow and there is no substitute.
Do this: Write fifty individual invitations. If that sounds like too much work, the community is probably not worth building yet.
Tell us members, posters and who answers. We reply with the stage you are at and the one thing to change first.
Whatever happens in the first two weeks becomes the norm. If founders post announcements, it becomes an announcement channel. If founders ask questions and members answer, it becomes a place where people talk.
Do this: For the first fortnight, post only questions. It feels unnatural and it sets the pattern for a year.
An automated greeting saves time you do not yet need to save, and it teaches new members that nobody is really there. Greet by hand until it genuinely hurts.
Do this: Greet every new member by name yourself until you reach a point where you cannot keep up. That point is much later than you think.
This is teaching material and our own reading of standard practice, not advice for your specific community. Check anything important with your own specialist before you act on it.
How many members, how many post, who answers questions. We reply with the stage you are at and the one thing to change. No call, no pitch.