You spent an afternoon with an AI assistant and shipped a tiny tool. Your first instinct was to drop it on Hacker News — or to push a Product Hunt launch the same week.
The usual failure is not “you built too slow.” The usual failure is walking into the wrong room. Those two places do not grade the same homework. The same founder can walk through all of them; each room asks a different question.
AI made building cheap. Distribution did not get cheaper. More people now walk into a room that was never testing what they brought.
A quick map
Indie culture here is less “genius coder hangout” and more a stacked habit for growing small products: say the idea out loud, ship early, find first users, put a price on it, do a real launch, take the feedback, turn a free tool into something people pay for.
Four rooms, roughly:
| Room | What it is | What it asks |
|---|---|---|
| Hacker News | Acid test | Is this real? Can I try it? |
| Product Hunt | Launch day | Can you present it in one clear package? |
| Indie Hackers | Revenue talk | Will anyone pay? How did you price it? |
| MicroConf | Operate | Can a small paid product stay alive for years? |
None of these is a “press this and explode” button.
Room 1: Hacker News — the acid test
A Show HN post is blunt: I made this. Try it.
This room is allergic to three shapes: AI wrappers with no real use, pretty landing pages with nothing behind them, and “quickly-generated one-offs.” That last phrase is now in the official Show HN rules — anybody can do that now.
What counts: something another person can open and use. Blogs, signup walls, newsletters, and listicles do not count as Show HN. Prefer no signup on first try. Do not ask friends to upvote.
The shapes that usually travel better are boring: a CLI, a browser extension, an open-source project, a narrow developer utility — something that runs without a pitch deck.
So HN is really asking: is this real, and can I touch it?
Do not drag a Product Hunt launch kit into a Show HN thread. That room likes a story. This room wants the thing first.
(Someone studied HN exposure and GitHub stars for AI/LLM repos. Averages moved after a hit. Averages are pulled up by a few blow-ups; most projects are quieter. Do not treat “every Show HN gains N stars” as a promise.)
Room 2: Product Hunt — launch day as packaging
This room is closer to a daily leaderboard of new products.
It grades: a one-line tagline, clean screenshots, a demo people can click, the maker’s own story, comment replies, and same-day spread on X.
One contrast is enough:
- HN asks: is it real?
- Product Hunt asks: can you present it?
Often the story starts before the product is “done”: email list warm-up, a coupon ready, a maker thread. Do not paste a raw GitHub README onto a Product Hunt card. That room is scoring how you show up on day one — not how long your repo README is.
Room 3: Indie Hackers — the revenue room
The site’s own line is clear: founders of profitable businesses and side projects share stories transparently.
The currency here is not frontpage points. It is:
- rough monthly recurring revenue (MRR = what you collect each month from subscriptions)
- where the first paying customer came from
- why you charged $9 instead of $19
- how long SEO took
- how many cold starts failed
This is not another Product Hunt. Applause for “what rank am I today” lands flat. Bring the ledger — or an honest zero.
Room 4: MicroConf — operate the small SaaS
This is the bootstrapped lane: small paid software that feeds itself, not the VC-unicorn track.
People talk about: whether a few thousand dollars of MRR is reachable, when to raise prices, why users churn, when to quit the day job, when to hire the first support person, when to sell the company.
This room does not care if you went viral today. It cares whether the small business can stand for years.
Default to selling — as an experiment
In this stack, “will someone pay?” is part of the experiment, not a personality flaw.
A well-worn script (community talk, not a guarantee): land a page, collect emails, sell a $9 or $19 monthly plan or a lifetime deal, then watch how the room reacts.
The shapes that convert in this culture are often intentionally boring: PDF tools, extensions, invoices, forms, tiny APIs. That is a product shape, not a ranked idea list.
One longer light path people repeat: small pain → landing page → post on X / HN / Reddit / Indie Hackers → roughly ~100 emails → a usable first version → price → listen → content for acquisition → collect payment → then decide whether to quit. Writing that as “do this and hit $20k MRR” would be fake. The $1k / $5k / $20k marks you hear are milestone talk in the community — not audited statements in this packet.
Why Agent builders keep losing here
Writing code is less scarce than it was.
What stays scarce: what to make, who pays, where the first users live, how you say the value in one line, how traffic keeps arriving.
Build is easy, distribution is hard.
Build in public is not a flex. It is laying pipe before launch day: screenshot today, revenue note tomorrow, postmortem the day after, feature vote a few days later — so launch day is not your first introduction.
Numbers work as social currency here. “I understand SaaS” earns a shrug. A concrete MRR range gets people to listen. Treat $500 / $2k / $10k the same way as the other soft numbers: common community scale talk, not your floor and not an official survey.
Which door today (pick one)
- Need people to actually try it and tell you it is fake? → Show HN. Make it runnable. Light on signup walls. No vote brigading.
- Need a launch day with a sentence, pictures, and a maker thread? → Product Hunt. Prepare the story before the repo feels “done.”
- Need to talk money, pricing, first 10 customers? → Indie Hackers. Bring numbers, or an honest zero.
- Need operating questions (churn, hiring, quitting, selling)? → MicroConf orbit — not a launch tweet.
Pick the room that matches the question.
Do not ask Hacker News to clap for packaging. Do not ask Product Hunt to replace a year of distribution.
Also on X: https://x.com/bb833dong/status/2102777606592499807