r/VibeCodeDevs • u/According_Good_6158 • 13h ago
11 things i learned after 12 months of using AI to find startup ideas instead of guessing
a year ago i was building random things based on gut feelings. most of them flopped. then i started using AI to actually research what people want before writing a single line of code.
these are the lessons that stuck.
- the best ideas aren't ideas at all. they're complaints. i stopped looking for "cool things to build" and started looking for people who are angry about existing tools. raw frustration = money in motion.
- one-star reviews are worth more than any market report. i've gone through thousands of negative reviews on g2, capterra, and app stores. probably 40% of them aren't about bugs. they're about missing features the company will never build. those gaps are your entry point.
- reddit threads tell you exactly what to build. someone writes "i wish there was a tool that..." and 47 people upvote it. that's not a shower thought. that's a purchase intent signal sitting in plain text.
- the "boring problem" filter works every time. i wasted months chasing ai wrappers and consumer apps. the ideas that actually converted to paying users were things like invoice reconciliation, review monitoring, niche data aggregation. nobody posts about these on twitter. they just quietly pay $99/month.
- validation speed matters more than idea quality. i used to spend weeks researching one idea. now i can check demand signals across multiple platforms in under an hour. most ideas die in the first 10 minutes of real research, and that's a good thing.
- competitor pricing tells you the floor, not the ceiling. if 5 tools charge $29/month for something and they all have bad reviews about the same missing feature, you don't build a cheaper version. you build the version that actually solves the complaint and charge $79.
- upwork job posts are an underrated signal. when companies hire someone $25/hour to do a repetitive task manually, that's a SaaS waiting to happen. i found 3 viable ideas just from browsing "data entry" and "virtual assistant" job listings in niche industries.
- the biggest waste was building before talking to anyone. i built two full MVPs before discovering the target users didn't care about the problem i picked. both times the research would have killed the idea in a day. i spent months instead.
- multi-source validation beats single-source conviction. a complaint on reddit means nothing alone. the same complaint on g2, on app store reviews, and on upwork job posts, that's a pattern worth building for.
- most "AI startup ideas" are just feature requests for existing products. i analyzed hundreds of ai-related discussions. the majority aren't new product categories. they're automations that bolt onto tools people already use. build the integration, not the platform.
- the research itself became my unfair advantage. while other founders are guessing what to build next, i already have a pipeline of validated problems ranked by demand. my hit rate went from maybe 1 in 8 to closer to 1 in 3.
i got tired of doing this research manually so i built something that uses MCP to pipe problem data from reviews, reddit, and job boards directly into my workflow.
so these days i start from a repo that groups complaints by how many different companies repeat them, then go read the original threads myself.
but honestly the core lesson is simple. stop building what sounds cool. start building what people are already paying to solve badly.
what's the most unexpected place you've found a real product idea?



