A few of your customers keep emailing you the same kind of question: how are other people using this? Someone suggests a Discord. You set one up on a Sunday, post a cheerful welcome, and three weeks later the newest message in #general is still yours.
This guide is for indie founders with a small paying user base, roughly 30 to a few hundred customers, who want a customer community that actually gets used. It covers when a community is worth it, picking its one job, choosing a platform (prices checked October 8, 2026), the first 20 members, rules, moderation, keeping it alive, measuring it, and when to shut it down.
Do you actually need a customer community?
You need one when your customers would get real value from talking to each other, not just to you. If every useful conversation has you in the middle, a community adds a second inbox and nothing else.
Check your reasons honestly before you build anything:
Good reason to start one | Weak reason to start one |
|---|---|
Customers already ask how other people set the product up | Every successful SaaS seems to have a Discord |
Your users share a craft or trade (photographers, accountants, teachers) and swap tips anyway | You want a cheaper support channel |
Power users have workflows worth copying, like templates, automations or setups | You hope it will bring in new signups by itself |
You can spend 20 to 30 minutes on it most weekdays for three months | You plan to set it up and let it run |
If most of your reasons sit in the right column, skip it for now. An announcements list can be an email or a changelog, and support works better as support. If you only want people to hear about updates, read how to write a changelog that brings silent users back instead.
One more check: your customers may already have a community. If they hang out in a trade forum, a subreddit or a Facebook group, being useful there can beat building your own room. The DEV piece on finding first users in threads where they already complain covers that route.
What job should your community do first?
Give it one job for the first three months. A community that tries to be support desk, feedback board, social club and launch list at once ends up as none of them.
Job | Fits products like | What you post | Sign it's working |
|---|---|---|---|
Show and tell | Tools where output is visible: templates, sites, designs, automations | "Share what you built this week" threads, your own examples | Members post setups without being asked |
Peer how-to | Products with many valid ways to use them | Questions you get by email, rewritten as public threads | Members answer each other before you do |
Craft talk | Users who share a profession or hobby | Questions about the work itself, not your features | Threads that never mention your product but keep people coming back |
Customer council | B2B tools with a few dozen engaged accounts | Rough mockups, pricing questions, "would you use this?" | Detailed replies within a day or two |
Craft talk is the one founders skip, and often the one that lasts. People return for the topic they care about, and your product sits next to it.
Discord, Slack, a forum or GitHub Discussions: which should you pick?
Pick the place your customers already open during their workday, then check that the platform fits the job. Chat suits quick back-and-forth. A forum suits questions whose answers should still be findable in a year.
Here is what each option looked like when we checked the vendors' own pages on October 8, 2026. Prices change, so check again before you commit.
Platform | Cost to start | Good at | Watch out for |
|---|---|---|---|
Discord | Free | Chat, voice, roles; forum channels for organized threads | Your business customers may not have it installed; messages sit behind a login |
Slack | Free plan, or Pro at $8.75 per user a month (monthly billing) | Business users who live in Slack all day | Free plan shows only 90 days of history; paid plans bill per active member |
Discourse | Free hosted plan, Pro at $100 a month, or self-host the open source version | Searchable Q&A and long threads that stay useful | Feels quieter than chat; people need a reason to visit |
GitHub Discussions | Free with a repository | Developer tools whose users already have GitHub accounts | Can feel unfamiliar to non-developers; it lives inside a repository |
Circle | Professional at $89 a month (annual billing), 14-day trial | Paid communities, courses and events in one place | A real monthly bill before you know the community works |
The details behind that table:
Slack's free plan forgets. Slack's page on free plan limitations says free workspaces are "limited to the most recent 90 days of message and file history, and all data in your workspace that's more than one year old will be deleted."
Slack's paid plans scale with members. The Slack pricing page listed Pro at $8.75 per user per month on monthly billing and $7.25 on annual billing, and Slack's Fair Billing Policy says you're "billed for all active members." Fine for a team, costly for a customer community.
Discourse has a real free tier. Its free plan page lists unlimited members, unlimited chat, 2 staff seats and a free .discourse.group domain. The Discourse pricing page lists Pro at $100 a month with 5 staff seats and says the software is "100% free and open source" if you'd rather self-host.
GitHub Discussions needs a repository. GitHub's About discussions page says an administrator must enable Discussions first, and then "anyone with access to a repository or organization can create and participate in discussions there." It supports marking answers and polls. If your code is private, one workaround is a small public repository used only for discussions.
Circle is built for paid communities. The Circle pricing page showed Professional at $89 a month, with prices "based on annual billing." That makes sense if the community is part of what you sell, less so as a side room.
If you're stuck: developer tool, GitHub Discussions. Buyers who live in Slack, a Slack workspace if you accept the 90-day memory. Most other indie products, a Discourse forum if answers should last, or Discord if your users are already there.
How do you set up a Discord server so it looks cared for?
Turn on Discord's Community features, keep the channel list short, and post before anyone arrives.
Discord's help article on enabling your Community server lists what you must switch on first: a verification level where members need a verified email before they can message, the explicit media content filter, a rules or guidelines channel, and a community updates channel for moderators. In return you get announcement channels, Server Insights and Community Onboarding, where new members pick roles and channels by answering a few questions. The same article limits Server Discovery to servers with more than 1,000 members and Partnered and Verified servers, so don't count on it for growth.
For question-and-answer use, Discord's Forum Channels FAQ says forum channels need Community enabled, support tags, and move inactive posts to an Older Posts section after a set time (3 days by default). Each question gets its own post instead of scrolling away.
A starting layout that works for most small products:
#start-here: what this space is for, who it's for, and the rules.
#introductions: name, what you do, what you use the product for.
One forum channel for the main job (for example "show-your-setup" or "how-do-i"), with three to five tags.
#announcements: read-only, used once or twice a month at most.
#general: everything else.
Five is plenty. Add a channel when people complain one is too crowded, not before.
How small should you start?
Start invite-only with 15 to 30 customers you picked by hand. A small room where people get replies feels alive. A big silent room feels like a failure, whatever the member count says.
Who to invite first:
Customers who reply to your emails with more than one line.
People who've shared a setup, a template, or a screenshot of their work.
Anyone who has asked "how do other people do this?"
A few newer customers, so it isn't only early adopters.
Invite them one at a time, by email or DM, with a reason that's about them. Example wording to adapt (our own):
"Hi Sam, you're one of the people whose setup I keep wanting to show others. I'm opening a small space for about 20 customers to swap how they use the product and talk shop. No sales pitches, and I'll be in there most days. Would you like an invite? No worries if not."
When each person joins, reply to their introduction within a few hours and ask one question about their work. That first reply often decides whether they post again.
An invented example to make this concrete. The product, person and numbers are made up. Ines runs Shotlark, a client-proofing tool for wedding photographers, with about 140 paying customers. Customers kept asking how others handled client picks and album deadlines. She chose craft talk as the job and a free Discourse forum, because she wanted good answers to stay findable. She invited 22 customers personally; 17 joined in the first week. She seeded six threads from real emails (with permission, names removed) and answered every introduction the same day. By week six, members were answering more questions than she was.
What rules should a small community have?
Write five or six short rules for the problems you'll actually see: self-promotion, rudeness, support requests and private data. Short specific rules get read.
Be kind, and argue with ideas, not people.
No unsolicited promotion or DMs selling things. Sharing your own work in the show-and-tell thread is fine.
Billing, account and urgent problems go to email. Give the address. The community isn't a support guarantee.
Don't post client or customer data. Blur screenshots.
Moderators may remove posts or members. Say who the moderator is (you).
If you want a fuller code of conduct, the Contributor Covenant has an interactive builder where you add your reporting contact and enforcement steps, and it comes in more than 40 translations. Link it from your rules post.
How do you keep a new community from becoming a ghost town?
Show up on a schedule, ask questions only members can answer, and make the first reply fast. Small communities often die quietly when the founder stops posting before anyone else feels it's their job.
Habits that work at small scale:
One weekly prompt, same day each week. "What are you working on this week?" or "Share one setup you changed recently." Predictable beats clever.
A monthly show-and-tell. Ask two members to explain one decision in their setup. Most people like being asked.
Same-day replies to first posts. Anyone posting for the first time should hear back within a day, from you or a member you've tagged.
Tag the person who knows. "Priya did something like this last month, maybe she can share?" turns you from answerer into connector.
Archive dead channels. A channel nobody used in a month makes the whole place look emptier.
Keep product updates to once or twice a month. A feed of release notes teaches people to mute it.
How much founder time does a small community take?
Plan on about two hours a week for the first three months, then less if members start answering each other. If you can't give it that time, don't start yet.
Most weekdays, 15 minutes: read new posts, reply to first-timers, tag helpers.
Weekly, 30 minutes: post the prompt, turn one emailed question into a public thread, clear spam.
Every two weeks, 20 minutes: invite the next few members.
Monthly, 30 minutes: review the numbers in the measurement table below.
These are planning estimates, not measurements. Track your own time for a month and adjust.
How do you handle feature requests and complaints in public?
Give requests one home, answer each with an honest status, and don't let the loudest member set the roadmap.
One ideas channel or category. One idea per thread, describing the problem, not the feature.
Four honest statuses. Planned, thinking about it, not now (with a reason), or won't do. A reason beats silence.
Log requests where you decide. Copy each request into the same sheet you use for support patterns, so the community is one input, not a separate roadmap. The IndieHunt guide on turning support tickets into product priorities has a scoring sheet that works for community requests too.
Complaints get a public first reply. Acknowledge it in the thread, move account details to email, then post back when it's fixed.
How do you moderate when it's just you?
Use the platform's built-in filters, require verified accounts, and remove spam the same day.
Turn on the safety basics. On Discord, the verified-email requirement and media filter come with Community mode. The Forum Channels FAQ also points to AutoMod for detecting and removing problem content automatically, and slow mode for limiting post volume.
Warn about DM scams in #start-here. "We'll never DM you asking for payment or passwords" helps people spot scam messages.
Remove, don't argue. Delete spam and ban the account. For a real conflict, one calm public note plus a private message is enough.
Add a helper later. After a couple of months, ask one or two of your most helpful members if they'd like moderator rights.
How do you know if your community is working?
Watch whether members talk to each other and whether members stay customers, not the member count. A community of 40 where 15 post every month beats 600 silent names.
Measure | How to get it | What good looks like at small scale |
|---|---|---|
Active posters in the last 30 days | Platform insights or a manual count | Steady or rising month over month |
Questions answered by a member, not you | Count the last 20 questions | Rising over the first three months |
Time to first reply on new posts | Spot-check ten posts a month | Under a day |
Members who are still customers after 90 days | Match member emails to your billing list | Compare with non-members, but don't assume the community caused the gap |
Ideas and stories you got from it | A running note | At least a few useful ones a month |
Be careful with the retention row. Your most engaged customers are the ones who join, so members will look better even if the community did nothing. Treat it as a hint and lean on the first two rows.
When should you shut a community down?
Shut it down, or merge it into something smaller, if after about three months of steady effort members still don't post without being prompted. An empty space linked from your site does more harm than none.
Announce it two to four weeks ahead and say where people can reach you instead.
Keep the useful threads. Export the best answers and turn them into help articles or a FAQ page. On Slack's free plan, do this early, since history past 90 days is hidden and data over a year old is deleted.
Thank the regulars personally. They're still your best customers.
Write down why. Wrong platform, wrong job, or not enough of your time. That note makes a second attempt better.
A 14-day plan to launch a small customer community
Day 1: Write down the one job and your weekly time budget. If you can't commit two hours a week, stop here.
Day 2: Pick the platform with the table above. Set up five channels or categories at most.
Day 3: Write #start-here (purpose, rules, support email, DM-scam warning) and turn on safety settings.
Days 4 to 5: Seed five or six threads from real customer questions, anonymized and with permission.
Day 6: List 15 to 30 customers to invite and write a personal line for each.
Days 7 to 8: Send the first ten invites. Reply to every introduction the same day.
Day 9: Post the first weekly prompt.
Days 10 to 11: Send the rest of the invites. Tag members into threads where they can help.
Days 12 to 13: Turn one emailed question into a public thread. Count active posters and member answers.
Day 14: Decide what to keep, what to drop and who to invite next. Put the next 12 weekly prompts in your calendar.
What mistakes kill small communities?
Launching to everyone at once. A big public launch into an empty room makes the silence very visible.
Treating it as free support. When every thread is a bug report, members tend to drift away and real support problems get missed.
Picking a platform your customers don't use. Asking accountants to install Discord for your product is a big ask.
FAQ
Should a customer community be free or paid-only?
For most indie SaaS products, make it free for paying customers and invite-only at first. A paid community is a separate product with its own expectations, content and support load. Start one only if teaching or connecting people is part of what you sell.
Can a community replace customer support?
No. Members can answer how-to questions, but billing, bugs and account access need a private channel with a clear response promise. Keep the support email in your rules and point people to it.
Will a community help my SEO?
Only if the content is public. Chat on Discord or Slack sits behind a login. Public forum threads, like a public Discourse forum or GitHub Discussions on a public repository, can be read without joining. Even then, write for members first.
A small community that does one job well can become the place your best customers learn from each other. Start with 20 people, show up on a schedule, and judge it by conversations, not headcount. And when you're ready to put your product in front of more indie makers, you can launch it on IndieHunt.
