How to Find SaaS Ideas on Reddit (Without Guessing)

You want to build a SaaS product, but every idea you write down feels like a guess. You cannot tell the difference between a problem people will pay to remove and a problem that only sounds interesting in your own head.

Reddit is full of people describing the second kind of problem in detail, out loud, for free. The trick is reading it on purpose instead of scrolling it.

Why Reddit Beats Brainstorming

Brainstorming produces ideas that sound clever to you. A thread produces a problem that already costs someone time, money, or patience.

Say someone posts: “I have been doing this by hand every Friday for two years and I am losing my mind.” That is not a niche. That is a person who has accepted a recurring cost and built a workaround around it. Workarounds are where small products come from.

The other advantage is that nobody is performing for you. A post written late at night in a small community is closer to the truth than anything said in a meeting.

Three things make a thread worth keeping:

• Specificity. “Accounting is hard” tells you nothing. “I export a CSV every Friday and reconcile 200 rows by hand” tells you what the tool has to do.
• Repetition. The same complaint, in different words, in different threads, months apart.
• Heat. Frustration, anger, exhaustion. People pay to make those feelings stop.

The Method: Search for Pain, Not for Products

Most people search Reddit wrong. They search for ideas, find threads where people list tools, and come away with a list of competitors.

Search for friction instead:

1. Pick a group you understand: a job, a hobby, an industry.
2. Search their communities for words that describe friction, not solutions.
3. Copy the thread text into a file along with the URL. Manual work, and worth it.
4. Group the quotes by the underlying problem. Many threads, one problem.
5. Only after that, ask whether a small tool could remove it.

Step three is the one people skip. If you do not keep the raw quotes, you drift back into your own assumptions within an hour. Run the loop on one community in an afternoon, or spread it over a week across several communities. The order matters more than the speed.

Real Search Terms You Can Use Today

Good search terms describe behavior, not products. Try these in a community search box or a site-wide search:

• “is there a tool that”
• “how do you all handle”
• “I still do this manually”
• “I wish there was”
• “what do you use for”
• “anyone else struggle with”

Then widen the net and ask why people leave the tools they already pay for: “switched from”, “too expensive”, “too complicated”, “canceled my subscription”. A complaint about a competitor is often a rough spec for the next product. Then run the same phrase in a completely different community. If the pain travels, the market is wider than the first group you looked at.

Keep one line per thread in a plain text file: the problem, the URL, and the exact quote. After a week you will have more usable material than a month of thinking.

Two Traps to Avoid

• Building for a hobby you do not understand. Enthusiasm is not expertise. If you cannot tell a good thread from a bad one, pick another community.
• Treating upvotes as demand. A funny comment gets votes; a desperate one often gets ignored. Read the replies, not the score.
• Falling in love with your first problem. Collect for a week before you commit to anything. Overlap between independent threads is the strongest signal you will get.

Turning Threads into a Shortlist

Score each problem on four questions:

• How often does it happen? Daily beats yearly.
• What does the workaround cost today? Hours, subscriptions, and hired help all count.
• Can one person ship a first version? If it needs a sales team, keep reading.
• Would the person notice a fix tomorrow? If yes, you can charge for it.

Problems that score well on all four go on the shortlist. Problems that score on one are interesting reading, nothing more.

Keep the shortlist short. Three problems you can describe in one sentence each will take you further than twenty ideas you cannot explain to anyone else.

FAQ

How many posts before I can trust an idea?

More than feels comfortable. As a rough working rule, aim for a few dozen posts spread over several weeks. If the same problem shows up in independent threads written by different people, you have something. If you found it once, you have an anecdote.

Is it okay to build for a problem I do not have?

Yes, but you have to borrow the context. Read the community until you can predict what people will complain about next. The risk is not that you lack the pain. It is that you stop reading and start assuming.

What if the community is too small?

Small communities are often better. Fewer posts, but more specific ones. Look for where professionals gather rather than the largest general community you can find.

Do I need to ask people directly?

It helps, but read first. A question invites polite answers. An archive of unprompted complaints shows what people actually did when nobody was watching.

Reading manually works, and it is slow: dozens of tabs to find a handful of threads that matter. If you want the same job done in a few minutes, run a report for 2.99 EUR and read the problems it surfaces, each one with quotes you can check against the original thread. For the manual version in more detail, read how to do Reddit market research. Before you write any code, read how to validate a startup idea.