How to introduce your product on Indie Hackers
Indie Hackers is a community of builders, not buyers, and it is thinner than it was after the Stripe-era layoffs. That changes what it is good for. Treated as a place for honest feedback and peer relationships rather than a traffic firehose, it still earns its hour.
Last updated June 17, 2026Indie Hackers is best for peer feedback and durable builder relationships, not for a wave of customers, and its reach has declined since the community team was cut. Introduce your product the way the community responds to: an honest build story with real numbers and real struggles, not a launch announcement. Expect a handful of thoughtful replies and a few relationships, treat it as one footprint channel among several, and put your customer-acquisition hopes on the communities where your actual users (not other founders) gather.
- The audience is other builders. They give excellent feedback and occasional early signups, but they are rarely your end customer, so calibrate expectations accordingly.
- Indie Hackers’ reach has cooled since Stripe’s ownership and the community-team cuts. It is still active, just quieter, and is increasingly read more than posted in.
- The format that works is a transparent build log: what you made, the real numbers, what failed, and a genuine question for the community.
- For early traction, Reddit (especially r/SideProject) has largely taken the role Indie Hackers held a few years ago. Use both, for different things.
Indie Hackers is a community of people building products, which is its strength and its catch. The strength is that builders give the most useful feedback you will get anywhere, because they have shipped and they know what matters. The catch is that builders are rarely your customer, and the forum is quieter than it was after the Stripe-era cuts to its community team. So introduce your product there for what it actually offers in 2026, honest feedback and durable peer relationships, and put your hopes for a flood of users somewhere your users actually are.
01 · Feedback and peers, not a firehoseWhat Indie Hackers is good for now
The single most important calibration is the audience. The people reading your post are overwhelmingly other founders. That makes Indie Hackers superb for a specific kind of value and poor for another.
It is excellent for considered feedback: post a rough product and you will get thoughtful, experienced critique that a random visitor never gives. It is excellent for relationships: the regulars become people you trade advice and encouragement with for years. It is good for the occasional early signup, especially if your product is itself aimed at builders. It is not good as a customer-acquisition firehose, because the room is full of people who build products, not people who buy yours.
Indie Hackers is owned by Stripe, and after the community team was cut, activity declined; some founders now describe it as feeling more like a blog than a busy forum. It is still active and still worth posting in. It is just quieter and more read-than-posted than it was a few years ago, so set your expectations to “a handful of good replies,” not “a launch event.”
02 · A build log, not an adThe format the community rewards
Indie Hackers responds to transparency and effort, and ignores marketing. The post that works is a build story, not a launch announcement.
The shape: say what you built and why, share the real numbers including the ones that sting, describe honestly what is not working, and end with a genuine question for the community. “I launched Pagewatch four months ago, I am at thirty users and stuck on activation, here is what I have tried, what would you do?” is exactly the register. It invites the experienced replies that are the whole reason to be there. A polished “introducing Pagewatch, the best way to monitor pages” gets scrolled past, because everyone reading has written that sentence themselves and knows what it is worth.
Show the numbers, including the embarrassing ones. Transparency is the currency here, and a vague win story buys nothing.
This is also why Indie Hackers pairs well with the built-isnt-launched reality: the community is at its best when you treat your launch as the start of a conversation about what is not working, rather than a declaration that you are finished.
03 · Different jobsIndie Hackers versus Reddit
A few years ago, Indie Hackers was where many products got their first traction. That role has largely shifted to Reddit, and it is worth being clear about why so you use each correctly.
Reddit’s reach held up while Indie Hackers’ cooled, and subreddits like r/SideProject now routinely deliver more early signups in a day than an Indie Hackers post does, because they are larger and more actively browsed. So for raw early traction, Reddit is the stronger channel. For considered feedback and relationships with people who have walked the same path, Indie Hackers is better. Most builders use both, for those two different jobs, and stop expecting either to be the other.
Before you ask builders for feedback, get the objective read
Indie Hackers will tell you what they think. Nilkick tells you what is measurably missing: whether your page is clear and parseable, and whether you have any footprint yet. Run the free report and bring the data to the discussion.
04 · Presence over a single postHow to actually spend your time there
As with every community, a single drive-by post underperforms genuine presence. The value compounds when you show up.
Comment on other people’s build logs with real substance, answer questions in your area, and become a name people recognise. Then your own intro post lands among people who already know you, and your follow-ups (the monthly “here is where I am now”) build a small audience of peers who are invested in your progress. This is slow, and it is the same lesson as everywhere else: standing first, then the share. The difference on Indie Hackers is that the standing is worth building even if you never get a single customer from it, because the feedback and relationships are the product.
05 · One node, not the centreWhere Indie Hackers fits in the bigger map
Treat Indie Hackers as one node in a small network of builder communities, not the centre of your launch. The active hubs in 2026 are spread out: build-in-public on X, accountability communities like WIP and Makerlog, the right subreddits, and a long tail of niche Discords and Slacks. Pick the two or three that fit your product and your temperament, be genuinely present in them, and let Indie Hackers be your feedback-and-peers node specifically.
The throughline with the rest of the launch-venue map: no single venue is the answer, each does one job, and the founders who get traction are the ones who matched the venue to the job instead of expecting one forum to deliver everything. Indie Hackers does its job well. Its job just is not “send me customers.”
Common questions
Get your free launch-readiness score
See what else is between your product and its first real users. Nilkick scores your readiness and hands you the map. Free, no login.
https:// optional · no account · we don't email you
Where to launch a product with no audience in 2026
A ranked, honest map of where to launch a product with zero audience in 2026, sorted by what actually sends you humans versus what just builds footprint.
How to share your product on Reddit without getting banned
Reddit can send your first real users or ban your account in five minutes. The 90/10 rule, karma and account-age gates, the per-subreddit reality, and how to post so it sticks.
Launching on Product Hunt with no followers: what actually works
Product Hunt in 2026 rewards early velocity and human curation, so a cold launch with no audience usually sinks. Here is what genuinely moves the needle, and when to skip it.