Fake Door Test: A Guide to Quickly Validating Ideas

You are building at night and over the weekends, but how do you know if people will buy?

We surveyed 294 founders in the Launching Next community on fake door tests. 63% told us they had never even heard of a fake door or painted door test. 42% said the part that stops them is very simple: They do not know how to design one. 36% said the whole thing feels misleading to users. And 47% said they would try it in the next three weeks if it could be done without code. That is the gap I want to close.

By the end of this guide, you will have a 5-step approach to fake door test and the metrics to know whether to build, park or stop the idea.

What is a fake door?

A fake door test is when you show people an entry point to a feature or product that does not exist yet. That entry point can be a button in your app, a banner in your dashboard, a CTA on your site, an email link or even a paid ad. When someone clicks, you tell them the truth: you thank them for engaging and invite them to leave an email or answer one question. You then look at three numbers. Views. Clicks. Completions.

That signal is the whole point. I want to know if a new idea deserves engineering time. I want a list of people who raised their hands. I want to understand what they expected. I also want to avoid building things that no one asked for.

A fake door test, also referred to as a “painted door test,” answers one question fast: If I show this to the right people right now will they try to use it.

I treat fake door tests as real experiments. I write a hypothesis. I pick an audience. I place the door where they already walk. I define the pass line before launch. Then I remove the door when the time box ends.

I have seen founders do this with paid ads that point to a landing page. I have seen product teams do this with in-app tooltips. I have seen marketers do this with feature teasers. All of those use cases are valid. The shape of the door can change, but the logic is the same.

Fake door test vs. painted door test

People use 3 names for the same family of tests. Fake door. Painted door. Trap door. Most teams do not care about the label. I do because it makes planning faster.

Fake door

I place the entry point inside a real product surface. New menu item in the dashboard. Extra card on the pricing page. Button inside a workflow. The user believes the feature lives here. When they click I tell them I am validating interest.

Painted door

I paint the entry point on a surface that is easier to change. Marketing page. Temporary landing page. Email. Social ad. Here I am often testing new value propositions or possible features before I bring them into the product.

When do I pick which

• I pick fake door when I want a clean signal from existing users inside the real experience.
• I pick painted door when I want to test a bigger idea with cheaper traffic before I touch the app.
• I pick either when I want early access signups so I have people to contact the day we ship.

Both of these are part of the same toolkit. Both must be transparent. Both must have a removal plan.

When to run a fake door test and when to skip it

I like clear rules. Here are mine.

Run a fake door when

• You have more ideas than developer hours
• You want to show evidence before building a product or service
• You want a beta list for a feature you are not ready to code
• You want to pick between two competing ideas
• You are setting price or packaging and you need a swing at demand
• You are coaching a small team on discovery and you want a fast win

Skip a fake door when

• The flow touches payment identity security or compliance
• The feature is so small that building it is faster than testing it
• The trust level with your audience is still fragile
• You cannot commit to a reasonable follow-up with the customer
• You cannot segment to the people who actually need this feature
• Your analytics cannot count views clicks and completions for this surface

Skipping is still a decision. Choose what’s right for your business.

TL;DR: 5 steps to launch a fake door test

1. Pick one idea to validate. Not three. Write the user facing value in one line. Example. Connect Zapier to send new leads to HubSpot.
2. Place the door where your best users already show up. That can be an in app menu item, a dashboard banner, a CTA on your current landing page, a link in your next email or a small social ad.
3. Route the click to a transparent follow up. Show a thank you page or modal that says you are validating interest, asks one or two clarifying questions and captures an email for early access.
4. Measure three numbers. Impressions. Clicks. Completions. Decide on your pass or fail threshold before you publish the door.
5. Follow up inside 24 to 72 hours. Tell people you are building it now, or that you are keeping it warm, or that you need a few more signals.

