How to get users for your app (the first 100, without ads)
Your app is live and nobody is using it. Here's how to find the first users one by one, where they actually talk, and what our own data says about where those people are.
Your app works. You shared it with friends, posted the link once, and the sign-up counter barely moved. That's normal. Nobody finds a new app by chance. The first users come because you went and found them, one by one.
This guide is about those first 100 users. It's not about ads or app store tricks. It's a method you can start today, for free, whether you built a mobile app, a web app or a browser extension.
Users and customers aren't the same thing
A user tries your app. A customer pays for it. For a free or freemium app, the first goal is people who use it and come back. If you sell a paid product to businesses, read how to get your first customers for a SaaS instead, because the steps after the first conversation are different.
Either way, the first step is the same: know exactly who you're looking for.
Step 1: write one sentence about who it's for
Fill in this sentence before you look for anyone:
"My app is for [a specific person] who [has this problem] and today [does this instead]."
_Example:_ "My app is for runners training for their first marathon who lose track of their plan and today use a spreadsheet or a printed PDF."
"Everyone who runs" is not a target. "First-time marathon runners with a spreadsheet" is. You can search for them, you know what they say, and you know what they use today.
Then write the words they would type when they have the problem: "marathon training plan app", "how do you track your training", "my plan spreadsheet is a mess". These are your search words.
Step 2: find people talking about the problem this week
The best first users are people who just wrote, in public, that they have your problem. They're already thinking about it, so a message about it doesn't feel random.
Search your words in the places your person reads:
- Communities about the topic, not about apps. Runners talk in running forums, parents in parenting groups, small shop owners in seller communities. They're rarely in app-maker communities.
- Reddit: search your words and sort by New. Read each subreddit's rules first. We wrote a full guide: how to find customers on Reddit.
- Bluesky, Mastodon and LinkedIn: search your problem words and look at the latest posts, not the top ones.
- Forums and Q&A sites in your niche: use their search and sort by date.
Keep only recent posts, ideally less than 7 days old. An older question has usually been answered already.
Step 3: reply to help, then offer the app
When you find someone, don't drop a download link. Start by helping:
- one sentence that shows you read what they wrote;
- one useful idea, even if they never install anything;
- one easy question.
If they answer, tell them you built something for exactly this and ask if they want to try it. One mention, once. People who say yes here are your best first users, because they said yes to a solution to their own problem, not to a pitch.
This feels slow. It is slow. But 10 people who chose to try your app teach you more than 1,000 visitors who bounced. For message templates, see the outreach message that gets replies.
Step 4: use your beta to recruit, not just to test
If you build a mobile app, the stores give you a reason to talk to people before launch.
- iOS: with TestFlight, Apple lets you invite up to 10,000 external testers. Your first build must be approved by App Review for TestFlight before external testers can join.
- Android: Google Play requires developers with personal accounts created after November 13, 2023 to run a closed test with at least 12 testers, opted in continuously for at least 14 days, before they can apply for production access.
That Android rule means you need 12 real people anyway. Don't fill it with friends who will never open the app. Use Steps 2 and 3 to find 12 people who have the problem. They'll give you honest feedback, and some of them will stay after launch.
Ask each tester one question after a few days: "What almost made you stop using it?" The answer tells you what to fix first.
What our data says about where people are
FounderPulse searches public posts to find people who just described a problem. On November 21, 2026, we read in our database where the people saved by FounderPulse accounts in the previous 30 days came from: 217 people, found on 45 different sites. LinkedIn was the biggest source (100 people, 46%), then Bluesky (40, 18%) and dev.to (20, 9%). The rest were spread across dozens of smaller sites: forums, Mastodon servers, Q&A sites and blogs.
What this means for you: the people who need your app aren't all in one place. Most founders post on two or three big sites and stop there. A good part of the people asking for help were on smaller sites that most people never search. Look beyond the obvious, and keep searching where your specific person spends time.
Mistakes that keep apps at zero users
- Launching once and waiting. A launch post brings one day of visits. Users come from repeated, small actions every day.
- Posting in app-maker communities. Other makers are nice, but most of them aren't your users.
- Talking about features. People don't care about your stack or your animations. They care whether their problem goes away.
- Asking for reviews too early. Get people using the app first. Store reviews from strangers who never used it break store rules and say nothing.
- Not tracking who came from where. Add a simple source tag to each link you share (`?from=reddit`, `?from=forum`) so you know which place actually brings users.
A 20-minute daily routine
- Search your words in your 3 places (5 minutes).
- Keep the 3 to 5 posts from people who have the problem now (5 minutes).
- Write one helpful reply to each (8 minutes).
- Note who you talked to and who tried the app (2 minutes).
After two weeks, look at your notes. Keep the places where people answered and tried the app. Drop the rest.
Where FounderPulse fits
Step 2 is the slow part: running the same searches every day and reading posts to find the few people who have your problem right now. FounderPulse does that part. You describe what you've built, and it searches recent public posts on Bluesky, Mastodon, Hacker News, Discourse forums and the open web. It checks the date of each post, drops ads and job offers, and tells you in one sentence why each person fits. For each one, it drafts a first reply that helps before it mentions your app. On the Pro plan, it can run your search each weekday morning.
What it doesn't do: it doesn't buy users, run ads or post for you. You read each draft, change what you want, and send it yourself. Plans and limits are on the pricing page.
You can try it free without signing up: paste your website and see three people to contact today.
Want your first customers found for you?
Paste your website or describe what you sell: FounderPulse finds real people who need it, writes the message for each, then gives you one action a day to sign them.
See my 3 people to contactFree try · no signup · no card