
ideaFast
Build what people actually want.
Every day I see founders asking the same question:
"How do you find startup ideas?"
I've tried a lot of approaches, but I keep coming back to Greg Isenberg's advice: don't look for ideas, look for recurring complaints.
The problem is that doing it manually takes hours.
So I built IdeaFast.
It analyzes Reddit discussions, groups similar problems together, scores recurring pain, and keeps every insight linked to the original Reddit posts so you can verify everything yourself. It can even suggest startup ideas based on those problems.
I'm still improving it, and I'd genuinely love feedback from fellow builders.
What would make a tool like this more useful for you?
I kept seeing builders (including myself) struggle with the same question:
“What should I build?”
Most of us end up copying something that already exists, or building based on assumptions.
But people are already talking about their problems every day on Reddit.
So I built IdeaFast to turn those conversations into something useful.
You pick the subreddits you care about. IdeaFast finds recurring customer pain, clusters and scores it, and links every pain point back to the original Reddit discussions. You can then turn the strongest problems into startup ideas.
The idea is simple:
Don’t start with an idea. Start with a real problem.
Would love to hear how other indie hackers currently find problems worth solving.
I’m still improving IdeaFast, so I’d genuinely love your feedback. What would you change or add?
2 Likes
3 Comments
3 Comments
-
1
I'm curious what made you decide recurring pain is a better starting point than founder intuition.
Did you notice ideas changing once you could trace them back to multiple conversations instead of a single discussion?
-
1
Yeah, that was the main reason. Founder intuition can point you in a direction, but recurring pain gives you a stronger signal that the problem isn’t isolated.
And yes, seeing the same pain across multiple conversations often changes the idea. You start building around what keeps coming up, rather than what one person happened to complain about.
-
1
Appreciate the context.
The shift from building around a single opinion to recognizing repeated patterns is the interesting part.
Would be good to understand how you're applying that process as you evaluate ideas.
What's the best email to reach you on?
-
-
About
I built IdeaFast because I struggled with what to build. It connects builders with real customer pain and conversations, so they can build what people actually need.


3 Comments
You’ve been iterating on IdeaFast for a few weeks now.
What have you learned from people actually using it that you didn’t know when you made the first post in July?
I really focused on positioning, and it was the first major lesson for me. I removed all the clutter and just focused on one service I'm offering and selling the result. I implemented a demo on the homepage and made the product clearer.
Although I'm offering a free trial, it's backed by a credit card because I'm incurring a real cost and didn't want it to get abused by casual users. But I don't know if I've built enough trust for customers to provide their credit card details. That's something I'm still figuring out.
Your review would really matter to me. Thanks for asking.
That’s a useful tension to investigate, especially because the credit-card requirement changes the trust threshold even if the trial is free.
I’d rather continue that conversation outside the thread than unpack the trust question here. What’s the best email to reach you on?