Skip to content
Newsletter signup is a demo: no addresses collected. Account access is real. University checkout is open; Operate is not on sale yet.
Back to the Journal
ValidationEditorial preview · Not yet published

Validating demand before you build

How to look for honest evidence that a problem is worth solving — and how to read weak signals without fooling yourself.

By Wildtools Editorial

A publication date will appear here once this article is genuinely published.

Enthusiasm is not evidence

People are polite. When you describe an idea, many will say it sounds great — and mean it — without any intention of paying for it. Compliments feel like progress but teach you almost nothing.

The signals that matter are behavioral: what people did the last time the problem occurred, what workaround they use today and what that workaround costs them in time, money or frustration. Past behavior is imperfect evidence, but it beats hypothetical enthusiasm every time.

Ask about the last time, not the future

Instead of "would you buy this?", ask "when did this last happen to you?" and "what did you do about it?". A person who cannot recall a recent occurrence probably does not feel the problem strongly. A person who describes a painful, recent, recurring workaround is telling you something worth hearing.

Keep the conversation neutral. If your questions lead people toward your solution, you are collecting agreement, not evidence.

Set your stop rule before you start

Decide in advance what evidence would justify continuing and what would make you pause. For example: continue if two of three conversations describe recent recurring friction; pause if the existing workaround turns out to be easy and cheap.

Writing the stop rule first protects you from the most expensive bias in side businesses: falling in love with your own idea and reinterpreting every weak signal as encouragement.

A directional signal is not a forecast

Three good conversations can tell you a problem is real for a few people. They cannot tell you how large the market is, what people will pay or whether you can reach them at a cost that works. Treat early validation as a decision aid, not a prediction.

The Opportunity Radar in Wildtools Operate scores how prepared an idea is for this kind of testing — its inputs and assumptions, never market demand. Use it to see what you still need to learn, not to certify an idea as promising.

Cap the cost of learning

Validation should be cheap. Public research, a handful of respectful conversations and a small manual test can happen in a few hours over a couple of weeks, with little or no spending.

If your validation plan requires building the product first, it is not a validation plan. Find the smallest experiment that could prove you wrong, and run that one first.

Get a short idea like this every morning

The free Wildtools newsletter is the daily companion to these longer reads. The signup below is a demo preview — no email is collected or sent.

Free · Every morning · No spam · Unsubscribe anytime

Demo only · No emails collected · No subscription created

Wildtools Operate

Want the guided version?

Operate has guided Launchpad examples with worksheets and milestones, plus University. It remains a paid offer in preview; nothing can be purchased yet.

Explore Operate