Validation · 2026-06-06

How to Validate Demand Before You Build Anything

The cheapest product to kill is the one you never built. Once you have written code, designed screens, and told your friends what you are working on, your judgment gets cloudy. You start defending the idea instead of testing it. So the smartest move is to prove demand before you build, while you can still walk away cheaply.

Validating demand is not about asking people if they like your idea. People are kind, and "that sounds great" costs them nothing. Real validation is about watching what people already do, already pay for, and already complain about, then putting a small offer in front of them and seeing if anyone reaches for their wallet.

Start with a problem people already pay to solve

The safest ideas attack problems that people are spending money on right now, just badly. If a problem already has a budget, you do not have to convince anyone it matters. You only have to convince them you solve it better.

Look for these signals:

A field with zero competitors is usually a warning, not an opening. It often means nobody will pay. A field with several flawed competitors is a gift, because the demand is proven and the door is open.

Go where the complaints live

Before you ask anyone anything, go read what they already say in public. Reddit threads, review sites, support forums, and comment sections are full of people describing their problem in their own words, unprompted and unfiltered.

Search for the problem, not your solution. Read fifty posts. Write down the exact phrases people use, what they have already tried, and what makes them angry. This becomes the language of your landing page and your sales pitch. When you describe a problem in the customer's own words, conversion gets easier because they feel understood.

Talk to ten real people, not your friends

Friends and family will lie to protect your feelings. You need ten people who actually have the problem and no reason to be nice.

Keep the conversation about their past, not your idea. Ask:

If they have never tried to solve it and never spent anything, the pain is too small. People who have already paid for a bad solution are your gold. They have proven they will open their wallet for this problem.

Put up a real offer and ask for commitment

Conversations reveal interest. Money reveals intent. To find intent, you need an offer people can say yes to with something real.

Build a simple landing page with a clear promise, a price, and a button. The button can take a deposit, a pre-order, or at minimum a high-friction signup like a card on file or a booked call. Drive a small batch of the right people to it. Then count who commits, not who clicks.

Decide your pass mark before you launch. For example: out of 60 targeted visitors, at least 10 leave their email and 3 pay a deposit. Write the number down so you cannot rationalize a weak result later.

Read the result and respect it

When the test is done, hold it against the line you drew. A clear yes means build the next small step. A clear no means the offer, the audience, or the problem needs to change before you write any code.

The hardest part is honesty. A few warm replies are not a yes. One deposit out of a hundred visitors is a no, even if that one person loved it. The whole reason you validate first is to get a verdict you can trust while changing course is still free.

Done right, this whole process takes a week or two and costs almost nothing. Compare that to six months of building a product the market quietly declines. Validation is not a delay before the real work. It is the work that decides whether the rest is worth doing.

If you want the research done for you, DemandSonar scan mines real Reddit demand and tears down competitor reviews, then returns an ICP, an offer, channels, and a daily plan, so you can prove demand before you build instead of guessing.

Stop guessing. See if anyone wants your idea.

Run a free scan