Pain Radar
Turn internet complaints into product opportunities
I built Pain Radar.
It scans the internet for what people are actually frustrated about, clusters the complaints into themes, and scores each on real demand and how monetisable it is.
Then it writes you the brief, what to build, and why.
Stop guessing what to make.
→ painradar.co (free weekly digest, no card)
I stopped trying to come up with start up ideas. The good ones were never in my head anyway, they were sitting in other people's complaints.
Here's what I believe after a while of building: the best opportunity isn't a clever idea, it's a problem people are already frustrated about, loudly, in public. Solve a real problem and the money's already waiting on the other side. The hard part was never the building, it was knowing what was actually worth building.
So instead of brainstorming, I built a machine to find the problems for me.
It's called Pain Radar. Every day it scans the places people vent YouTube comments, Google searches, strips the noise, clusters the complaints into themes, and scores each one on how painful it is, how common, and how monetisable. For the ones worth chasing, it writes a one-page brief: what to build, who for, and why now.
The part I like most, I point it at its own data to decide what I build next. I built a layer on top that filters thousands of pains down to the handful a solo dev could realistically ship, scored for how buildable they are and how well they fit my stack. So my roadmap isn't a hunch anymore. The radar picks it.
I'll be honest about where this is: it's early. I'm a solo builder and a vibe coder. I steer the strategy and an AI agent writes the code. There are tens of thousands of complaints and a few hundred scored opportunities in there now, and exactly zero users. I'm growing the data slowly on purpose to keep costs sane, and building the whole thing in public from day one.
The reason I'm sharing it here. My goal is to find the pain so other builders don't have to guess what to make. I genuinely want you to win too, if you're stuck on what to build, that's exactly who this is for.
So I'm curious how the rest of you do it. When you start something new, are you going off gut and a hunch, or something more systematic? What's actually worked for you?
Hey IH,
I'm Jordan, a solo builder from Australia.
Most founders build first, then hunt for users. I flipped it: I built Pain Radar (painradar.co) a machine that scans where people vent, clusters the complaints, and scores them, then writes a brief on what to build and why.
My goal is to find the pain so other builders don't have to guess. I want you to win too.
What's the last thing you were properly frustrated by that no tool solves? I might run it through the radar.
-
1
This is a strong wedge because you are not just helping founders “find ideas.” You are turning messy public frustration into ranked product signals, which is much closer to founder research infrastructure than a normal idea generator.
The part I would pressure-test early is the brand frame. Pain Radar is clear, but it may box the product into “finding pain points” when the bigger direction is broader: market signal detection, opportunity scoring, user complaint intelligence, and build briefs for founders.
That matters before more users, reports, search results, and content start locking in around the current name, especially with painradar.co already adding some friction if this becomes a serious product discovery platform.
Exirra .com would fit the larger direction better because it feels more like a signal intelligence layer for finding hidden demand, ranking opportunities, and turning market noise into build decisions.
-
1
Really appreciate this! "Turning messy public frustration into ranked product signals" is a sharper way to put it than I've managed. Thanks for that.
You've actually pegged where I want it to go, less idea generator, more signal/opportunity intelligence. The pain is the raw input, the real output is the scored opportunity and the one-page build brief, what to build, who for, why now. That's the direction I'm leaning into.
On the name, fair pressure test, and I've felt that tension too. For now I'm keeping Pain Radar because it ties tightly to the core mechanic and the story I'm telling (find the pain, build the thing), and it's early enough that positioning can carry the broader framing under the name. But you're right that it's worth deciding consciously before equity locks in. I'll keep it front of mind rather than drift into it.
Genuinely curious though, when you've rebranded mid-build before, what told you it was the right call vs premature?
-
1
The signal is not “do I like another name better?”
The signal is when the product’s future category and the current name start pulling in different directions.
If Pain Radar stays mostly “find pain points from Reddit,” the name is strong enough. It is clear, memorable, and tied to the mechanic.
But if the product is really becoming opportunity intelligence for founders, with scored demand, market signals, user complaints, and build briefs, then Pain Radar may start feeling like the input, not the company. The pain is only the raw material. The actual product is the decision layer on top.
That is when I’d treat a rebrand as strategic, not premature: before users, reports, SEO pages, screenshots, and word-of-mouth all lock the product into the narrower frame.
I’d pressure-test it very simply: put Pain Radar and Exirra side by side against the category you want to own.
Pain Radar sounds like finding pain.
Exirra sounds more like signal intelligence and opportunity scoring.If the second direction is where you’re actually building, I’d decide that early rather than after the .co, content, and product surfaces are harder to unwind.
-
-
Comment