ReadySetLaunch · Demand validation
Startup Demand Validation
Demand is the most-cited reason startups fail in the broader literature. The pillar is held to the sharpest evidential bar for a reason: you can survive a rough execution, a weak channel, a soft monetisation pitch — but you cannot survive nobody wanting what you built. Here is a structured method for collecting demand signal that survives contact with reality.
Demand is the most-cited reason startups fail in the broader literature. Roughly four in ten failed startups in the broader literature and the RSL case database shipped a product nobody wanted. The pillar is held to the sharpest evidential bar for a reason: you can survive a rough execution, a weak channel, a soft monetisation pitch — but you cannot survive nobody wanting what you built.
This page is the structured method for collecting demand signal that survives contact with reality.
What demand signal actually is
Behavioural evidence. Not stated interest.
The distinction matters because the two are correlated weakly. A meaningful fraction — but only a fraction — of people who say they would buy a product actually buy it when given the chance. Validation built on stated interest overestimates demand by a multiple — which is enough to kill a startup that built infrastructure for the inflated number.
Three classes of behavioural evidence, in increasing strength:
- Pre-orders with cards on file. Even £20 counts. The act of putting in payment details filters social politeness from real intent.
- Paid pilots. A customer pays you (£500, £2,000, whatever) to use a manual version of the product. The price filters out the curious from the buying.
- Deployed prototype with repeat usage. Customers come back unprompted. The product is solving a real problem for them.
Aim for 30+ data points across at least one class before you believe the signal. Less than that is anecdote.
How to collect demand signal
Four moves that work, in order of speed:
1. Pre-order page with paid traffic
Build a single landing page describing the product. Add real card capture (Stripe, Gumroad, whatever). Spend £100 on targeted ads to it.
Measure conversion rate. If 30+ people convert at acceptable CAC, the demand is real and the price you tested is approximately right. If conversion is low, the gap is in the pillar — problem, customer, differentiation, or pricing — and you have surfaced it cheaply.
2. Paid pilots
Sell the outcome before the product exists. Recruit 5–10 customers willing to pay £500 to £5,000 for a manual version of the product. Deliver it manually.
Two things happen: you collect strong demand signal (paid pilots are the strongest behavioural evidence outside of recurring revenue), and you learn what the customer actually needed — which is usually different from what they said they needed.
3. Waitlist with conversion data
A waitlist is only useful if you measure the conversion from cold traffic. "5,000 signups" tells you nothing without the underlying conversion rate. A waitlist that converts at 30% from cold ads to a sharp landing page is a strong signal. A waitlist that converts at 1% is noise.
4. Charge from day one
Free tools that try to monetise later usually cannot. Charge symbolically if needed. The act of charging tests the value proposition; the price floor matters less than whether anyone is willing to cross it.
What does NOT count as demand validation
- "I asked 30 people in customer interviews and they all said they'd use it." — Stated interest, not demand.
- "We have 5,000 newsletter subscribers." — Audience, not demand. Different signal.
- "Reddit thread on r/startups got 200 upvotes." — Social validation, not demand.
- "Our beta has 100 users." — Usage signal, not demand. Free users do not predict paying ones.
Each of those is some signal, but none of them is demand signal. Confusing them is how startups end up with high engagement, no revenue, and 12 months of runway running out.
How ReadySetLaunch tests it
Demand signal is one of seven pillars in the framework, and it is the heaviest weight (25% of the composite). Launch Control tests the pillar with structured questions about behavioural evidence — not opinion, not interest, not enthusiasm. The signal strength resolves to Insufficient, Emerging, or Strong, and the gap-closing loop pushes weak answers toward sharper specificity until the underlying experiment design is clear.
The output is not a number. It is a per-pillar diagnosis that tells you exactly which behavioural test to run, and what bar to clear before you trust the signal.
Run the test
ReadySetLaunch's Launch Control runs demand-signal validation as part of the full seven-pillar pressure-test. 30–45 minutes. Three free trial credits, no card required. The first run usually surfaces a weak demand signal — that is the system working.
Frequently asked questions
How do you validate demand for a startup?
By collecting behavioural evidence — money on the table, pilots running, signups converting — not stated interest. The bar to clear: 30+ data points where someone took an action with skin in the game. Pre-orders with cards on file, paid pilots, deployed prototypes with repeat usage. 'I'd love to use that' from interviews is stated interest, not demand.
What is the difference between stated interest and demand signal?
Stated interest is what someone says they want. Demand signal is what they do with their time, money, or calendar. The two are correlated weakly — a meaningful fraction — but only a fraction — of people who say they would buy a product actually buy it when given the chance. Demand validation that does not test behaviour overestimates demand by a multiple, which is enough to kill a startup.
How many customers should I talk to before validating demand?
Customer interviews are useful for problem discovery, not demand validation. For demand specifically, you want behavioural data: 30+ paid pre-orders, 5–10 paid pilots, or a waitlist with measured conversion from cold traffic. The number of conversations matters less than the number of people who took an action.
Can demand be validated without a finished product?
Yes — and that is the point. Pre-orders, paid pilots, and waitlists with conversion data all test demand before the product ships. The strongest demand signal is the one collected pre-build, because it gives you permission to build with confidence.
What is the best way to test startup demand?
A pre-order page with real card capture, run against £100 of targeted paid traffic. The conversion rate is your demand signal. If 30+ people convert at acceptable CAC, the demand is real. If they do not, the gap is in the pillar — either the problem, the customer, or the differentiation — and you have surfaced it cheaply, before any code was written.
Stop reading. Start pressure-testing.
ReadySetLaunch's Launch Control walks you through thirteen structured questions across the seven pillars. Three free trial credits, no card required.
Start Launch Control