How to Mine Indie Hackers and Product Hunt for Real Startup Pain Points (Step-by-Step Guide)

Most pain-point research guides send you to Reddit, Amazon reviews and YouTube comments, and for good reason, those sources are full of end users describing problems in their own words. Indie Hackers and Product Hunt are a different kind of source entirely. The people posting there are usually founders themselves, which means the complaints you find are often secondhand, filtered through someone who already built a product and is now describing what their own customers keep asking for or pushing back on. That secondhand quality sounds like a weakness, but it is also what makes these two sites valuable: a founder's milestone post or a comment thread under a launch often contains a more structured, already-analyzed version of the same pain points you would otherwise spend weeks finding scattered across Reddit.

This guide covers what each site is actually good for, where the real signal hides on both, how to tell a founder's honest lesson from a disguised sales pitch, and how to fold what you find into a validation process instead of treating it as the whole thing.

Why these two sites complement, not replace, user-facing sources

Indie Hackers and Product Hunt sit one level removed from the end user. A Reddit thread about bad invoicing software shows you the user's own frustration directly. An Indie Hackers post about building invoicing software shows you a founder's interpretation of that same frustration, usually after months of support tickets and churn conversations have already filtered the noise out. That filtering is useful, a founder who shipped three pricing changes in response to complaints has effectively done part of your research for you, but it also means you are reading someone's conclusion rather than the raw complaint. Treat what you find here as a shortcut to a hypothesis, then go verify that hypothesis against the user-facing sources where the original complaints actually live.

Where the signal hides on Indie Hackers

The milestone and lessons-learned posts are the richest vein. Founders writing about why they pivoted, which feature actually drove upgrades, or what support tickets kept repeating are effectively publishing a condensed research report for free. Search for phrases like users kept asking, the biggest complaint was, or we had to rebuild because, which tend to surface exactly the moment a founder describes a pattern rather than a one-off request. The comments under these posts matter just as much as the post itself, since other founders in adjacent niches frequently reply with their own version of the same problem, which is a faster way to confirm a pattern than searching five separate subreddits.

The product pages on Indie Hackers, where founders list their tools and revenue, are a second useful layer. Reading the reviews and comments left on a competitor's product page there surfaces a specific kind of complaint you will not find on a review site: other builders critiquing the product from a user's perspective while also understanding exactly what it would take to fix it, which often points straight at the gap worth building toward.

Where the signal hides on Product Hunt

Product Hunt comments split cleanly into two categories, and only one of them is useful. A large share of comments on any launch are polite congratulations from people supporting a friend's launch, which carry no research value at all. The comments worth reading are the specific questions, the does it support, the how is this different from, and the I tried something similar and the problem was replies. Those questions are usually a potential user describing their own unmet need in the process of deciding whether to try the new tool, which makes them close to a free customer interview conducted by someone else.

The most valuable single feature on Product Hunt for this purpose is checking a competitor's launch from a year or more ago, then reading how the comments and the product itself have diverged since. A launch that promised a feature in the comments and a changelog that never shipped it is a visible, dated record of a gap the founder either could not solve or decided not to prioritize, which is exactly the kind of whitespace worth investigating further.

Telling a founder's honest lesson from a disguised pitch

Both sites attract posts that look like lessons learned but are actually marketing dressed up as insight, a founder describing a problem only so they can pivot straight into pitching their own product as the solution. The tell is usually in the specificity, a genuine lesson includes concrete detail, exact numbers, named features, direct quotes from support tickets, while a disguised pitch stays vague about the problem and detailed only about the solution. Weight posts and comments that describe the problem in more depth than the fix, and discount ones that rush past the pain to get to the call to action.

A worked example: subscription cancellation flows

An Indie Hackers milestone post from a solo SaaS founder describes losing a painful amount of monthly revenue to silent cancellations, then rebuilding the cancellation flow around a one-question exit survey instead of a single cancel button. The comments under that post include three other founders independently confirming the same pattern in their own products, one of them noting a measurable drop in cancellations after copying the approach. A Product Hunt launch for a dedicated churn-survey tool, posted around the same period, has comments asking whether it integrates with specific billing platforms, repeated across several commenters, which signals real buying intent rather than curiosity. None of this is a user directly complaining about cancellation flows, but it is a tight, cross-confirmed signal that the underlying problem, and a market for tools addressing it, is real.

The limits of this source

Founder communities skew toward a specific kind of problem, the ones solo and small-team founders personally run into, which overrepresents SaaS, tools for other founders, and anything easy to build and launch quickly. Physical products, local services, and niches outside the startup bubble barely appear here at all. There is also a selection bias toward success stories, since founders write milestone posts when something worked, which means the far larger number of ideas that quietly failed to find this kind of pain point rarely get written up anywhere you can search.

Putting it together

Use Indie Hackers and Product Hunt as a fast way to generate hypotheses, not as proof. Search milestone posts and launch comments for a specific phrase describing your candidate problem, note which founders and commenters independently confirm the same pattern, then take that hypothesis to the sources where the original end-user complaints live, Reddit, Amazon reviews, YouTube comments, Quora threads. A pain point that shows up in a founder's lessons-learned post and then independently in a user's own words on Reddit is a far stronger signal than either source alone. UserConcern cross-checks candidate pain points across 8 sources in about 60 seconds, so a pattern you first spotted in a launch comment thread only counts as validated once it holds up outside the founder bubble where you found it.