ReadySetLaunch · Demand Signal · Playbook

How to Validate Demand Signal for Your Startup

Demand is the single most-cited reason startups fail. Held to the sharpest evidential bar for a reason: you can survive a rough execution, a weak channel, a soft monetisation pitch. You cannot survive nobody wanting what you built.

Why this pillar matters

Demand validation is the difference between "people say this is a great idea" and "people signed up, pre-paid, or booked a pilot". The former is noise. The latter is signal. Most founders arrive at Launch Control with only stated interest - they've pitched the idea and people nodded. That's not demand. Demand is what someone does with their time, money, or calendar, not what they say over coffee.

The validator question

What behaviour, not opinion, proves that target customers will actually pay or commit?

This is the question your answer has to survive. Vague answers are red flags. If you find yourself reaching for marketing language or hedging with "we believe" or "we expect," the pillar is not yet validated.

Step 1 — Write the answer in the customer's language

Open a blank document. Answer the validator question in two to three sentences. Do not edit. Do not pitch. Use language pulled from real customer interviews, not your pitch deck.

If the language sounds like marketing copy, the answer is not yet sharp. Rewrite.

Step 2 — Identify the behaviour that would prove it

Stated interest is not behavioural evidence. For each pillar, the behaviour that proves it is different:

• Problem clarity: a customer can describe the problem unprompted, in your absence, with the same specificity you can.
• Target customer: you can name one real person, with their company and role, who fits the ICP.
• Demand signal: a stranger pays you, before the product is built, with a card on file.
• Differentiation: a customer who currently uses a substitute switches — or commits to switching on a known timeline.
• Execution feasibility: a working prototype of the technical critical path exists, not a slide deck.
• Distribution readiness: a tested channel acquires 30 real customers (not friends) at acceptable CAC.
• Monetisation viability: the price has been charged, the unit economics work at the smallest sustainable scale.

Step 3 — Run a 2–4 week experiment

Pick the behaviour. Design the smallest experiment that would generate it. Run it. Measure it. The output is either evidence (the pillar holds) or a gap (the pillar needs more work).

Step 4 — Score honestly

Three states per pillar:

• CLEAR — specific, evidence-backed, would survive a sceptical buyer's questions.
• PARTIAL — working hypothesis, no behavioural evidence yet.
• GAP — you do not know.

Mark this pillar one of the three. Then move to the next.

What the data shows

Across the 190 demand signal-related cases in the ReadySetLaunch database, one pattern dominates: the founders who shipped without closing the gap on this pillar almost always paid for it later, and almost never recovered. Closing it pre-launch is days of work; closing it post-launch is months of runway.