Finding startup ideas on Reddit, and what that method can and cannot tell you

All guides

Public complaint threads are one of the few places where people describe a problem before anyone is selling them a solution to it. That makes them genuinely useful, and it is also exactly why they mislead: a thread is a sample of who was annoyed enough to type, not of who would pay.

What you are looking for is recurrence, not novelty

The instinct when reading threads is to hunt for an idea nobody has had. That is the wrong target. Novel complaints are usually novel because they belong to one person with an unusual setup.

What is worth finding is the boring complaint that keeps reappearing — the same friction, described in different words, by people who do not know each other, across months. Recurrence is the signal. It is evidence that the problem survives outside the mood of a single thread.

Three things raise a complaint's value, and none of them is how strongly it was phrased:

• It names a workaround. Somebody already built a spreadsheet, a script or a manual process. That is a person who has spent effort, which is the cheapest available proxy for spending money.
• It recurs across unrelated sources. The same friction on a forum, in a review and in a job posting is a much better signal than the same friction three times in one thread.
• It comes with a number. Hours lost, a rejected invoice, a churned customer. Vague annoyance is not costed; a number is the beginning of a price.

The method, by hand

1. Pick one market you can name in a sentence, not a category.
2. Read complaint threads in it until you stop learning — usually sooner than expected.
3. Write down each specific friction as a sentence someone actually said, with the link.
4. Group them. The groups that survive are the ones that appear across separate sources.
5. For each surviving group, ask who has budget for it. Not who is annoyed — who signs.

Step 3 is the one people skip, and skipping it is what turns research into confirmation. If a problem cannot be written as a sentence with a link, it is a memory of a thread, not a finding.

Where the method breaks

Threads are a complaint sample, not a market sample. Satisfied users do not post. So the loudest problem in a community is often the problem of its most vocal minority, and volume of complaints is not volume of demand.

Communities select their members. A niche forum is a filter, and what you conclude from it generalises only to people who are already there. That is a real segment, but it is not the market.

Complaining is free; paying is not. The distance between "this is infuriating" and "I would pay monthly for a fix" is where most idea lists quietly die. Nothing you read can close that distance — only an ask can.

Manual reading does not scale, and it self-confirms. By the fourth thread you know what you are hoping to find, and you find it. This is not a discipline problem; it is what reading is.

What we actually source, and where Reddit is not

Here is the part worth stating plainly, because a guide about mining discussions should say what its author's own tool reads.

Our published Discovery run pulled 56 documented problems from 41 sources, and read 24 pages in full. The hosts it actually read were:

• saashub.com
• trustmrr.com
• remotive.com

Reddit is not among them, and we do not source it. Our connectors read Hacker News discussion threads, alternatives and review sites, revenue comparables and job boards — surfaces that are fetchable, permitted by their own robots rules, and structured enough to attribute a claim to a specific page. Reddit sits in a later slot that has not been built. If you came here expecting a Reddit-mining tool, that is the honest answer.

That is also the argument for reading threads by hand, and for reading them the way this article describes. The technique does not depend on anyone's connector list.

Of those problems, 32 carry a link you can open. The rest are labelled as our estimate. A problem without a link is a signal, not evidence, and the two should never be rendered the same way — which is the same discipline step 3 asks of you.

What to do with what you find

A recurring, costed, workaround-shaped complaint is a candidate. It is not yet a business, and the gap between the two is where the actual work is.

The questions that decide it are not about the thread:

• Is there a real, documented problem behind it?
• Is there a path to money that repeats?
• Is there a repeatable way to reach the buyer?
• Can it charge enough to be worth one person's time?
• Can it run without hand-holding every customer?
• Does it survive if one platform changes its rules?
• Is there a product left if an AI vendor ships this feature?
• Can you, specifically, sell and operate it?
• Can it launch without licences or compliance audits?
• Can it sell without legal review and a sales team?

Notice that none of them can be answered by reading more threads. Distribution, pricing power and support load are properties of the business you would build, not of the complaint you found. The research tells you a problem is real. It cannot tell you the business is.

So the honest end of this method is a shortlist and a test — a specific promise put in front of the people who complained, with a real ask attached and a date by which you stop.

The short version

• Look for recurrence across unrelated sources, not for a novel complaint.
• Write each finding as a sentence with a link, or it is not a finding.
• Threads sample complainers, not buyers; volume of annoyance is not demand.
• We do not source Reddit — our runs read the hosts listed above, and the published run is open.
• No amount of reading answers the questions that actually kill an idea. Go and ask for money.