This flow is designed for 2 to 5 hours of work. That matches what 56% of founders in our survey said they will realistically invest in a simple landing page style fake door. Start with one door. Learn. Then run the next one.

Step-by-step guide to fake door tests

Here is the simple version you can follow today.

Step 1: Pick the feature or idea

Founders carry many ideas in their head. Pick the one that will cost the most time if you get it wrong. Write the value line the way a user would say it. Example: “Create weekly PDF reports and send to my client.” That line becomes the button text and the headline.

Step 2: Decide where people will see the door

Choose the place where your current traffic already shows up.

• One social ad or Google ad to a potential audience if you do not have app traffic yet
• In-app menu item for products that already have active users
• Dashboard banner for products with light usage
• CTA on your current landing page if you are still pre launch
• Email CTA if you have even a small list

Step 3: Build the door so it looks real

This is where 42 percent of founders said they get stuck. Copy what your own product already looks like. Same color. Same button size. Same icon. Then add believable text.

• Try AI Reports
• Add team member
• Generate proposal
• Enable SMS alerts
• View pricing plans

If you are doing this on a landing page make the button the primary action on the page. If you are doing this in app make it show up inside the part of the product the feature would actually live in.

Step 4: Reveal and collect

When the person clicks, show them a modal or page that says something like:

Thanks for clicking. We are validating interest in this feature right now. Drop your email to get it first.

Keep it short. The goal is to turn a fake entry point into a real lead for that feature. This also speaks to the 36 percent who said the method feels misleading. We tell the truth right away.

Step 5: Track and timebox

Track three numbers.

1. How many people saw it
2. How many people clicked
3. How many people completed the form

Leave it live for a few days or one week. Then make a decision. Do not leave dead doors all over your app. That is how trust gets chipped away.

Make a decision based off the data

A fake door only helps if it gives you a real yes or a real no. That means we have to set rules before we put it in front of users.

Set the success line before launch

If this door is inside your product and only the right users will see it look for a click rate that makes sense in context. For many small startups a 5 to 15 percent click rate on a very relevant in app CTA is strong enough to move the idea forward. If you are driving colder traffic with an ad count email captures as the main win.

Map this to what founders said they value.

• 39 percent want proof that people actually want the idea
• 34 percent want to collect early signups
• 27 percent want to save engineering time

Pick the one that matters for this test and judge the numbers against that.

Show it only to the people who care

If you are testing a reporting feature show it to users who created reports in the last 14 days. If you are testing team accounts show it to users who already invited someone. Relevance makes the signal cleaner and it reduces the risk that people will think you are playing tricks.

Add a removal plan

Before you start write down the start date the end date the owner the goal number and where the door lives. When the test ends remove the door. Then email the people who clicked. Tell them what you learned and what you are building instead. This turns a small experiment into a trust building touchpoint.

When you run it this way you get a fast answer. You either have enough intent to justify a build or you have a clear reason to park the feature. Then you can move on to the next door.

Tools to run a fake door without code

I hear this in almost every call. I would do this if it did not require my developer. Good. Here is the stack I give founders.

Note: I am not affiliated with these companies. Pick what works best for your goals and stack.

To place the door

• In app and no code: Userpilot, Pendo, Appcues, Intercom. These let you add modals tool tips, slide outs and small banners to live products without shipping code.
• On landing pages: Webflow, Unbounce, Framer, Carrd. These let you spin up a page in under an hour.
• In email: Whatever you already use. Kit (previously ConvertKit), MailerLite, HubSpot, Mailchimp. The link becomes the door.

To track the door

• GA4 event on-click
• Mixpanel or Amplitude for funnels and cohorts
• Native analytics in the in app tool if you use Userpilot or Pendo
• Simple UTM parameters if you are running ads

To follow up

• Your CRM or email tool
• A short survey with Jotform or Typeform to understand intent
• A calendar link if you want to talk to the highest intent people

To control exposure

• Use a feature flag product if you want to show the door only to a small cohort
• Segment users within an existing product to target heavy users only

