Check real complaints before using AI for SaaS ideas
Asking AI for SaaS ideas can produce answers that sound confident but are hard to trust. The problems include weak sources, bad , missing signals like Reddit upvotes, and made-up or outdated customer pains. A better method is to pick niche communities by hand, group repeated complaints from the past week, find the exact comments behind them, and only then turn those patterns into SaaS .
The first test looked at construction, an industry the er did not already know. From June 20 to June 27, 2026, the scan covered 1,920 rows from r/Construction, 809 from r/ConstructionManagers, and 422 from r/estimators, for 3,151 rows total. The strongest signal was that construction workers struggle to trace estimate numbers back to drawings, PDFs, , , and s.
Supporting evidence included missing product details being pushed into formal questions, painful manual page renaming, and estimators moving PDF markups by hand.
Key points
- SaaS ideas can sound convincing while resting on weak evidence.
- The proposed method starts with recent complaints in niche communities.
- The construction test scanned 3,151 Reddit rows from one week.
- The clearest pain was tracing estimate numbers back to source documents and s.
- Useful product should come after evidence, not before it.