How to validate product demand before building more features
Look for repeated evidence of a problem and a meaningful commitment to your proposed solution. Compliments, likes and a large waitlist can be useful signals, but they do not answer whether someone needs the product enough to adopt it.
This process works before a launch and after one. If you already built the product, use it to choose the next experiment rather than treating the time spent building as proof of demand.
Start with a real task
Paul Graham's advice on ideas is to “look for problems, preferably problems you have yourself.” That is a starting heuristic, not proof that your own problem represents a market. How to Get Startup Ideas.
Name a person, a situation and the job they need done. Replace “people need productivity” with something inspectable, such as a freelancer collecting approved hours for an invoice.
Ask about the last occurrence
Ask what happened the last time the person faced the problem. What did they use? Where did the process fail? What did it cost in time, money or frustration? Who decided which tool to use?
Avoid leading questions such as “Wouldn't it be helpful if this were automatic?” People can agree with a convenient hypothetical without having any intention of changing their workflow.
Offer a small, honest test
Choose a pilot, trial task, demonstration or paid service that tests the core value. Be clear about what exists and what is still manual. Do not disguise an illustrative animation as a working feature.
| Signal | What it tells you | What it does not establish |
|---|---|---|
| A compliment | The idea sounds appealing | Adoption or willingness to pay |
| A contact request | Interest in learning more | Product fit |
| Time spent trying a real task | Willingness to investigate | Continued use |
| A paid pilot | A purchase under that offer | A scalable market |
| Repeat use | Ongoing value for that user | Broad demand across audiences |
Make the offer easy to inspect
Use a clear page, genuine example and one next action. If the task is hard to explain, a recording can show it. If you need a short branded introduction, Teasr lets you use the public page as the brief and review a promo without building a video-editing workflow. Presentation helps communicate the hypothesis; it does not validate it by itself.
Decide in advance what you will change
Write down which evidence would make you continue, narrow the audience or change the offer. Keep a record of refusals as well as positive responses. Several people liking the design does not cancel a repeated objection about the core task.
For turning the learning into outreach, see finding first paying customers. For the broader sequence, see a first-month marketing plan.