Someone on r/SaaS built 4 apps on ideas AI told him were great. All 4 failed. His conclusion: the signals were fake.
Thread: Read the Reddit Discussion
So here are ideas from the opposite direction. I ran 5 scans across niches I care about, the engine pulled 60 real complaints, and these are the 5 loudest unsolved problems. Every idea comes with the raw Reddit thread AND the full research report, so you can judge the demand yourself instead of trusting me.
Take them. Build them. I make the scanner, not the startups.
The complaint: Non-technical founders ship an MVP with Lovable or Cursor, then hit a wall. Timeouts, heavy logic jammed into the frontend, and no way to fix it without hiring an engineer.
The gap: A hundred tools help you generate an app. Almost nothing audits and hardens the mess afterward for someone who cannot read the code.
The complaint: Founders losing 5 to 8% of MRR to involuntary churn. Stripe retries are fine, but the dunning emails read like robot receipts and land in Promotions. One founder reports a plain text message alone recovers 30% of failed payments.
The gap: Everyone optimizes retries. The unsolved part is communication: decline-reason-specific messages, SMS-first, priced for indie SaaS instead of scale-ups.
The complaint: Teams running agents in production say traces alone don't explain why the system took a path, eval workflows are full of gaps, and per-agent cost burn is unpredictable. Some are building their own spend caps rather than waiting for a product.
The gap: Tracing exists (Langfuse, LangSmith). Granular cost CONTROL does not: hard per-agent budget ceilings that stop spend the moment the limit hits.
The complaint: Devs say vector search returns what looks similar, but agents need what worked vs what failed. Duplicate memories pile up and agents behave inconsistently. Everyone rebuilds this layer on every project.
The gap: Memory products are appearing, which proves demand. The threads say outcome-aware retrieval and dedup are still open problems.
The complaint: Rankings look stable, traffic is gone. AI Overviews answer the query, CTR collapses on informational pages, and standard dashboards keep telling site owners everything is fine.
The gap: Rank trackers measure a game that is shrinking. Site owners want to know what AI engines actually consume and cite from their pages, and what to do about it.
How this was made: the reports above are straight from PainBase, a scanner I built. It crawls Reddit, HN, Dev.to and X for high-frustration language ("hate this tool", "why is there no", "impossible to") and scores every complaint by severity vs how few solutions exist.
Sixty complaints are evidence of frustration, not willingness to pay. For each idea, add the workaround already in use, who owns the budget, and what the failure costs. Hard agent spending caps look strongest when teams are already building internal controls; the next test is a paid design partner with active agents and a recent cap incident, not another scanner score.
I like that you're treating customer complaints as the starting point instead of product ideas.
The shift from "find an idea, then validate it" to "find recurring frustration, then decide whether it's worth building" feels much more robust. Even if someone never builds one of these exact ideas, that validation process is valuable in its own right.