Validation methods
The Cheapest Validation Test: Pre-order vs MVP vs Concierge MVP vs Fake-door
Four methods, four price tags, four different signals. This page compares pre-orders, minimum viable products, concierge MVPs, and fake-door tests side-by-side and shows the decision flow that picks which one to run first.
Last updated September 21, 2026
Quick answer
Which validation test is the cheapest?
The cheapest validation test is the one that produces the signal you actually need. A fake-door test is the cheapest if you need to know whether anyone wants what you plan to build. A concierge MVP is the cheapest if you need to know whether they will pay and stay. A pre-order is the cheapest if you need real money before you build anything. A minimum viable product is the cheapest if you need a working artifact to close a sale or onboard a channel. The four methods answer four different questions; running the wrong one wastes the founder's most scarce resource, which is time, not money.
Key takeaways
What founders need to remember about the four validation tests
- Each method answers a different question. A fake-door test answers 'is there demand?' A concierge MVP answers 'will they pay and renew?' A pre-order answers 'will they commit cash before the product exists?' An MVP answers 'does a usable product work for real users?'
- Cost runs from $0 (fake-door) to thousands of dollars (a real MVP), but the binding constraint is founder time, not dollars. A concierge MVP costs almost nothing in cash and 30 hours a week in founder attention.
- Run the cheapest test that produces the signal you actually need. If you do not yet know which assumption is most at risk, run a fake-door test first. If you already know people want it but doubt the price, run a pre-order or a concierge MVP.
- The four tests stack. Many founders use two or three in sequence: a fake-door to confirm demand, a concierge MVP to confirm willingness to pay, then a thin MVP only after the first two are positive.
- A method's signal is only as good as the audience. A fake-door test with no traffic produces no signal. A concierge MVP with the wrong ICP produces a flattering renewal rate that does not generalize. Always pair the test with the named buyer.
Side-by-side
The four validation methods at a glance
Cost, time, signal strength, and the failure mode each method carries. Every row is a distinct test a solo founder can run without a team.
| Method | Cash cost | Time to first signal | What it measures | Failure mode |
|---|---|---|---|---|
Fake-door test A CTA that points at a product or feature that does not yet exist. | $0 in product cost. The price is the time to build the page and the traffic to send it. | Days, once the page exists and traffic is paid or organic. | Click-through and signup intent, but no payment proof. | Polite clicks do not predict payment. A high signup rate with a 0% conversion to paid is a vanity metric. |
Pre-order A refundable deposit or a charged card against a future shipment or delivery. | Setup of a payment page. Stripe fees only on converted orders. | One to three weeks of outreach to a named buyer list. | Real payment before the product exists. The strongest pre-build signal money can buy. | A refund request is louder than a no. Refund handling and the legal posture of selling what does not yet exist are real frictions. |
Concierge MVP The founder manually delivers the service the product would automate, behind a paid subscription or one-time fee. | Almost no cash. The price is 20 to 40 hours a week of founder time. | 30 to 60 days, long enough to observe one renewal cycle. | Whether paying customers renew after the novelty wears off — the question an MVP cannot answer cheaply. | The founder becomes the bottleneck. The service does not scale. The signal is real but the artifact is not a product. |
Minimum viable product The smallest product that real users can use without the founder in the loop. | Hundreds to tens of thousands of dollars, depending on scope. | Weeks to months. | Whether the product holds up without the founder handholding the workflow. | An MVP that is too small to be useful produces churn. An MVP that is too large was the kind of build a validation test was supposed to prevent. |
Which to run first
A four-step decision flow
A practical order: which test a solo founder should run, given what they currently believe about the idea.
Step 1
If you do not yet know whether anyone wants the product, run a fake-door test first.
A landing page or a feature flag that points at a non-existent product is the cheapest way to find out whether the demand you assumed actually exists. Eric Ries, in The Lean Startup (Crown Business, 2011), describes the smoke test as the moment the founder separates the question 'can we build it?' from the question 'should we?'. Y Combinator's startup curriculum teaches the same lineage under the names smoke test and fake-door test.
Step 2
If a fake-door shows demand but you doubt the price, run a pre-order or a concierge MVP.
A pre-order is the right next test when you already have a list of named buyers. A concierge MVP is the right next test when you do not, or when the product's value is hard to put on a landing page. Both produce a payment signal before the build; the difference is whether the founder can identify the buyer before they reach out.
Step 3
If payment holds across a renewal cycle, run a thin MVP — only then.
Steve Blank, in The Four Steps to the Epiphany (2005), distinguishes customer discovery (steps 1 and 2 above) from customer validation (this step). The MVP's purpose at this stage is to remove the founder from the workflow, not to ship a polished product. The MVP that follows a paid concierge period looks nothing like the MVP a founder would have built on day one.
Step 4
If the founder cannot run any of these tests, the problem is the ICP, not the test choice.
A fake-door test without a channel to drive traffic produces zero signal. A concierge MVP without a named ICP produces a flattering renewal rate from friends. Rob Fitzpatrick's The Mom Test (2013) is the canonical guide to having the conversations that surface the real buyer before any test runs. The decision flow returns to step 0.
Worked example
A concierge MVP that came after a fake-door test
Hypothetical scenario, anonymized and illustrative only. Names, prices, and dates are fictional.
A first-time founder wants to build a $39/month dashboard for SaaS founders who run paid ads. The founder has no audience, no list, and no existing customers. The founder's stated assumption is 'SaaS founders running paid ads need a faster way to see which creatives are profitable.'
Method 1
Step 1 — Fake-door. The founder builds a 90-minute landing page, ships it on a $50 Reddit Ads budget to r/SaaS and r/PPC, and waits 7 days. 1,200 people see the page. 38 sign up for the waitlist. The signup rate is 3.2%, which the founder treats as 'demand exists, weak.'
Method 2
Step 2 — Concierge MVP. The founder emails the 38 signups and recruits five to a 30-day concierge at $39/month — a manual weekly report delivered through Notion and email. The founder spends 20 hours a week doing the work.
Method 3
Step 3 — Renewal signal. By day 14, four of five customers use the weekly report. By day 30, all five renew. By day 60, two have cancelled. By day 90, only one remains. The 30-day signal looked like recurring demand; the 90-day signal showed the report was useful but not load-bearing.
Method 4
Step 4 — Decision. The concierge MVP answered the question the fake-door could not: 'will paying customers renew after the novelty wears off?' The answer was 'one in five, in this ICP.' The founder narrows the ICP from 'SaaS founders who run paid ads' to 'B2B SaaS founders spending $5,000+/month on paid ads' and re-runs the concierge. The second cohort's 30-day renewal rate is four out of four. The MVP is now worth building.
Common mistakes
Four ways founders pick the wrong validation test
These are the failure modes the Yibud startup validation reports see most often. Each one is a method mismatch — the right test for a different question.
Method 1
Running an MVP before proving the demand
A founder who knows the problem exists in their own life assumes it exists for buyers. The MVP is then used as a way to find out whether anyone wants the product, which is the question a fake-door test answers in days and tens of dollars, not the question an MVP answers in months and thousands.
Method 2
Treating polite interest as willingness to pay
A founder runs a fake-door test, gets a 4% signup rate, and concludes the product will sell. The signup rate is intent, not payment. The Mom Test (Fitzpatrick, 2013) names the failure mode explicitly: compliments are not data, and a polite email reply is not a price.
Method 3
Charging for a fake-door test
A fake-door test's CTA points at a product that does not exist. Charging money for what does not yet exist is a pre-order, not a fake-door. The two tests answer different questions and the legal posture of charging for a non-existent product is meaningfully different.
Method 4
Building an MVP that requires the founder to run it
A concierge MVP that requires the founder to operate every customer is a service, not an MVP. The MVP's purpose at this stage is to remove the founder from the workflow. If the founder is the workflow, the founder has learned something about pricing but nothing about the product.
What these tests cannot tell you
Three boundaries the four methods share
Every validation test is a tool that answers one class of question. Outside that class, the tool produces no signal — or worse, produces a signal that looks like one and is not.
None of the four tests predict long-term retention
A pre-order captures a moment of intent. A concierge MVP captures one renewal cycle. A fake-door test captures a click. None of these predict whether the customer is still paying in year two. Long-term retention requires an MVP that runs long enough to observe the second renewal cycle, which is months of post-build evidence.
None of the four tests generalize across audiences
A concierge MVP with five customers in one ICP produces a signal for that ICP, not for adjacent ICPs. A fake-door test on one channel produces a signal for that channel's audience. The signal a founder extracts from a single test is always narrower than the market the founder plans to enter.
None of the four tests remove the need for a clear hypothesis
A founder who cannot name the assumption being tested will get a confusing signal regardless of which method they pick. Fitzpatrick's The Mom Test (2013) is the canonical guide to stating the hypothesis clearly before the test begins.
Where these ideas come from
Four primary sources behind the comparison
Each method and each decision step traces to a published primary source. None of the rows above are invented for this page.
Eric Ries, The Lean Startup (Crown Business, 2011)
Ries names the build-measure-learn loop and the MVP as the smallest experiment that produces validated learning. The page's definition of an MVP, and its placement at step 3 of the decision flow, follow this book.
Rob Fitzpatrick, The Mom Test (2013)
Fitzpatrick's rules for honest customer interviews — never ask hypothetical questions, never ask whether people would buy, ask about specifics in the customer's recent past — are the discipline that makes the fake-door and pre-order signals worth interpreting. The mistake section quotes Fitzpatrick's principle directly.
Steve Blank, The Four Steps to the Epiphany (2005)
Blank's customer development framework separates customer discovery (steps 1 and 2 here) from customer validation (step 3 here). The concierge MVP lineage traces to Blank's teaching on getting out of the building before building the building.
Giff Constable, 'What is a Smoke Test?' (smoketestmethod.com)
Constable's canonical definition of the smoke test — a small experiment designed to test a critical assumption before building — is the operational definition of a fake-door test used here.
FAQ
Questions founders ask about the four validation tests
- Can a pre-order and a fake-door test be the same thing?
- Not really. A fake-door test's CTA points at a product that does not yet exist; the conversion event is a click or a signup. A pre-order's CTA points at a payment; the conversion event is a charged card. A founder who wants both signals should run them as two separate tests, in sequence, with the fake-door first.
- Which validation test should I run if I have no audience?
- A fake-door test on a paid channel is the right first test if you have no audience. A concierge MVP requires an audience to recruit from. The YC curriculum teaches that an audience is itself a test: a founder who cannot recruit five ICP-matched people from any channel has learned something the test was supposed to find out.
- Is an MVP always more expensive than a concierge MVP?
- Almost always, in cash terms. The concierge MVP's cost is founder time, which most solo founders do not count as cost. The MVP's cost is engineering hours, which are paid or borrowed. The cheapness of a concierge MVP is therefore a founder-time trade, not a cash trade.
- When does a fake-door test produce a misleading signal?
- When the audience the test reaches is not the ICP. A landing page ranked on a SEO keyword that attracts job-seekers produces a flattering signup rate that does not generalize. The test is honest; the audience is wrong. Pair every test with the named buyer.
- Do I need to run all four tests?
- No. Most founders run two. The common pairings are fake-door → concierge MVP (validate demand, then validate willingness to pay), and concierge MVP → MVP (validate pricing, then remove the founder). A founder who can only run one should run the cheapest test that produces the signal they need.
- How long should a concierge MVP run?
- Long enough to observe at least one renewal cycle. A monthly subscription needs 60 to 90 days to see whether the second payment lands. A one-time product needs long enough to see whether the customer uses the artifact after the initial purchase. Shorter than one renewal cycle produces a sign-up signal, not a retention signal.
- What is the difference between a smoke test and a fake-door test?
- The two terms describe the same operational test. Smoke test is the older name (Constable, Ries); fake-door test is the name that came in later and is now more common. A smoke test was originally a release-engineering term for a test that checks the build is not on fire; Ries repurposed it for the validation analog.
- When should I just build the product?
- When the cost of being wrong is small enough that the validation cost is higher than the rebuild cost. A weekend hobby project does not need a concierge MVP. A two-year, two-engineer build does. The decision flow returns to step 0 whenever the validation cost exceeds the failure cost.
Run the Startup MRI validator
Five short questions. A structured 8-dimension report in under 60 seconds. Free, no signup.