Key Takeaways
- 42% of startups fail because they built something nobody wanted — and the cheapest fix is to test demand in 7 days, before any code.
- The 7-day framework: 1 problem statement + 100 surveys + 10 interviews + 1 landing page + a $200 smoke test = a clear GO / PIVOT / KILL signal.
- Total cost: under $300 (free survey tool + landing page $0-15 + $200 paid traffic) and zero lines of product code.
- What "validated" looks like: 30%+ survey signal, 7+ interviews with the same pain pattern, 3%+ landing-page email conversion.
- The single biggest mistake: pitching the solution before you've heard the problem in the customer's own words.
Startup idea validation is the process of testing whether the problem you want to solve is painful enough, frequent enough, and addressable enough to justify building the business. Most failed startups didn't fail at execution — they failed at validation. The founders built something nobody wanted because nobody asked the customer first.
Why 90% of startups skip validation
Most founders skip validation for two reasons. First, building is more exciting than asking — code looks like progress, conversations don't. Second, validation feels like it might disconfirm an idea the founder is already emotionally committed to. That's exactly the point. You want to disconfirm a bad idea in 7 days, not 7 months.
This guide walks through the smallest set of experiments that gives you real signal on three dimensions: problem depth, audience reach, and willingness to pay. No code. No funding. No co-founder required. Read it once, then run it.
The 7-day framework at a glance
| Day | Activity | Signal you're testing | Cost |
|---|---|---|---|
| Day 1 | Write a 1-sentence problem statement | Specificity of the problem | $0 |
| Day 2 | Survey 100 prospects (5 questions) | Problem frequency + acuity | $0 |
| Days 3-4 | 10 customer interviews (20 min each) | Workflow + workaround patterns | $0 |
| Days 5-6 | Landing page + $200 smoke test | Willingness to give an email (proxy for $) | $200-300 |
| Day 7 | Score, decide, document | Overall: GO / PIVOT / KILL | $0 |
Day 1: Write the problem statement
Before any survey, interview, or landing page, write your problem statement in one sentence using this exact format:
If you can't fill every slot with a concrete word, your idea isn't ready to validate — you're solving a vague feeling, not a problem. Spend the morning rewriting until every blank is specific.
Bad: "Small businesses need better marketing."
Good: "Solo agency owners struggle to retain clients past month 3 because manual reporting in Google Sheets eats 8 hours a week."
The good version names the audience, the outcome, the workaround, and the pain — each in concrete language.
Day 2: Survey 100 prospects
Build a 5-question survey in Tally or Google Forms. Post the link to 5 relevant subreddits, 3 Facebook groups, and DM 20 prospects on Twitter or LinkedIn. Target: 100 completed responses by end of Day 2.
| # | Question | Answer type | What it measures |
|---|---|---|---|
| 1 | Do you experience <the pain>? | Yes / Sometimes / No | Existence of the problem |
| 2 | How often does this happen? | Daily / Weekly / Monthly / Never | Frequency |
| 3 | What do you do today to handle it? | Open text | Workaround behaviour (the gold) |
| 4 | How painful is it, 0-10? | Slider | Acuity / intensity |
| 5 | Would you pay to solve it? | Yes / Maybe / No | Willingness-to-pay signal |
At least 30% answer "yes" to Q1 AND rate the pain ≥7 on Q4. If under 20%, the problem isn't acute — pivot the audience or the angle.
Days 3-4: Run 10 customer interviews
From your survey respondents, pick 10 who scored the pain at 8+ and DM them for a 20-minute call. Use Rob Fitzpatrick's Mom Test rules: ask about past behaviour, not future intent.
The four questions that do all the work:
- "Tell me about the last time you faced this problem." Past-tense, specific event. Disarms hypothetical thinking.
- "What did you do?" Captures the actual workflow and workaround in their language.
- "How much time or money did it cost?" Quantifies pain in their currency.
- "What did you try before this?" Surfaces failed alternatives — which is your competitive landscape.
Never pitch your solution in the call. The moment you describe what you're building, the interviewee shifts into politeness mode and tells you what you want to hear. Listen for 18 minutes. Pitch in the last 2 only if they ask.
After 10 calls, write up the pattern. If 7+ interviewees describe the same workflow, the same workaround, and the same frustration, you have a validated problem. If interviews surface 10 different pains, the audience is too broad — narrow the segment.
Days 5-6: Ship a landing page + smoke test
Build a one-page landing site in Carrd, Framer, or Webflow. Structure:
- Headline: your problem statement (the one you wrote Day 1)
- Subhead: one-line solution description
- 3 bullets: the 3 most painful workarounds from interviews
- Primary CTA: "Get early access" → Tally email form
Run $200 of paid traffic via Reddit Ads, Twitter Ads, or a niche newsletter sponsorship. Target the exact persona from your interviews.
Below 1% conversion usually means the message isn't resonating — that's a headline or audience problem, not a product problem. Iterate the headline before you kill the idea.
Day 7: Decide GO / PIVOT / KILL
Score the week against three criteria. Two yes's = GO. One yes = PIVOT. Zero yes's = KILL.
| Criterion | Pass threshold | Your number | Pass? |
|---|---|---|---|
| Pain depth | 7+ of 10 interviewees describe the same acute pain | __ / 10 | Y / N |
| Audience reach | ICP in 1 sentence; find 1,000 of them on a single channel | __ channels | Y / N |
| Willingness to pay | Landing page converts above 3% to email signup | __% | Y / N |
One yes usually means the problem is real but the angle is wrong. Re-write the problem statement, re-target the audience, re-run Days 1-7. Most "killed" ideas in the wild are actually first-iteration ideas that needed a pivot.
Validation benchmarks — what good looks like
How your numbers compare to the median of 180 validation cycles tracked in 2024-2026:
5 common validation mistakes to avoid
Your network will tell you the idea sounds great because they love you. Survey strangers from the actual target segment.
"Would you use a tool that does X?" gets 70% yes from anyone. "Tell me about the last time you faced this problem" gets the truth.
Surveys and interviews test pain. The landing page tests willingness to act. Without the smoke test, you'll build something people say they want but won't pay for.
One bad result usually means wrong audience or wrong angle. Pivot the inputs, not the idea, before you kill.
If you start coding during Days 1-7, the sunk cost will bias every interpretation. Validate first, code zero.
Frequently asked questions
First 10 Customers Playbook · SaaS Pricing for Founders · Startup glossary · Free business tools · Free idea generator