I Read 20+ Indie Founders' "First 100 Users" Breakdowns. The Same Four Channels Did the Work.

You shipped the thing. You polished it for months. Launch day comes — you post it, and… almost nothing. A handful of signups from friends, then it goes quiet. You post in a few places and nobody replies. You email a few people and nobody writes back. You refresh the dashboard. Five users. Maybe seven.

Distribution — getting the product in front of people — is the part most builders quietly treat as someone else's job. So instead of theorising about it, I did the boring thing. I read more than twenty indie founders' own breakdowns of exactly how they got their first 100 users. Real posts, real names, real numbers. I wasn't hunting for a growth hack. I was looking for what repeats.

Four channels kept showing up. And the one most founders sprint to first — the big public launch — turned out to be the least reliable of the lot. Here's the pattern, with the receipts.

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

"Build it and they'll come" quietly assumes the product is the hard part and the users arrive as a reward. The breakdowns say the opposite. The product was rarely the bottleneck. Finding the first hundred people who felt the pain — and getting in front of them one channel at a time — was the whole job.

One definition before we go further, because I kept tripping on it myself: a channel is just a repeatable place or method you use to reach potential users — a specific subreddit, cold email, posting on LinkedIn every day. Not "the internet." Not "social media." One concrete, nameable route. Four of them did the heavy lifting.

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

A community channel is an online space where a specific group already gathers to talk about a shared problem or interest — a subreddit, a Discord server, a Slack group, a niche forum. The trap is heading for the biggest, most general room (r/SaaS, r/programming). Those are crowded, competitive, and mostly full of other founders, not your buyers. The winning move is the adjacent, narrower room — the one where the people who actually feel your pain hang out and complain about it.

Why it works: in the right room you're not interrupting strangers, you're answering a question someone already asked out loud. The relevance does the selling for you. Twenty of the exact-right people beat ten thousand random impressions — which is why a tight, well-defined niche is this channel's best friend.

The clearest case: the founder of 1000 Pound Club, a powerlifting web app. Reddit gave him 60 of his first 100 users; Discord came second, Indie Hackers third — Twitter and Hacker News gave a flat zero. His read: a niche product needs a niche room. Ten thousand people seeing it on a general feed is worthless if almost none of them lift.

Three other SaaS founders, in a Reddit teardown, did the same thing deliberately — they skipped the obvious subreddit, found the rooms where users discussed pain points, and spent weeks genuinely helping before ever naming their product (roughly ten helpful posts for every one mention). Even Shopify seeded its early users inside the Rails developer community before it was Shopify.

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Direct outreach means reaching out one-to-one, by hand, to specific people who probably have the problem — a direct message on LinkedIn or X, a personalised cold email. "Cold" just means they didn't ask to hear from you. This is the opposite of broadcasting to a crowd: you pick named individuals and talk to them like humans.

Why it works at this stage: you don't need a scalable marketing machine yet — you need conversations. A message that names the recipient's actual situation gets read and answered, because it's about them, not about you. It's slow and unglamorous, and that's exactly the point: with no audience and no budget, you can still start today. The one rule — generic blasts get ignored or marked as spam; the personalisation is the channel. The receipts:

The thread that ties them together: it doesn't scale, and that's the point. You're not building a machine yet. You're having a hundred conversations.

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Building in public means openly sharing the journey of building your product — what you're working on, the calls you're making, what's working and what broke — as a steady stream of posts on one public platform (X, LinkedIn, or Threads). Instead of hiding until launch day, you grow an audience while you build, by being useful and visible along the way.

Why it works: people follow a person and a story, not a landing page. By the time you have something to sell, a group of people already know you, trust you, and want you to win — so launch isn't a cold start. The discipline the data is strict about: pick one platform and go deep. Spreading thin across seven gets you nothing anywhere; consistency on one compounds. It's the slowest to start, because trust takes time — but it pays back the longest.

This is the one I'm running for RFA myself — more on that below.

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Audience-first means building a group of interested people — an email newsletter list, a following, a small community — before the product is ready, so launch day lands on a warm crowd instead of an empty room. You attract people by being consistently helpful about the problem space, gather them somewhere you control (ideally an email list, since you own it outright), and they become your first users the day you ship.

Why it works: it removes the cold-start problem entirely — launch stops being a gamble because the people are already there, waiting. The founders who looked like overnight successes almost always did this quietly, months earlier.

The uncomfortable part: this one takes the longest. If you have no audience today, you can't conjure one for next week's launch. Which is exactly why "start before you need it" keeps being the advice nobody wants to hear.

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Here's the surprise that kept repeating: the big public launch — Product Hunt, or a Show HN post — was the least dependable channel in the whole set. (A Show HN post just means putting your project in Hacker News's "Show" section.)

A founder who profiled 80 Indie Hackers companies found that even a successful Product Hunt launch was a temporary spike that faded within a week or two — after which founders had to do the real work of building durable channels. Tally's own Product Hunt launch doubled their users in a day, sure — but the lasting growth came from the months of manual outreach, not the spike. And 1000 Pound Club, remember, got a flat zero from Hacker News.

Launches aren't useless. They're amplifiers — they make a channel that already works louder. They don't create one from nothing.

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

You don't run all four. You pick the one that matches where your users already are, go deep for 60–90 days, and only then add a second. A rough decision guide from the patterns:

And the contrast the breakdowns punish hardest:

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

For RFA, I've put my chips on Channel 3 — building in public, mostly here and on LinkedIn. This newsletter is that channel in action: I take a problem founders actually hit, pull apart what the evidence says, and publish it in the open. Pattern over hype.

So this isn't a top-down playbook. It's the synthesis of what twenty-plus people who've actually done it wrote down — and the lane I chose because of it. If you're working one of these four channels, tell me what's landing for you. Comparing live notes beats any single post.

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

If you've shipped something and gotten even your first ten users: which channel actually brought them — and which one did you waste a month on before quitting?

Come compare notes with other founders working on the same problem in the RFA community on Skool. That back-and-forth is worth more than any single post when you're working out where your first users come from. And if a friend is heads-down building with no plan for users yet — forward them this.

— Bibhash

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━