I always prefer simple over robust or perfect. I would rather see you ship one door in two hours with Webflow and GA4 than wait two weeks for a designer to mock it.

Metrics and decision rules

A fake door only works when you decide what success looks like before anybody clicks. I write this into the brief.

Track three numbers

1. Views: People who saw the door.
2. Clicks: People who attempted to go through.
3. Completions or conversions: People who finished the form or waitlist.

Simple formulas

• Click rate: Clicks ÷ views
• Completion rate: Completions ÷ clicks

Benchmarks I use

Ultimately, your targets will depend on your business model and financial forecasts. But, I’m providing rough guidelines to get started. Please adapt accordingly to your business.

• In-app promotions that are highly relevant and shown only to the right segment: 5-15% click rate is strong enough to build
• Marketing landing page to a warm audience: 3-8% click rate, although check your financial model to see if 3% would be profitable
• Paid ad to a cold audience: Judge on an email capture rate, like 25% or higher, not on the ad’s clickthrough rate

These are starting lines. Your own product may show higher or lower. The important thing is to decide your pass line in advance and write it down.

Timebox

• Keep the door live for 7 to 14 days
• Remove it on the date you wrote in the brief
• Email everyone who clicked

Timeboxing protects trust. It keeps old fake doors from cluttering up your UI. It also gives you a clean dataset.

Keeping trust while you test

Thirty six percent of the founders in my survey said this method feels misleading. I take that seriously. I treat fake doors as a conversation not a trick.

Rules I follow

• I tell the truth on the first screen after the click
• I say thank you because they helped me do product research
• I offer something small such as early access a discount on launch or a short roadmap call
• I keep the audience tight so the risk is small
• I always follow up even when I decide to park the idea
• I document the result and share it with the team so everyone sees that we listen

If you are in a sensitive industry add one more line that explains why you validate ideas this way. People accept experiments when you explain the benefit.

How to run a fake door without feeling fake

A lot of founders told me this is the part that makes them pause. Thirty six percent said it feels misleading. I get that. You spent months trying to convince people to trust you. You do not want to undo it with one experiment.

Here is how I run it so trust goes up instead of down.

My rules

• Tell the truth right after the click. One modal or one landing page that says you are exploring the feature and that their click gave you a real signal.
• Say thank you. The person helped you shape the product. Say so.
• Offer something. Early access, a discount on launch, a short call, a roadmap preview. Small founders win when they make people feel closer to the build.
• Keep the cohort tight. If you are worried about blowback, only show the door to people who use that part of the product.
• Follow up even when you decide to park it. Send a short note. Tell them only 7 people clicked so you decided to work on another item first. That type of message creates trust.

This approach lines up with what you see in good product research. Be transparent. Timebox it. Close the loop. When you do that, a fake door becomes a signal of respect. You asked before you built.

Fake door test examples

Feel free to borrow any of these patterns.

Buffer style validation

Buffer ran a very simple test in their early days. A landing page that explained the product. A button that said Plans and Pricing. A second page that said the product was not live yet and asked for an email. That gave them demand and pricing signals before code.

Dropbox style attention grab

Before building the full product, Drew Houston recorded a short video that walked through the experience and linked to a waitlist. That was a form of fake door. It proved people would sign up for a tool like that which made the heavy engineering investment worth it.

Analytics tool feature

Let’s say you run a 2-person analytics tool. Customers keep asking about CSV export. You are not sure how many will use it. You add an Export to CSV button on the report list. 11% of active users click within 4 days. 60% of those leave an email. You now have a real signal and a small beta list.

A market test example

Let’s say have two feature ideas. An AI summary or webhook notifications. You create two different links in your newsletter. Both go to transparent wait pages. You look at clicks and email captures. Highest intent wins. That is backlog sorting without a single code change.

Product team inside an active SaaS

