How to validate a business idea before spending money: interviews, tests and pre-sales

TUREFF• •0

Most new businesses fail not because they are badly built but because not enough people want what they offer, at a price that works. Validation means finding that out cheaply, before you spend savings on stock, an app or a shop lease. The aim is not to prove yourself right but to find out quickly if you are wrong.

1. Write down your assumptions

Put your idea into a few sentences:

Who has the problem (be specific: "freelance designers who invoice monthly", not "small businesses").
What the problem is and how they deal with it today.
Why your solution is better.
How much they would pay, and how you would reach them.

Then mark which assumptions, if wrong, would sink the idea. Test those first.

2. Problem interviews

Talk to 10 to 20 people in your target group before building anything. The goal is to learn about their problem, not to pitch.

Ask about past behaviour, not opinions: "Tell me about the last time this happened. What did you do? What did it cost you?"
Ask how they solve it now. If they have not tried to solve it at all, the problem may not be painful enough.
Avoid "Would you use this?" or "Would you pay for this?". People are polite and will say yes.
Listen for strong emotion, workarounds, wasted money and time. Those are signs of a real problem.
Take notes and look for patterns across interviews, not one enthusiastic person.

3. Research the competition

Competitors are usually good news: they prove people pay for a solution. No competitors at all can mean no market.

Search for existing products, including indirect alternatives such as spreadsheets, agencies or doing nothing.
Read their reviews, especially the complaints. Repeated complaints show where a newcomer can win.
Look at their pricing pages, which tell you what customers are used to paying.
Ask yourself honestly why customers would switch to you.

4. Landing page test

Build a simple one-page website describing the product as if it existed: the problem, the solution, the main benefits and a clear call to action, such as "Join the waiting list" or "Get early access". Then send targeted visitors to it through small ad campaigns, relevant communities (following their rules) or your network. Measure how many visitors take the action. An email sign-up is a weak signal, but if almost nobody signs up from a well-targeted audience, that is a strong warning. Try different headlines or prices to see which message lands.

5. Pre-sales: the strongest signal

Nothing validates like money. Ask people to commit before the product exists:

Take pre-orders or deposits, with a clear delivery date and an honest refund policy.
Offer a founding customer deal at a discount in exchange for early access and feedback.
For business customers, ask for a signed letter of intent or a paid pilot.

If people who said they loved the idea will not pay even a small amount, take note. Follow your local consumer rules on taking payment in advance, and refund promptly if you do not go ahead.

6. Run small experiments

You can often deliver the service manually before automating it:

Concierge test: do the job by hand for a few customers, the way the product eventually would.
"Wizard of Oz" test: customers see a simple front end, but you do the work behind the scenes.
Small batch: make a few units, or sell at a market or online, before ordering in bulk.
Single channel: test one way of reaching customers properly before spreading effort across many.

Set a time limit and a success threshold for each experiment before you start, so you cannot move the goalposts afterwards.

7. Decide: continue, change or stop

At the end of each round, look at the evidence:

Continue if people pay, come back, and tell others.
Change direction (pivot) if the problem is real but your solution, customer group or price is off. Interviews often point to a better angle than the one you started with.
Stop if, after honest tests, nobody shows strong interest. Stopping early is a success: you saved the money and months a full launch would have cost.

Keep a simple log of what you tested, what you expected and what happened. It keeps you honest and makes the next idea faster to test. What idea are you testing, and what did your first customer conversations tell you? Share your experience or questions in the comments.