An Idea Validation Framework You Can Actually Fail

An idea validation framework is a fixed sequence of tests with the pass mark written down before you run them. This one has four gates: problem, buyer, commitment, money. Each gate names the evidence that counts, the number you have to hit, and what you’ll spend getting there. Fail a gate, and you stop or change one specific thing.

TL;DR

  • Validation rarely fails on the tests. It fails because nobody set the pass mark first, so whatever comes back reads as encouraging.
  • Four gates, in order: is the problem real, can you name and reach the buyer, will they give up something that costs them, will they pay.
  • Every gate has a different evidence bar. Enthusiasm from people who know you clears none of them.
  • Decide the numbers and the budget before you start. That’s the part every other framework leaves out.

The number nobody writes down

Twelve interviews in, an honest founder can tell you exactly what she heard: eight people said the problem was real, four said they’d probably pay, nobody laughed her out of the room. So she built for four months. The product landed to silence.

Nothing in that story is a bad test. The interviews were fine. What was missing is a number written down beforehand that said eight out of twelve means go, six means stop. Without it, results don’t get evaluated, they get interpreted, and interpretation always leans toward the thing you already want to build. “No market need” remains the most common cause of startup death in CB Insights’ post-mortem analysis, and the founders in those post-mortems were rarely lazy. Most of them tested. They just graded their own homework afterwards.

So the first move in any validation framework is clerical, not strategic: open a document, write the four gates, and fill in the pass column before you talk to anyone.

The four gates

Run them in this order. The order isn’t arbitrary: each gate is cheaper than the one after it, and each one kills a different idea. Skipping ahead means paying for a test whose answer an earlier gate would have given you free.

Gate The question it settles What counts as evidence Pass mark (you set this first) Budget
1. Problem Does this cost them enough that they’ve already tried to fix it? Unprompted accounts of the problem in the last 90 days; a workaround they built, bought, or hired for e.g. 7 of 10 target-buyer conversations describe it without you naming it ~1 week
2. Buyer Can you name one segment and reach it repeatedly? Named places where they gather: specific communities, lists, events, search terms with real volume e.g. 3 channels you can reach twice a week without paying a gatekeeper ~2 days
3. Commitment Will a stranger give up something that costs them? Email from cold traffic, a booked call, a waitlist deposit, a signed letter of intent e.g. 20 signups and 5 booked calls from 200 targeted visitors ~1 week + a small ad budget
4. Money Will they pay before the thing exists? Pre-order, deposit, paid pilot, a card actually charged e.g. 3 pre-orders at the real price, not a discount 1–2 weeks

The pass marks above are examples, not benchmarks. Nobody can hand you the right number for your market, and anyone who prints one is guessing. Pick yours from what the decision costs: if failing means you lose a weekend, set a loose bar. If it means you quit your job, set a bar that scares you.

Gate 1: the problem, not the solution

The evidence that clears this gate is always historical. What did they do about it last time it happened, how long did it take, what did it cost them. Rob Fitzpatrick’s The Mom Test is the whole method in one book: ask about past behaviour, never about future intent, because future intent is free to promise. A person who built a spreadsheet to survive your problem has told you more than ten people who say the idea sounds useful.

Gate 2: one buyer, reachable twice

Founders skip this one and pay for it at Gate 3, when they discover there’s no way to put the page in front of the right people. Reachability is a real constraint, not a marketing detail. If your buyer is “small business owners,” you don’t have a buyer; you have a census category. Narrow until you can name three specific places you could show up on Tuesday.

Gate 3: something that costs them

Attention is free, so it proves nothing. The cheapest costly thing is usually an email address given by someone who found you cold, and the strongest is a scheduled call, because a calendar slot costs time that can’t be refunded. This is the gate where a demand page earns its keep: send targeted traffic to a page that asks for a commitment, then count. The tactics live in our guide to validating a startup idea.

Gate 4: money before the product

Charging early isn’t about revenue at this stage. A person who pays becomes a different kind of informant: specific, impatient, and honest about what’s missing. If a pre-order is genuinely impossible in your market, substitute the nearest costly commitment, like a signed pilot agreement with a start date. Substituting interest is how founders talk themselves through this gate without passing it.

