How to validate a startup idea in India before you build it
Before you write code, spend a few weeks finding out whether anyone will pay. Most of it costs little more than your time.
Building is the expensive way to find out nobody wants something. It takes months, and when it fails you learn very little about why. Testing demand first feels slower, but it is cheap, and every test teaches you something specific.
This guide is for builders in India, where a few things work differently. A lot of everyday conversation happens in WhatsApp groups, paying a small amount on UPI is quick, and a customer in a metro may behave very differently from one in a smaller town.
Write down what you are guessing
Every idea rests on a handful of guesses. Write them down, one sentence each, before you test anything, so you know what you are trying to prove:
- Who has the problem, as specifically as you can say it. "Tuition teachers in Indore who teach from home" beats "teachers".
- What happens, and how often.
- What they do today instead, and what that costs them.
- What you would charge, in rupees, and how: once, monthly or per use.
- How you would reach them: which groups, shops, apps or people.
Each line is now something you can check. A common mistake is to test the idea as a whole ("do people like it?") instead of testing the guesses one at a time. An idea can be loved and still fail because you guessed wrong about who pays or how you reach them.
Talk to people who have the problem
Your first test is conversations, and the way you ask matters more than how many you have. People are kind. Ask whether they would use your app and many will say yes to avoid disappointing you. Ask about what already happened and there is nothing to be polite about, because the past is just facts.
Asking about the future, and asking about the past
About the future
Would you use an app that reminds parents to pay tuition fees on time? How much would you pay for it?
Talk in the language people are comfortable in. If your customers think in Hindi, Marathi or Tamil, a conversation in English may get you shorter, more careful answers. Meet them where they work if you can. A shop owner explains the problem better standing behind the counter than on a video call.
Quick question
Which question is most useful in a customer conversation?
Use the groups you are already in
WhatsApp groups are where a lot of everyday problems get talked about: housing society groups, school parent groups, trade and market associations, alumni groups, groups for a profession. They are also easy to annoy. A link dropped with "please check out my startup" will be ignored at best.
It works better to ask the admin first, say who you are, and ask about the problem instead of pitching a product. "I'm trying to understand how other societies collect maintenance. How does ours do it, and what goes wrong?" starts a conversation. The people who reply are your first interviews.
Once the problem is posted on Suggst, add it to a group list and share the list's one link in the group. Everyone who opens it can vote, mark I'd pay for this, and answer How often does this happen to you? Votes on the list go to the post itself, so you build public demand while you learn.
Ask for money early, in rupees
Words are the weakest evidence you can collect, and money is the strongest. In India, asking for a small amount is easy: a UPI request or a QR code takes moments to set up and moments to pay.
Try a pre-order or a refundable deposit. Say exactly what people get, roughly when, and that you will refund them if you do not deliver. Then keep that promise. A few people paying ₹99 or ₹199 for something that does not exist yet tells you more than a crowd saying it sounds useful.
A lighter step is a pledge on Suggst. On a problem or idea, people can say "I'd pay ₹X if someone builds this". Nothing is charged, so treat a pledge as weaker than a payment. It is still useful, because people have to pick a number, and the spread of numbers gives you a first sense of price.
When you talk price, test real figures in rupees and ask what people pay today. In many categories your competition is free: a notebook, a WhatsApp group, a relative who helps. Your price has to make sense next to that, so show what the free option costs in time or mistakes. Ask whether paying monthly or once feels right, too. Some customers are happy to pay once and wary of anything that renews.
Metros and smaller towns are different tests
If you build in Bengaluru, Mumbai or Delhi, your first conversations will probably be with people like you. That is fine as a start and risky as a conclusion. Customers in smaller towns can differ in the language they prefer, how they like to pay, whom they trust, how they hear about new things and what they think is a fair price.
None of that makes one a better market than the other. It means you should test in the place you plan to sell. If you plan to sell in both, test both, separately, and do not average the results. A strong yes from metros and a quiet no from smaller towns is two findings, not one lukewarm one.
Decide with a rule you set in advance
The hardest part of validation is being honest at the end. After weeks of work it is tempting to read any result as encouraging. Set your bar before you start, write it down and share it with someone who will hold you to it.
The numbers are yours to choose, based on your price and how many customers you need. As an example of the shape, not a benchmark: "If at least ten of the thirty people I talk to describe this problem without prompting, and at least five pay a refundable deposit, I build a first version."
Before you build
0/7If you are still choosing what to test, finding a startup idea people will pay for covers where to look. When you do start building, mark I'm building this on the problem, so the people who wanted it hear when you launch.
Post the problem you want to test, then share it with the people who have it.
Describe a problemWritten by the Suggst team. Example requests about real apps are made up to show how to write them, not reports about those apps.