Every week, someone walks into a development conversation with an app idea they are genuinely excited about. They have thought through the features, sketched out the screens, and already have a name in mind. What they have not done is confirm that anyone else wants it.
This is how most app projects fail — not at the development stage, but long before it. The idea was never tested against reality. By the time that becomes clear, months and significant money have already been spent.
Validation is the step that sits between idea and investment. Done well, it either confirms that you are building something people want, or it saves you from spending a rupee on something they do not.
What Validation Actually Is — And What It Is Not
Validation is not asking your friends and family whether they like your idea. They will almost always say yes, because they like you. Their encouragement is not market data.
Validation is also not a formal market research report, an expensive survey, or a prototype. It does not require a developer, a designer, or any technical work at all.
What validation actually is: a structured process of gathering honest evidence from real strangers that the problem you are solving exists, that they experience it with enough frequency and pain to want a solution, and that they would engage with the kind of solution you are proposing.
The output is not a green light. It is clarity — either the confidence to move forward or the information you need to change direction before it costs you anything significant.
Validation is not about proving you are right. It is about finding out whether you are wrong before it is expensive to be wrong.
Step 1 — Define the Problem, Not the Features
The most common mistake at this stage is starting with a solution. Most people describe their app idea as a list of features: “It will have a booking system, a chat function, a dashboard, and push notifications.” That is a feature list. It is not a problem definition.
Start instead with the problem you are solving. Be specific:
- Who has this problem?
- What are they doing right now to deal with it?
- How often does this problem occur?
- What does it cost them — in time, money, or frustration — when it does?
The more precisely you can articulate the problem, the easier validation becomes. A problem like “people find it hard to manage home service bookings” is vague. “Home service customers in Dubai lose an average of two hours per week coordinating between multiple vendors with no single point of contact” is specific, measurable, and testable.
Write your problem statement down in one or two sentences before you do anything else.
Step 2 — Identify Your Target User Precisely
Your app is not for everyone. The broader you define your audience at this stage, the harder validation becomes and the weaker your eventual product will be.
Define your target user with enough specificity that you could find ten of them in a day:
- What industry are they in or what role do they have?
- Where are they located?
- What is their approximate age or income range?
- What tools or apps are they already using to deal with the problem?
This matters for validation because you need to talk to the right people. Feedback from the wrong audience — people who do not actually have the problem — will mislead you in both directions. It may falsely confirm demand or falsely deny it.
Step 3 — Talk to Real People Before You Build Anything
This is the most important step in validation and the one most people avoid because it feels uncomfortable. You need to have honest conversations with strangers who match your target user profile.
Aim for at least 10 to 15 conversations. Fewer than that and the patterns you think you see may just be coincidence.
How to find people to talk to
- LinkedIn — search for people with the relevant job title or industry and send a short, honest message explaining what you are researching
- Industry groups and communities — WhatsApp groups, Facebook groups, Reddit communities, and professional associations
- In-person — if your target user is local, go where they are. Shops, offices, markets, events
- Your own network — not to ask them about your idea, but to ask for introductions to people who fit the profile
What to ask in these conversations
Do not pitch your idea. Ask about their experience with the problem. Good questions to ask:
- Tell me about the last time you had to deal with [the problem]. What happened?
- How are you handling it right now?
- What is the most frustrating part of the current solution?
- Have you ever looked for a better way? What did you find?
- How much would it be worth to you to have this solved properly?
Listen more than you talk. The goal is to understand their experience, not to validate your assumptions by telling them what you think the solution should be.
The most valuable moment in a validation interview is when someone describes a pain point you had not anticipated. That is real signal.
Step 4 — Check Whether the Problem Is Already Solved
Before you go further, do a thorough competitive audit. Search the App Store and Google Play for apps that solve the same or similar problem. Search Google. Look at what your target users are already paying for.
Finding competitors is not bad news — it is confirmation that the problem is real and that people are willing to pay to solve it. The question is not whether competition exists, but whether you can build something meaningfully better, faster, cheaper, or more targeted.
What you are looking for in this research:
- What do existing solutions do well?
- What do their reviews say is missing or broken?
- Who are they built for — and is there a segment they are not serving well?
- What is the pricing model and what do users say about value for money?
The App Store review section is one of the most underused research tools available to anyone planning a new app. Read the one and two-star reviews of your competitors. They will tell you exactly what users want that they are not getting.
Step 5 — Test Demand Without Building the App
You do not need to build the app to test whether people want it. There are several methods to generate real demand signal without a line of code:
Landing page test
Build a simple one-page website — using Webflow, Carrd, or even a basic WordPress page — that describes the app as if it already exists. Include a clear value proposition and a call to action, such as joining a waitlist or registering for early access. Run a small amount of paid traffic to the page and measure the conversion rate.
A conversion rate above 15 to 20% on a cold audience is strong validation. Below 5% is a signal to revisit the proposition.
Manual concierge test
For certain app types, you can deliver the service manually before automating it. If your app is meant to match home service providers with customers, try doing the matching yourself through WhatsApp for a week. If it works and people pay, the automation is worth building. If nobody engages, the assumption was wrong.
Pre-sales
For B2B apps especially, asking potential users to sign a letter of intent or pay a small deposit before the app is built is the strongest form of validation. If someone is willing to commit money to a product that does not yet exist, they have the problem and they believe in the solution.
Step 6 — Validate Willingness to Pay
This step is where many validation exercises fall short. People will happily tell you they want something when it is free. The question that matters is what they will pay for it.
Ask directly in your interviews. After understanding their problem and current solution, say: “If an app solved this problem for you, what would you expect to pay for it — and what would make it obviously worth that price?”
Listen for hesitation. Listen for the conditions they attach to payment. Those conditions often contain your most important product requirements.
Also test pricing assumptions in your landing page. Present a pricing tier and see whether the conversion rate changes when you include price versus when you do not. The gap tells you something about price sensitivity.
How to Interpret Your Validation Results
After 10 to 15 conversations and a landing page test or pre-sales attempt, you should have a clear enough picture to make a decision. Here is how to read what you have found:
Strong validation signals
- Multiple people described the problem in almost the same words without being prompted
- People are already paying for an imperfect solution to the same problem
- Your landing page converted at 15% or above on cold traffic
- One or more people asked when the app would be ready or offered to pay now
Weak or negative signals
- People said they “might” use it but could not describe a recent instance of the problem
- The only people who liked the idea were people who already knew you
- You could not find 10 relevant people willing to have a conversation
- Landing page conversion was below 5% across multiple traffic sources
Weak signals do not always mean the idea is bad. They may mean the framing is wrong, the target audience is too narrow, or the problem is not as frequent as assumed. Use what you learn to refine the idea and test again — that is the point of validation.
A failed validation is not a failed idea. It is free information. The goal is to learn as much as possible before spending money on development.
What Comes Next
If your validation is strong, the next step is defining exactly what to build — starting with the smallest version of the app that delivers real value to real users.
Read the next post in this series: What Is an MVP App and Why Every First-Time Founder Needs One
Or return to the full planning guide: How to Plan a Mobile App: The Complete Guide for Business Owners (2026)