What doesn’t count

  • “I’d definitely use that.” Future intent, offered for free, usually to be kind.
  • Friends, colleagues, your own followers. They’re responding to you, not to the idea.
  • Survey answers about hypothetical purchases. Ask a hundred people if they’d buy and you’ll learn about politeness.
  • Free signups from untargeted traffic. A viral post brings tourists. Gate 3 counts strangers who came from a channel you can use again.
  • Advice from other founders, including good advice. They’re guessing about your market with less information than you have.

Copy this

Paste it, fill the pass column, and don’t edit that column after the data arrives.

IDEA: ________________________  DATE: ________
BUYER (one segment, specific): ________________

GATE 1 — PROBLEM        pass mark: ____ / ____ conversations   result: ____  □ pass □ fail
GATE 2 — BUYER          pass mark: ____ reachable channels     result: ____  □ pass □ fail
GATE 3 — COMMITMENT     pass mark: ____ from ____ cold visits  result: ____  □ pass □ fail
GATE 4 — MONEY          pass mark: ____ paid at $____          result: ____  □ pass □ fail

TOTAL BUDGET BEFORE DECIDING: ____ days, $____
IF A GATE FAILS TWICE, I STOP. Signed: ________

The signature line is not a joke. It’s there because the version of you reading the results is more optimistic than the version writing the plan.

Where this breaks

Long enterprise sales cycles bend Gate 4 out of shape: a six-month procurement process can’t produce a pre-order in two weeks, so the honest substitute is a champion who will put a pilot date in writing. Brand-new categories bend Gate 1, because people can’t describe a problem they’ve never had a name for, and you have to look for the workaround instead of the complaint. Regulated markets bend everything, since the binding constraint is approval rather than demand.

What doesn’t bend is the pass mark. The moment you start deciding what a result means after seeing it, you’ve stopped running a framework and started building a case.

If you’d rather not run the gates by hand, compare the tools that do parts of this honestly, including where each one beats us, or see how a scored report differs from an evidence run in ProofMachine vs ValidatorAI. And when Gate 3 passes, the next problem is recruiting the people who cleared it: that’s getting your first users.

Steve Blank’s customer development writing is still the best free background reading on why any of this works.

Idea validationFrameworksDemand testing

Frequently asked questions

What is an idea validation framework?

A fixed order of tests, each with a pass mark you set before running it. The order matters because it puts the assumption that would kill the idea first, and the pass mark matters because it's what stops you from grading your own homework after the results are in. A process tells you what to do next; a framework tells you when to stop.

How is this different from Lean Startup or Customer Development?

It isn't a rival to either. Steve Blank's customer development gives you the method for getting out of the building, and Lean Startup gives you build-measure-learn. Both assume you'll define your own success criteria, and that assumption is where most founders quietly go wrong. Treat the four gates as the scoreboard you bolt onto whichever method you already use.

How many interviews do I need before Gate 1 passes?

Stop when you can predict the answers. In practice that lands somewhere around ten to fifteen conversations with the same kind of person, and if you're still getting surprised at twenty, your segment is too broad rather than your sample too small. Count only the people who match your buyer definition; the rest are practice.

Is a waitlist signup real proof?

Only if the traffic was cold. A hundred signups from your own followers proves that people who like you will click a button. The same hundred from strangers who arrived from a search or a community thread is a genuine signal, which is why Gate 3 is written in terms of where the visitor came from rather than how many of them there were.

What do I do when an idea fails a gate?

Change one named thing and re-run that gate: the segment, the problem you're pointing at, or the price. Failing twice on the same gate with different variables is the honest kill signal. Founders who skip this rule tend to keep re-running the gate they already passed, because passing feels productive.

Can I run all four gates in a week?

Gates 1 through 3 fit in a focused week if you already know who you're talking to. Gate 4 usually doesn't, because asking for money means having something concrete enough to pay for. Budget two weeks for the whole set and treat any plan longer than a month as a sign you're building instead of testing.

Stop guessing. Start validating.

ProofMachine turns a fuzzy idea into a brutally honest validation kit in about 10 minutes.

Validate your idea free