1. Idea and validation
  2. Waitlist
  3. Private beta
  4. Launch
  5. First 100 users
  6. First 1,000 users
Communities

Recruit beta testers in niche communities

Post in the communities your users belong to, describe the problem plainly, and ask for a small number of testers.

What's required15–20 minutes a day for two weeks of participation, then an hour per post and replies.
Accounts
Accounts on 2–3 communities where your users already talk: subreddits, Discord or Slack groups, forums.
Assets
A working beta, a signup or invite link, one screenshot or 30-second clip, a short form for feedback.
Time
15–20 minutes a day for two weeks of participation, then an hour per post and replies.
Cost
Free.
Prerequisites
A beta that works end to end, even if rough, and a way to hand out access.

What to do

  1. Pick 2–3 communities where your users already ask questions. A small subreddit, Discord or Slack group where people discuss your exact problem beats a huge general one. If you do not know where they are, start with finding where your users talk.
  2. Read the rules before you do anything. On Reddit, check the sidebar, the wiki and pinned posts; on Discord and Slack, read #rules or #welcome. Look for self-promotion limits, “feedback Friday” or weekly promo threads, and minimum karma or account age. Many communities remove posts from new accounts automatically.
  3. Participate for two weeks before you ask for anything. Answer 1–3 questions a day with real help, no links. This builds karma and a post history, and moderators and members recognize your name. See answering threads for how to do it well.
  4. Ask the moderators first. Send a short message: “I’m building X for people who Y. I’ve been active here for a couple of weeks. Would it be OK to post once asking for 10 beta testers? Happy to follow any format you prefer.” A yes protects your post from removal, and sometimes mods pin it.
  5. Use the channels built for this. Many communities have a place where asking is welcome:
    • weekly “feedback wanted”, “show-off Saturday” or “self-promotion” threads on subreddits,
    • #introductions, #show-and-tell or #projects channels on Discord and Slack,
    • subreddits made for testers, such as r/alphaandbetausers or r/TestMyApp, as a backup.
  6. Write the post about the problem, not the product. Start with the problem in one or two sentences, say who it is for, show one screenshot, and ask for a specific small number: “Looking for 10 people who do X weekly”. A small number makes it feel exclusive and tells people you will actually talk to them.
  7. Offer something that costs you little. Free lifetime access, a “founding member” badge, or a big permanent discount for the first testers. Say it plainly and keep the promise.
  8. Handle signups by DM, one person at a time. Ask each person one question about their situation before sending the invite. It filters out tourists and gives you context for the onboarding call.
  9. Report back in the same community. After two or three weeks, post what you changed based on their feedback. It thanks testers in public and earns you a second post without looking like spam.

If you have no karma or history

A new account posting a link on day one will usually be removed or ignored. Build a small footprint first:

  • Week 1: join the communities, read the top posts of the last month, and leave 2–3 helpful comments a day. On Discord and Slack, post in the intro channel: “Hi, I’m [name], I’m building [thing] for [who]. Here to learn how you all handle [problem].”
  • Week 2: keep answering. Start one discussion post with no link, asking how people deal with the problem today. The replies tell you who to invite later.
  • Week 3: message the mods, then post your tester request in the allowed place. DM the people who replied to your discussion post, since they already told you they have the problem.

Template for the tester post:

Looking for 10 [role]s to test a tool for [problem]

I’ve been [doing X] for [time] and kept running into [problem]. I built a small tool that [does one thing]. It’s rough but it works.

Looking for 10 people who [specific situation] to try it for two weeks. You get free lifetime access; I get honest feedback. Comment or DM me and I’ll send an invite.

Screenshot: [link]

Why it works

Communities are full of people who already have the problem and like trying new things. Two weeks of helping first makes you a member instead of a stranger with a link, so people read your post with good will. A small, specific ask signals that you will pay attention to each tester, which is what makes people say yes.

How it gets users

A good post in a well-matched community usually brings somewhere between a few and a few dozen signups, mostly in the first 24–48 hours. Many will not finish setup; expect a handful of active testers per post. Two or three communities over a month is often enough to get 10–30 real beta users, which is plenty at this stage.

Common mistakes

  • Posting a link on day one from a fresh account.
  • Posting the same text to ten communities in one afternoon. Mods talk, and it looks like spam.
  • Ignoring the rules because “this is different”.
  • Asking for “feedback” in general instead of a specific number of testers with a specific situation.
  • Promising lifetime access or perks and then quietly dropping them.
  • Disappearing after the post instead of answering every comment.

Next steps

This guide is connected to these guides on the map. Numbered ones come next; faded ones come before it.

  1. 103 Private beta · Direct outreachOnboard every beta user on a callSet up the first users yourself on a short call and note where they get stuck.
  2. 204 Launch · CommunitiesShare your launch on RedditPost in the few subreddits that allow project posts, follow each one’s rules, and write as a member rather than an advertiser.
  3. 305 First 100 users · CommunitiesAnswer questions where they are askedSearch communities and Q&A sites for people describing the problem, and give a useful answer that mentions the product only where it helps.