How to Validate Your Startup Idea Before Building Anything
Building without validation is the most common and most expensive startup mistake. Here is how to validate quickly and cheaply before spending on development.
Let me save you potentially months of work and lakhs of rupees with one sentence: do not build anything until you have real evidence that people will use it.
I know that sounds obvious. And yet the most common startup post-mortem I hear is some version of "we built it and nobody came." Almost always, a few weeks of proper validation would have revealed the problem.
Why Friends Are Useless for Validation
When you describe your idea to friends and family, they will almost always be encouraging. "That sounds amazing! I would definitely use that!" This is not validation — it is social courtesy.
Real validation comes from people who have no social obligation to encourage you. Strangers who represent your target users. People who currently deal with the problem you are trying to solve.
When we were building NestSpace, I deliberately talked to people I did not know — random young professionals at cafes, students in paying guest accommodations, people scrolling through OLX in frustration. Their unfiltered accounts of the problem were far more useful than anything friends would have said.
Method 1: Problem Interviews (Most Important)
Find 15 to 20 people who have the problem your app solves. Not who might have the problem — who have it today.
Do not pitch your solution. Ask about their experience with the problem. Listen more than you talk. The questions that produce useful answers are specific and open-ended: "Tell me about the last time you tried to find a flatmate." "How do you currently handle X?" "What is the most frustrating part of this?"
You are looking for: genuine pain (they get animated talking about the problem), frequency (it happens regularly, not once a year), and current workarounds (they have developed hacks to deal with it, which suggests they care enough to try).
If people struggle to describe the problem clearly, or if it does not seem particularly painful, that is important information.
Method 2: Landing Page Test
Build a simple landing page — one page describing the app's main benefit, a single call to action (email signup or "get early access"), and a brief explanation of what you are building.
Drive 300 to 500 visitors to it through Instagram ads (Rs 5,000 to 10,000 is usually enough), relevant Reddit or Facebook groups, or LinkedIn posts.
If 5 percent or more of visitors sign up with their real email address, you have meaningful validation. If 1 percent sign up, that is a signal to reassess.
Method 3: Pre-Selling
Before building, offer your future product for sale at an early-access discount.
"Pay Rs 2,000 now for lifetime access when we launch" is a dramatically stronger validation signal than an email signup. People who give you real money for something that does not exist yet are telling you very clearly that the problem is real and your solution sounds credible.
Even 10 to 20 pre-sales is meaningful validation. Zero pre-sales after genuine effort to sell is meaningful feedback too — better to learn that now than after months of development.
What Counts as Real Validation
An email signup: weak, but something. Payment: strong. Consistent use of an early prototype: strong. "That sounds interesting" from a friend: not validation at all.
At Rooted Tech, we encourage founders to validate before building. We have built our own product (NestSpace) and understand the validation process from experience. Reach out at rootedtech.in/contact.
Found this useful? Share it.
Building something? Let us talk.
Tell us what you are building. We will come back within 24 hours with honest feedback and a rough plan.