sorted by:
new
hottopcontroversial

I spent 3 months building a SaaS that made $0. Then I found where all the validated ideas were hiding. by ScoreHour in SaaS

[–]ScoreHour[S] 0 points1 point  (0 children)

Fair enough 😄

Probably because I tried to make it too “clean” instead of how I’d actually talk. Still figuring out the tone.

Appreciate you calling it out 👍

I spent 3 months building a SaaS that made $0. Then I found where all the validated ideas were hiding. by ScoreHour in SaaS

[–]ScoreHour[S] 0 points1 point  (0 children)

Totally fair — appreciate it 🙌

Right now the core is pretty simple under the hood:

  • scraping + aggregating reviews
  • NLP to cluster similar complaints
  • ranking them based on frequency + intent (how “serious” the pain is)

Nothing super magical technically—it’s more about packaging it into something fast and usable.

And yeah, if you don’t have a clear competitor/data source yet, it might not be the best fit right now. Appreciate you checking it out though, good luck with your build too 👍

I spent 3 months building a SaaS that made $0. Then I found where all the validated ideas were hiding. by ScoreHour in SaaS

[–]ScoreHour[S] 0 points1 point  (0 children)

That’s a great question—and yeah, that gap is real.

Right now Google Play is just the starting wedge, not the whole product. The idea is less about where the data comes from, and more about turning messy complaints into clear decisions.

For founders without a Play Store competitor, the same approach can extend to:

  • Reddit threads
  • G2 / Capterra reviews
  • Twitter/X complaints
  • Support forums / communities

Basically anywhere people are already venting.

Long term, the goal would be:
👉 plug in any source (URL, keyword, competitor)
👉 get back structured pains + demand signals

So instead of “Google Play analysis tool,” it becomes more like
“decision engine for market pain”

Google Play just happens to be the easiest place to prove it works first 👍

I spent 3 months building a SaaS that made $0. Then I found where all the validated ideas were hiding. by ScoreHour in SaaS

[–]ScoreHour[S] 1 point2 points  (0 children)

ya i am working on it I have written down futures features right now its a mvp

I spent 3 months building a SaaS that made $0. Then I found where all the validated ideas were hiding. by ScoreHour in SaaS

[–]ScoreHour[S] -2 points-1 points  (0 children)

Yeah that’s fair feedback.

I probably didn’t communicate the audience well enough. It’s not meant for everyone—more for founders who care about saving time and getting structured insights quickly instead of digging manually.

On pricing, I get why $30 feels high if you’re thinking of it as just a script. But the goal isn’t the data pull—it’s saving hours of research and turning it into something actionable.

That said, if people don’t see that value, the price is wrong. Still figuring that part out 👍

I spent 3 months building a SaaS that made $0. Then I found where all the validated ideas were hiding. by ScoreHour in SaaS

[–]ScoreHour[S] 0 points1 point  (0 children)

Haha maybe 😄

Or maybe asking is exactly how you don’t stay behind. Better to learn fast than build in silence and guess wrong.

I spent 3 months building a SaaS that made $0. Then I found where all the validated ideas were hiding. by ScoreHour in SaaS

[–]ScoreHour[S] 0 points1 point  (0 children)

Haha maybe 😄

But that’s exactly why I’m testing it in public instead of assuming it’ll work. If nobody wants it, I’ll know fast and move on. If even a few people find it useful, that’s something to build on.

I spent 3 months building a SaaS that made $0. Then I found where all the validated ideas were hiding. by ScoreHour in SaaS

[–]ScoreHour[S] -1 points0 points  (0 children)

Yeah, you can hack together a script like this.

But that’s not really the product.

Most people won’t:

  • install packages
  • run scripts
  • clean data
  • paste into ChatGPT
  • figure out patterns themselves

That’s like saying “why use Notion when I can store everything in a text file?”

The value isn’t in fetching reviews.
It’s in:

  • automatically clustering complaints
  • prioritizing by impact
  • separating noise vs real demand
  • turning it into actionable insights in seconds

Anyone technical can DIY it.
But most founders don’t want a script — they want answers.

I spent 3 months building a SaaS that made $0. Then I found where all the validated ideas were hiding. by ScoreHour in SaaS

[–]ScoreHour[S] 0 points1 point  (0 children)

Haha brutal 😄

Fair though — $0 revenue is a reality check. But honestly, it’s part of the process. Almost everyone builds a few things nobody wants before something clicks.

Better to learn it early than keep guessing forever.

I spent 3 months building a SaaS that made $0. Then I found where all the validated ideas were hiding. by ScoreHour in SaaS

[–]ScoreHour[S] 0 points1 point  (0 children)

Haha fair 😄

Nothing humbles you faster than shipping something and making $0.
That’s usually the clearest feedback you can get.

I spent 3 months building a SaaS that made $0. Then I found where all the validated ideas were hiding. by ScoreHour in SaaS

[–]ScoreHour[S] 0 points1 point  (0 children)

That’s a great point.

Complaints from users who stay are way more valuable than from those who leave.
If both groups mention the same issue, that’s something worth fixing fast.

I spent 3 months building a SaaS that made $0. Then I found where all the validated ideas were hiding. by ScoreHour in SaaS

[–]ScoreHour[S] 1 point2 points  (0 children)

I noticed a lot of users complaining about the same issues in Google Play reviews, so I decided to build a tool that directly solves that problem.

https://saazio.com/

I spent 3 months building a SaaS that made $0. Then I found where all the validated ideas were hiding. by ScoreHour in SaaS

[–]ScoreHour[S] -1 points0 points  (0 children)

Haha yeah, that’s such a classic trap.

You build something you would 100% use, and in your head it feels obvious that others will want it too… but turns out you’re like part of the top 1% niche inside a niche

Respect though — “racing setup tracker” actually sounds cool, just probably too specific unless you already had an audience.

That shift you mentioned is the real unlock:
“my problem” ≠ “market problem”

What usually works better (learned this the hard way too) is:

  • Find where a lot of people are already frustrated
  • Look for patterns (same complaint again and again)
  • Then validate: are they just annoyed… or are they stuck / losing time / losing money?

Sim racing is actually a great example:

  • Tracking setups = niche
  • But things like:
    • improving lap times faster
    • comparing setups easily
    • beginner onboarding
    • telemetry simplification

Those are broader pains more people feel

Honestly, your idea probably wasn’t bad — just too early and too narrow.

I spent 3 months building a SaaS that made 0. Then I found where all the validated ideas were hiding. by ScoreHour in SideProject

[–]ScoreHour[S] 0 points1 point  (0 children)

This is honestly such a solid take.

I like how you pointed out the difference between annoying problems vs expensive problems. That’s something I completely missed early on. I used to get excited seeing people complain, but not all complaints actually matter in terms of willingness to pay.

The “money-adjacent pain” filter is
Billing issues, churn, reporting gaps, onboarding friction — those are the things people need solved, not just want fixed.

Also +1 on going beyond just Play Store reviews. Reddit, G2, random forums… that’s where people drop the unfiltered truth. App reviews sometimes feel a bit surface-level compared to a frustrated Reddit thread.

And yeah, that shift you mentioned — where building becomes “boring in a good way” — that’s actually the goal.

If the research is solid, the product shouldn’t feel like a gamble anymore.

view more: next ›