How to validate a business idea before you build it

Most ideas die not because they were bad, but because nobody checked whether the problem was real before building the solution. In CB Insights’ analysis of startup post-mortems, “no market need” is consistently among the most-cited reasons companies fail — teams built something no one was waiting for. Validation is the discipline that runs before the build to lower that risk. It isn’t market research theater and it isn’t asking your friends if they like the idea (they’ll lie to be kind). It’s a short ladder of experiments, each one cheaper than the build it might save you from. Here’s the ladder.

Step 1 — Write the idea as a problem, not a product

Start by separating the problem from your solution. “An app that does X” is a solution; validation is about the problem underneath it. Rewrite your idea in one sentence as: [specific person] struggles to [do something] because [reason], and today they cope by [current workaround]. If you can’t name the person or the workaround, that’s your first finding — you have a solution in search of a problem, and the rest of the ladder will tell you fast.

The presence of an ugly current workaround (a spreadsheet, a group chat, a paid tool people bolt together, a manual routine) is one of the strongest early signals there is. It means the pain is real enough that people already spend effort on it. No workaround often means no pain.

Step 2 — Talk to people about their past, not your idea

This is the step everyone skips, and the one that matters most. The trap is asking hypotheticals — “Would you use an app that…?” — because people answer hypotheticals generously and inaccurately. Rob Fitzpatrick’s widely used framing (The Mom Test) is the fix: ask about their actual past behavior, not your idea. Good questions sound like:

• “Walk me through the last time you dealt with [problem].”
• “What did you do about it? What did that cost you — time, money, hassle?”
• “Have you looked for a better way? What did you try?”

Talk to 5–10 people who plausibly have the problem. You’re listening for one thing: evidence they already spend time, money, or emotion on this. Compliments are worthless. Stories of past effort are gold. If nobody has ever tried to solve it, that’s a real answer — and cheap to learn now.

Step 3 — Look for evidence that already exists

Before you build anything, the internet has already run part of your experiment. Look for:

• Search demand — are people actively looking for this or its workaround?
• Existing complaints — forum threads, subreddit posts, reviews of adjacent tools with the same recurring gripe.
• Existing paid solutions — competitors are usually good news. They prove people pay. “No competitors” more often means “no market” than “untapped goldmine.”
• Cobbled-together stacks — people duct-taping three tools to get the job done are telling you exactly what to build.

Absence of any signal is itself a signal. You’re not looking to confirm the idea — you’re looking to disconfirm it cheaply.

Step 4 — Test willingness to act, not just interest

Interest is free; action costs something. The core lesson from lean-startup practice (Steve Blank, Eric Ries) is to design the smallest test that asks someone to do something, not just nod. Depending on the idea, that might be a landing page that measures sign-ups, a pre-order or waitlist, a “concierge” version where you deliver the outcome manually for a few people, or a paid pilot. The bar to clear isn’t “people said they liked it” — it’s “people took an action they wouldn’t have bothered with if they didn’t care.” A single stranger paying, waiting, or repeatedly using beats a hundred polite yeses.

Step 5 — Decide with a rule you set in advance

Validation only works if you decide before the test what result would make you stop. Write it down first: “If fewer than X of the 10 conversations describe a real past effort, I shelve this.” Deciding the threshold ahead of time is what stops you from rationalizing a weak signal into a green light because you’re already attached. This is where a structured lens helps — instead of one gut verdict, you rate the idea on its separate parts and let the weakest one speak.

Where the free scorer fits (honestly)

Validation is legwork, and no tool replaces the conversations in Step 2. What a structured scorer can do is keep you honest about which part of the idea you’ve actually validated and which you’re hand-waving. IdeaSweetSpot scores an idea live, free, on your device across four circles — Care, Capability, Need, and Paid path — and surfaces the one that’s weakest, so “I love this idea” doesn’t quietly paper over “I have zero evidence anyone will pay.” Scoring is free and needs no account; the full exportable one-page build brief, the guided journey, and the multi-idea compare board are the Builder plan ($49/yr, cancel anytime). Use it as the cheap first rung, then go do Steps 2–4 in the real world. It’s a reflection and prioritization tool, not financial or legal advice, and it makes no promise of income or success.