1
0 Comments

Searching for pain points to build around was itself the pain

Hey IH! First post here — excited to share what I've been building.


Like a lot of indie hackers, I wanted to build something people actually need. So I did what everyone says to do: look for pain points.

I spent hours scrolling Reddit threads, digging through GitHub issues, reading Hacker News comments. Every time I found something interesting, I wasn't sure if it was a real recurring problem or just one person venting. There was no signal — just noise. The search itself became exhausting.

That's when it clicked: searching for pain points is a pain point.


What I built

Devache collects real developer pain points from across the web, scores them by severity (1–10), and uses AI to generate SaaS ideas grounded in actual frustrations.

The pipeline works like this:

  1. Perplexity Sonar queries developer discussions across the web

  2. Claude extracts and structures pain points with severity, category, and metadata

  3. Semantic deduplication merges near-identical issues

  4. You pick a technology + business model, and get 3 AI-generated SaaS ideas backed by the pain data

Right now the database has pain points across 500+ technologies — React, Next.js, Python, Rust, Docker, and more.


Where it's at

Honest answer: early. The data pipeline is working, the idea generator is live, but I'm still figuring out what's actually useful to builders.


My ask

What technology or tool causes you the most pain day-to-day?

And if you try the generator, I'd love to know — does the data feel accurate? Are the ideas actually useful?

posted toAvatar for product Devache
Devache