Your Startup Idea Isn't Special. Here's How to Find Out Before You Waste ₹10 Lakh Proving It

Every founder thinks their idea is the exception. The one that doesn't need validation because it's "obviously" needed. I've watched enough of these ideas die quietly six months after launch to know: obvious is not the same as validated.

Here's the uncomfortable truth. Most startup ideas aren't bad — they're just untested. And the gap between "sounds good in a pitch deck" and "someone will actually pay for this" is where most of the money disappears. Development is expensive. Validation is cheap. Yet founders routinely reverse that order.

If you're about to spend money building something, do these five things first.

1. Talk to 20 people who are NOT your friends

Friends and family are the worst validation panel you can assemble. They love you, so they'll tell you what you want to hear. "That's such a cool idea!" is not market research.

Find 20 strangers who actually fit your target user. Cold DM them, post in relevant communities, ask for 15 minutes of their time. Don't pitch — ask about their current process. How do they solve this problem today? What do they use? What annoys them about it? What have they already tried and abandoned?

If people can't describe the pain in their own words without you prompting them, the pain might not be big enough to build a business on.

2. Try to sell it before you build it

This is the fastest gut-check there is. Build a one-page landing site describing what you're building, the core benefit, and a clear call to action — "Join the waitlist" or "Pre-order now." Run a small ad budget behind it, or share it organically where your audience hangs out.

You're not measuring page views. You're measuring intent: email signups, pre-orders, or better, actual payment commitments. A hundred people saying "cool idea" in the comments means nothing. Ten people giving you their card details means everything.

3. Build the fake version first

Before writing a line of production code, build the "Wizard of Oz" version — where the front end looks real but the back end is manual. Booking a service? You confirm it by hand. Automating a report? You generate it yourself and email it over.

It's unglamorous and doesn't scale, but it tells you two critical things: whether people actually use the thing once it exists, and where the real friction points are — which are almost never where you assumed they'd be.

4. Check if the market is already voting with its wallet

If nobody else is attempting to solve this problem, that's not automatically a good sign — sometimes it means there's no money in it. Look for adjacent or competing solutions, even clunky ones like spreadsheets, WhatsApp groups, or Craigslist-style workarounds. Their existence is proof people are already paying (in money or effort) to solve this. Your job becomes making that solution better, not creating demand from scratch.

5. Set a validation budget and a kill number, before you get emotionally attached

Decide upfront: "I will spend ₹50,000 and 4 weeks testing this. If I don't see X signups / Y pre-orders / Z paying customers, I stop and rethink."

Write this down before you start. Once real money and time go into building, sunk cost bias kicks in hard, and founders keep shipping features to a market that never asked for them in the first place.

The point of all this

Validation isn't about proving you're right. It's about finding out you're wrong as cheaply and quickly as possible, so the version you eventually build is the one people were already asking for.

Development cost isn't just money — it's the 3-6 months you can't get back if the idea doesn't land. Spend that time listening and testing first. Building comes after, not instead.