DEV Community

Maxime Bignolet
Maxime Bignolet

Posted on

I built a tool to spot real product pain without reading forums for hours

Like a lot of founders, I kept starting projects from vague ideas, Twitter vibes, or half-remembered complaints.

The problem wasn’t a lack of ideas — it was signal extraction.

Reading forums manually is slow, noisy, and mentally draining:

- 90% of posts are advice, opinions, or meta discussions

- the real pain is buried in a few frustrated sentences

- after 30 minutes, you don’t know what actually repeats
Enter fullscreen mode Exit fullscreen mode

So I built I Wish There Was.

It scans recent public forum discussions indexed by search engines, filters for explicit everyday frustrations (time wasted, confusion, friction, costs), and clusters them into clear problem statements.

For each cluster, it outputs:

- a concise problem title

- a short summary

- who is affected

- why it hurts

- verbatim user quotes

- a recurrence level (low / medium / high)
Enter fullscreen mode Exit fullscreen mode

Important:
This is not market validation.
It doesn’t tell you what to build or guarantee demand.

It’s a signal tool — meant to help you decide what’s worth exploring next, instead of starting from a blank page.

The UX is intentionally simple:

- pick topics (and optional keywords/sources)

- choose a time range (7 / 14 / 30 days)

- run a scan

- get results in minutes
Enter fullscreen mode Exit fullscreen mode

Pricing is credit-based (1 free scan, then small one-shot packs).
No subscription — this is a tool you use at a decision moment, not every day.

I’m sharing this here to get feedback from builders:

- Does this feel useful in your workflow?

- What would make the output more actionable without turning it into “fake validation”?

- Where would you personally use something like this?
Enter fullscreen mode Exit fullscreen mode

https://i-wish-there-was.com/

Happy to answer questions or explain how it works under the hood.

Top comments (1)

Collapse
 
dogemosjosh profile image
Josh Lee

To answer your question about workflow: this feels incredibly useful for the 'Ideation' phase. I personally would use this to scan for frustrations around SEO tools and social analytics. In my project, X-AlgoVision, we manually scanned for user complaints about 'shadowbans' before automating it. If your tool can cluster those 'I wish there was a way to check de-boosting' complaints, it’s a goldmine for devs.
​Suggestion: To make it more actionable, maybe add a 'Solution Gap' score—how many people are asking for it vs. how many existing tools they mention? Great work on the 'No Subscription' model, very founder-friendly!