How to validate a startup idea before writing any code
Most startups fail because nobody needed what they built. Here is a practical, low-cost way to test demand first.
It is tempting to start building the moment an idea feels exciting. But the most common reason young companies fail is simple: they build something people do not want enough to pay for. Validation is how you find out cheaply.
1. Write the problem, not the product
Describe who has the problem and what it costs them today, in one sentence. "Small shop owners in Dhaka lose sales because they can't take card payments" is testable. "An app for payments" is not.
2. Talk to real people
Have at least 15–20 conversations with people who fit your description. Ask about their past behaviour, not your idea:
- When did this last happen to you?
- What did you do about it?
- What does your current workaround cost in time or money?
People are polite about ideas and honest about their habits.
3. Look for existing spending
If people already pay for a clumsy workaround — an extra employee, a spreadsheet service, a middleman — that is a strong signal. No spending and no workaround often means the problem is not painful enough.
4. Test with a smoke test
Create a simple landing page describing the solution, with a clear call to action: join a waitlist, book a demo, or even pre-order. Share it where your target customers are. The sign-up rate tells you more than any survey.
5. Do it manually first
Before automating, deliver the service by hand to a few customers — this is sometimes called a concierge MVP. You learn exactly what they value, and early revenue proves demand.
Warning signs
- Everyone says "great idea" but nobody gives an email or payment
- You have to explain the problem before people recognise it
- Your target customer changes after every conversation
The bottom line
Validation is not about proving yourself right. It is about finding the version of your idea that people will actually pay for — before you spend months building.