u/Leading-Length-8024

I’m trying to get better at early validation and would love to hear how others handle this.

The hard part for me is the stage before you have users, customers, or meaningful analytics.

At that point, most “validation” seems to become one of these:

• asking friends, who are too polite
• reading random Reddit threads
• checking competitors
• making a landing page
• pretending waitlist signups equal demand
• doing customer interviews, if you can find the right people

I’m especially interested in how people separate real pain from noise.

For example, if 20 people complain about a workflow online, how do you decide whether that means:

1. real business opportunity
2. small annoyance
3. loud minority
4. already solved problem
5. something people complain about but won’t pay for

Do you use any structured process for this?

Or is early validation always partly messy and instinctive?

I’m building a small product research tool for micro-SaaS founders.

The idea came from my own frustration: I can build, but I’m not always good at knowing whether something is actually worth building.

So the product is intentionally narrow.

You put in a product idea, and it generates a research report based on recent public conversations. The report tries to answer:

• is this a real pain or just a founder fantasy?
• who has the pain?
• how are they solving it today?
• what competitors or alternatives already exist?
• are there any buying signals?
• what MVP would be small enough to test first?

The part I care about most is that every conclusion has evidence behind it. Not just “AI says founders need this.” More like: claim, snippet, source link, confidence level.

I’m not trying to build a huge market research suite. More like a “should I spend the next 2 months on this?” report.

For micro-SaaS builders here: would this help you, or do you already have a research process that works well enough?