How to validate a business idea before you spend a dollar
Most new products fail because nobody needed them, not because they were built badly. Here is a practical way to test demand first — cheaply and quickly.
The most expensive mistake a founder can make is building something nobody wants. It's also the most common. Before you pay for a logo, a website or an app, spend a few weeks proving that real people have the problem you want to solve — and that they'd pay to have it solved.
1. Write the problem down in one sentence
Not the solution — the problem. "Busy parents in Richmond Hill can't find a reliable after-school tutor at short notice" is a problem. "An app that matches tutors with parents" is a solution. If you can't describe the problem clearly, you aren't ready to build anything yet.
2. Talk to at least 15 people who have that problem
Not friends and family who want to be supportive — actual people in your target group. Ask about their past behaviour, not their opinions about your idea:
- "When did this last happen to you?"
- "What did you do about it?"
- "What did that cost you, in time or money?"
- "What have you already tried that didn't work?"
If people describe the problem vividly, have already tried workarounds, or have spent money on it, that's a strong signal. If they shrug, that tells you something too.
3. Look at what people already pay for
Competition is usually a good sign — it means a market exists. Search for existing products, read their reviews (especially the one- and two-star ones) and note what customers complain about. Those complaints are often your opening.
4. Test demand with a simple landing page
A one-page website that explains the offer and asks visitors to join a waitlist, book a call or pre-order is one of the cheapest experiments you can run. Send a small amount of targeted traffic to it — from a local Facebook group, a short ad campaign, or your own network — and measure how many people take action.
5. Try to deliver it manually first
Before you automate anything, try delivering the service by hand to a handful of customers. A tutoring marketplace can start as a spreadsheet and a phone. You'll learn what customers actually value, and you'll know exactly what the software needs to do when you build it.
6. Decide what "validated" means before you start
Set a clear bar in advance — for example, "20 waitlist sign-ups from 300 visitors" or "5 customers who pay for the manual version." If you hit it, move forward with confidence. If you don't, change the idea or the audience, not the goalposts.
The bottom line
Validation isn't about proving you're right. It's about finding out quickly and cheaply whether you are. A few weeks of conversations and small experiments can save months of building the wrong thing.