Validate Market Demand Before You Build or Buy Ads

01What actually counts as evidence of market demand?

Demand is evidence that someone will give up something to solve the problem, offered without you asking for it. Grade every signal on two axes: whether you prompted it, and whether it cost the person anything. Only unprompted, costly signals are demand. The rest is interest, and interest is free to produce in unlimited quantities.

This sounds pedantic until you notice that almost every activity in the standard playbook produces prompted, free responses. You email a survey and someone answers it. You book a call and someone is encouraging on it. You buy traffic and someone types an email into a box. You initiated each exchange and the other person spent nothing, so the response tells you about your prompt, not their problem.

The sharpest statement of this came as a throwaway reply on a shutdown postmortem, and it contradicts the benchmark the highest-ranking guides publish.

Unsolicited-curious is a better unit than any conversion rate, because it cannot be bought. You can buy a signup. You cannot buy a stranger deciding, on their own initiative, that this might be worth money to them. Here is the full grid.

Two of those rows are free and still count, because you did not prompt them. Cost is one way to filter out politeness. Not having asked is the other, and it is cheaper.

02What do founders mistake for demand?

The failure mode is not laziness. The recommended activities produce numbers, and numbers feel like evidence. One postmortem is unusually precise about the arithmetic: $1,078 on ads and 226 registered users, roughly $4.77 each, and no willingness to pay consistently. The signups were real. They were the wrong measurement.

Compare that to what the pages ranking for this question tell you to do. The most comprehensive recommends a landing page, a few hundred dollars of ads, and treating 3% to 5% email signup as a validation benchmark. That benchmark is a fact about copy and traffic quality. It is the same instrument that produced those 226 registrations, and no guide warns you that hitting it proves nothing about willingness to pay.

The second thing founders mistake for demand is agreement. The people around you optimise for your mood, not for accuracy, and they do it convincingly.

The third is logical coherence. The postmortem names it directly: the founder assumed the problem was strong because the idea made sense logically. A use case a reasonable person agrees is useful is not the same as a task somebody currently loses money or hours to. Coherence is the cheapest thing in a business plan and the least predictive.

03Where does the real signal come from before you build?

Mostly from records that already exist. The unprompted evidence you need was generated by other people, for their own reasons, before you had the idea. Three corpora carry almost all of it, and the best answer in these threads reads all three at once rather than trusting any one alone.

The triangulation is the point. A public complaint proves annoyance. A one-star review of an incumbent proves annoyance from someone who already paid to fix it. A job posting whose duties are your feature list proves a company converted the problem into salary, the strongest of the three, because payroll is the least reversible commitment a business makes.

Search demand belongs alongside them and is the cheapest check on the list. The top reply on the postmortem makes the case in two lines: always check the search keywords first, because it is five minutes of work that could save you months. Note its limit. Volume in the language of the problem means people go looking; silence means either no demand or no vocabulary yet, and the number cannot tell you which.

None of this requires a product, a landing page or a budget. It requires reading, which is why founders skip it. Our companion guide on mining complaint threads for product ideas covers the pattern matching in more detail.

04Can you validate demand by spending on ads?

No, and the confusion is structural rather than careless. Ads answer a question about reach and cost: given an audience you can target and a message you can write, what does it cost to get one of those people to act? That is a channel question. Whether the problem hurts enough to pay for is a different one, and no budget converts one into the other.

The postmortem is a clean worked example. The third mistake it names is traffic: the core keywords had lower search volume than expected, which made paid acquisition hard to scale. The product being interesting and the channel being viable were separate facts, and the ad spend found the second one at full price after the build was finished.

The sequencing that avoids this is boring and rarely stated on the pages that rank. Establish the problem from records you did not create. Establish that one person will pay, ideally by delivering the outcome by hand. Only then buy traffic, to answer a cost question against a number you set in advance. A more grounded guide in this category frames the same idea as triangulating what people say, what they search for, and what they already do, with conversations doing the work that a spreadsheet cannot.

05What does a costly, unsolicited signal look like in practice?

Small, specific and uncomfortable to ask for. That last property is why founders run traffic instead. The strongest version is asking for money before the product exists, which sounds premature and is the entire point.

A discounted pre-sale, a paid pilot, a letter of intent and a manual delivery of the outcome are versions of one instrument. Each converts an opinion into a commitment with a cost attached. The discount is not a concession, it is the price of finding out early.

Friction works the same way. A trial that asks for a card filters for people who expect to still be here at renewal, and filters out a familiar kind of time sink.

The counterintuitive part is how small the numbers can be. One founder who had already failed the polished-product way treated distribution as a day-zero problem the second time: a waitlist page before the product was live, which produced around ten emails, some of whom became paying customers. Ten is not a meaningful sample. It was a meaningful signal anyway, because the founder had gone and found those people rather than bought them. Two hundred signups from a broad audience tell you less than three who asked the price.

06What if there are no competitors and no search volume?

Treat both as warnings, not as an opening. This misreading survives longest, because an empty market flatters the founder who found it.

A living competitor proves somebody pays for this category. It converts the hard question, does demand exist, into the tractable one, can you serve a specific slice better. That reframe has a limit, which one commenter put as a question nobody answered well: how would you know an idea is already validated, and if it is, why has nobody solved it properly? Sometimes the segment is too small to interest the incumbent, which is a real wedge. Sometimes the problem is unpleasant to solve and the market priced that in.

The honest admission: nothing here tells you how to separate those two in advance. The practitioners in these threads do not know either, and the guides claiming a framework for it are selling a score. What you can do is make the distinction cheap to test, by asking a few people in that segment to pay for the outcome delivered by hand. For the community-listening half in step-by-step form, see validating a SaaS idea on Reddit.

07The two-week version, and the number that ends it

Write the stop rule first, with a date on it. A missing kill criterion is what turns a two-week test into an eighteen-month project. One useful page outside the top five is explicit that kill criteria protect you from negotiating with your own sunk cost, which is exactly the trap the postmortems describe from the inside.

Then, in order:

• Read the record you did not create. Search demand in their words, one-star reviews of incumbents, complaint threads, and job posts for the manual version. Write down the exact phrases people use.
• Name one buyer, not a segment. A role, a context, and the moment the problem becomes urgent. If you cannot name twenty specific people who match, the segment is still a guess.
• Sell the outcome before the product. Deliver it by hand for money if you have to. It is the only step that tests willingness to pay, and the step every failed postmortem skipped.
• Count unprompted price questions. Track them like a metric, because they are one. Zero after a month of a live beta is an answer.
• Only then buy traffic. With a target cost per paying customer written down beforehand, and a spend cap you actually honour.

One caveat about the rest of this search result. Several strong guides, including the four-signal framework built on retention curves and the very-disappointed survey, answer a different question. Those signals need existing users with usage history, so they measure product-market fit after launch. They are good at that and useless the week before you decide whether to build.

What we could not verify: the postmortem numbers, the pre-sale outcomes and the waitlist conversions here are self-reported, with no independent confirmation. Treat them as testimony about a failure mode, not as benchmarks. The pattern repeats across enough separate accounts to act on. No single number in it is a figure to plan against.

Frequently asked questions