The fastest way to waste months as a solo founder is to build something nobody asked for. Validate first: talk to real people, watch what they already pay for, and try to take money before you write a single line of code. If you cannot get a clear yes from a handful of strangers, the product is not ready to build yet.
This is the loop I run before every new product. It is cheap, a little uncomfortable, and it has saved me from shipping things to an empty room more than once.
What does it mean to validate an idea?
Validation means getting evidence that real people will pay for a solution, before you build it. It is not asking friends if your idea is "cool." It is finding strangers with the problem, showing them a rough offer, and watching whether they lean in, sign up, or pay. Interest is cheap; commitment is the signal.
The trap is confusing encouragement with demand. People are polite. They will say "I'd totally use that" and then never open their wallet. Your job is to design tests where the only honest answer costs them something — time, an email, or money.
How do I test demand before building?
Start with the smallest test that produces a real commitment. In rough order of strength:
- Conversations — Talk to 10 people who have the problem. Ask what they do today and what it costs them. Do not pitch; listen.
- A landing page — Describe the outcome, add a single call to action, and drive a little traffic to it. Measure sign-ups, not visits.
- A waitlist with a reason — Offer early access or a founding discount so joining means something.
- A pre-sale — Ask for money up front for something you will deliver soon. This is the strongest signal there is.
Each step costs more credibility to fake, so each step tells you more. If people will pay before the thing exists, you have a business. If they will not even give you an email, you have a hobby.
How many conversations are enough?
There is no magic number, but patterns usually show up within 8 to 12 focused conversations. You are looking for the same problem described in the same words by different people. When three or four strangers independently describe the same painful workflow, you have found something worth building.
Keep the conversations short and specific. Good questions sound like:
- "Walk me through the last time you dealt with this."
- "What did you try? Why did it not work?"
- "If this were solved, what would change for you?"
Bad questions sound like "Would you use a tool that does X?" — that invites a polite, useless yes.
What signals mean you should actually build?
Build when you see commitment, not just curiosity. Concrete green lights:
- People describe the problem before you do.
- Someone asks "When can I have it?" without prompting.
- A pre-sale converts, even at a small scale.
- People are already paying for a worse solution.
If you see none of these after a real effort, change the idea or the audience — do not push forward on hope.
Frequently Asked Questions
Isn't validation just an excuse to procrastinate?
It can be, if you let it drag on. Set a deadline: two weeks of conversations and one demand test. After that, you either have enough signal to build a small version or enough signal to move on.
What if I can't reach people who have the problem?
That is itself a validation result. If you cannot find the audience now, you will not magically find them after launch. Pick a problem inside a community you can already reach.
Can I validate and build at the same time?
Yes, in small doses. A rough landing page or a one-page offer is "building," and it doubles as a test. The rule is simple: do not build the actual product until something gives you a commitment.
