Most failed startups didn't fail because the code was bad. They failed because nobody wanted what they built.

Validation isn't a phase you do before the real work. It is the real work. If you skip it, you're not moving fast, you're just spending money on the wrong thing faster.

Here's how to know if your idea is worth building before you write a line of code.

Talk to 10 Real People First

Not your friends. Not your family. Not people who will nod politely and tell you it sounds great.

Find 10 people who actually have the problem you're solving. Talk to them for 20 minutes each. Don't pitch. Ask questions. Specifically:

  • How do they deal with the problem today?
  • How much time or money does it cost them?
  • What have they already tried?
  • How bad does it actually hurt?

If they're not already doing something clunky to solve it, a spreadsheet, a workaround, a manual process, the pain probably isn't sharp enough to build on. Sharp pain drives purchasing decisions. Mild inconvenience does not.

Define What a 'Yes' Looks Like

Before you validate, decide what validation actually means. Otherwise you'll cherry-pick the positive signals and ignore the red flags.

Set a threshold before you start talking to people. Something like: "If 7 of 10 people tell me they've actively tried to solve this and would pay at least £50/month for a better solution, I'll build it." Then hold yourself to it.

This sounds obvious. Almost nobody does it. They start talking to people, get a few enthusiastic responses, and convince themselves they have signal. That's confirmation bias, not validation.

Build the Smallest Possible Proof

You don't need an app. You need proof that someone will take an action.

Some of the most effective validation tools cost almost nothing:

  • A landing page with a waitlist or a payment link
  • A Typeform or Notion page pretending to be a product
  • A manual process you run yourself behind the scenes (the "Wizard of Oz" test)
  • A cold email to 50 potential customers with a clear offer

If someone gives you their email address, that's a weak signal. If someone gives you their credit card number, even if you refund them, that's a real signal. Money moves are the most honest feedback you'll ever get.

Look for the Riskiest Assumption and Test That First

Every startup idea has a load-bearing assumption, the one thing that has to be true for everything else to work.

Maybe it's: "Recruiters will pay for this." Or: "SMEs will switch from the tool they already use." Or: "People will trust AI to do this task."

Write down all your assumptions, then rank them by risk. Which one, if wrong, kills the whole idea? That's the one you test first. Not the fun stuff. Not the features. The existential assumption.

Most founders do the opposite. They build everything first and test the riskiest assumption last, usually when they're out of runway.

Know When to Stop Validating

Validation is not the same as certainty. You will never have certainty. At some point, you have enough signal to make a bet and you either make it or you don't.

The signal you're looking for: people are already doing something painful to solve this problem, they'd switch if something better existed, and at least a handful of them have shown that willingness with their time, attention, or money.

When you hit that, stop validating and start building. But build the smallest thing that proves the core value, not the full product, not the version with all the features. The MVP. Fast and focused.

Validation tells you what to build. It doesn't tell you how to build it well. That's a separate problem, and one worth solving with people who've done it before.

If you've got an idea you're trying to pressure-test, book a free call with us at novion.one and we'll tell you honestly whether it's worth building.