How to Validate a Startup Idea Before You Spend Money on Development

Before a project with us starts, I usually ask founders three questions: who exactly has this problem, how do they solve it today, and what have they paid to solve it before? The answers predict more than any feature list.

Step 1: Write down the problem in one sentence

"Salon owners lose bookings because clients cannot see free slots outside working hours." Specific customer, specific pain, specific consequence. If you cannot write this sentence, start there.

Step 2: Talk to ten to fifteen target customers

Ask about their past behaviour, not your idea: when did this last happen, what did you do, what did it cost, what have you tried? The book The Mom Test by Rob Fitzpatrick is a practical guide to asking questions that do not lead the answer.

Step 3: Study what people use today

Spreadsheets, WhatsApp groups, a competitor, an old tool: the current workaround tells you what your product must beat. If people are happy with the workaround, the problem may not be painful enough.

Step 4: Test demand with a landing page

Describe the outcome, not the features, and ask for a clear action: join a waitlist, book a call or pre-order. Send a small amount of targeted traffic and measure how many take the action.

Step 5: Put a prototype in front of users

A clickable prototype shows whether people understand the product and can complete the core task. Read MVP vs prototype vs proof of concept to choose the right test.

Step 6: Read the signals honestly

The Startup India portal also lists programmes and resources that can help Indian founders at this stage.

Interview questions that work

• "Tell me about the last time this happened. What did you do?"
• "What have you already tried to solve it? What did that cost?"
• "What is the hardest part of doing this today?"
• "Who else is involved in deciding how this gets solved?"
• "If this problem disappeared tomorrow, what would change for you?"

Avoid questions like "Would you use an app that does this?" People are polite, and the answer will almost always be yes.

Validating a B2B idea

For business customers, the buyer and the user are often different people. Talk to both. A finance head may approve the budget while the operations team uses the tool every day. Strong B2B signals include a paid pilot, access to real data for a trial, or a named person committing time to test the product.

Mistakes to avoid

• Only talking to friends and family.
• Pitching the solution in the first five minutes of an interview.
• Treating a large number of social media likes as demand.
• Changing the target customer after every conversation instead of looking for patterns.
• Waiting for certainty. Validation reduces risk; it never removes it.

Once you know which test you need, our guide on MVP vs prototype vs proof of concept helps you pick the right first build.

Step 7: Build the smallest version that solves it

Once the signals are strong, write a short PRD, cut it to the core job with the scoping framework, and build an MVP. At Creuto that first working version typically takes about 4 weeks.