How to Validate a Business Idea Before You Build Anything

Validation is not asking people whether they like your idea. Everyone likes ideas. Validation is designing the cheapest experiment that could prove you wrong, running it honestly, and being willing to act on the answer.

Most founders skip this because building feels like progress and interviewing feels like delay. The arithmetic says otherwise: a fortnight of structured business idea validation routinely saves six to twelve months of building the wrong thing.

The four questions that decide everything

Every idea rests on four assumptions. Rank them by how badly you would be hurt if they were false, then test the most dangerous one first.

1. Problem. Does a specific group of people have this problem badly enough to already be spending money, hours or workarounds on it?
2. Willingness to pay. Will they pay your price, from a budget that already exists?
3. Reachability. Can you reach enough of them repeatedly, at a cost lower than what they are worth?
4. Feasibility. Can you deliver the outcome at a margin that works?

Founders overwhelmingly test feasibility first, because it is the one they enjoy. It is almost always the least dangerous assumption.

Step one: define the buyer narrowly enough to fail

"Small businesses" is not a buyer. "Heads of finance at 50-500 person B2B software companies in the UK who close the month manually" is a buyer. The test of a good definition: could you produce a list of 100 named organisations that fit it by Friday? If not, tighten it.

Narrow definitions feel like shrinking the opportunity. They are actually the only way to make validation possible, because you cannot interview an abstraction.

Step two: run problem interviews, not pitch meetings

Book 10-15 conversations. The goal is to learn what people already do, not to describe what you intend to build. Do not mention your solution until the last five minutes.

Questions that produce evidence:

• Walk me through the last time you dealt with this. What did you actually do?
• How long did it take, and who else was involved?
• What have you already tried or bought to fix it?
• What happens if you simply carry on as you are?

Questions that produce noise: Would you use a tool that...? Does this sound useful? How much would you pay for this? Hypothetical questions get hypothetical answers.

The signal you are looking for is existing spend or existing workaround. A spreadsheet someone maintains at 11pm on the last day of the month is worth more evidence than ten enthusiastic "that sounds great" replies.

Step three: test willingness to pay with something that costs the buyer

Stated intent is close to worthless. Design a test where the buyer gives up something real:

• Pre-sale or deposit. The strongest signal available. Even a small refundable deposit separates interest from intent.
• Letter of intent. Common in B2B; weaker than money but useful when procurement is slow.
• Paid pilot. Charge for a manual version of the outcome, delivered by hand.
• Time commitment. A booked, attended, hour-long working session is a real cost to a senior buyer.

A concierge pilot — you delivering the outcome manually for three customers — tests problem, price and feasibility at once, with no product built.

Step four: prove you can reach them

An idea can be right and still fail because acquisition costs more than the customer is worth. Before building, establish one plausible route to buyers:

• Run a small paid test to a landing page describing the outcome and measure the cost per qualified enquiry.
• Test outbound to 100 named accounts and measure reply and meeting rates.
• Publish two pieces of content aimed at the exact search terms the buyer uses and see whether the traffic converts.

You are not looking for scale yet. You are looking for evidence that a repeatable channel exists at a cost that the unit economics survive.

Step five: write down what would make you stop

Set the thresholds before you run the tests, in writing. For example:

Pre-committed thresholds are what separate validation from confirmation. Without them, every result becomes evidence for continuing.

Common validation mistakes

• Interviewing friends and peers. They are kind and they are not your buyer.
• Testing the solution before the problem. A polished demo makes people respond to the craft, not the need.
• Treating enthusiasm as demand. Only budget, signature or diary time counts.
• Validating once. Each significant pivot invalidates the previous evidence.
• Building an MVP that is neither minimum nor viable. If it took four months, it was not an experiment.

What a strong validation result looks like

By the end you should be able to state, in one paragraph and with numbers attached: who the buyer is, what they do today, what that costs them, what they said they would pay, how many of them agreed to pay, and how you would reach the next hundred. If any of those clauses is missing, that is where the next two weeks go.

Pressure-test your idea

The Meta2IQ Stress Test applies this framework to your specific idea and returns a scored report covering market reality, differentiation, revenue model soundness, execution risk and the assumptions most likely to break — plus the experiments to run next.