All postsForgex SaaS Growth System

How to Validate SaaS Demand Before You Build: The Validation Ladder

The SaaS validation ladder, ranked weakest to strongest, and how to prove real demand before you write a line of code.

Hamza Iqbal6 min read

Demand validation is proving people will *act* on a problem, not just agree it exists. Every signal sits on a ladder from weakest to strongest: verbal interest, email signup, a booked call, and payment or a pre-order. The only true validation is people committing something that costs them, time, reputation, or money. Roughly 80% of "sounds great" responses are false positives, and 85% of SaaS ventures fail within 18 months, mostly from scaling before real demand signals exist.

Demand validation is proving that people will take a costly action to solve their problem, not just agree the problem is real. Discovery told you the pain exists. Validation tells you people will sign up, and ideally pay, to make it go away, which is a completely different and higher bar. This post lays out the validation ladder, from the signals worth almost nothing to the ones worth building on, so you know exactly what counts as proof.

What is demand validation and how is it different from discovery?

Demand validation is the stage where you stop asking whether the problem is real and start testing whether people will act on it, because acting is the only thing that predicts paying. Discovery is about understanding; validation is about commitment. You can finish discovery certain the pain exists and still have no idea whether anyone will actually buy.

The distinction matters because the two stages fail in different ways:

Get posts like this when they go up no noise, just relevant.

  • Discovery answers: is this problem real, frequent, and expensive? You learn this by asking about the past.
  • Validation answers: will people take a real action, hand over an email, a card, or a signature, to solve it? You learn this by watching what they do, not what they say.
  • The trap between them: a problem can be genuinely real and still not be worth paying to solve. Plenty of real problems get tolerated forever. Validation is how you tell "real" apart from "worth money."

There's a concrete reason to treat validation as its own stage rather than folding it into discovery. Roughly 85% of SaaS ventures fail within 18 months, primarily from premature scaling, building and spending before demand signals exist. Validation is the deliberate act of producing those signals before you commit, so you're scaling toward proven demand instead of hope.

What is the validation ladder?

The validation ladder is a ranking of demand signals from weakest to strongest, and the whole job of this stage is to climb it before you write code. Each rung costs the customer more than the last, and cost is exactly what makes a signal trustworthy, because people give away cheap things freely and part with expensive ones only when they mean it.

The rungs, weakest to strongest:

  1. Verbal interest. "That sounds useful." Nearly worthless. Everyone says this about everything, and it costs the speaker nothing.
  2. Email signup. They gave you something small and real, an address, in response to a specific promise. A mild but genuine signal.
  3. A booked call they actually attend. Time is expensive. Someone who blocks 20 minutes to talk about the problem is showing serious interest.
  4. Payment, a pre-order, or a signed letter of intent. Money or a signature before the product exists. This is the top of the ladder and the only signal that fully counts.

The rule that follows: distrust the bottom rung completely, treat an email signup as a hint rather than a conclusion, and don't commit months of your life to anything that hasn't reached rung three or four. If all you have is compliments and a few signups, you haven't validated demand, you've collected attention.

Why isn't verbal interest enough to validate an idea?

Verbal interest isn't enough because saying "I'd use that" costs nothing, and a signal that costs nothing carries no information about whether someone will pay. This is the gap between what people say and what they do, and it is wide, measurable, and expensive to ignore.

The numbers make the case:

  • Around 80% of enthusiastic "sounds great" responses turn out to be false positives. The warmth is real; the future purchase usually isn't.
  • There's a name for it: the niceness gap. The difference between the people telling you your idea is good and the far smaller number willing to actually buy it. Interviews, surveys, and casual feedback all leave this gap wide open.
  • Compliments from your network are the worst offenders. People who know you are biased toward supporting you, so their enthusiasm is the least reliable data you can collect.

This is why the ladder exists. Every rung above verbal interest introduces a cost, an email, an hour, a payment, that filters out the people who were only being polite. The higher someone climbs while still saying yes, the more you can trust that their yes is real. A signal you can trust is always one that cost the person something to give.

How much validation is enough to start building?

Enough validation is a combination of real pain, real behavioral signal, and real commitment, gathered inside a fixed time-box so you don't validate forever. A single strong signal in isolation can mislead; a stack of them across the ladder is what justifies building.

