How to get your first users as a solo builder (without a launch strategy)

No team, no audience, no launch playbook. Here's how solo builders actually find their first real users — quietly and without burning out.

There's a moment most solo builders know well. The product works. It's not perfect, but it works. And then you sit there, refreshing the analytics dashboard, waiting for someone — anyone — to show up.

They don't.

Not because the product is bad. Not because you failed at some launch ritual. Just because shipping something and getting users are two completely different problems, and nobody really tells you that until you're already in it.

This is about the second problem.

Why "just launch on Product Hunt" doesn't work the way people say

Every indie forum has at least one thread that goes like this: "I launched on Product Hunt and got 300 upvotes and zero paying customers." The comments are always the same mix of sympathetic shrugs and tactical suggestions that mostly miss the point.

The issue isn't the platform. It's that a launch event is a single spike of attention aimed at a general audience that wasn't already looking for what you built. It can work. But for most solo builders without an existing audience, it's a coin flip dressed up as a strategy.

First users don't usually come from launches. They come from repeated, specific, low-pressure contact with people who already feel the problem you're solving.

Start with the problem, not the product

Before you mention your product to anyone, spend a week just talking about the problem.

Post on X about the frustration. Write a short blog post about why the existing tools don't quite cut it. Answer a Reddit or Indie Hackers thread where someone is venting about exactly the thing you're building for. Don't link to anything. Don't pitch. Just be genuinely useful and honest about what the problem feels like from the inside.

This does two things. It builds a small trail of signal that says this person understands this problem. And it finds you the people who are already nodding along — the ones most likely to actually try what you've built.

When you do eventually share your product, it lands differently. It lands as a solution from someone who gets it, not a cold product link from a stranger.

Find one place where your ICP already lives

You don't need to be everywhere. You need to be somewhere, consistently, where the right people already gather.

For most indie builders, that's one of: X (if your ICP follows other makers), a specific subreddit, a niche Discord or Slack, or even a small newsletter community. The platform matters less than the specificity.

The goal is not to broadcast. It's to become a familiar name to a small group of people who have the exact problem your product solves. Familiar enough that when you say "I built something for this," they already have enough context to trust it.

This takes longer than a launch. It also works more reliably.

The five-person rule

Before you optimize anything — the landing page, the onboarding, the pricing — try to get five real people using it. Not beta testers you recruited through a waiting list form. Five people who found it through something you wrote or said, tried it, and came back.

Five is small enough to be achievable without a marketing budget. It's also large enough to tell you something true about whether the core problem-solution fit is real.

Pay attention to what they do, not just what they say. What do they actually use? Where do they stop? What do they come back for? That information is worth more than a hundred signups who never opened the app.

Don't optimize for visibility — optimize for resonance

Most early distribution advice is about reach. Post more. Be consistent. Use the algorithm.

But for solo builders in the early stage, reach is the wrong metric. Resonance is what matters. One person who reads something you wrote and thinks "this is exactly what I've been trying to say" is worth more than a hundred impressions from people who scroll past.

Resonance comes from specificity. Writing about your exact problem, your exact user, your exact tradeoff — not the generic version of it. The more precisely you describe the thing, the more strongly the right person feels it.

This is also, not coincidentally, the kind of writing that compounds. Specific, honest, process-transparent content keeps finding new readers long after you wrote it. It builds trust slowly, but it builds it durably.

The unsexy truth

Getting your first users as a solo builder is mostly just about being useful in public, consistently, over a longer period than feels comfortable.

No growth hack replaces that. No launch event shortcircuits it. You're building a small body of signal that says: I understand this problem, I'm working on it seriously, and here's what I've learned.

The people who need what you're building will find that signal. Some of them will try what you made. A few of them will stick around.

That's how it starts.