Founders & product teams
Find needs worth testing before you build.
Find needs worth testing before you build.
The work at hand
Make the question specific.
Understand current workarounds and switching barriers
Turn observations into a small validation plan
Keep the evidence and its limits together.
A complaint is a lead, not proof of willingness to pay. Keep existing solutions, counterexamples and unknown conditions alongside every opportunity.
Available platforms, fields and coverage are defined in the task scope and capability details.
A fixed example you can inspect
DemoBottle travel mug
The same 6 authored records, viewed from different deliverables. Synthetic material, not a customer case.
What are you working on today?
Next: review sources, scope and availability. Nothing runs from this form.Custom / advanced question
A few useful details
Does an opportunity mean I should build it?
No. The deliverable helps identify the next interview or test. Demand, payment and distribution still need direct evidence.
Will viewing the example change my question?
No. The example keeps its fixed DemoBottle subject and your task draft stays separate. Preparing a scope does not execute it.