A practical four-week gate that founders use:

  • 15 interviews showing clear, consistent pain. The discovery foundation. Watch for people describing the problem unprompted, ideally 60%+ of interviews raising the pain without you leading them.
  • A 3 to 5% landing page conversion from cold traffic. Real strangers acting on your promise, not friends being kind. (More on the mechanics of this in the next post.)
  • 5 or more pre-orders or paid waitlist signups. At least a handful of people who climbed to the top rung and committed money.

Hit all three inside four weeks and you have validated demand, start building. Miss it, and the demand isn't there for this framing, so reframe the offer or pick a different problem before you sink months into a build. For a micro-SaaS specifically, even 5 to 10 genuinely engaged, committing buyers can be enough to justify starting. The exact numbers flex with your market, but the principle is fixed: you want evidence from multiple rungs, and you want a deadline on collecting it.

What are the strongest and weakest signals to watch for?

The strongest signals are behavioral and costly; the weakest are verbal and free, and learning to sort them in real time is the core skill of this stage. A useful rule: the higher the customer's cost of saying yes, the stronger the evidence, whether that cost is time, workflow disruption, political capital, or budget.

Green lights, signals worth trusting:

  • Users raise the real problem unprompted, before you describe your solution.
  • They ask about your timeline, pricing, or when they can start.
  • They ask to involve a colleague or their boss, spending reputation on you.
  • They put down money, a deposit, a pre-order, a pilot commitment.

Red flags, signals that look like validation but aren't:

  • Polite praise with no accompanying commitment.
  • Having to over-explain the value before they "get it."
  • Constant comparisons to free tools, a sign the pain isn't worth paying to remove.
  • Easy signups from broad, untargeted traffic that will never convert.

The single most important habit is to measure hard commitments over soft enthusiasm. A founder who can say "22 of 30 interviewees described the exact problem, my landing page converted cold traffic at 12%, and three signups paid in the first week" has something real. A founder with a hundred compliments and no commitments has a warm feeling and no evidence.


This is the first article in Stage 3 of the Forgex SaaS Growth System, demand validation. In upcoming articles, we will be covering more about demand validation

Frequently Asked Questions

What is demand validation for a SaaS product?

It's the stage where you prove people will take a costly action, sign up, book a call, or pay, to solve their problem, rather than just agree the problem is real. Discovery confirms the pain exists; validation confirms people will act on it, which is a higher and more predictive bar. The goal is to produce real demand signals before you build, because roughly 85% of SaaS ventures fail within 18 months, mostly from scaling before those signals exist.

What is the validation ladder?

It's a ranking of demand signals from weakest to strongest: verbal interest ("sounds cool"), an email signup, a booked-and-attended call, and payment or a pre-order. Each rung costs the customer more than the last, and that cost is what makes the signal trustworthy. The whole job of validation is to climb the ladder before you write code, distrust the bottom rung, treat signups as hints, and aim for the payment rung before committing months to a build.

Are email signups enough to validate a SaaS idea?

No, email signups are a mild hint, not proof. They sit on the second rung of the validation ladder, above worthless verbal interest but well below a booked call or a payment. Signups are directional because giving an email costs almost nothing, and broad or viral signups are heavily diluted by people who will never use the product. Watch post-signup behavior and reply rates, not raw signup counts, and push for higher-cost signals before building.

How do I know if I've validated enough to start building?

Aim for evidence from multiple rungs inside a fixed time-box. A workable four-week gate is 15 interviews showing clear pain, a 3 to 5% cold-traffic landing page conversion, and 5 or more pre-orders or paid signups. Hit all three and build; miss them and reframe the offer or pick a different problem. For a micro-SaaS, as few as 5 to 10 genuinely committing buyers can be enough. The principle is fixed even when the numbers flex: gather costly signals, and give yourself a deadline.

Why do people say they'll buy but then don't?

Because saying yes costs nothing, so people say it freely to be encouraging, especially people who know you. Around 80% of "sounds great" responses turn out to be false positives, a gap wide enough to have a name: the niceness gap. The fix is to stop trusting words and start measuring costly actions. Every rung of the validation ladder above verbal interest, an email, an hour, a payment, filters out the people who were only being polite.

Work with Forgex

If this sounds like where you are, I'd like to hear what you're building.

hamza@forgex.systems

Comments