We launched The Eureka Database yesterday, and honestly I did not expect to feel this much.
I did not build this to launch it. I made it for myself and used it quietly for a few weeks to decide what to work on next. Sharing it was a late call, and the response has been way more than I expected.
Thank you to everyone who upvoted, commented, tried it, and told me where it falls short. We made the top 10, finished 5th place in Vercel Day, and we even got featured in Product Hunt's newsletter, The Leaderboard, in an edition called "Steal your next startup." You can read it here: https://www.producthunt.com/news...
Announcing the launch of The Daily Eureka, our free newsletter!
Every morning you get one validated startup idea in your inbox. You see the problem, who has it, the market, how it could make money, and the exact Reddit thread it came from. It's one concrete opening you could genuinely run at, and it takes about 30 seconds to read.
Hey Product Hunt!
Once again, thank you for overwhelming support and reviews these past few days. The community is coming together and co-founder relationships are forming (which melts my heart as a founder myself).
Love the concept. As someone who builds products, I've definitely fallen into the trap of building something because it sounded exciting instead of validating demand first. Mining real Reddit discussions for recurring pain points, then turning them into actionable specs with MCP integration, feels like a much more practical workflow. Wishing you a successful launch, Jeremy! 🚀
@jeremy_galang This is actually something that I was looking for recently. Are you considering Quora as well? There are a lot of threads there where people directly ask for ideas or describe a gap. This might be a good additional source.
@alieksia Quora is genius! Thank you, Anastasiia. I'll be adding that into our list of sources :)
@jeremy_galang Congrats on the launch, Jeremy! That Founder story hit close to home. "AI let me waste weekends faster" might be the most honest sentence I've read on PH this week.
What I like is you're solving the part most people skip: knowing if anyone's annoyed enough to want the thing.
The part I'd watch for is that repeating complaints prove people are frustrated, and that's a great place to start. But it doesn't yet prove someone will pay a specific price for your specific fix. Different validation, still worth doing, just a different mile of the race.
"I could waste weekends faster" hit a nerve, I'm on the other side of that right now, built the product first and I'm doing the demand-validation work in reverse. One thing I'd push on: a repeated complaint proves the pain is real, but people complain about plenty of things they'd never pay to fix. Does the database distinguish "loud problem" from "monetizable problem" beyond listing competitors who charge? That gap is where most idea-mining tools miss.
@cannetjam Thanks Kenneth! Good question, and it's the thing we spend the most time on.
We don't really weigh how loud a thread is. What moves the needle is whether someone's already spending time or money on a workaround, so "I wish this existed" barely registers, but "I've tried three tools and I'm still stuck in a spreadsheet" scores high. Whether competitors already charge is a smaller signal on top, it doesn't decide much on its own.
Half of the good indie products started as someone's Reddit complaint anyway, you just made the pipeline official. How do you filter complaints that are loud from complaints people would actually pay to fix? Congrats on the launch
@alex_tomilin Hey Alex! Couple things that actually do the work here:
A single loud thread is almost a red flag for us. The way the math works, upvotes get put on a log scale, so going from 50 to 5,000 upvotes barely moves the score, one viral rant is usually just one bad week for a product. Frequency is its own separate input though, so the same complaint quietly recurring across different subreddits over months counts for way more than one big thread.
Before any of that, there's a filter that reads the actual language of the post. It's looking for phrases that signal a real job-to-be-done, things like "alternatives to X," "what do you all use for," "still doing this in a spreadsheet," and it throws out pure venting and "someone should fix Facebook" posts before they ever become an idea.
Then whether people would pay is its own score, blended from a few things, how severe the pain is, how often it recurs, and willingness-to-pay signals, each weighted separately so upvotes can't fake it. Recency plays in too, we only pull from the last year so a pain that fizzled out won't surface.
Thanks for the kind words on the launch :)
would love to see a freshness score on each idea so we know how recently the underlying complaints popped up, since some pain points fizzle out fast and others keep showing up year after year
@ceyda299740 Great idea, Ceyda! Right now we only pull threads from the last year and surface the most recent ones first, so everything in there is at least reasonably fresh. But a visible freshness score is better, it'd let you tell a pain point that's been building for years apart from one that just spiked last week. Adding it to the list. Thanks!
I have shipped over 30 projects and my problem was never building, it was picking ideas nobody asked for, so this speaks to me. One thing I keep wondering though. If hundreds of members see the same top idea with the same build spec, do we all end up shipping the same product? Any way to see how many people already pulled a spec?
@abdullah_javaid3 You're 100% right, Abdullah. Under the hood we already only pull from the last year and rank the newest complaints first, so nothing's coming from a five year old thread. A trend signal on the idea itself is the better version, whether the complaint is picking up or fading, and whether the profitable players are actually growing. Puts it right in front of you instead of asking you to trust it. On the list :)
@jeremy_galang Good to know the mining already leans fresh, that removes the stale thread worry. The trend signal on ideas sounds like the right move. Still curious about the other half though, can I see how many members already pulled the spec for an idea before I commit a weekend to it?
finally a tool that skips the brainstorming step and gets straight to building. i pulled a saved idea over mcp and it dropped the schema into my agent without me touching a prompt
Funny timing, I spent this morning digging through Reddit threads about client content chaos for exactly this reason. Though my product came from pain I lived myself, not a database. How do you tell a loud complaint from one people would pay to kill? Volume alone seems like it'd surface a lot of venting.
@vladimir_iudin true as person solve his own problem or aspiration than the idea book. But this may give you validation, that how many other also facing the same problem.
Thank you for the kind words, Fajar! :)