How to Validate a Startup Idea in 7 Days (The Complete Playbook)

Most founders spend 3–6 months building before they discover their idea has a fatal flaw. This is entirely preventable. You can learn 80% of what you need to know in 7 days — without writing a line of code.

Need to define your product scope? Use our interactive Feature Prioritizer to filter your absolute must-haves, or apply for a complimentary Free MVP Scope blueprint designed by our Senior Architect.

Day 1: Define the Hypothesis

A proper hypothesis has 3 parts:

Who: The specific person with the problem

Problem: The exact pain they experience, with real consequences

Willingness to pay: A specific price they would pay to solve it

Template: *"[specific person] struggles with [specific problem] which causes [specific consequence]. They would pay $[price]/month for a solution that [core function]."*

Write this down. It is what you are testing.

Day 2: Research the Market

Google searches to run:

• "[problem] reddit" — find organic discussions
• "[competitor] review" — read G2/Capterra reviews for complaints
• "[problem] alternative" — see what people currently use

What you are looking for: evidence people complain about this problem unprompted. If you cannot find anyone, that is important data.

Day 3: User Interviews (5 conversations)

The 5 questions that matter:

*"Walk me through the last time you dealt with [problem]."*

*"What is the worst part of that process?"*

*"What have you tried to fix this?"*

*"What would the ideal solution look like?"*

*"If a tool existed that did [core function], how much would you pay for it?"*

The signal you want: 3+ people describing the same pain in similar language, expressing genuine frustration, and mentioning they have tried to solve it.

Day 4: Build a Landing Page

A "fake door" landing page describes your product before it exists. It needs:

• A specific headline (problem + solution in one sentence)
• 3 benefit bullets
• A price anchor ("Early access: $19/month")
• A single CTA: "Join the waitlist"

Tools: Carrd, Webflow, or Framer. Build this in 2–3 hours.

Day 5–6: Drive Targeted Traffic

Send 100–200 qualified visitors to your page via:

• 3–5 niche communities
• Your 30 most relevant LinkedIn connections
• Relevant subreddits
• DMs to people who have posted about the problem

Conversion benchmarks:

• Below 5%: messaging is not resonating
• 5–15%: moderate demand
• Above 15%: strong signal

The Decision Rule Before You Start

Write your pass/fail thresholds before you drive traffic. For example: 10 interviews, at least 3 people with the same urgent pain, 5% waitlist conversion from qualified traffic, 3 booked follow-up calls, or 1 paid pre-order. The exact threshold depends on the market, but it must exist before the results arrive.

This prevents founder math. Without a rule, every weak signal starts to look promising because you want the idea to work. A validation sprint is useful only if it can kill or reshape the idea.

Day 7: Analyze and Decide

Signal	What It Means
15%+ landing page conversion	Strong demand
3+ interviews with same pain language	Real problem, right ICP
People asked "when is this launching?"	Product urgency
Nobody converted	Pivot before building

If the signal is strong — move to scoping and building. If it is weak — pivot the hypothesis and repeat. It is always better to find this out now than 6 months into development.

---

Written by Milad Kalhur *Founder & Chief Architect at Needmvp* Milad has designed, architected, and shipped over 40+ web applications for Y Combinator founders and VC-funded startups. Having pioneered the 3-week fixed-price MVP model, he actively consults on software development efficiency, database modeling, and high-performance serverless architecture.