Question

How do you validate a business idea?

How to validate a business idea before writing code: the 9-step process, 4 evidence methods, and the four-condition gate that tells you when you're validated enough to build.

TL;DR

Run nine framework-backed decisions in order before writing code: define the buyer, prove the pain is painful, name the winning angle, scope V1 to the smallest test of the hypothesis, get behavioral evidence (paid pre-orders, signed letters of intent, or credit cards on file from a Fake Door Test), then ship. Most failed startups skipped at least three of those nine. Plan to spend two to four weeks on this. It saves six to nine months of building the wrong thing.

The fast version

Validation is the work of generating real evidence (not vibes) that a specific buyer will pay you for a specific product. The minimum bar:

  • 10+ interviews with people who match your buyer profile, focused on what they DID last time they had this problem
  • 3+ behavioral commitments: paid pre-orders, signed letters of intent, or credit-card-entered Fake Door Test conversions
  • A defended “why now” answer that points to a present-tense trend, not a hypothetical future one
  • A scoped V1 that tests one specific hypothesis, not “the product”

Below all four conditions: not validated. Don’t write production code yet. Stay in interview mode.

Why most “validation” doesn’t validate

Open any startup post-mortem on Indie Hackers and you’ll see the same words: “I thought I had validated it.” The founder talked to friends. The friends were enthusiastic. There was a Twitter post that got 100 likes. There were 500 email signups for early access. None of this is validation. It’s interest, which correlates poorly with revenue.

The four conditions above filter out everything except behavioral evidence. Behavioral evidence is the only kind that holds up after launch.

The 9-step process

ShipFit’s 9-step pre-code playbook sequences validation as a series of gated decisions. Each step has a defensible answer or you stop:

  1. Worth Building? Market verdict + signal confidence + key opportunities
  2. Who Pays? Defined buyer with budget authority and pain
  3. What Hurts? Above-the-line problems scored by frequency × intensity
  4. How to Win? The unfair advantage you’ll have at maturity (one of the 7 Powers)
  5. What’s V1? The smallest test of the hypothesis
  6. How to Charge? Defended price from Van Westendorp + willingness-to-pay interviews
  7. Will They Pay? Behavioral evidence via Fake Door Test, Gold/Silver/Bronze signal tiers, or pre-orders
  8. How to Launch? Channel mix that fits where the buyer already is
  9. What to Export? Validated playbook handed to your dev tools

The order matters. Step 6 (pricing) needs the buyer from step 2. Step 8 (launch) needs the V1 from step 5. Skip a step and the next one runs blind.

The four methods that actually generate evidence

In increasing order of signal strength:

  1. Mom Test interviews focused on past behavior. 10-15 conversations minimum. The signal: 3+ unrelated buyers describing the same pain in the same words.
  2. Fake Door Test with weighted signal tiers. Gold = credit card entered. Silver = demo booked. Bronze = time spent. Worthless = email signup. Weight your conversion accordingly.
  3. Paid pre-orders at proposed price. 3-5 pre-orders from 30 conversations is meaningful.
  4. Signed letters of intent for B2B. The friction is the test.

Skip surveys. Stated preference and revealed preference are different species; survey data has near-zero correlation with revenue.

What you walk away with

After 2-4 weeks of disciplined validation, you have a defensible answer to:

  • Is the market real? (size + growth + timing)
  • Who is the buyer? (named, specific, reachable)
  • What hurts? (3-4 above-the-line pains, scored)
  • Why us? (one of the 7 Powers, defended)
  • What’s V1? (Differentiator + Operational only, Delight cut)
  • What’s the price? (Van Westendorp band, justified)
  • Will they pay? (behavioral commitments)

That’s the validated playbook. Everything after is execution against an answer the market gave you, not a guess you talked yourself into.

Common mistakes

1. Asking friends instead of strangers. Friends are polite. Strangers tell you the truth.

2. Counting interest as validation. Interest is free. Only commitments (money, time, reputation) count.

3. Pitching too early in interviews. The moment you pitch, the conversation contaminates. Apply the Mom Test discipline.

4. Skipping the buyer-definition step. Validating “should I build this for everyone?” is unanswerable. Pick a specific buyer first.

5. Treating one positive interview as proof. Patterns emerge around interview 10. Below 10, you have anecdotes.

Further reading

Related

Framework

The Mom Test

The Mom Test is Rob Fitzpatrick's framework for customer interviews that generate real signal. Not praise. Three rules, applied step-by-step, with examples.

Framework

Jobs to be Done (JTBD)

Jobs to be Done reframes every product decision: customers don't buy features, they hire products to get a job done. Here's how to apply it without faking it.

Framework

The Lean Startup

