Fake Door Testing (Painted Door Test): Validate Demand Before You Build

Fake door testing (also called a painted door test) is a validation method where you show users an entry point to a feature that does not exist yet — a button, menu item, or pricing tier — and measure how many people try to use it. The clicks reveal genuine demand before you invest engineering time, and a short follow-up turns each interested user into qualitative insight about why they wanted it.

The principle is older than the name: do not build it until you have evidence people want it. A fake door is the cheapest possible experiment to generate that evidence.

Why fake door testing matters

Building the wrong thing is the most expensive mistake in product development, and it is shockingly common:

• CB Insights found that roughly 35% of startups fail because there was no market need for the product.
• The Standish Group's CHAOS research reported 64% of software features are rarely or never used, and a later Pendo analysis put that figure at 80%.
• The canonical example: before building Dropbox, Drew Houston posted a short demo video of a product that did not fully exist. As documented in Eric Ries's The Lean Startup, the beta waitlist jumped from 5,000 to 75,000 sign-ups overnight — validating demand before a single sync feature was finished.

A fake door test is the operational answer to those numbers. Instead of shipping a feature and hoping, you spend a day building a convincing entry point and let real behavior tell you whether to proceed.

"The only way to win is to learn faster than anyone else." — Eric Ries, The Lean Startup

How fake door testing works

The mechanics are simple:

1. Create the entry point. Add the UI element a user would click if the feature were real — an "Export to PDF" button, a new nav item, a premium plan tile, or an in-app card promoting the capability.
2. Instrument the click. Track who clicks, from where, and how often. Click-through rate is your primary demand signal.
3. Be honest at the door. When the user clicks, show a transparent message: "This feature is coming soon — want early access?" Never leave users feeling tricked. Capturing an email here turns interest into a recruitment list.
4. Compare against a benchmark. A click rate is only meaningful relative to expectations or a control. Decide your threshold before you run the test.
5. Decide: build, refine, or kill. Strong demand justifies investment; weak demand saves you from the 64-80% unused-feature trap.

Fake doors work best for evaluating demand for a clearly describable feature. They are not a substitute for usability testing (which evaluates whether a built thing works) or for discovery interviews (which uncover problems you did not know existed).

What metrics to track

• Click-through rate (CTR): the share of users exposed who engage the fake door. Your headline demand metric.
• Reach and segment: which user segments clicked? A feature that excites power users but no one else changes your business case.
• Repeat intent: users who return and click again signal durable, not novelty, demand.
• Opt-in rate: of those who clicked, how many left an email for early access? This filters idle curiosity from real intent.

The ethics: do not actually trick people

Fake door testing has a reputation problem because it has been done badly. The rule is simple: measure intent, never waste it. Show a clear "coming soon" message, offer a real way to be notified, and limit exposure so you are not repeatedly disappointing the same users. A well-run painted door test leaves users feeling heard, not deceived — and gives you a warm list of people to talk to next.

The biggest weakness of fake doors — and how to fix it

A fake door tells you how many people want something. It does not tell you why, what they expected behind the door, or whether your solution would actually satisfy them. A high click rate on "Export to PDF" might mean users want PDFs — or it might mean they want to share read-only reports and assumed PDF was the only option. Build the literal feature and you may still miss the real job.

That gap between a number and its meaning is where most fake door tests stop short. Closing it requires talking to the people who clicked.

The modern approach: pair the painted door with AI follow-up

This is where Koji makes fake door testing dramatically more valuable. The opt-in list your painted door generates is a perfectly qualified audience — people who just raised their hand for this exact capability. Koji lets you interview all of them, automatically.

• Auto-interview every clicker. Send each opt-in a link to an AI-moderated interview in voice or text. Koji runs them 24/7, so you can talk to everyone who clicked instead of a hand-picked handful — turning a quantitative signal into qualitative depth within days.
• Quantify and explain in one conversation. Koji's structured questions — six types: open_ended, scale, single_choice, multiple_choice, ranking, and yes_no — let you ask "how likely would you be to use this weekly?" on a scale, then have the AI immediately probe for the reasoning. You capture the demand number and the story behind it together.
• Surface what they actually expected. Automatic thematic analysis clusters responses so you learn whether "Export to PDF" really meant PDF — or sharing, archiving, or compliance. That is the difference between building the feature and building the right feature.
• Move at experiment speed. Because Koji automates moderation, transcription, and synthesis, you get real-time insight while the test is still warm — no PhD in research methods required. Compared with manually scheduling interviews, teams using AI-assisted research see far faster time-to-insight.

A fake door without follow-up answers one question: should we build it? A fake door plus Koji answers the harder one: what exactly should we build, and for whom?

Fake door vs. related validation methods

• Smoke test: often used interchangeably; a smoke test usually validates a whole product concept (like a landing page), while a fake door validates a single feature inside an existing product.
• Wizard of Oz testing: the feature appears to work, but humans perform the work behind the scenes. Use it to test the experience, not just demand.
• Concierge MVP: you deliver the outcome manually for a few customers. Higher effort, deeper learning.
• Pretotyping: the broader discipline of testing "would people use it" before "can we build it." Fake doors are a core pretotyping tactic.

Real-world patterns that work

Fake doors show up in several reliable formats:

• The feature button. An "Export to PDF" or "Schedule send" button that, when clicked, reveals a coming-soon message and an early-access opt-in. Best for validating demand for a specific capability.
• The pricing tier. A new plan or add-on shown on the pricing page. Clicks on "Upgrade" or "Contact sales" measure willingness to pay before you build the underlying functionality.
• The empty-state promo. A card in an empty dashboard promoting a capability you are considering. Intent runs high here, because the prompt appears exactly when the user feels the gap.
• The demo or explainer. Dropbox's screencast is the classic: present the product as if it exists and measure sign-ups. Best for validating a whole concept rather than a single feature.

A fake door test checklist

Before you launch, confirm that:

• You defined a success threshold in advance, ideally against a control or a comparable existing feature.
• The entry point looks genuine — a half-hearted fake door under-measures real demand.
• The coming-soon message is honest and offers a real way to be notified.
• You are capturing emails so interested users become a research and beta list.
• Exposure is limited so the same users are not repeatedly disappointed.
• You have a plan to follow up with clickers to learn why — the step that turns a number into a decision.

When not to use a fake door

Fake doors are wrong for some situations. Avoid them in safety-critical or trust-sensitive flows — payments, security settings — where a non-functional element erodes confidence. They are also weak for measuring satisfaction or usability, since a click proves interest, not that your eventual solution will work. And in small or high-touch B2B accounts, a single disappointed champion can cost more than the learning is worth; there, a direct conversation beats a painted door. Always match the method to the risk.

Frequently asked questions

Is fake door testing unethical? Not when done transparently. Always show a clear "coming soon" message, offer a way to be notified, and avoid disappointing the same users repeatedly.

What is a good click-through rate? There is no universal number — set your success threshold before the test, ideally against a control or a comparable existing feature.

Related Resources

• Smoke Test Product Validation — validate an entire concept before building
• Structured Questions in AI Interviews — quantify and explain demand in a single conversation
• Wizard of Oz Testing — test the experience with humans behind the curtain
• Concierge MVP Guide — deliver the outcome manually to learn deeply
• Assumption Testing Guide — identify and validate your riskiest assumptions
• MVP Validation Guide — choose the right validation method for your stage