# How Do You Validate a Business Idea? The Honest Playbook

> Source: [https://botensten.com/articles/how-to-validate-a-business-idea-2](https://botensten.com/articles/how-to-validate-a-business-idea-2) (canonical)
> Author: Botensten — Botensten, https://botensten.com
> Published: 2026-08-21

## TL;DR

Validate a business idea by testing real demand before you build: interview 15 to 30 potential customers about a problem they already have, then run a cheap demand test like a landing page with a price or a pre-order. Watch behavior, not compliments. Money, a booked call, or a firm commitment is real validation; a friendly "I'd totally use that" is not. CB Insights found "no market need" is the top reason startups fail, so proving demand first is the whole game.

CB Insights' analysis of startup post-mortems found "no market need" is the top killer of new companies, named in 35% of failures. You validate a business idea by talking to 15 to 30 real potential customers about a problem they already have, watching what they currently do and pay for, and writing code only after people show they want the outcome. Validation tests demand, not opinions.

## What does it mean to validate a business idea?

Validating a business idea means getting evidence that real people will pay to solve a specific problem, before you build the full product. It is the difference between "people said they liked it" and "people gave me money or their time."

Opinions are cheap and polite. [The Mom Test by Rob Fitzpatrick](http://momtestbook.com) makes the core point: ask about the customer's past behavior and real spending, never about your idea. "Would you buy this?" invites a lie. "Walk me through the last time you dealt with this problem" gets you facts.

Good validation produces three things: proof the problem is frequent and painful, proof people already spend money or effort on it, and a signal they will switch to your solution.

## How do I validate a business idea in one week?

You can run a credible first validation pass in five working days without writing any product code. The goal is signal, not certainty. Here is a tight sequence a solo operator can execute this week.

1. Write one sentence naming the customer and the problem, not your solution.
2. List 20 people who have that problem and can be reached directly.
3. Run 10 to 15 problem interviews using past-behavior questions.
4. Publish a one-page offer describing the outcome and a price, with an email capture or pre-order button.
5. Drive 100 to 300 real visitors through a small ad budget or a relevant community.
6. Count concrete actions: sign-ups, replies, deposits, or booked calls.

If nobody acts when it is easy to act, that is your answer. A lukewarm response now becomes silence after you spend three months building.

## Which validation methods actually work?

The strongest methods force a real decision from the customer; the weakest ask for opinions. Direct problem interviews and a paid pre-sale beat surveys and family feedback every time. Use this comparison to pick your next test.

| Method | Signal strength | Cost | Best for |
|---|---|---|---|
| Problem interviews | High | Low | Confirming the problem exists |
| Landing page + pre-order | High | Low | Testing willingness to pay |
| Concierge / manual delivery | Very high | Medium | Proving people want the outcome |
| Small paid ads to a waitlist | Medium | Medium | Measuring cold demand |
| Surveys | Low | Low | Broad context, not decisions |
| Asking friends and family | Very low | Low | Emotional support only |

[Steve Blank's customer development method](https://steveblank.com) calls this "getting out of the building." The best signal is money or a firm commitment; the second best is repeated, specific behavior you can observe.

## How we validate features at Botensten before we build

We build production software with AI every day, and we still refuse to build a feature until a real request forces it. Our rule is simple: a feature needs two unprompted requests from paying members before it enters the build queue.

We learned this the expensive way. We once spent four days building a detailed analytics dashboard because it felt obviously useful. Usage after launch was near zero. Members wanted a single weekly email, not another screen to log into. We rebuilt it as a plain email digest in an afternoon, and open rates were strong. The dashboard was our opinion; the email was their behavior.

Now we validate cheaply first. Before writing the real feature, we ship a fake door: a button that records intent and shows a short "want this?" capture. If clicks are flat, we drop it. That costs an hour and saves weeks. Talking to customers is not a phase we finished; it is the input to every build.

## What are the most common validation mistakes?

The most common mistake is asking leading questions that fish for a yes instead of the truth. The second is treating enthusiasm as demand when no money or time changed hands.

- Pitching your solution instead of studying the problem.
- Asking "would you buy this?" instead of "what do you use today?"
- Counting compliments and likes as validation.
- Interviewing friends who cannot say no to you.
- Building an MVP before a single person committed anything.
- Ignoring what people already pay to solve the problem.

## When should you stop validating and start building?

Stop validating and start building once you have clear, repeated evidence of demand: several people committed money, time, or a firm pre-order for the same specific outcome. Validation never fully ends, but you have enough to build the smallest version when the signal is consistent, not just polite.

Eric Ries' Lean Startup frames this as the minimum viable product: the smallest thing that keeps you learning from real users. A practical bar is three to five customers who paid or pre-committed and describe the same problem in similar words. Below that, keep testing. Above it, build the smallest slice that delivers the outcome and put it in front of those exact people first.

## Related reading

- [What Does Building an MVP Actually Mean?](/articles/what-does-building-an-mvp-mean)
- [Why Is It Important to Build an MVP?](/articles/why-build-an-mvp)
- [How Long Should It Take to Build an MVP? The Honest Answer](/articles/how-long-to-build-an-mvp)
- [How Do I Start a Business? A Build-In-Public Playbook](/articles/how-to-start-a-business-startup-bootstrapping-playbook)

## Frequently asked questions

**How do I validate a business idea?**

Interview 15 to 30 real potential customers about a problem they already have, then run a cheap demand test like a priced landing page or pre-order. Real actions (money, sign-ups, booked calls) validate; compliments do not.

**How many customer interviews do I need before building?**

Aim for 10 to 15 problem interviews for a first pass. Look for the same specific problem described in similar words; that pattern matters more than a large sample.

**Can I validate a business idea without spending money?**

Yes. Problem interviews, a free landing page, and outreach in relevant communities cost little. Small paid ads sharpen the signal but are optional for a first test.

**What is the best question to ask in a validation interview?**

Ask about the past: "Walk me through the last time you had this problem and what you did." Past behavior is honest; hypothetical answers about your idea are not.

**Is a survey enough to validate an idea?**

No. Surveys give context but not decisions. People say they would buy things they never actually pay for, so surveys overstate demand. Test behavior instead.

**How long does it take to validate a business idea?**

A useful first pass takes about a week: define the problem, run interviews, and publish a priced offer. Deeper validation continues as you build.

**What is the number one reason startups fail?**

CB Insights' analysis of startup post-mortems found "no market need" is the top reason, named in 35% of failures, which is exactly what validation is meant to prevent.