How to get your first 10 users for your AI-built app (without spending a dime on ads)
You built your app without writing code. Getting your first 10 real users is harder than building — but it doesn't require a marketing budget. Here's what actually works.
Building your app was the part you worried about. Then you finished it, shared the link with three people, and discovered that the actual hard thing is getting anyone to care.
You can build an app without coding in a weekend. Getting strangers to use it — and come back — is a different problem entirely. Most first-time builders expect users to appear once the thing exists. They don’t. But the first 10 are findable, if you look in the right places.
Here’s what actually works, from people who’ve done it.
Start smaller than you think you need to
The instinct after finishing an app is to announce it everywhere at once: Product Hunt, Reddit, Twitter, a newsletter, friends-of-friends. That instinct is wrong, and it’s wrong for a specific reason: you don’t yet know if your app works for strangers.
It works for you. You built it. You know where to click, you know what the broken corners are, you know what it’s supposed to do. A stranger who finds your app through Product Hunt and is confused in 30 seconds will just close the tab. They won’t tell you why. You’ll get zero users and zero signal.
The move is to start with 2 or 3 people you can actually talk to while they use it. Not friends who’ll be polite — people who have the actual problem your app solves. Watch them use it. Watch where they get confused. Listen to the thing they’re trying to do when they hit the broken part. Fix it. Then repeat.
By the time you’ve done that with 3 or 4 people, you’ll know which part of your app’s description is wrong, which feature is missing, and which workflow that seemed obvious to you is invisible to everyone else. You couldn’t have known those things without a real person who wasn’t you.
Where to find the first 3
Not your family. Not your friends unless they genuinely have the problem. The right people are in communities built around the problem your app solves.
A few places worth checking:
Reddit. Find the subreddit where your target user hangs out and read the posts from the last month. Look for threads where people are complaining about the thing your app fixes, or asking for recommendations for tools that do what your app does. Message those people directly. Not with a pitch — with a question: “I saw your post about [problem]. I’ve been working on something related. Would you be willing to spend 20 minutes looking at what I’ve built and telling me what you think?”
Most people won’t respond. Some will. The ones who do are exactly who you want.
Discord and Slack communities. Most niches have active community Discords — indie hackers, specific industries, hobbyist groups, professional groups. The same approach works: find people talking about the problem, introduce yourself as someone building a solution, and ask for 20 minutes.
Your existing network, filtered correctly. You probably know someone who has the problem, or knows someone who does. Think about who you know, then think about who they know. A direct introduction from a mutual connection converts much better than a cold message.
The goal at this stage isn’t 10 users. It’s 3 honest conversations with people who actually need what you built.
Turn those conversations into referrals
Here’s the thing that most first-time builders miss: if someone spends 20 minutes trying your app and found it useful, they know other people who have the same problem. They’re the best possible distribution channel you have, and asking them directly is not awkward — it’s expected.
At the end of every early conversation, ask: “Is there anyone else you think would find this useful? I’m looking for a few more people to test it before I launch more broadly.”
Some will say no. Some will text you a name on the spot. One warm referral from someone who just used your app is worth more than 50 clicks from a launch post, because that person will actually try it instead of glancing and moving on.
Keep a simple list — a notes app, a spreadsheet, whatever — of who you’ve talked to and who they referred. Not because you need to track it, but because it forces you to actually follow up. Referrals you don’t follow up on don’t convert.
The launch post, timed correctly
Once you’ve had 5 or 6 real conversations, fixed the things that confused people, and have at least a handful of people who’ve come back to use the app a second time — then it’s time to write a launch post.
The format that works is straightforward: what the app does, who it’s for, what problem it solves, and how to get started. Three paragraphs. A screenshot or short recording of the app actually running. A link.
Where to post depends on your audience. A few options:
- The communities where you found your first users — many of these allow “I built a thing” posts, especially if you’ve been a genuine participant first.
- Hacker News “Show HN” — straightforward, no pitching, just “here’s what I built.” The feedback is unfiltered and sometimes harsh, but it’s real.
- Twitter/X, if you have even a small following. A thread that explains the problem and shows the solution outperforms a simple link post.
- Product Hunt — best when you have some users already, because early votes and comments matter enormously for visibility.
The most important thing about the launch post: do not do it before you’ve had real users. A launch post that lands when your app is still rough is wasted. You get one first impression. Use it after you’ve fixed the obvious problems.
What to do with the users who come from the launch
After a launch post, you’ll see a spike of signups and then — if you don’t do anything — silence. Most of those people will create accounts, poke around, and disappear. That’s normal. Your job in the 48 hours after a launch is to talk to as many of them as possible.
Message every new signup personally: “Hey, I saw you just signed up for [app name]. I’m the person who built it. What were you hoping to use it for?” Not a form. Not an automated email. A personal message.
Most won’t reply. Some will. And the ones who do will tell you things you couldn’t have figured out on your own — what they were trying to do when they signed up, what they expected the app to do, what stopped them. That’s the signal you use to decide what to fix next.
The first 10 users don’t come from a perfect launch strategy. They come from genuinely engaging with every single person who shows up, treating each one as someone worth a real conversation, and asking them to bring a friend. It’s slow and it doesn’t scale — and that’s exactly why it works when you’re starting from zero.
The thing nobody tells you about the first 10
Getting to 10 users feels like a milestone you reach once and then move past. It isn’t. The first 10 users are the people you’ll learn the most from, and the learning compounds. One person from your first 3 conversations tells you the real problem. A second person shows you a use case you didn’t design for. A third becomes your most vocal advocate.
You cannot buy that. You can only earn it by showing up, asking real questions, and building what they’re actually asking for rather than what you thought they wanted.
The app you built in a weekend is the opening offer. The conversations that follow are how you figure out what you actually built.
If you’ve shipped your first AI-built app and are trying to get people to use it — try the 2-3 honest conversations approach before you launch anywhere public. The difference between “I launched and got no users” and “I launched and got traction” is almost always that the second person talked to real users first.