How to Get Your First 100 Users for a Vibe-Coded App

You built the app. It works. You shipped it. And then the thing nobody warns you about happened: nothing. No signups, no traffic, no users. Just you, refreshing an analytics dashboard that says zero.

This is the wall every vibe coder hits, and it is harder than anything that came before it. Building got easy. Shipping got easy. Getting people to actually use the thing you built is still exactly as hard as it has always been, and AI did nothing to change that.

This article is the honest playbook for going from zero to your first 100 users. Not 100,000. Not a viral launch. The first 100 real people who use what you made. That number matters more than any number after it, because the first 100 is where you find out whether you built something people want, or just something you wanted to build.

Why the first 100 is the only number that matters right now

It is tempting to think about growth in big numbers. A million users. A viral moment. A launch that blows up. Forget all of that. At this stage, those numbers are a distraction, and chasing them will make you do the wrong things.

The first 100 users do one job: they tell you the truth. They tell you whether anyone wants this, whether they understand it, whether they come back, and what they actually use it for versus what you thought they would use it for. You cannot learn any of that from zero users, and you do not need 10,000 users to learn it. A hundred is enough signal to know if you have something real.

Here is the part most people get backwards. The first 100 users do not come from marketing. They come from you, manually, one conversation at a time. This feels wrong to technical builders who want a scalable system. There is no scalable system for your first 100 users. There is only doing things that do not scale, which is exactly why most people skip this step and then wonder why their app has no users.

Before you chase a single user: the one-sentence test

Stop and answer this in one sentence: who is this for, and what does it do for them?

If you cannot say it cleanly, no amount of distribution will help, because you will not know who to talk to or what to say to them. "It is a productivity app" is not an answer. "It helps freelance designers send invoices without opening a spreadsheet" is an answer. The second one tells you exactly who to find and exactly what to say when you find them.

Most vibe-coded apps that fail to get users do not fail because of distribution. They fail because the builder cannot describe who it is for. They built a general tool for everyone, which is a tool for no one. The apps that get their first 100 users fast are almost always the ones with a painfully specific answer to this question.

If your answer is fuzzy, fix that before you do anything else in this article. Everything below assumes you know exactly who you are looking for.

The mindset shift: go to them, do not wait for them

There are two ways to get users. You can build something and wait for people to find it, or you can go find the people. For your first 100, only the second one works.

Waiting for people to find you is a strategy that works when you already have an audience, a budget, or existing momentum. You have none of those yet. So the entire game at this stage is going to where your users already are and putting your app in front of them, one at a time, in a way that does not feel like spam.

This is uncomfortable for most builders. It feels like begging. It is not. If you built something that genuinely helps a specific person, telling that person about it is a favor, not an imposition. The discomfort you feel is just the gap between being a builder and being someone who talks to users, and crossing that gap is the actual skill that separates apps with users from apps without them.

Where your first 100 users actually come from

Here are the channels that work for the first 100, in rough order of how fast they pay off. You do not need all of them. You need two or three that fit where your specific users hang out.

1. The communities your users already live in

Every audience has gathering places. Designers are on specific subreddits and Discords. Founders are on Indie Hackers and X. Developers are in particular GitHub discussions and Slack groups. Your users are somewhere specific right now, talking to each other.

Find those places. Join them. Do not post your link on day one. Spend a week or two being genuinely useful, answering questions, sharing what you know. Then, when someone describes the exact problem your app solves, you mention it. Not as a pitch, as an answer to their actual question.

This is slow and it does not scale and it is the single most reliable source of your first 100 users. One genuinely helpful comment in the right community, at the right moment, brings better users than a thousand impressions of an ad. The people you reach this way came with intent, which means they are far more likely to stick around than someone who clicked a link out of idle curiosity.

The mistake people make here is treating communities as billboards. They join, drop a link, and leave. It does not work, it gets you banned, and it burns the channel. The builders who win in communities are the ones who were genuinely part of the community before they ever mentioned their product.

2. Talking to people one at a time

This is the channel nobody wants to hear about, and it is the most powerful one for your first 50 users especially.

Make a list of people who have the problem your app solves. People you know, people in your communities, people you find on X or LinkedIn talking about the problem. Message them directly. Not a mass blast, a real message: "I built a thing that does X because I kept running into this problem, you mentioned the same thing the other day, want to try it?"

This feels like it cannot possibly scale to 100 users, and it cannot. But it does not need to. Twenty of these conversations, done well, get you twenty engaged users who tell you exactly what is working and what is not. Those twenty become your foundation. Some of them tell their friends. The early traction you build by hand is what makes the scalable channels work later.

Founders of companies you have heard of did this. They messaged people one at a time until they had enough users to stop. There is no shortcut around it, and the ones who embrace it instead of resisting it get to 100 faster.

3. Launch platforms, used correctly

Product Hunt, Hacker News (Show HN), and the various launch directories can deliver a burst of users in a day. But they are spiky, not sustainable, and they only work if you have done the groundwork first.

A launch with no existing supporters falls flat. A launch where you have spent two weeks building relationships in communities, where twenty people already use and like your app, where a handful of friends are ready to upvote and comment in the first hour, that launch has a chance. The platforms reward early momentum, and early momentum comes from the manual work you did before launch day.

Treat a launch as an amplifier of traction you already have, not as a way to create traction from nothing. Launch once you have your first 20 to 30 users, not before. And do not blow your one good launch on an empty app.

4. Content that answers what your users search

This is slower than the others, taking weeks to months to pay off, but it compounds in a way nothing else does. If your users search for their problem, an article that genuinely answers it brings you users for years.

