The first 100 users won’t come from Product Hunt
Launch day is a spike, not a channel. Where early software users actually come from, and why the unglamorous answer keeps winning.
A launch is an event, and events end. That is the part founders discover the Thursday after, when the traffic graph returns to the shape it had the week before and the signups that arrived on the day turn out to have been mostly other founders. The launch was not a mistake. It was just never a distribution strategy, and treating it as one costs a month that early companies do not have.
The mechanics are unforgiving. A launch platform sends people who are interested in launches. That audience is generous with attention, quick to sign up and structurally unlikely to have the problem you solve, because they were browsing new products rather than looking for a fix. You get a number, and the number flatters you into thinking the hard part is over.
What the first hundred are actually for
The first hundred users are not a revenue milestone. They are a research instrument, and the way you acquire them determines whether the instrument works.
Users who arrived because they had the problem will tell you what the product is missing, argue with your onboarding, and renew. Users who arrived because they were browsing will churn quietly and teach you nothing — worse, they will pollute every metric you use to make the next decision. Activation looks broken when it is only mismatched. Retention looks fatal when it is only curious.
Recruit the wrong hundred and you spend the next quarter fixing a product that was never the problem.
So the question is not how to get a hundred signups quickly. It is how to get a hundred people who would be annoyed if you took the product away.
Where they actually come from
The channels that produce those people are slower, less repeatable and much less fun to talk about.
- Places where the problem is already being discussed. Not a subreddit for your category — a thread where someone describes your problem in their own words and asks what people use. Answering those, usefully, without a pitch, is the highest-yield hour in early distribution.
- People who already trust someone who trusts you. The first twenty users of most B2B software come through a warm path: a former colleague, an investor introduction, a customer of an adjacent tool. This does not scale, which is exactly why it works when nothing else does.
- Communities you were part of before you needed anything. Standing in a Slack group, a professional forum or an industry mailing list is earned in advance. Arriving the week of launch is visible and it does not work.
- Concierge onboarding. Doing the job manually for the first users — setting up their account, importing their data, sitting on a call while they try it — converts far better than any funnel, and generates the only product feedback worth having.
None of these produce a graph you can screenshot. All of them produce users who stay.
Why founders keep choosing the spike
Because it is legible. A launch has a date, a checklist and a public result, and that is enormously comforting when the alternative is a month of conversations with no visible progress. It also produces something to report — to investors, to a team, to yourself.
The quieter work has none of that. Twenty useful forum replies look like nothing on a dashboard until the fourth one turns into a customer who brings two more. The compounding is real but it is invisible for weeks, and invisible progress is hard to keep funding with your own attention.
What a launch is genuinely good for
This is not an argument against launching. A launch is a good forcing function and a legitimate credibility asset — a dated, public artefact you can point at for years. It also occasionally puts you in front of someone who does have the problem, and those people are worth catching.
The mistake is sequencing. Launch after you have twenty users who would be annoyed to lose the product, not before. By then you know what to say, you have a claim that survives contact, and the spike lands on a foundation instead of on nothing.
- Write down the exact sentence your buyer uses to describe the problem. Not your sentence — theirs.
- Find ten places that sentence already appears this month. Answer in five of them without linking to yourself.
- Onboard your first twenty users personally, even if it does not scale. Especially because it does not scale.
- Only then book the launch — and treat the traffic as an audition, not a result.
Before planning launch day, count how many current users would be genuinely inconvenienced if the product disappeared tomorrow. If the answer is under ten, the launch is early. Spend that week in the places your buyers already are, and launch when you have something that keeps the people it attracts.