I spent a month building a tool that reads Reddit/HN forstartup ideas — here's what "real pain" actually looks like
Spent the last month building a tool that surfaces startup
opportunities from Reddit, Hacker News, and X discussions. Solo,
bootstrapped, no team. More data sources on the roadmap —
including user-submitted ones (drop in a CSV of your own
support tickets, for example).
I expected the hard part to be the AI. It wasn't. The hard part
was figuring out which complaints online are actual paying
problems, and which are just people venting into the void.
Four things that surprised me:
-
Pain ≠ demand. Threads where everyone angrily agrees "someone
should build X" almost never convert. Real demand sounds smaller
and more specific — "I currently use Notion + 3 spreadsheets and
it breaks every Tuesday" is a buyable problem. "Why is no one
solving X!" is not. -
The best signals hide in boring subreddits. r/SaaS and
r/Entrepreneur are crowded and contaminated with "I'm building"
posts. Niche subs like r/MedicalCoding, r/SmallFarms, and Etsy
seller communities have 10x less noise and 10x more specific
workflow language. -
HN, Reddit, and X surface very different signals. HN is great
for technical feasibility and early-adopter behavior. Reddit has
the most raw emotional language. X is mostly noise unless you
already know who to follow. -
AI is surprisingly bad at distinguishing "rant" from "need"
out of the box. A generic "summarize this thread" prompt will
tell you every thread is a goldmine. I had to build explicit
scoring for pain signal, demand signal, and willingness-to-pay
before outputs got useful.
What I built: a platform called MonetScope (free beta right
now). It scores opportunities across pain / urgency / market
size / execution difficulty, and each opportunity comes with the
actual Reddit quotes that sparked it, plus a rough MVP plan.
Still 20 things to fix.
Where I am: a small batch of early users, honest feedback is
what I want most right now — not traffic.
Genuine question for the room: what's the worst "validated idea"
you ever built — one where the online discussion looked like
obvious demand, but the market turned out to be hollow? Trying
to get better at spotting that specific trap.
The distinction between 'frustrated' and 'actually paying to fix it' is the most important filter in idea validation. People complain about hundreds of things - only a few of those complaints generate enough friction to motivate spending.
The tell is always: what are they doing instead? If they have a workaround - a spreadsheet, a manual process, three duct-taped tools - that's the signal. The workaround is proof of willingness to invest effort. Swap the workaround for a product and you have a customer.
Reddit/HN mining is good for finding the frustration layer. The next step is finding the workaround layer: 'what do you do when X breaks?' - that's where the real product brief lives.
Applied this to a Solopreneur OS I'm building. The pain wasn't 'solo founders want a Notion template.' It was 'solo founders are running CRM in a spreadsheet, projects in Trello, revenue in Stripe, and decisions in their head, and things keep falling through.' The workaround was the product spec.
What was the most surprising 'real pain' pattern you found - a complaint type that showed up way more than you expected?
The workaround layer = product spec is the cleanest framing I've heard. Going to steal that.
Most surprising pattern from the DB so far: founders running 'meta-stacks' to track their own AI tool subscriptions. Spreadsheet with 8-15 columns (tool name, monthly cost, what task it replaces, last used date, cancel-by date). Showed up in ~40 independent posts across r/SaaS and HN over 2 months. Nobody's calling it a market — but the workaround is identical across every post.
How's Solopreneur OS handling the "decisions in their head" layer? That's the part I'd assume is hardest because there's no clean spreadsheet workaround to begin with — it's just lost-in-head.
Really appreciate this kind of systematic approach to idea validation. The "frequency × intensity" mental model you're implicitly using is solid — a problem people mention once is noise, but one they keep coming back to is signal.
One thing I'd add from experience: look for problems where people have already built workarounds (spreadsheets, duct-tape automations, manual processes). That tells you the pain is real AND that people are willing to invest time to solve it. Did you find many ideas in that category vs ideas where people just complained without acting?
Strong addition — the workaround filter is probably the single biggest methodology improvement.
Rough split from what I've seen: ~60-70% of opportunities surfaced are 'pure complaint' (people venting, no documented workaround), 20-30% have explicit workaround signals. The latter category produces dramatically higher-quality opportunities — the workaround constraints often dictate the MVP spec better than any survey would.
Adding 'workaround mentioned: y/n' as a scoring dimension after reading your comment. What's your validation stack look like for WcardSaaS — are you mining for workaround signals or working from your own founder network?