Write the piece you wish existed when you had the problem your app solves. Not a sales pitch, a genuinely useful guide. People searching for that problem find your article, the article helps them, and a fraction of them try your app. This is the channel that keeps working long after you stop actively pushing it, and increasingly it is how AI tools like ChatGPT and Perplexity discover and recommend products too.

The catch is patience. Content published today does not bring users tomorrow. It brings users in three months and then keeps bringing them. Start it now, expect nothing for a while, and let it compound underneath everything else you do.

5. The people already mentioning you

Once you have any users at all, some of them will mention you, in a tweet, a comment, a Discord message. These mentions are gold and most builders ignore them.

Every time someone mentions your app, show up. Thank them, answer their questions, ask what they are building. This does two things: it makes that person more likely to keep talking about you, and it shows everyone watching that there is a real human behind the product who cares. Word of mouth is the strongest channel there is, and it starts with you noticing and nurturing the first few people who spread the word on their own.

The thing that matters more than any channel

You can do everything above perfectly and still fail to keep your first 100 users, because all of these channels are amplifiers. They bring people to the door. What happens after they walk in is what decides whether you have 100 users or 100 signups who never came back.

The first-run experience is the whole game. When a new user opens your app for the first time, how fast do they get to the moment where it actually helps them? If that moment is buried behind a confusing signup, an empty dashboard, and a setup process, you will lose them before they ever see the value. Every channel leaks if the first run is rough.

Spend as much energy on the first five minutes a user spends in your app as you spend on getting them there. Watch real people use it. Sit next to someone, or screen-share, and say nothing while they try to figure it out. The places they get stuck are the places you are losing users, and you cannot see those places from inside your own head as the person who built it.

This is also where the unglamorous backend work quietly decides your fate. The app needs to actually work when a real person uses it. Logins that hold, data that saves, pages that load, an experience that does not break the moment someone does something you did not expect. None of that is visible in a demo, and all of it is visible to your first 100 users. A backend that handles real people reliably is the difference between users who stay and users who hit a bug on day one and never return. This is the part of building that AI tools handle well when the foundation is solid, which is exactly why getting that foundation right before you start chasing users is worth the time.

A realistic 30-day plan to your first 100

Here is what this actually looks like, week by week. Adjust to your situation, but the shape holds.

Week 1: Foundation and listening. Nail your one-sentence description. Find the three communities where your users live and join them. Do not post about your app. Just read, learn how people talk about the problem, and start being helpful. Meanwhile, make sure your app actually works for a stranger - get one friend who is not you to use it cold and watch where they struggle.

Week 2: The manual outreach. Make a list of 30 people who have the problem your app solves. Message them one at a time, personally. Aim to get 10 to 20 of them actually using it. Talk to every single one. Ask what they expected, what confused them, whether they would use it again. Fix the most common point of confusion before week three.

Week 3: Communities and content. Now that you have a handful of real users and have fixed the worst friction, start contributing your app as an answer in the communities you joined - only when it genuinely fits a question someone asked. Publish one genuinely useful article about the problem your app solves. Keep talking to every new user.

Week 4: Amplify. If you have 20 to 40 engaged users who like the app, now consider a launch on Product Hunt or Show HN, with your early users ready to support it. Keep doing the manual outreach in parallel - it still works. Respond to every mention. By the end of the month, between manual outreach, community presence, a launch, and early word of mouth, 100 is within reach.

It will not be clean. Some weeks will bring ten users and some will bring two. The point is not the precise number on day 30. The point is that by doing this, you will know whether you built something people want, and you will have a hundred real humans telling you what to build next.

The mistakes that keep people stuck at zero

A few patterns kill more first-100 attempts than anything else.

• Building more instead of talking to users. When getting users feels hard, it is tempting to retreat into what feels comfortable: adding features. More features do not get you users. Talking to users gets you users. If you find yourself building a new feature instead of messaging ten people, you are hiding from the actual work.
• Waiting until it is perfect. Your app does not need to be perfect to get its first 100 users. It needs to solve one real problem for one specific person. The builders who wait until everything is polished never launch, and the ones who get users are slightly embarrassed by the version their first users saw. Ship the embarrassing version and improve it with real feedback.
• Trying to reach everyone. A message aimed at everyone reaches no one. The narrower your target, the easier every channel becomes, because you know exactly where to go and exactly what to say. Specific beats broad every single time at this stage.
• Treating distribution as a phase that comes after building. The most expensive mistake is thinking of getting users as something you do once the app is done. The builders who succeed are thinking about who will use this and how they will find it from the very beginning. Distribution is not a step at the end. It is a thing you design for from the start.

The honest truth about your first 100

Nobody is coming to save you. There is no growth hack, no single channel, no clever trick that delivers 100 users while you sleep. The first 100 come from doing unglamorous, unscalable, slightly uncomfortable work: talking to people, being useful in communities, watching strangers use your app, and fixing what you see.

This is good news, actually. It means the bar is not cleverness or budget or luck. The bar is willingness to do the work most people skip. Most vibe coders build something, post it once, get nothing, and quit. The ones who get their first 100 users are simply the ones who kept showing up, one conversation at a time, until the thing they built found the people it was for.

You already did the hard technical part. You built a working app - something that would have taken a team and months not long ago. Getting it in front of 100 people is a different kind of work, but it is work you are entirely capable of. Go find them.

Frequently asked questions

Building something and worried the backend will not hold up when real users arrive? That reliability is exactly what decides whether your first 100 users stay or bounce. Butterbase gives your AI coding tool a complete backend that handles real traffic from day one, so the foundation is solid before you start chasing users.