How to run a fake door test that measures demand without annoying anyone
A fake door test is a button for a feature you haven't built. Set the threshold first, tell clickers the truth at once, size the test and never take money.
A fake door test is a button for a feature you have not built: show it to real users, count the clicks and tell clickers the truth straight away. It answers a question interviews can't: will people act when the option looks real? The cost is a small disappointment for everyone who clicks, so keep the test small and never take money for the missing feature.
It is also called a painted door test, and the door can be a button, a menu item, a pricing option, a landing page or an ad. Optimizely's glossary describes the method as advertising a feature before it exists to gauge demand (Optimizely). A pretotyping quick reference from Alberto Savoia's Pretotype Labs lists the Fake Door as a way to measure initial interest by creating artifacts that suggest a product exists and is available (Pretotyping quick reference).
1. Use one after interviews, away from stressful screens
It fits when:
- Interviews or a concept test have already shown the problem is real and the idea makes sense to buyers; market validation covers that step.
- Enough people pass the spot where the door would go for the numbers to mean something.
- Your question is whether people will choose this option, at this point in their work.
It fits poorly when:
- The door would sit in a critical task, such as running payroll or changing security settings. A "coming soon" message is mildly annoying on a dashboard. On the payroll screen late on a Friday, it is a reason to call support.
- Your users are a few dozen enterprise accounts. The numbers are too small to read and every disappointed admin matters. Interview them instead.
- You are tempted to collect payment for the missing feature.
If the request came from a customer, how to test a feature request covers other ways to check it before building.
A made-up example: a vendor button for landlords
A company sells property management software to small landlords. Several customers have asked for help finding repair contractors. Before building a vendor marketplace, the team puts a button labeled "Find a vendor for this repair" on the maintenance request page, shown to a random half of landlords for 30 days.
Clicking the button opens a short message: "We're thinking about building this and haven't yet. Thanks for clicking. It helps us decide. What were you hoping it would do?" Below that is a one-line answer box and a checkbox to hear if it launches.
2. Write the hypothesis and threshold before you start
Savoia's pretotyping method suggests writing a market engagement hypothesis in the form "X% of Y will do Z" before you test (Pretotyping.org). In the example: "At least 5% of landlords who open a maintenance request in the next 30 days will click Find a vendor."
Pick the number that would justify building the feature, and write it down before the test starts so nobody can move it. (Moving it afterward is very tempting when the result is close.) Optimizely makes a similar point: know before you start what a positive, negative and neutral result would look like.
3. Make the door look normal and the reveal honest
The door should look and sit like a real option. Put it where the need arises, with the same visual weight as the buttons around it. Skip the flashing "New" badge, which draws curious clicks that say little about demand.
The reveal should be immediate and plain. Say the feature doesn't exist yet and you are considering it. Offer something in return for the click:
- A one-question follow-up: "What were you hoping it would do?"
- An opt-in to hear if you build it.
- A workaround, if one exists.
Savoia's quick reference gives a restaurant example: if someone orders a dish that isn't actually available, tell them, apologize and offer them something else for free. In software, the equivalent is a clear apology and, where it makes sense, a small credit or a workaround.
Ads and landing pages need extra care. Google Ads' misrepresentation policy does not allow ads that promise products or offers that are unavailable or cannot easily be found from the destination (Google Ads). For a landing-page test, describe the product as coming soon and ask people to join a waitlist. Don't say "Buy now" for something you can't sell, and don't collect card details on a pretend checkout. If you do take pre-orders, rules such as the FTC's Mail Order Rule may apply; market validation summarizes it.
4. Fix the sample size up front and don't stop early
Decide in advance how many people should see the door. Evan Miller shows that checking results repeatedly and stopping at the first significant-looking difference inflates false positives (Evan Miller).
A rough guide to size is the margin of error on the click rate. By the standard normal approximation, if 1,000 people see the door and 40 click (4%), the 95% margin of error is about plus or minus 1.2 percentage points. With 200 viewers it is about plus or minus 2.7 points, too wide to tell 4% from 2%. These figures are our calculation.
Compare its click rate with a familiar option on the same page, so you can tell interest in this feature from general clicking.
5. A click is a small yes, so read what clickers wanted
In the example, 1,800 landlords saw the button and 117 clicked: 6.5%, with a margin of error of about plus or minus 1.1 points, so the range runs from about 5.4% to 7.6%. That clears the 5% threshold.
A click overstates demand when the placement is unusually prominent or the label promises more than you would build, and understates it when the label is unclear or easy to miss. Read the follow-up answers before deciding anything. If most landlords who clicked wanted contractor phone numbers, a simple directory may serve them. If they wanted to book and pay a contractor inside the product, that is a much bigger build.
Then look for stronger evidence: Savoia's quick reference describes asking interested people for a deposit to join a waiting list, and a paid pilot plays the same role for business software. Interview five landlords who clicked about what they expected and what they do today.
6. Every fake door spends some trust
- Tell people immediately. No fake loading screen and no pretend error message.
- Keep doors out of critical workflows.
- Limit exposure to a share of users and a fixed period, then remove the door.
- Never charge for the missing feature or collect payment details.
- Follow up with everyone who opted in, including if you decide not to build it.
- Avoid repeating fake doors on the same users; each one spends some of their trust.
Some teams prefer an openly labeled version: a "Coming soon, tell us if you want this" option or a waitlist. It measures a softer signal, but nobody hits a surprise dead end. If you are unsure, run the labeled version.
Your next step
Write your hypothesis in the form "X% of Y will do Z," the place the door will go and the reveal message, before anyone builds the button. Then plan five interviews with people who click.
To hear from people in the market who are not yet your users, Instant Expert can find people who match a description such as "property managers who handle maintenance for 20 to 200 rental units." It sends your invitations and you pay for each call that gets booked. The directory pages for property management consultants and product professionals in property management are one place to start.