Add a small CTA inside the part of the app where the future feature belongs. Show it only to users who touched that area in the last 14 days. Route to a short modal. Ask what they wanted to do.

Growth or marketing team

Run a low budget ad to a landing page for the future feature. Tell people you are validating interest. Count CTR and email capture. This is the painted door version that tools like Userpilot describe.

E-commerce or marketplace

Add a category or filter that does not exist yet. When people click show a small message that says you are stocking this next season. Capture email. This is a real way to see demand before you commit inventory.

Company with a freemium plan

Show a new upgrade row in the pricing table. When people click tell them this upgrade is in planning. Count clicks. Invite them to a roadmap session. Then go back to product with a list of names.

Newsletter or media operator

Drop two different feature links into the same issue. Both go to transparent wait pages. Compare clicks. Keep the winner. This is the simplest backlog sorter I know.

Enterprise or B2B account team

Send a feature preview link to a single customer who asked for it. Call it validation. If they and two more accounts click you have a customer led signal to take to product.

The pattern across all of these examples is the same. Pick the smallest surface your audience already sees. Put the door there.

Stealable asset

Copy this outline below into a doc and run it today.

Launching Next Fake Door Test Brief

• Hypothesis: Users who create projects want to export them to CSV to share with clients.
• Audience: Logged in users who created a project in the last 14 days.
• Door location: Project list view. Primary button.
• Door copy: Export to CSV
• Reveal copy: You found a brand new feature. We are validating interest in CSV export right now. Add your email to get it first. Tell us what format you need.
• Success metric: At least 30 clicks and at least 10 email submits in 5 days.
• Owner: Growth or founder.
• Removal date: Fourteen days from launch.

Run it once. Write down what happened. Improve the next one.

Taking the first step

Many founders are trying to market an offering that they already built, even though no one has asked for it. That is expensive. A fake door is cheaper.

The real win is clarity. You know what to build because people clicked. You know what to park because people scrolled past it. You know who to invite to a beta because they gave you an email.

FAQs about fake door tests

What is a fake door test

A fake door test is a controlled experiment where we show people an entry point to an offer or feature that is not live yet. We then tell them the truth, capture their intent, and decide if the idea should be developed.

Is fake door testing ethical

Absolutely, but you need to set expectations with people. Tell people immediately that the service/offer is not available, capture only the data you need, and give them a timeline on when you will follow up. It becomes unethical when you hide the fact that the feature is not ready or when you run it for weeks without closing the loop.

How many people do I need for a fake door test

For small offerings, I aim for at least 100 clicks and at least 5 completions inside a week. That is the target I used in the fake door test brief at the end of the original article. Although, 200-400 clicks would be better, as I once saw a fake door test perform well on 200 clicks that didn’t scale to 1,500 clicks. For higher traffic products, you can push this higher.

How do I know if my fake door test was successful

Decide on the success rates before launch, then check three numbers: views, clicks and completions. If the click rate and completion rate meet or beat the threshold I set, I move the idea forward or at least talk to the people who raised their hands.

Where should I place the fake door for the best signal

Place fake door tests where target customers already are, such as on a landing page, a menu item or within a tool.

How long should I run a fake door test

I keep fake door tests live for 7 to 14 days. Write the start and end date into a planning doc and remove the door on schedule so people do not keep clicking on something that will not immediately deliver.

Can I run more than one fake door at a time

Avoid stacking multiple fake doors in front of the same user at the same time. Instead, segment users to only show one test at a time.

How is a fake door test different from A/B testing

A/B testing compares two working experiences to see which one wins. Fake door testing checks if the experience deserves to be built. If you have high enough traffic levels, you can A/B test two fake door tests against each other.

What do I do if the test fails

Email everyone who clicked. Tell them the outcome, and thank them. If you’d like, you can include a survey to ask what features/offerings would they like to hear next, and then follow-up with them as part of an idea validation conversation. This single message builds more trust than pretending the test never happened.