How to get your first 100 users for a vibe-coded app

You built the thing. It works. And now it's sitting there with a user count of one, which is you, and the quiet realisation that building was somehow the easy part. This is the most common place for a vibe-coded app to die, and it's completely avoidable.

Here's the short answer: your first 100 users come from going where they already are and showing them something useful, two or three places, done properly. Not a launch-everywhere blast. Not waiting to be discovered. Let me give you the actual playbook.

Why "build it and they will come" fails

It fails because there are more good small apps than there has ever been, and AI made that worse overnight. Nobody is searching for your app, because they don't know it exists. Discovery is not automatic, and it never was. The job in front of you isn't building more, it's putting what you built in front of the right hundred people.

So stop polishing. The app is good enough to show. The work now is distribution, and it's a craft you can learn in an afternoon.

Go where your users already gather

The instinct is to post everywhere once. Resist it. One post each on ten platforms gets you ten polite nothings. Three thoughtful posts in one community where your users actually live gets you real people who actually try it.

Make a short list of where the people who'd love this already hang out:

• A niche subreddit. Not r/apps, the specific one. Trail runners, indie game devs, note-taking nerds, whatever your app serves. Reddit drives a genuinely large share of indie first-users when you respect the room.
• A relevant Discord or Slack. Active communities have a "what are you building" or "show off" channel. That's an invitation.
• Show HN, if your app has any developer or technical angle. Hacker News rewards "I built this, here's how, here's what didn't work."
• Product Hunt, when you've got a polished demo and a clear one-liner.

Pick two or three. Then actually be a member, not a drive-by link-dropper. The communities that convert are the ones you'd have joined anyway.

Lead with a story, not a pitch

This is where most posts die. "Check out my new app" is an advert, and people scroll past adverts. What travels is a story with a useful thing attached.

The format that works, almost everywhere:

I kept hitting [specific problem]. I couldn't find a tool that did [specific thing], so I built one. Here's what I learned, and here's the app if it's useful to you.

That's honest, it's human, and it gives people a reason to care before you ask for anything. Attach a working demo or a short clip, because the demo is the real pitch. On Reddit and HN especially, the story-first post earns goodwill that a launch announcement never will.

And read the room's rules first. Reddit subs have self-promotion limits, often under ten percent of your activity, and karma minimums. Breaking those gets you removed and learns you nothing. Spend a little time being useful in the community before you post your thing.

Collect proof as you go

Getting someone to your page is half the job. The other half is them trusting it enough to actually use it, and a brand-new app with zero signal is a risk nobody wants to take first.

So build the proof on purpose. Ask your first handful of users for one honest sentence about what worked. Put that somewhere visible. A page with eight real reviews converts the ninth visitor far better than a slick page with none.

This is exactly why Shipyard exists, so the proof has a home. You post the project, real members leave honest reviews, and that becomes the thing you point newcomers at. Reach gets people to the door; proof gets them through it. If you take one idea from this, take that one, and start asking for it from user number one.

Make it a habit, not an event

The biggest mistake is treating this as a single launch day. You post everywhere, get a spike, the line goes flat, and you decide distribution "didn't work."

The builders who get to 100 and past it treat it as a steady drip. Ship a small improvement, say something about it. Hit a milestone, say something. Learn something from a user, write it up. None of those are launches, and all of them keep the thing alive. Twenty quiet weeks of showing up beats one loud day, every time.

That's the whole playbook. Two or three channels, a story instead of a pitch, proof from day one, and the patience to keep showing up. The app being good is assumed, you've handled that. The rest is just refusing to let it die quietly in a folder.

If you'd rather not grind every channel by hand, that's the bet Shipyard is built on: post once, get honest feedback, and let it distribute to the people who should see it. We're letting in the first 50 founding members now. If getting seen is your bottleneck, come and build with us.