Sites That Show Real Customer Pain Points

Where to Find Customer Pain Points Online

Customer pain points are easier to find than most founders think. People complain about products, describe workflow frustrations, and ask for alternatives in public forums every day—without being prompted by a survey or interview. The challenge isn't finding these discussions. It's knowing where to look and what signals to pay attention to.

Here are the best types of sites where real users share real frustrations, and what each is useful for.

Best Sites to Find Customer Pain Points

1. Reddit

Reddit is arguably the richest single source of unfiltered user sentiment. Unlike review sites, people on Reddit aren't filling out a form—they're venting, asking for help, and describing problems in their own words.

Best for: Almost any niche. SaaS, productivity tools, AI tools, B2B software, consumer apps, hobbies, professional workflows.

What to look for:

• "Does anyone else hate [X]?" posts
• "Is there a tool that can [X]?" requests
• "I'm so tired of [X]" rants
• Long comment threads where users debate the shortcomings of a product
• "What's the best alternative to [X]?" discussions

2. X / Twitter

X is where people share quick, honest reactions to products and tools they're using. Because the format is short and the audience is public, people are often more direct than they would be in a review.

Best for: Real-time sentiment, SaaS products, AI tools, developer tools, products with active user communities.

What to look for:

• Quote tweets complaining about a product
• "Hot take:" threads about industry tools
• Replies to product launch announcements pointing out missing features
• "Someone please build [X]" tweets

3. Hacker News

Hacker News is the go-to community for developers, startup founders, and technical users. The discussion quality is high, and people often write detailed critiques of products, tools, and industry trends.

Best for: Developer tools, SaaS products, open-source projects, technical workflows, startup-focused products.

What to look for:

• "Ask HN" threads asking for tool recommendations
• "Show HN" comment sections where users point out gaps
• Threads about switching from one tool to another
• Detailed technical complaints about existing solutions

4. GitHub Issues

GitHub Issues is a goldmine for pain points related to developer tools, open-source projects, and any product with a public repository. Users report bugs, request features, and describe workflow problems in detail.

Best for: Developer tools, open-source alternatives, APIs, CLI tools, infrastructure products.

What to look for:

• Feature requests with high thumbs-up counts
• Issues where users describe workarounds they've built
• Long discussion threads about a missing capability
• "This would be great if it could also [X]" comments

5. G2 and Capterra

These are the biggest B2B software review platforms. Reviews tend to be structured, which makes scanning easier, and they often include specific feature complaints.

Best for: B2B SaaS products, enterprise tools, marketing software, sales tools, project management tools.

What to look for:

• Reviews that say "I like it, but..."
• Reviews from users who switched from a competitor (and why)
• Feature requests in the review text
• Low-star reviews with detailed explanations

6. Product Hunt

Product Hunt is where new products launch, but the comment sections are just as valuable for research. Early adopters often compare new tools to existing solutions and point out what's still missing.

Best for: SaaS products, AI tools, productivity apps, browser extensions, indie hacker products.

What to look for:

• Comments comparing the product to incumbents
• "I'd use this if it had [X]" feedback
• Makers asking for feedback and getting honest answers
• Discussions about pricing and value

7. App Store and Chrome Web Store Reviews

Mobile app stores and the Chrome Web Store contain a massive volume of user feedback. Reviews are short, but the volume can reveal clear patterns.

Best for: Mobile apps, browser extensions, consumer apps, B2C products.

What to look for:

• Recurring feature requests across multiple reviews
• Users describing specific workflows the app doesn't support
• "Used to love this but..." reviews that explain why someone left
• Complaints about pricing, bugs, or missing integrations

8. YouTube Comments

YouTube comments are an overlooked source of pain point data. Under product review videos, tutorials, and "best [X] tools" roundups, users often describe their specific needs and frustrations.

Best for: Consumer products, creative tools, software with active tutorial communities, hardware.

What to look for:

