Validation2 min read
How to validate your idea before building.
How to test your idea in a week, with almost no money.
Start before you have anything to show
Most founders want to validate an idea by showing people the product. The problem is that by the time there's a product, you've already spent the money.
You can learn most of what you need with a notebook, a phone and a week of conversations. No designs, no code.
Write the problem in one sentence
Who has the problem, what happens to them, and what it costs them today. Keep it boring and specific.
Bad: "People struggle with appointments."
Better: "Dentists in small clinics spend an hour every morning calling patients to confirm the day's bookings."
If you can't get it this specific, that's your first finding. You don't know your user well enough yet.
Talk to people who have the problem, not people who like you
Friends and family will be kind. That's their job, and it's useless for this.
Go where your users already are. For the dentist example, that's clinics near you, a dental association's WhatsApp group, or someone you know who knows a dentist. Ask for fifteen minutes and say up front that you're not selling anything.
Ten honest conversations will tell you more than a hundred survey responses.
Ask about last week, not about your idea
If you describe your idea and ask "would you use this?", almost everyone says yes. It costs them nothing to say it.
Ask about things that already happened instead:
- Tell me about the last time this happened.
- What did you do about it?
- What have you already tried?
- Did you pay for anything to fix it? How much?
- What's annoying about how you handle it now?
Watch what they do, not what they say they will do.
What a real signal sounds like
You're on to something when people bring up the problem before you do, when they've built their own workaround (a spreadsheet, a notebook, a staff member who only does this), or when they ask if they can try your thing.
You're probably not when the answers are polite and vague. "Yeah, that could be useful" is a no.
Then test the promise, cheaply
Once the conversations look good, make one small thing that asks for commitment. A one-page website with a signup form. A two-minute screen recording of a clickable design. Or just do the job by hand for three customers and see if they come back.
Signups, a booked call, a deposit, a pilot. Each of those costs the other person something, which is why they mean more than a compliment.
If the answers are mixed
That's normal. Usually it means you're talking to the wrong group, or describing the problem too broadly. Narrow it and run another round.
A week spent learning this is cheap. Three months spent building the wrong thing isn't.