How to Validate a Business Idea Before You Spend Money

Rahul spent eight months and ₹4 lakh building an app to help hostel students split bills. It was well made. He launched it, shared it with friends, and got 40 downloads and zero regular users.

Nobody had told him it was a bad idea. Everybody had said "Nice, I'd definitely use that." They were being kind. Nobody had a real need.

Validation is how you avoid this. You find out whether people have the problem, care enough to fix it, and will pay, before you spend months or lakhs.

Ideas usually start with a solution: "an app that does X". Rewrite it:

[Specific type of person] struggles with [specific problem] when [situation], which costs them [time / money / stress]. They currently solve it by [current workaround].

Examples:

• "Freshers in tier-2 cities struggle to understand salary offers because CTC breakdowns are confusing. They currently ask friends or rely on HR. See CTC vs in-hand salary for the kind of confusion."
• "Small bakeries with 5 to 20 orders a day lose track of custom cake orders on WhatsApp, and miss orders."

If you can't fill this in, you don't yet understand the problem. Keep going back to it.

"Everyone" is not a customer. Choose a narrow group you can reach this month: "final-year engineering students at three colleges in Coimbatore" or "home bakers in my city on Instagram".

Every idea rests on assumptions. Write them and rank them by risk:

• The problem is real and frequent.
• It's painful enough to pay to fix.
• They're already trying to solve it (time or money spent).
• We can reach them cheaply.
• They'll pay a price that supports a business.
• We can deliver a solution.

Test the riskiest first. Usually, it isn't "can we build it?" but "does anyone care?".

Aim for 10 to 20 conversations with people in your target group before writing any product code. This is the most valuable step and costs only time.

• Friends of friends, college alumni groups, WhatsApp and Telegram communities
• LinkedIn and Instagram messages (short and polite)
• Forums, subreddits and local groups
• Physical places: shops, markets, campuses, offices

Don't pitch. Say you're researching a problem and want to learn how they handle it. Offer a small thank-you, such as coffee or a voucher, if appropriate.

Friends and family will encourage you. That's kind, and useless. Follow these rules, based on the "Mom Test" approach:

1. Talk about their life, not your idea.
2. Ask about the past, not the future. Past behaviour is a fact. Future promises are hopes.
3. Ask for specifics, such as stories, numbers and examples.

Bad questions:

• "Do you think this is a good idea?"
• "Would you use an app that does this?"
• "Would you pay ₹500 a month for it?"

Good questions:

• "Tell me about the last time you [had this problem]. What happened?"
• "What did you do about it?"
• "What did that cost you in time or money?"
• "What have you tried? What was annoying about it?"
• "Why is it still a problem?"
• "Who else is involved in this?"
• "If you could change one thing, what would it be?"

Take notes, and listen more than you talk. Watch for:

• Strong signals: they describe the problem in detail with emotion, they have already spent money or time on workarounds, they ask when it'll be ready, they offer to introduce others.
• Weak signals: polite praise, "sounds interesting", hypothetical enthusiasm.

Every problem has a current solution, even if it's a spreadsheet, a WhatsApp group, a notebook or doing nothing.

• If people pay for a current solution, there's a market, and your job is to be better, cheaper or different for a narrow group.
• If they have no workaround at all, it may not be a pain point.

Also research competitors. Competition means demand. If you find none, ask why.

Once you've heard the same problem several times, run a small test of the solution, with minimal building.

A landing page. Create a one-page site that explains the problem, your solution, the price or plan and a sign-up button. Drive some traffic from communities or small ads. Measure sign-ups. Simple page builders and templates make this possible in an afternoon. If you're curious how pages work under the hood, see how a website works.

A concierge test. Deliver the service manually for a few customers. For example, if your idea is a meal-planning app, create plans in a spreadsheet and send them on WhatsApp. You'll learn what matters before automating.

A "Wizard of Oz" prototype. The customer sees a working product, while you do the work behind the scenes by hand.

A clickable prototype with design tools, shown to users to test the flow.

A pre-sale. Ask people to pay or put a deposit down before it exists. If 10 of 50 interested people pay, you have strong evidence. If none will, that's a lesson too.

If you take pre-orders, make it clear what's being sold and when it will be delivered. Refund promptly if you don't deliver. Be transparent, and follow consumer protection and tax rules.

Before the test, write:

"If at least X out of Y people do Z, I'll continue. If not, I'll change the idea or stop."

Examples:

• "If 30 of 200 landing page visitors leave their email and 5 pay the ₹499 deposit."
• "If 8 of 15 interviewees describe the problem unprompted and 4 agree to a paid pilot."

Setting the bar beforehand prevents you from adjusting it afterwards to feel good.

Possible outcomes:

• Strong evidence: people want it, and pay or commit. Go build a small first version and keep talking to customers.
• Mixed evidence: the problem is real, but your solution or audience is off. Adjust, and test again.
• Weak evidence: little interest. Pivot to a related problem you heard, or stop. Stopping early is a success, because you saved months.

• Falling in love with your solution.
• Only asking friends and family.
• Collecting compliments instead of commitments.
• Building before talking.
• Targeting too broad a market.
• Ignoring pricing until later.
• Counting free sign-ups as demand. Free is easy. Paying is evidence.
• Waiting for perfection. Test with something rough.

• Start small. Test with money you can afford to lose. Your own financial safety net matters, so build an emergency fund first and keep your job while you test.
• Register the business when it makes sense. Options in India include sole proprietorship, LLP and private limited company. Each has different tax and compliance. The Startup India portal explains schemes and registration. Talk to a CA or lawyer before you take investment or sign contracts.
• GST and taxes may apply once you earn above thresholds or sell certain services. Check current rules.
• Protect your name and brand where it matters, and respect others' intellectual property.

Once you have your first customers, read how to get your first 10 customers.

Ideas are rarely the problem. Execution is. Don't keep your idea secret, since you need feedback. Share it with potential customers, not with a fear of being copied.

Until you stop hearing new things, usually 10 to 20 per customer segment.

Only after you've confirmed the problem. Keep the first version as small as possible, and aim to deliver one clear benefit.

Not to validate. Many tests need no code. For building, you can use no-code tools, freelancers or a co-founder. If you want to learn to build, see learning to program in the AI era.

Good. You've saved time and money, and you've learnt about a customer group. Many successful businesses came from pivoting after early research.

This article is general educational guidance, not legal, tax or investment advice. Regulations differ by business type and location.