Eric Ries's Lean Startup, stripped of consultant fluff. Validated learning, Build-Measure-Learn, MVP, pivot or persevere. What it means and where it gets misapplied.

Spoke

Idea Validation

Most founders confuse idea validation with idea-receiving-encouragement. The two have nothing in common. Here's what real validation looks like, and the four methods that actually produce it.

Spoke

Market Research

Most founder market research is a TAM slide that nobody believes. The numbers that actually matter are smaller, harder to defend, and tell you whether the market exists for the ten-customer version of your business.

Spoke

MVP Scope

Most founders ship an MVP that's actually V1.3 with bugs. Real MVP scoping cuts ruthlessly until you can name the one hypothesis V1 proves, and ships a product that tests it.

Glossary

Product-Market Fit

The state in which a product satisfies a strong market demand such that demand pulls the product through the company. Coined by Marc Andreessen in 2007. Most rigorous measure: 40%+ of active users would be 'very disappointed' to lose the product (Sean Ellis test).

Glossary

MVP (Minimum Viable Product)

The smallest version of a product that lets you test a falsifiable hypothesis about a buyer's behavior. Coined by Frank Robinson in 2001; popularized by Eric Ries in 'The Lean Startup' (2011). Not a stripped-down launch product. A learning tool.

Frequently asked questions

Can I validate a business idea in a day?
Not properly. A day is enough to talk yourself into the idea. Real validation needs 10-15 buyer interviews (which can run over 1-2 weeks), a Fake Door Test (a few days to set up + a few days of traffic), and ideally 3+ pre-orders or signed LOIs. Realistic minimum: 10-14 days. Anyone selling you 'one-day validation' is selling you a feeling of progress, not evidence.
Do I need to validate every idea?
Yes if you're committing real time or money. The cost of validation is 2-4 weeks. The cost of NOT validating, when the idea is wrong, is 6-9 months and $20,000-$80,000. The math is brutal: even if 20% of your ideas would have worked without validation, the average expected cost of skipping validation across a portfolio is far higher than the cost of running it. Validate.
What's the first thing to do when validating an idea?
Define the buyer. Not 'founders' or 'small businesses', but a buyer specific enough that you could write down 10 names of real people who match. If you can't, that's stage 0: get specific before you do anything else. Most validation work fails because the buyer was too vague to test against.
How is validation different from market research?
Market research tells you the market is big or growing. Validation tells you a specific buyer in that market will pay you for a specific product. Market research uses public data and reports. Validation uses interviews, Fake Door Tests, and pre-orders. You need both, but validation is the harder and more decisive one. Markets are real; whether YOU can capture a slice of one is the validation question.
Should I validate before or after building the MVP?
Before. The whole point of validation is to learn whether the MVP is worth building. If you build first then validate, you've already spent the money you were trying to protect. The Lean Startup conflates this slightly by talking about 'build-measure-learn' loops, but Eric Ries is explicit that the build is supposed to be the smallest possible test, often a landing page or a manual concierge service, not a coded product.
Related on ShipFit

Keep exploring

Master guide
Validate your business idea

The 9-step playbook from market verdict to ship-ready spec.

Framework
The Mom Test

The Mom Test is Rob Fitzpatrick's framework for customer interviews that generate real signal. Not praise. Three rules, applied step-by-step, with examples.

Framework
Van Westendorp Price Sensitivity Meter

The Van Westendorp framework uses 4 questions to surface a defensible price range for any product. Here's how to run it, interpret results, and avoid the cheapest mistakes.

Spoke
Idea Validation

Most founders confuse idea validation with idea-receiving-encouragement. The two have nothing in common. Here's what real validation looks like, and the four methods that actually produce it.

Spoke
Market Research

Most founder market research is a TAM slide that nobody believes. The numbers that actually matter are smaller, harder to defend, and tell you whether the market exists for the ten-customer version of your business.

Calculator
CAC / LTV ratio calculator

Does each customer make you money? Or cost you money?

Q&A
What is an MVP (Minimum Viable Product)?

The smallest version of a product that lets you test a single, falsifiable hypothesis about a buyer's behavior. Coined by Frank Robinson in 2001; popularized by Eric Ries in The Lean Startup (2011). Often not a working product at all (a landing page, a Wizard of Oz prototype, a manual concierge service). The defining feature: it can fail. If your MVP can't fail, it's not an MVP, it's just a small launch.

For founders
indie hackers

For indie hackers who've wasted months on dead ideas. ShipFit forces 9 decisions before you write a line of code. Proven frameworks, exports to Cursor.

Comparison
Buildpad

If you want a conversation partner, Buildpad. If you want to stop researching and ship, ShipFit. Both solve different problems for different founders. Don't pick on hype.

Ready to make your next product a success?

9 decisions between your idea and a product worth building.

No credit card required.

Try an example: