How to Validate a Startup Idea (Before Building It)
To validate a startup idea: talk to twenty people with the problem before building anything, test demand with a landing page and real traffic, ask for money or a commitment rather than an opinion, and only build once someone has paid or pre-committed.
Validation fails when it collects encouragement instead of evidence. People are generous with enthusiasm and stingy with money, and only one of those predicts a business. Every test below is designed to produce the second kind of signal.
The steps
- 1
Talk to twenty people with the problem
Ask about their current behaviour, not your idea. 'How do you handle this today, and what does it cost you?' reveals whether the problem is real. 'Would you use an app that...' produces polite agreement that predicts nothing.
- 2
Find out what they do today
Every problem worth solving already has a workaround — a spreadsheet, a WhatsApp group, an employee doing it manually. If there is no workaround, the problem may not be painful enough to pay to solve. The workaround is your real competitor.
- 3
Test demand with a landing page
Build one page describing the offer and drive ₹10,000–₹30,000 of targeted traffic to it. Measure whether people take a meaningful action. This costs a fraction of building and tells you more than any amount of survey work.
- 4
Ask for money or a commitment
A pre-order, a deposit, a signed letter of intent, a scheduled onboarding call. Anything that costs the person something. Interest is free and unreliable; commitment is the only signal that consistently predicts revenue.
- 5
Test the price, not just the idea
Name a number and watch the reaction. Many validated ideas fail on price rather than concept — a genuine problem that nobody will pay enough to solve is still not a business. Learn this before building, not after.
- 6
Do it manually first
Deliver the service by hand for your first few customers — WhatsApp, spreadsheets, your own labour. You will learn what the software actually needs to do, and some businesses turn out to work fine without software at all.
- 7
Write down what would falsify it
Decide in advance what result would mean the idea is wrong, and honour it. Without that, every ambiguous signal gets read as encouraging, which is how people spend two years building something nobody wanted.
Common mistakes
They will encourage you. Talk to strangers who have the problem and no reason to be kind.
Ask about their current behaviour before describing your solution. Once you pitch, the conversation stops being useful.
A free email sign-up costs nothing and predicts little. Ask for money or a scheduled commitment instead.
Validate with a landing page and manual delivery first. Building is the most expensive way to learn something a ₹20,000 test would have told you.
Want us to handle this instead?
Tell us where you're stuck. We'll give you a straight answer on scope, cost and whether it's worth outsourcing at all.
Frequently asked questions
How many customer interviews are enough?
Around twenty for a first pass, though you will usually hear the same themes by ten. What matters is talking to people who genuinely have the problem rather than reaching a number. Five real users beat fifty polite acquaintances.
What counts as real validation?
Someone paying, pre-ordering, signing a letter of intent, or committing time in a way that costs them something. Email sign-ups, survey responses and verbal enthusiasm are all free to give, which is exactly why they predict so little.
How much should validation cost?
₹10,000–₹1,00,000 covers a landing page, some targeted traffic and your time. If validation is costing more than ₹2,00,000 you have probably started building. The whole point is spending little to avoid spending a lot on the wrong thing.
What if people say they like it but won't pay?
That is a clear result and a useful one — the problem is real but not painful enough at your price. Either find a segment where it hurts more, change the price, or move on. It is not a signal to build anyway and hope.