--- slug: first-100-users-indie-app title: "How to Get Your First 100 Users for an Indie App" excerpt: "Getting your first 100 users for an indie app isn't about going viral. It's about four channels and ten conversations. Here's the actual playbook." primaryKeyword: "first 100 users indie app" publishedAt: 2026-05-14 readingTimeMin: 7 author: "Robert Boylan" tags: - indie-dev - app-launch - distribution - shipping - vibe-coding --- You shipped on a Tuesday night. You posted a screenshot on X, threw the link in your bio, dropped it in one Slack you barely use. You got 12 likes. Two of them were from your sister and your old college roommate. By Thursday the chart is back to a flat line that mostly tracks you opening the analytics page to check if anyone else did. This is the part nobody told you about. The build was the hard part you trained for. The launch was the part you imagined for months. But the week after launch is where most indie apps quietly die, and almost nobody writes about it because there's nothing dramatic to say. The app works. The waitlist is empty. Now what. Getting your first 100 users for an indie app is a real, learnable thing. It just doesn't look anything like the launch posts on your timeline. It's four channels and ten conversations, repeated until something clicks. ## The week-after-launch problem nobody warned you about Every successful launch you've ever seen was either someone with an audience already, or a survivor-bias artifact of the one in fifty that broke out. You're not seeing the other forty-nine versions of that same Tuesday night where the chart stayed flat. The playbook in your head is wrong. You're waiting for traction to find you. Real first 100 users don't show up at your door because of one big launch moment. They show up because you went to where they already are, ten at a time, for six weeks. That sounds like a lot. It is. But it's the part you can actually control, which is more than you can say for the algorithm gods. ## The four channels that actually work for indies Most launch advice is written for companies with budget and headcount. You have neither. So forget paid ads, forget hiring a "growth" person, forget the 47-tactic listicles. There are four channels that consistently work for solo builders and small teams. Pick two, ignore the rest. **Niche subreddits.** Not r/SaaS, not r/Entrepreneur. Those are graveyards of self-promotion. Find the subreddit where your actual user already hangs out talking about the problem. If you built a tool for tabletop game designers, that's r/RPGdesign. If you built something for plant-shop owners, that's r/houseplants. Read for two weeks before you post. Then post about the problem, not the product, and mention what you built at the bottom. **Product Hunt, with realistic expectations.** PH is great for one specific thing: a single concentrated day where developers, founders, and curious early-adopters give your idea attention. It is bad at: ongoing traffic, mainstream users, anyone who isn't already in the tech bubble. Treat it as one channel, not the launch. If you get 200 signups, that's a great day. If you get 30, that's still a fine day. **X / Twitter, but the reply game.** Posting your launch into the void doesn't work unless you already have followers. What works is replying. Find ten accounts in your niche posting daily. Reply with something useful, not promotional, every day for a month. Your bio link does the rest. This is slow. It also compounds in a way nothing else does. **One niche community where you're already a member.** A specific Discord, a Slack group, an indie forum, a hobbyist mailing list. If you join a community to post your launch, everyone smells it instantly. If you post your launch in a community where you've been a real participant for a year, people genuinely want to help. There's no shortcut around that year, sorry. Notice what's not on this list. Cold email. SEO (it works, but it's a 6-month play, not a first-100 play). Influencer outreach. Press. They're not bad channels. They're just bad first channels for an indie with no audience. ## The "10 conversations" rule before you spend a cent Before you do anything else, before you write a single ad, before you tweak the landing page copy for the fourth time, there is one thing that's worth more than all of it combined: ten real conversations with prospective users. Not "feedback from friends." Not "I posted in a Slack and three people said it sounded cool." Ten conversations, by name, with people who have the actual problem you're solving and aren't related to you. Here's the question set: 1. When was the last time you ran into the problem this app solves? 2. What did you do about it that day? 3. How long did it take? Did it work? 4. If a tool existed that did exactly this, where would you go to find it? 5. What would you happily pay for it, if anything? That's it. The answers to question 4 tell you which channels to use. The answers to question 5 tell you whether you have a real product or a free side project people will use once and forget. The answers to questions 1, 2, and 3 tell you whether your understanding of the problem matches reality. A real signal is someone saying "I literally did this yesterday, and I tried X tool but it didn't quite fit." A fake signal is "yeah that sounds useful, I'd probably use it." The first person becomes a beta user. The second person was being polite. Ten of these conversations will save you three months of building things nobody asked for. ## Why launch day is overrated and what week 2 to 6 actually looks like The launch day fantasy is the chart that hockey-sticks the moment your post goes up. The reality, for almost every indie app that eventually works, is a slow stairstep over six to ten weeks. Week one: 30 signups, of which maybe 8 actually try the thing. Week two: nothing. You panic. You consider rewriting the landing page in a different colour scheme. Week three: a Reddit post from week one quietly gets upvoted in a weekly digest. 12 new signups. Week four: one signup DMs you with a feature request. You ship the small thing. You post about it on X. 4 signups, but one of them has 8,000 followers and reposts it. Week five: 20 signups in a day. Then back to 2 a day. Week six: another niche community post, plus a small podcast you replied to. 25 signups. You're at 92. This is not a glamorous chart. It's a stairstep. What makes it work is a weekly cadence: every week, you ship one small thing and tell people about it in one place. Not a launch. Just a small public update. After six weeks of those, you've built a tiny but real audience of people who've watched you ship and start to root for you. If you want a sanity check on whether your own timeline is realistic, [the realistic timeline for shipping a vibe-coded app](/blog/vibe-coded-app-timeline) covers what build and launch actually look like in calendar weeks. ## When to start charging vs stay free Most indie devs get this wrong in one of two ways. They charge from day one with no users, or they stay free forever because "I'll add pricing once I have traction." The second mistake is worse. Free-forever apps select for users who don't value the thing enough to pay. When you eventually try to charge, half of them churn and the other half are confused. You haven't validated demand, you've validated that people will accept free things, which is not news. A reasonable rule: stay free until you have around 50 active users (people who've come back at least twice). Once you hit 50, introduce paid tiers. Keep a free tier so you don't lose top-of-funnel, but make the paid tier do the real work. The "I'll charge later" trap is worth naming clearly. Every week you delay charging is a week you don't know if anyone would actually pay. You can ship a payment integration in an afternoon with Stripe or Lemon Squeezy. You don't need a pricing strategy MBA. You need three tiers and a button. If you want the longer version, [how to actually price an indie app](/blog/pricing-your-indie-app) walks through what pricing looks like when you only have a hundred users to work with. The other failure mode is the inverse: putting up a paywall before you have any traction at all. If literally nobody is using the free version, charging won't fix it. The order is: 50 users using the thing, then a paid tier, then more growth. Not the other way round. ## The single mistake that kills first-100 momentum Going broad too early. You ship a productivity app and start telling everyone with a job that they should try it. You target "freelancers" or "small teams" or "people who use Notion." Your messaging is generic because your audience is generic. Your replies on X are generic because you're trying to talk to everyone. Result: nobody feels like the post is for them. Indie apps die on the rocks of "for everyone." The apps that get to 100 users almost always start with one painfully specific group. Tabletop game designers who run Patreons. Plant-shop owners doing Instagram restocks. Solo financial advisors who keep client notes in Notion. Boring, narrow, and absurdly specific. When your audience is narrow, your reply game is sharper, your subreddit choice is obvious, your Product Hunt copy writes itself, and your ten conversations are easy to schedule because you know exactly who to ask. You don't have to stay narrow forever. You just have to start narrow long enough to get the first real users. Once you have 100 of them, expanding to "freelancers" or "small teams" is something you can do from a position of having actual traction, not theoretical hope. This is also why scoping the product matters before you scope the marketing. If your MVP is doing eight things for everyone, your first 100 users are going to be hard. [Scoping an MVP that actually ships](/blog/mvp-scope-ships-in-a-weekend) covers the build side of the same problem. ## The thing nobody tells you The reason most indie apps don't get their first 100 users isn't bad marketing or a weak product. It's that the founder couldn't describe who the app was for in a single sharp sentence. They could describe the features. They could describe the screens. But the audience was always "kind of for X, and also Y, and I guess Z would like it too." Distribution is downstream of clarity. If you can't say "this is for X who needs to do Y when Z" in one breath, every channel is going to feel like wading through mud, because every message has to be retrofitted to whoever might be in the room. Niche subreddit posts read as generic. Replies on X feel like they're trying. Your ten conversations turn into ten polite "yeah, sounds useful" responses. The fix isn't a marketing trick. It's getting the description of the audience and the problem locked down before you start the channel work. That's the real first-100 lever. That's what Draftlytic is built for. You describe the idea, and it walks you through the questions that pin down who the app is for, what the one painful problem is, and what the first version is actually doing. The output is a spec that goes straight into your AI tool of choice (Cursor, Lovable, whichever) and, more usefully, a description of your audience sharp enough that your first reply on X writes itself. The first 100 users for an indie app come from being clearly for someone. The thinking before the launch is the part that makes the launch work.