What is a fake door test and how do you run one in 24 hours?

A fake door test is a landing page describing a solution to a specific problem with a signup form for something that does not yet exist. Build it in an afternoon using Framer, Carrd, or plain HTML. Drive 50-200 targeted visitors via community posts or $20-50 in ads. Measure how many attempt to sign up.

How many user interviews are needed to validate a SaaS idea?

10-15 targeted conversations with your ideal customer profile are sufficient to validate or invalidate most SaaS ideas. Target people who have expressed the specific problem publicly, not just your network. Four out of five people describing the same frustration in similar language is genuine validation.

What signup numbers actually indicate SaaS validation?

Under 10 signups: wrong problem or wrong audience. 10-20: weak signal, iterate the positioning. 20-50: moderate validation, build a focused MVP. 50-100: strong validation. Over 100: build immediately. The number matters less than follow-up engagement. People who email asking when the product will be ready show real buying intent.

What three questions should every SaaS validation interview include?

How do you handle this problem today? What have you tried that did not work? What would an ideal solution look like? These reveal current workarounds (your real competition), failed alternatives (what not to build), and the exact language users use to describe value (your marketing copy). Record exact wording.

How to Validate a SaaS Idea in 7 Days Without Code

Q: How do you write a problem statement strong enough to test?

A valid problem statement names a specific person, a specific pain, and a measurable cost. 'Solo founders waste 10 hours per month reconciling subscriptions across multiple tools' is testable. 'An AI-powered dashboard' is not. If it cannot be written in one sentence, the problem is not understood well enough to validate.

Most founders spend months building a product nobody wants. The tragedy is not that the product failed. It is that the failure was preventable with one week of validation before writing a line of code.

This is a proven process to validate a SaaS idea in seven days. No code required. No budget required. Just a laptop and the willingness to talk to people who have the problem.

Day 1: Define the Problem in One Sentence

Write one sentence that describes the problem you are solving. Not what your product does. What problem the user has. "Solo founders waste 10 hours per month reconciling subscriptions across multiple tools" is a problem statement. "An AI-powered subscription management dashboard" is a product statement. You need the problem.

If you cannot write the problem in one sentence, you do not understand it well enough to build a solution. Keep refining until the sentence is crystal clear.

7-Day SaaS Idea Validation Sprint

Day 1

Define the problem

Day 2

Find 20 people

Day 3

Send 20 messages

4-5

Have conversations

Day 6

Build fake door

Day 7

Drive traffic

0-9

Wrong problem

10-20

Weak signal

20-50

Moderate

50-100

Strong

100+

Full validation

Signups below the bar show you need to reframe. Signups above it mean you can start building.

Day 2: Find 20 People Who Have This Problem

Search Twitter, Reddit, IndieHackers, and LinkedIn for people who have publicly mentioned this problem. Founders complaining about subscription overload. Developers frustrated with deployment workflows. Marketers struggling with analytics. Find 20 people who have expressed this pain in their own words.

Day 3: Send 20 Messages

Message each person. Not a pitch. A question: "I noticed you mentioned [specific problem]. I am researching this space. Would you be open to a 10-minute chat about how you handle it today?" Expect 6 to 8 replies. Schedule 4 to 5 conversations.

Message template: "Hey [name], saw your post about [problem]. I am researching how founders handle this and would love your take. Got 10 minutes this week for a quick chat? No pitch, just learning." Personalize the problem reference. Do not send copy-paste.

Never mention your product idea in the first message. You are researching the problem, not selling the solution. If you pitch too early, people stop being honest about their pain.

Days 4-5: Have the Conversations

Ask three questions: How do you handle this problem today? What have you tried that did not work? What would an ideal solution look like for you? Listen more than you talk. Take notes on the exact words they use. Those words become your marketing copy.

If four out of five people describe the same problem and the same frustration, you have validation. If the problems are all different, you do not have a market yet.

Day 6: Build a Fake Door

Create a simple landing page that describes the solution in the language your potential users used. Add a signup form. No product needed. Just a page that tests whether people want what you are building.

Day 7: Drive Traffic and Measure

Share the landing page in the communities where your target users gather. Post it in relevant Reddit threads. Share it on Twitter with the problem statement. Run $20 to $50 in targeted ads if you want faster data.

If 50 or more people sign up in a week, you have validation. If fewer than 20 sign up, you either have the wrong problem or the wrong audience. Either way, you learned this in seven days instead of seven months.

What Your Signup Numbers Tell You

0 to 9 signups: your problem statement is wrong or your landing page does not communicate value. Rework both before spending more money. 10 to 20 signups: weak signal, the problem exists but your solution positioning needs work. Iterate the page and test again. 20 to 50 signups: moderate validation, the problem is real, move forward with a focused MVP. 50 to 100 signups: strong validation, you have product-market fit potential, build fast. Over 100 signups: full validation, start building immediately and keep these people updated.

The signup number matters less than the conversation quality. If people sign up and also email you asking when it will be ready, you have real validation. If they sign up and never respond to follow-ups, you have weak validation.

How to Validate a SaaS Idea in 7 Days Without Writing a Line of Code

Day 1: Define the Problem in One Sentence

Day 2: Find 20 People Who Have This Problem

Day 3: Send 20 Messages

Days 4-5: Have the Conversations

Day 6: Build a Fake Door

Day 7: Drive Traffic and Measure

What Your Signup Numbers Tell You

Frequently asked questions

Related articles

Why No-Code MVPs Fail Founders (And What to Do Instead)

The Real Cost of Building a SaaS MVP: Time, Money, and What Nobody Tells You

The First 50 Users: A No-BS Launch Playbook for SaaS Founders