Most startups do not fail because they could not build the product. They fail because nobody needed it enough to pay. The good news is that you can find this out in weeks, with very little money, before paying for development.
Step 1: Describe the problem, not the product
Write one sentence: “[Specific people] struggle with [specific problem], which costs them [time / money / stress].”
Weak: “An app for restaurants.” Strong: “Small restaurant owners lose orders because they take calls and WhatsApp messages by hand, which costs them hours every day.”
If you cannot name a specific customer and problem, you are not ready to build.
Step 2: Talk to real people
Interview 15–20 people who match your target customer. Do not pitch; ask about their life:
- “Tell me about the last time you faced this problem.”
- “How do you handle it today? What does that cost you?”
- “What have you tried? Why did it not work?”
- “Would you pay to solve it? How much do you pay now?”
Look for pain, frequency and existing spending. People already paying for workarounds are the best customers. Be wary of polite answers like “sounds nice”.
Step 3: Check the market and competitors
Competitors are good news — they prove demand. Study what they charge, what people complain about in reviews and what gaps exist. Decide how you will be meaningfully different for a specific group.
Step 4: Test interest cheaply
Before building software, try:
- A landing page describing the benefit with a call to action: join a waitlist, book a demo or pre-order.
- A small ad budget or posts in communities to bring targeted visitors.
- A prototype — clickable screens to show people. See MVP vs prototype vs proof of concept.
- Pre-sales or a paid pilot — the strongest evidence of all.
Measure how many visitors take the action. A few genuine commitments beat thousands of likes.
Step 5: Deliver the result manually
You can often simulate the product by hand: take orders over messaging, manage bookings in a spreadsheet, send reports manually. If customers love the result even when it is manual, automation will make it scalable. If they do not care, you have saved yourself months of work.
Step 6: Define success before you start
Decide in advance what counts as a pass, for example:
- 10 customers say they would pay and 3 pre-pay.
- 30% of landing-page visitors join the waitlist.
- 5 pilot users use it every week for a month.
Writing this down protects you from fooling yourself.
Step 7: Build the smallest real version
Only now build an MVP with 3–5 core features. Follow our SaaS MVP roadmap and plan your budget with the app cost guide. Get inspired by practical app ideas for India.
Red flags that mean “stop or change direction”
- Only friends and family say it is a good idea.
- Nobody currently spends money or time solving the problem.
- You cannot reach your target customers cheaply.
- Customers want something quite different from your plan.
- You keep adding features instead of finding customers.
Changing direction early is a success, not a failure — it saves your money.
Ready to build the validated idea?
We help founders turn tested ideas into working products. Explore our SaaS and web app service, mobile app service or get a free quote.