• "This would be perfect if it could [X]" comments
• Users comparing the reviewed product to alternatives
• People describing their specific use case and asking if the tool supports it
• Frustration with missing features mentioned in the video

9. Niche Forums and Communities

Every industry has its own forums: Stack Overflow for developers, Indie Hackers for solo founders, specialized Facebook groups, Discord servers, and countless others. These communities often contain the most detailed, context-rich discussions.

Best for: Niche-specific research. Developer tools, specific industries, professional communities.

What to look for:

• Long-running threads about common problems
• "What do you use for [X]?" discussions
• Members describing their current workflow and its limitations
• Tool recommendation threads with detailed pros and cons

10. Quora and Stack Exchange

Q&A sites capture people actively looking for solutions. When someone asks "What's the best tool for [X]?" or "How do you handle [Y] in your business?", they're describing a pain point in the form of a question.

Best for: B2B problems, professional workflows, specific "how do I solve [X]" questions.

What to look for:

• Questions with many answers and high view counts (signal of widespread interest)
• Answers that describe workarounds instead of off-the-shelf solutions
• "Is there a tool that can [X]?" questions with no satisfying answer

What Signals to Look For

Across all these sources, you're looking for specific types of signals, not just general negativity:

• Alternative-seeking behavior — "Is there a tool that does X?" or "What's the best alternative to Y?" These are direct demand signals.
• Workaround descriptions — When people describe a manual process or a patchwork of tools they've built to solve a problem. This means the problem is real enough that they've invested time in a fix.
• Recurring feature gaps — The same missing capability mentioned by different users in different places over time.
• Switching intent — "I'm planning to leave [X] as soon as I find something better." These users are already in the market for a new solution.
• Price sensitivity complaints — "I'd use [X] if it wasn't so expensive." This signals a potential opportunity for a more affordable or differently-priced alternative.

The Problem with Manual Research

If you're serious about finding pain points, you can absolutely start with manual research. Open Reddit, search a few keywords, read some threads. It's free and it works—to a point.

The problems come when you try to do it systematically:

• Time: Searching across even three or four sources takes hours, and you'll still miss things.
• Pattern recognition: The human brain isn't great at spotting frequency patterns across dozens of threads from different platforms. You might read three complaints and think it's a trend, or miss a trend because the complaints use different words.
• Confirmation bias: When you already like an idea, it's easy to notice evidence that supports it and skip over evidence that doesn't.
• Tracking: Without a system, you'll lose links, forget which threads you've read, and struggle to organize findings into something actionable.

Manual research is a good starting point. But as you get more serious about a direction, the limitations start to compound.

How DemandHunter Approaches Multi-Source Scanning

DemandHunter addresses the manual research problem by scanning multiple public sources at once—Reddit, X, Hacker News, GitHub, YouTube, and others—and returning a structured report.

Instead of opening 30 tabs and taking scattered notes, you get:

• Pain point clusters grouped by theme
• A demand score indicating signal strength
• Opportunity cards translating complaints into potential product directions
• Evidence links back to the original discussions

The value isn't that it finds things you couldn't find manually. It's that it finds them faster, across more sources, and structures them in a way that helps you make a decision—rather than leaving you with a pile of open tabs and a vague feeling.

FAQ

Which single source is best for SaaS ideas? Reddit is usually the best starting point for SaaS because of the volume and variety of discussions. But combining Reddit with Hacker News and G2 reviews gives you a much more complete picture than any single source alone.

How do I know if a pain point is worth acting on? Look for pain points that appear across multiple sources, not just one platform. If the same frustration shows up on Reddit, in G2 reviews, and on X, that's a much stronger signal than a single thread with a few upvotes.

Can I do this research without a paid tool? Yes. Start with the free sources on this list. The trade-off is time and thoroughness. If you're exploring casually, manual research works. If you're making a build decision, a structured tool can help you move with more confidence.

Next Step

Ready to see what pain points exist in your market? Start with a scan that covers multiple sources at once.

Run a demand scan →

Prefer to focus on Reddit specifically?

Analyze Reddit pain points →