The short answer
To find early users before your product is built, go to the places where your target problem is already being discussed, make a direct ask, and offer something in exchange for their time. Reddit threads, LinkedIn posts, niche Slack or Discord communities, and waitlist landing pages are the most reliable starting points. You do not need a product to recruit people who have the problem.
Most founders treat user recruitment as a post-launch task. That order is backwards. The conversations you have before building are the ones that tell you whether building is worth doing at all. If you cannot find ten people willing to spend 30 minutes talking about a problem, that is signal in itself.
This article covers specific channels and approaches for finding those first users. For the broader question of how to stress-test your idea end-to-end, see the pillar guide on validating a software idea before you build.
Why recruit users before the product exists
Early user conversations serve two purposes at once: they confirm the problem is real and common enough to be worth solving, and they surface the language your future customers actually use, which makes every subsequent marketing decision easier.
A user who signs up for your waitlist before launch is also more invested than one who stumbles across you six months later. They have skin in the game. That investment makes them more likely to give honest feedback rather than polite feedback.
Where to find early users
1. Communities where the problem lives
Every niche has gathering places: subreddits, Facebook groups, Slack workspaces, Discord servers, LinkedIn groups, or industry forums. The goal is not to post an ad. Search first. Find threads where people describe frustrations, workarounds, or questions that map to the problem you are solving.
Then post something honest: "I'm looking into building a tool for [specific problem]. Before I start, I want to talk to five people who deal with this regularly. 30-minute call, no pitch. Would anyone be up for it?"
Specificity matters. "I'm building a scheduling tool" gets ignored. "I'm looking to talk to freelance designers who invoice more than five clients a month" gets responses.
Channels worth checking by audience type:
| Audience | Where they gather |
|---|---|
| SaaS founders | r/SaaS, Indie Hackers, MicroConf Slack |
| Small business owners | Facebook groups by industry, local chamber forums |
| HR / ops professionals | LinkedIn groups, People Operations Slack |
| Developers | Hacker News, Dev.to, relevant Discord servers |
| Healthcare / legal niches | Specialty association forums, LinkedIn |
2. Your own network, used deliberately
Most founders either ignore their network entirely or send one vague mass message. Neither works.
Write a short, specific post on LinkedIn or Twitter describing the problem you are exploring, not the product you are building. Ask anyone who has faced that problem to comment or send you a message. Then send direct messages to ten people you know who fit the profile, individually, with a personal note.
The key phrase is "I'd like your advice" rather than "I want to show you something." People who would decline a demo will take an advice call.
3. A waitlist landing page
A one-page site with a clear problem statement and an email sign-up does two things: it gives you a place to send traffic, and it creates a small psychological commitment from people who sign up.
The page does not need to be polished. It needs to name the problem precisely, hint at the solution, and ask for an email. Tools like Carrd or a simple Notion page with a Typeform embed are enough.
Once it exists, you can share it in communities, run a small paid social test to see if strangers sign up, or include it in your LinkedIn post. A hundred sign-ups from people who do not know you is a meaningful signal.
4. Competitor review pages
People who leave detailed negative reviews on G2, Capterra, or Trustpilot for a competing product have just described your opportunity in public. Read those reviews carefully. Many reviewers link to their LinkedIn profiles or company websites. Some will respond to a brief, honest outreach message.
"I read your review of [product] and noticed you mentioned [specific problem]. I'm exploring building something that handles that differently. Would you be willing to share 20 minutes with me?" That framing shows you did your homework and makes the ask feel earned.
5. Cold outreach to the right-fit person
If your target user has a clear professional profile, you can find them on LinkedIn and send a short direct message. Three rules for cold outreach that gets replies:
- Be specific about why you chose them (their job title, a post they wrote, their industry)
- Ask for a conversation about the problem, not feedback on your idea
- Keep the message under 80 words
Expect a 5 to 15 percent reply rate. That means 100 messages yields 5 to 15 calls, which is more than enough to start.
6. In-person and meetup environments
Industry meetups, trade conferences, co-working spaces, and local business events put you in the same room as people who have the problem. The conversation is easier in person and the conversion to a follow-up call is higher than any digital channel.
Go to three events in the next month. Do not pitch. Ask questions. Collect contact details from people who describe the problem you are targeting.
What to offer in exchange for their time
Early users are giving you something valuable. Acknowledge that.
For a 30-minute discovery call, the offer can be simple: a summary of what you learn from all the conversations (people like knowing they contributed to something), early access when the product launches, or a discounted rate. You do not need to pay cash.
For structured beta testers who will test a working prototype later, more tangible offers make sense: free access for six months, a named credit, or input into the roadmap. The specifics matter less than making the exchange feel fair.
How many early users do you need
For problem validation conversations, ten to fifteen interviews is enough to surface recurring patterns. You will hear the same three or four frustrations repeatedly. That repetition is the signal.
For beta testing a working product, aim for twenty to fifty active testers. Fewer than that and you are relying too heavily on individual preferences. More than fifty at the pre-launch stage and the feedback volume becomes difficult to process without a system.
Common mistakes that kill early recruitment
Leading with the solution. Once you describe the product, people start evaluating it instead of sharing their actual experience. Save the product reveal for later in the conversation.
Targeting too broadly. "Small business owners" is not a target. "Yoga studio owners who manage their own scheduling" is. The narrower your initial target, the easier it is to find them and the more useful their feedback will be.
Giving up after ten messages. Early user recruitment requires repetition. One post in one community rarely does it. Expect to work five or six channels before momentum builds.
Asking friends who will say yes. Friends want to be supportive. Their feedback is kind but not representative. Target strangers who have the problem and no social reason to spare your feelings.
From users to product: what comes next
Once you have early users and a validated problem, the next decisions involve money. Understanding how development is typically scoped and priced will shape what you ask your early users to help you define. A breakdown of what goes into a development quote is worth reading before those conversations: what a software dev quote includes.
And when you get to the point of engaging a developer or development service, the pricing structure you choose affects your risk exposure significantly. Fixed price vs hourly contracts covers that decision in detail.