Topic Hub
Startup Validation — The Complete Guide
The complete hub for everything we publish on testing startup ideas before you build them. Built for first-time founders, indie hackers, and anyone staring at a blank Notion doc.
Last updated · August 31, 2026
Key takeaways
Startup validation, summarized
- Startup validation is the disciplined process of testing the assumptions behind an idea before committing months of building.
- Validation answers four questions: is the problem real, can you reach the customer, will they pay, and can you execute?
- The output is evidence, not certainty — every claim is sourced and every score traces back to a specific fired rule.
- Validation is cheaper than building: a problem interview, a landing-page test, and a paid pilot can run in two to six weeks.
- The output you want is not a score but the identification of the single assumption that, if false, would invalidate the rest of the plan.
Concepts in this guide
How validation connects to the rest of starting a company
Validation is not a single topic. It is the spine that connects every other part of starting a company. The links below show the chain, in the order a founder typically walks it.
Validation
Test the problem and customer.
Customer discovery
Find the people who have the problem.
MVP
Build the smallest useful version.
Pricing validation
Test willingness to pay.
Willingness to pay
Define the term, then test it.
First customers
Reach the first 10 paying users.
Product–market fit
Earn retention without paid acquisition.
Problem–solution fit
Confirm the proposed solution fits a real problem.
Customer interview questions
Ask questions that produce evidence, not compliments.
Positioning against an incumbent
Write the [for–unlike] wedge that holds in a sales call.
Definition
What is startup validation?
Startup validation is the disciplined process of testing the assumptions behind an idea — the problem, the customer, the willingness to pay, and the founder's ability to execute — before committing months of work to building the product.
It is not a single event. It is a sequence of cheap, fast experiments that turn vague intuition into evidence you can act on. The goal is not to prove the idea is good. The goal is to discover, as early and as cheaply as possible, where the idea might fail.
Why it matters
The cost of skipping validation
Most failed startups do not fail at launch. They fail at the keyboard — months earlier, when the founder chose to build a product nobody had asked for. The four months you spend coding are the four months you cannot spend learning what to build instead.
Time
Months of building, gone
Most founders spend 3–6 months building before they discover the problem nobody asked them to solve. Validation can find that out in days.
Money
Capital spent on untested bets
Every month of building is a month of runway burned on an idea that may have no customers. Validation reduces the size of the bet.
Confidence
Decisions backed by evidence
A validated idea still might fail. But the failure is a market failure, not a guess. You learn from it instead of blaming the execution.
Pick the tool
Which tool fits your question?
All four tools run the same Startup MRI engine. The difference is which question each one helps you answer first. Pick the framing that matches where you are today; switch any time.
If your question is…
…which assumption should I test first?
Names the rung to climb this week. The 7-rung Validation Test Ladder maps each Startup MRI dimension to its cheapest behavior-signal test, ordered by what the founder can run tomorrow.
Open →If your question is…
…is this idea worth my execution capacity?
Places your idea on a 2×2 idea-strength vs execution-readiness grid. Each quadrant maps to a distinct next action — build, co-found, reposition, or skip.
Open →If your question is…
…what number does this idea deserve?
Returns a 0–100 score across the seven dimensions, with four bands and four patterns so you can interpret the number rather than just see it.
Open →If your question is…
…what should I do this week?
Returns the full Startup MRI report: the single critical assumption, a 7-Day Validation Action Plan derived from the highest-risk dimension, and a 4-week first-customer plan.
Open →
The learning path
A guided reading path
Start at the top or jump to the product type closest to your idea. Each step links to a published guide and adds a different validation lens.
Beginner path
Start with the problem and customer before choosing a product type. Finish these five steps, then move to the experiments that fit your idea.
Start here — the mindset
Why Founders Build Before They Validate
Why do so many founders reach for the keyboard before they reach for the phone? Read this first to understand the psychological pattern that makes us skip validation.
15 min read ·Read this step →
The framework
How to Validate a Startup Idea Before You Build
A practical four-stage framework for testing the problem, the customer, the business model, and your own ability to execute — before writing a line of code.
17 min read ·Read this step →
Problem-solution fit
Problem-Solution Fit: How to Know Your Solution Solves a Real Problem Before You Build It
The rung before product-market fit: does the proposed solution address a real, recurring problem for a defined customer? Five rungs of evidence, six failure modes, and a 14-day validation framework built around workaround analysis instead of polite-yes interviews.
22 min read ·Read this step →
The checklist
Startup Validation Checklist: Before You Build
Thirty concrete checks across the four stages. Read it once, then come back with your specific idea in mind.
17 min read ·Read this step →
Finding the first customers
How to Find Your First Customers Before You Build
Where the future customers actually gather, how to start a conversation that is not a pitch, and a weekly plan you can start this week.
16 min read ·Read this step →
Willingness to pay
How to Test Willingness to Pay Before You Build: Six Experiments, Four Cases, and a Seven-Day Plan
Interest is not payment. The most dangerous startup assumption is that 'I would buy this' means anything. Learn the experiments that separate polite agreement from real money.
14 min read ·Read this step →
Willingness to pay validation
Willingness to Pay Validation: The Framework, the Signal Ladder, and Why Interest Is Not Payment
A definitions-first guide to what willingness to pay actually means, the five-rung signal ladder from polite words to real money, and the cheapest experiment you can run this week.
14 min read ·Read this step →
Product-market fit
Product-Market Fit Validation: How to Know You Have It Before You Announce It
PMF is observed, not declared. The four signals that show you have it, the seven failure modes that show you do not, and a 30-day validation framework that separates real retention from paid acquisition.
22 min read ·Read this step →
MVP validation
MVP Validation: How to Test a Minimum Viable Product Before You Build It
How to test the smallest useful version of your product before committing to a full build. Six methods ranked from cheapest to strongest, a five-step framework, and the seven failure modes that show up before the founder notices them.
20 min read ·Read this step →
SaaS specifically
How to Validate a SaaS Idea Before You Build It
A focused playbook for early-stage SaaS and micro-SaaS founders — the recurring-revenue assumption stack and the cheapest experiment that tests each one.
16 min read ·Read this step →
AI specifically
How to Validate an AI Startup Idea
Test workflow value, output quality, model-layer risk, and defensibility before treating an AI capability as a business.
21 min read ·Read this step →
AI versus SaaS
AI Startup vs SaaS Startup: How Validation Is Different
Compare the validation questions that change when software depends on a model layer rather than only conventional product infrastructure.
18 min read ·Read this step →
Marketplace specifically
How to Validate a Marketplace Startup Before You Build It
Test both sides of the market, the first narrow wedge, and the conditions that let useful transactions happen.
17 min read ·Read this step →
Mobile specifically
How to Validate a Mobile App Idea Before You Build It
Validate the user habit, distribution path, retention signal, and app-store constraints before building the app.
17 min read ·Read this step →
Chrome extensions specifically
How to Validate a Chrome Extension Idea Before You Build It
Test the browser workflow, permission boundary, distribution channel, and repeat use case before shipping an extension.
16 min read ·Read this step →
B2B specifically
How to Validate a B2B Startup Idea Before You Build It
Test the problem, buying committee, design-partner path, and evidence required for a business customer to adopt the product.
17 min read ·Read this step →
API specifically
How to Validate an API Startup Idea Before You Build It
Test the developer workflow, integration friction, reliability expectations, and first distribution path before building the API.
18 min read ·Read this step →
Distribution specifically
Distribution Channels Ranked for Solo Founders
Eleven customer-acquisition channels ranked for solo founders — and the 4-week first-100-customers plan that tests two of them without burning out.
14 min read ·Read this step →
The Mom Test
The Mom Test Explained for Solo Founders
Rob Fitzpatrick's three rules applied to indie founders: talk about their life, not your idea; ask about specifics in the past; listen more. Plus a 5-interview script you can run this week.
14 min read ·Read this step →
Customer interview questions
Customer Interview Questions for Startup Validation: How to Ask Ones That Produce Evidence
The question-by-question execution guide: how to ask customers about past behavior, current workarounds, real spending, and decision context — and how to convert each answer into a smaller to-do list.
18 min read ·Read this step →
Demand before coding
How to Validate Demand Before Coding (Without Building the Wrong Thing)
The pre-build gate for non-technical and solo founders: five evidence checks that justify starting to code, three labeled examples, and a seven-question rule that decides build-now-vs-validate-more.
14 min read ·Read this step →
Intermediate paths
Choose the product-specific or distribution path that matches your idea. Each guide tests a different risk; stop when the evidence changes your next decision.
Featured articles
Every pillar, by collection
The pillar articles, organized into four editorial collections. Each collection answers a different question in the validation process.
Foundations
The mindset before the method
Customer Discovery
Who has the problem, and how do you find them?
Customer Research
How to Know When Customer Interviews Are Enough (A Stop-Rule for Solo Founders)
A practical stop-rule for early-stage customer interviews: when to stop, how to recognise the saturation point, why twelve is usually the right number for a single segment, and the four failure modes that keep founders interviewing long after the evidence has stopped arriving — including the difference between code saturation and meaning saturation and the named Guest, Bunce & Johnson (2006) study that produced the empirical baseline.
13 min read
Customer Research
Customer Interview Questions for Startup Validation: How to Ask Ones That Produce Evidence
Customer interview questions for startup validation, organized by what you need to learn — past behavior, current workarounds, decision context, and spending — plus the questions founders should stop asking, an interview-to-decision framework, and a realistic B2B SaaS scenario.
18 min read
Customer Research
The Mom Test Explained for Solo Founders
Rob Fitzpatrick's book, applied to indie founders — the three rules, twelve questions, and a 5-interview script you can run this week to test whether anyone has the problem you think they have.
14 min read
Customer Research
How to Find Your First Customers Before You Build
Where early customers actually gather, how to recognize real Early Adopters vs polite audiences, and a one-week customer-discovery plan you can start this week.
16 min read
Validation
Testing the idea before building it
Validation Guide
How to Size a Market You Can Actually Reach: TAM, SAM, SOM, and the Two Numbers That Are Usually Useless
A founder's guide to estimating the market they can actually reach — what TAM, SAM, and SOM actually mean, why two of the three are usually useless for solo founders, how to do a defensible bottom-up sizing in a single afternoon, where to source the data, and the failure modes that produce a market-size claim a partner or investor will not trust.
16 min read
Validation Guide
How to Write a Smoke-Test Landing Page in 60 Minutes
The shortest path from a hypothesis to a real conversion number — page structure, headline formula, the four signal lines, the seven things to leave off, the 60-minute build checklist, and how to read the conversion data at small N.
14 min read
Validation Guide
Fake Door Test: How to Validate Demand Without Writing a Single Line of Code
A complete playbook for the fake door (painted door) test — the cheapest credible demand test in the startup validation toolkit. Includes the original methodology from Alistair Croll & Benjamin Yoskovitz's Lean Analytics, the six-step process, the Unbounce 2024 benchmark that defines what counts as a 'good' smoke-test conversion rate, the two documented case studies (Buffer, Dropbox), the seven failure modes that produce false positives, and what the test cannot prove.
16 min read
Validation Guide
How to Validate Demand Before Coding (Without Building the Wrong Thing)
A step-by-step playbook for non-technical and solo founders who need to know whether anyone will pay for an idea before writing a line of code — including the five pre-code evidence checks, three labeled hypothetical examples, the seven-question rule that decides 'build now vs. validate more,' and the failure modes that lead founders to mistake enthusiasm for demand.
14 min read
Monetization Validation
How to Price a New SaaS Product: Three Decisions, Four Questions, and the Only Pricing Test That Survives Launch
The three pricing decisions a new SaaS founder actually owns (model, value metric, price points), the four Van Westendorp questions that produce real willingness-to-pay data, and the eight-week playbook that turns the answers into a defensible price.
18 min read
Validation Guide
Startup Failure Analysis: How to Read a Failed Startup the Right Way
Startup failure analysis is the discipline of converting documented startup failures into testable assumptions. Five real cases — Quibi, Webvan, Juicero, Homejoy, WeWork — analyzed with a seven-rung framework, then turned into the validation experiments a solo founder can run this week.
26 min read
Validation Guide
Lean Startup Validation: How To Choose, Design and Interpret Validation Experiments
How to use Eric Ries's Build-Measure-Learn loop to pick the next validation experiment — including the five-question decision framework, decision-threshold thinking, three labeled hypothetical examples, and the failure modes that distort the loop before the founder notices them.
17 min read
Validation Guide
Problem-Solution Fit: How to Know Your Solution Solves a Real Problem Before You Build It
Problem-solution fit is the state where a defined customer has a defined problem and a defined solution would meaningfully improve their situation. The five rungs of evidence that prove the fit is real, the six failure modes that show it isn't, and the 14-day validation framework that separates real pain from polite enthusiasm.
22 min read
Validation Guide
MVP Validation: How to Test a Minimum Viable Product Before You Build It
MVP validation is the discipline of testing the smallest useful version of your idea before committing months to a full build. Six methods, a five-step framework, and the seven failure modes that show up before the founder notices them.
20 min read
Validation Guide
Product-Market Fit Validation: How to Know You Have It Before You Announce It
Product-market fit is observed, not declared. The four signals that show you have it, the seven failure modes that show you do not, and a 30-day validation framework that separates real retention from paid acquisition.
22 min read
Monetization Validation
Willingness to Pay Validation: The Framework, the Signal Ladder, and Why Interest Is Not Payment
What willingness to pay actually means, the five-rung signal ladder from polite words to real money, and the Problem → Customer → Value → Price → Payment framework every pricing experiment is a sub-test of — before you write code.
14 min read
Validation Guide
How to Validate an API Startup Idea Before You Build It
The API- and developer-tool-specific tests for technical buyers, integration cost, trust, documentation prototypes, and design-partner pilots — before you write the first endpoint. A practical handbook for API founders, SDK builders, infrastructure product teams, and developer-tool indie hackers.
18 min read
Validation Guide
How to Validate a B2B Startup Idea Before You Build It
The B2B-specific tests for buying committees, procurement, ROI proof, founder-led sales, and the manual pilot — before you write code. A practical handbook for SaaS founders selling to businesses, enterprise software teams, and technical founders.
17 min read
Validation Guide
How to Validate a Chrome Extension Idea Before You Build It
The browser-extension-specific tests for Manifest V3 fit, Chrome Web Store policy, distribution outside store search, willingness to pay, and unlisted pre-launch testing — before you ship a packaged extension. A practical handbook for indie hackers, SaaS founders, AI tool builders, and browser extension developers.
16 min read
Validation Guide
How to Validate a Mobile App Idea Before You Build It
The mobile-app-specific tests for problem, retention, onboarding, distribution, and willingness to pay — before you ship a binary to the App Store. A practical handbook for consumer, productivity, lifestyle, health, education, and local-service apps.
17 min read
Validation Guide
How to Validate a Marketplace Startup Before You Build It
The marketplace-specific tests for supply, demand, liquidity, take rate, and two-sided interviews — before you build the platform. A practical handbook for B2B, consumer, local, creator, and talent marketplaces.
17 min read
Validation Guide
AI Startup vs SaaS Startup: How Validation Is Different
Why AI startups need workflow, output-quality, and dependency tests on top of every SaaS validation question — and the cheapest experiment that proves each one before you build.
18 min read
Validation Guide
How to Validate an AI Startup Idea
Validate an AI startup idea by testing workflow demand, output quality, pricing, model dependency, distribution, and defensibility before building.
21 min read
Validation Guide
How to Validate a SaaS Idea Before You Build It
The five recurring-revenue assumptions that decide whether a SaaS product survives month six, and the cheapest experiment that tests each one — before you write code.
16 min read
Monetization Validation
How to Test Willingness to Pay Before You Build: Six Experiments, Four Cases, and a Seven-Day Plan
Six pricing experiments you can run this week, four documented startup cases that show the pattern, and a seven-day Stripe-checkout plan that asks for money — before you build.
14 min read
Validation Guide
Startup Validation Checklist: Before You Build
21 concrete checks across four validation stages — problem, customer, business, execution — with how to test each one, the common mistake to avoid, and a printable summary.
17 min read
Validation Guide
How to Validate a Startup Idea Before You Build
The four assumptions every startup depends on, the four questions that test them, and the cheapest experiments that produce evidence in 2–4 weeks — before you build.
17 min read
Founder Psychology
Why we skip the steps that save us
Founder Mindset
The Build-vs-Buy Decision for First-Time Founders: When to Ship Software, When to Pay for It, and the Only Test That Picks
A first-time founder's guide to the build-vs-buy decision — when to pay for an existing SaaS, when to assemble a no-code stack, when to fork an open-source project, when to hire a contractor, and when the only honest answer is to build from scratch. The four-question test that picks the right path, the five situations where the answer is pre-decided, and the six-month read-out that proves which side was right.
14 min read
Founder Mindset
How to Position Against an Incumbent: The [for–unlike] Wedge That Holds When a Competitor Already Owns the Category
A founder's guide to writing a positioning wedge when a more-funded, more-distributed competitor already exists in the category — April Dunford's five-component positioning, the four wedge types (segment, persona, capability, distribution), the [for–unlike] sentence template, the five cheap tests that catch a positioning that won't hold, and the failure modes that produce a wedge the team cannot defend in a sales call.
17 min read
Founder Mindset
Why Founders Build Before They Validate
Why the keyboard feels safer than the phone — confirmation bias, action bias, sunk cost, and a small weekly habit that breaks the build-first loop.
15 min read
Related topics
Adjacent resources
Validation touches every other part of starting a company. These resources cover the parts this hub does not.
FAQ hub
Frequently asked questions
Direct answers about how Startup MRI works, what the scores mean, and how to use the report.
Read more →Glossary
The vocabulary of validation
Plain-language definitions of every important concept — MVP, product-market fit, willingness to pay, and more.
Read more →Validator
Startup idea validator
What a startup idea validator does, how it scores across 7 dimensions, who it is for, and how the free Startup MRI analysis works.
Read more →Evaluator
Startup idea evaluator
A 7-dimension evaluation of your idea — validation, market opportunity, distribution, monetization, competition, build difficulty, and founder fit. Same engine, evaluator-shaped vocabulary.
Read more →Score
Startup score calculator
A 0–100 startup score across 7 dimensions, built from a one-sentence idea plus a small set of structured inputs. Same engine, score-shaped output.
Read more →Practical checklist
Startup validation checklist
Nine sections, thirty-plus yes/no checks you can run before writing a line of code. The structured companion to the hub, built for scanning.
Read more →Method
AI idea validator alternative
Yibud vs typical AI idea validators: deterministic scores, optional prose polish, free and no signup. For founders comparing model-scored tools.
Read more →The product
Run a structured scan
Five short questions. A deterministic 7-dimension report in under 60 seconds. Free, no signup, and the same inputs always produce the same report.
Read more →
Common questions
The questions every founder asks
Short answers here. Longer answers live in the linked pillar articles.
- What is startup validation, in one sentence?
- It is the discipline of testing the assumptions behind your idea — the problem, the customer, the willingness to pay, and your ability to execute — before you commit months of building. The full definition lives in the pillar article on validation.
- What should I validate first?
- Start with the problem. Most founders skip this and end up building solutions for problems that do not exist. The validation checklist walks through every check, in order, so you do not skip the part that matters most.
- How do I know if people will actually pay?
- Only by charging them. Surveys, interviews, and landing pages produce polite interest, not payment. The willingness-to-pay guide walks through the small, fast experiments that separate real demand from imagined demand.
Test your own idea
The free Startup MRI evaluation takes about five minutes and produces a structured 7-dimension report — free, no signup, and reproducible from the same inputs.