Finding beta users on Reddit and Indie Hackers
Beta users are not clients. Where early-stage founders find people willing to try an unfinished product — and how to ask without sounding like an ad.
Beta users are not clients
The first honest distinction in this post: a beta user is not a client. A client pays for a solved problem. A beta user agrees to try an unfinished product and tell you what breaks. Confusing the two ruins both relationships — you pitch a beta user like a buyer and they leave, or you treat a buyer like a tester and they never pay. This post is about finding the first group, and only the first group.
Where beta users actually hang out
Early-stage founders find beta users where people build in public and ask for help in the open. Three rooms are worth your time. r/Startup_Ideas is where founders post ideas and ask whether anything is worth building; the people who engage seriously there are often willing to try an early version. r/StartupSoloFounder is where solo builders compare notes on building alone, including what tools they are testing. r/indiehackers is the Reddit side of the Indie Hackers world, where bootstrappers talk about launches, pricing, and getting first users.
Indie Hackers itself, the platform, is the fourth place: founders post launches and milestones, and the comments are full of people who like trying new things early. Read the rules of each room before posting anything. Every one of them punishes disguised ads, and a beta request that reads like a launch announcement will be removed faster than a bad pitch.
How to ask without sounding like an ad
The ask that works is specific and small. Say what the product does in one sentence, who it is for, what stage it is at, and exactly what you want from the tester: try it for a week, tell you where it confuses you, or compare it with what you use now. Offer the unfinished state as the point, not a secret: "It is rough, the onboarding is ugly, and I want to know where you get stuck." People volunteer for honesty like that. They run from "revolutionary" and "game-changing."
Ask in the open, in the thread, rather than by cold direct message. A public ask lets others see the answers too, and it lets the room judge whether you belong there. If someone shows interest, move to a conversation about their problem before sending any link. The link is the last step, not the first.
What to do with the people who say yes
A beta user who says yes needs a job, not a login. Give them one task: get through onboarding, try one workflow, or break one feature. Then ask three questions: where did you get stuck, what did you expect that did not happen, and would you pay for this when it works? The third question is the one that separates a beta user from a future client, and it is worth asking early, kindly, and only once.
Keep the group small enough to talk to individually. A hundred silent signups teach you nothing; ten people who reply teach you everything.
The short version
Beta users live where founders build in public: r/Startup_Ideas, r/StartupSoloFounder, r/indiehackers, and Indie Hackers itself. Ask small, in public, with the rough edges admitted, and give each tester one job plus three questions. If you want the same approach for finding buyers rather than testers, Avrel's community directory tracks the rooms where buyers ask who to hire, scored with source evidence.
Related content
More from the blog
What to say when someone asks 'how much do you charge'
What to say when someone asks 'how much do you charge': anchor on the outcome, give an honest range, and move the exact figure to a conversation.
Read articleHow to score a Reddit lead in 60 seconds
Five checks before you reply: buyer or browser, real budget, timing now, your service, thread alive. Sixty seconds that saves your week.
Read articleA weekly community-led routine for agencies
A practical week plan for a small agency: which platforms to scan, how to split threads across the team, and a Friday review of the week's scored leads.
Read article