Separate problem evidence from product praise
Someone saying your idea sounds good is weaker than someone independently describing the problem. Collect evidence that exists before your pitch enters the conversation.
Validation gets stronger when it starts with observable behavior: people asking for help, searching for alternatives or describing a painful workflow in public.
Someone saying your idea sounds good is weaker than someone independently describing the problem. Collect evidence that exists before your pitch enters the conversation.
Save the original source, date and a short exact quote. The wording people use often teaches you more about positioning than a generic survey answer.
A conversation can perfectly match your positioning while still requiring a feature you do not support. Treat capability fit as its own gate rather than inflating a relevance score.
If none of the conversations are strong enough, return nothing. Forcing a lead makes the dashboard look better while making the product less trustworthy.
Ask whether the evidence changes what you build, who you target, or how you describe the problem. Validation is useful when it changes a decision, not when it only produces a reassuring score.
The method on this page works. Running it every weekday is a job. The Daily 5 does the reading and sends you five real conversations where someone is asking for something that doesn’t exist yet — each one with its source, so you can judge it yourself.
Free. One email a day. Unsubscribe in one click.
Seek starts from your product and ICP, surfaces public conversations, explains why they match, and keeps the original source inspectable.
Find demand signals ↗