How do I build a community around my product?
Most early products should not start their own community — they should show up in the ones their users already belong to. A community works when members get value from each other, not just from you; until you have users who talk to you unprompted and have reasons to talk to each other, your own Discord will be an empty room that quietly signals nobody is here. When the demand is obvious, start small, host it personally every day for the first few months, and treat it as a channel with a real weekly cost rather than a growth shortcut.
First ask whether you need one
"Start a community" gets recommended to founders far earlier than it should be. The test is not whether you would like one — everyone would. It is whether your users have a reason to talk to each other. If the value flows only from you to them, what you actually need is documentation, a changelog, and a support inbox. Communities work when members answer each other's questions, trade templates and workflows, or share a problem that binds them together outside your product.
The cost of getting this wrong is not zero. An empty Discord is worse than no Discord: a prospect who clicks your community link, sees four messages from three months ago, and leaves has just learned something discouraging about your traction. That first impression is hard to undo, and it is entirely self-inflicted. Waiting costs you nothing by comparison, because the people who would have joined are still reachable later.
Where to build it
"Community" is not one choice. The cheapest versions borrow an audience that already exists; the expensive version asks you to recruit one from scratch. Most founders should work down this table from the top, not start at the bottom:
| Option | Best when | What it really costs |
|---|---|---|
| Show up in existing communities (subreddits, forums, Discords you don't own) | Always — and especially before you have users | A few hours a week of genuine participation; you must be useful before you are promotional |
| Build in public on a social platform | You can write consistently and your journey is itself interesting | Sustained posting cadence; the audience is yours but rented on someone else's platform |
| A shared space for your customers (Discord, Slack, Circle) | Users already message you unprompted and ask to talk to each other | Daily presence for months, moderation, and seeding every conversation early on |
| A public forum or knowledge base | Questions repeat and answers stay useful for years | Slow to feel alive, but it compounds in search and in AI answers |
What it costs, and what actually works
If you do open a space, the failure mode is predictable: launch, a burst of joins, silence by week three. Avoiding it is mostly unglamorous work that does not scale, which is exactly why it works.
- Be the host, not the owner — for the first few months you personally start conversations, ask questions, and reply to every message. A community with no visible host dies quietly, and no tool fixes that.
- Invite narrowly — twenty people who share a problem will talk; two hundred randoms will not. Density of interest beats headcount, especially at the start.
- Give a reason to return — something they cannot get from your docs: early access, your roadmap thinking, direct answers, or each other's hard-won workarounds.
- Count it honestly — judge it like any other channel, on cost per real outcome, the same way you would decide where to double down. Members is a vanity number; conversations that happen without you is not.
- Earn the right to mention your product — in communities you do not own, the ratio matters and the rules are enforced. This is its own skill, covered in getting users from Reddit.
We follow our own advice here, which is a useful test of it. AgentCeres runs a Reddit community specialist, so we are a company that would obviously benefit from a thriving community — and we still have not opened our own Discord, because the bar has not been met: our users do not yet need each other. The customers who have found us through community found us in threads we do not own, where our topic came up and someone was genuinely useful in the replies. That is the honest order of operations: borrow an audience until you have earned one, then host the room. For the definition and where this motion fits a wider plan, see community-led growth.
FAQ
- Discord or Slack for a startup community?
- Discord suits consumer, developer, and creator audiences: it is free at any size, public by default, and people already have it open. Slack suits B2B communities where your members live in Slack all day and a work-adjacent tone fits, but free workspaces hide older messages, which quietly destroys the archive that makes a community searchable and useful over time. If you genuinely cannot decide, that hesitation is usually a sign it is too early to open either one.
- How many users do I need before starting a community?
- There is no threshold number, because it is not about count — it is about whether members have a reason to talk to each other. Some products hit that at 30 users; some never do, and that is fine. The practical signal is unprompted: users already message you with questions others would benefit from, or ask whether other customers are doing something similar. Until you see that, your effort is better spent in the communities where those people already are.
- Can a community be my main growth channel?
- It can, but it is slow and it is rarely a first channel. Community compounds — members bring peers, and answers left behind keep working — but it takes months before it produces meaningful acquisition, and it demands consistent human presence the whole time. Most founders are better served treating it as a retention and word-of-mouth layer on top of a channel that already brings people in, rather than the thing that has to fill the top of the funnel.
Want this done for you?
AgentCeres is a managed AI marketing team — specialists draft the work, you approve what ships. 14-day free trial, from $19/month.