How to Validate Your App Idea Before You Spend on Building It
Every week, someone spends months and thousands of dollars building an app that nobody downloads. The code works. The design looks good. The problem is simpler and harder to fix: nobody wanted the app in the first place. Most apps do not fail because the code was bad. They fail because the idea was never tested with real people who have the real problem. Validation is the work you do before you build, to find out whether your idea solves a problem people care about, whether they will use it, and whether they will pay for it.

Validation is not a survey that asks strangers whether they like your idea. People are polite, and polite answers are worthless. Validation is a series of small, cheap tests that get harder to pass as you go. First you listen. Then you watch what already exists. Then you put something simple in front of real users and watch what they do, not what they say.
This guide gives you the steps in order, from cheapest to most expensive. You do not need a team, a budget, or a working app to start. You need ten honest conversations, a careful look at your competitors, a simple landing page, a clickable prototype, and a way to tell a real yes from a polite one.
The short answer: five cheap tests before you build
If you only read one section, read this one:
- Talk to 10 people who have the problem: ask about their life, not your idea, and listen for pain they already pay to fix
- Study competitors and their reviews: if nobody sells anything similar, find out why, and if they do, read what users complain about
- Build a simple landing page with a waitlist: describe the promise in one sentence and see if strangers leave an email address
- Test a clickable prototype with 5 users: give them a task, watch them try it, and count how many finish without help
- Ask for money or a written commitment: a pre-order, a deposit, or a letter of intent for a business tool is real proof
Validation is not one test. It is a chain of tests, and each one should make you more confident, not less. A good idea passes the early tests easily and survives the harder ones. A weak idea usually fails early, while it is still cheap to stop. That is the whole point: fail fast on paper, so you do not fail slowly in code.
The five validation steps, cheapest first
1. Talk to 10 people who have the problem
Find ten people who already have the problem your app would solve, and talk to them before you describe your solution. Ask how they deal with the problem today, what it costs them in time or money, and what they have already tried. If they have tried nothing and the problem does not bother them, your app is solving a problem they do not feel.
2. Watch competitors and their reviews
Search for apps, tools, spreadsheets, and services that already help with this problem. Competitors are good news: they prove someone will pay. Read their one star and three star reviews first, because those reviews list the exact gaps your app could fill.
3. A simple landing page with a waitlist
Make one page that states the promise in a single sentence, shows who it is for, and asks for an email address to join the waitlist. Share it where your future users already spend time, not only with friends. A page that gets visits but no signups is telling you something important: the promise is not clear, or the problem is not painful enough.
4. A clickable prototype test with 5 users
Draw the main screens in Figma or a similar tool, link them together, and give five people a task to complete, such as booking a slot or finding a price. Do not explain the screens. Watch where they tap, where they hesitate, and where they give up.
5. Pre-selling or letters of intent
For a business tool, the strongest test is a written commitment. Ask a business to sign a short letter of intent that says they will trial the tool when it is ready, or ask early users to pre-order at a discount. Money is the clearest signal of all, because it costs the buyer something.
What counts as a real yes, and what does not
A real yes costs the person something. An email address costs a little trust. Time costs a little of their day. Money costs the most, so it proves the most. When someone signs up for a waitlist, books a call, completes a prototype task, or pays a deposit, they have spent something real. That is a yes you can build on. Collect several of those, from people you did not know before, and your idea has passed its first real test.
A polite yes costs nothing, and it is the most dangerous answer in validation. ‘That sounds great’, ‘I would definitely use that’, and ‘Let me know when it is ready’ feel like encouragement, but they predict almost nothing. People say these things to be kind, or because they are imagining a perfect version of your app that does not exist yet. The test is not what people say about the future. It is what they do today, with the version in front of them.
Got an idea and a good feeling? Test the feeling first.
A good feeling is a fine place to start, and a terrible place to finish. Before you spend on design and development, put the idea in front of real users and let their actions decide. A short prototype test can show you in a week what months of building would only reveal too late. If the tests pass, you will build with confidence, and you will know exactly who you are building for.
How to run interviews and prototype tests without leading people
Start with their problem, not your solution. The first ten minutes of an interview should be about their day, their work, and the last time the problem happened. Do not mention your app until you understand how they cope today. If you open with your idea, every answer after that is a reaction to your pitch, not evidence about their life.
Ask about the past, not the future. ‘What did you do last time this happened?’ gives you facts. ‘Would you use an app that did this?’ gives you a guess, and guesses are usually generous. Past behaviour is the best predictor you have: what they paid for, what they tried, and what they stopped using.
Give prototype users a task, then stay quiet. A good task sounds like real life: ‘Book a cleaning for Saturday morning’ or ‘Find the cheapest plan for two people’. Then watch. Do not point, do not explain, and do not rescue them. Every time you help, you lose the information you came for.
Test with strangers, not friends. Friends want to encourage you, and they already know too much about the idea to use it like a stranger would. Five strangers who match your future users will tell you more than fifty friendly opinions.
Interview questions that actually work
Good questions ask for stories and facts. Bad questions ask for opinions about your idea. Try these instead:
- Tell me about the last time this happened. What did you do, and how long did it take?
- What have you already tried to fix it? What did you pay for, and why did you stop?
- What would happen if you did nothing? If the answer is 'not much', the pain is not strong enough yet.
Prototype tasks that reveal the truth
A prototype test is not a demo. You are not showing off the design. You are watching someone try to get something done:
- Give one clear task. One goal, no hints, and a realistic starting point.
- Count completions, not compliments. How many finished, how long it took, and where they stopped.
- Ask what they expected to happen. The gap between what they expected and what they saw is your next fix.
Three mistakes that make validation useless
Most validation fails for the same three reasons, and all three are avoidable:
- Asking friends and family. They love you, so they love the idea. Their praise tells you nothing about strangers.
- Asking about the future. 'Would you use it?' is a guess. 'What did you do last time?' is evidence.
- Counting praise as proof. Compliments are free. Emails, time, and money are not. Only the second group counts.
When to stop, pivot, or build
- Build when strangers act, not just agree. Real signups, completed prototype tasks, and at least a few people willing to pay are a green light. Build the smallest version that delivers the core promise, and keep testing as you go.
- Pivot when the problem is real but your solution is wrong. If people feel the pain but ignore your landing page or fail your prototype, the problem may be real and the answer different. Change the audience, the promise, or the main feature, then test again.
- Stop when nobody feels the pain. If ten interviews find no real cost in time or money, if competitors have no paying customers, and if a clear landing page gets no signups, the kindest choice is to stop.
- Stop when the only yeses come from people who know you. Friends, family, and colleagues are not a market. If strangers stay silent, the market has already answered.
- Revisit when the world changes. A ‘no’ today is not a ‘no’ forever. New rules, new tools, or a new audience can turn a weak idea into a strong one. Keep your notes, and test again when something real has changed.
A worked example: validating an idea in two weeks
Imagine you want to build an app that helps small clinics manage patient reminders. You do not build it yet. In week one, you talk to ten clinic managers and ask how they remind patients today, what missed appointments cost them, and what they already pay for. Seven of them say missed appointments cost real money, and three already pay for a reminder tool they dislike. That is a real problem with real spending behind it.
In week two, you make a one page site that promises fewer missed appointments and share it in a clinic managers group. Forty strangers leave an email address. Then you draw three screens in Figma, link them, and ask five managers to book a reminder for a patient. Four finish without help, and one gets stuck on the date picker. You fix the picker, and two clinics sign a short letter of intent to trial the finished tool. You have spent two weeks and almost no money, and you now have proof that strangers care, forty email addresses, and two clinics waiting for the product.
- Week one, interviews: 10 conversations, about 5 hours, cost $0
- Landing page and waitlist: one evening to build, 40 signups from strangers
- Clickable prototype: 3 screens in Figma, 5 user tests, 4 completed the task
- Commitment: 2 letters of intent from real clinics
- Decision: build a small MVP for those two clinics first, not a full app for everyone
Two weeks of testing: roughly 15 hours of your time and almost no money. Compare that with building the full app first: months of work, thousands of dollars, and the same questions answered only after launch, when fixing them is ten times harder. Validation does not guarantee success. It guarantees that you start with evidence instead of hope.
So what should you do first?
No users yet. Start with ten interviews. Do not design anything until you can describe the problem in the exact words your users used, and name what it costs them today.
Competitors already exist. Read their reviews before you write a line of code. The complaints are your feature list, and the praise tells you what you must match on day one.
You already have a prototype. Test it with five strangers this week. Give them one task, stay quiet, and fix the place where most of them stop. Then test again.
People say they will pay. Ask them to prove it. A small pre-order, a deposit, or a letter of intent turns a nice conversation into a decision you can plan around.
Our prices, in the open
Once your idea has passed its tests, itcroc LLC can build the prototype or the MVP for you. We publish our prices so you can plan before you talk to us:
- Brand Identity from $600
- UI/UX Design from $1,200
- Website Development (WordPress or Framer) from $1,300
- Motion Design from $320
- WordPress Care Plans from $49/month
Custom software and MVP work is quoted per scope, after a short scoping conversation. Every project is a fixed price agreed before we start, 50% to begin, 50% on delivery. No hourly billing, no surprise invoices, and you own your website, domain and files.
Frequently asked questions
How many people do I need to interview to validate an app idea?
Ten is a good start. Ten honest conversations with people who have the problem will show you the main patterns. If the same pain, the same workarounds, and the same spending come up again and again, you have enough to move on.
What if there are no competitors for my app idea?
Be careful, and find out why. It can mean an open market, but it more often means nobody has found paying customers for this problem yet. Look for indirect competitors too: spreadsheets, manual work, and services that solve the same problem in a slower way. If people pay for any of those, the problem is real.
How do I know if a landing page test has passed?
Set the rule before you start. A useful rule is at least 30 email signups from strangers in two weeks, from a page that states one clear promise. Signups from friends do not count. If the page gets visits but no signups, the promise is unclear or the problem is not painful enough.
Is five users really enough for a prototype test?
For finding the biggest problems, yes. Five users will find most of the serious issues in a flow, because they tend to get stuck in the same places. Test five, fix the biggest problem, then test five new users.
What is the difference between validation and market research?
Market research tells you how big a market is. Validation tells you whether real people will act. A market can be huge and still ignore your app, so validation is the more useful question for a founder.
When should I stop validating and start building?
When strangers have given you something real: email addresses, their time in a prototype test, and ideally money or a written commitment. That is enough to build the smallest version that delivers the core promise.
Your idea deserves proof before it gets a budget
Start with a free UX audit. Send us your prototype or your idea, and a senior designer will review it by hand and send you a clear report on what is working, what is confusing, and what to test next.
Get your free UX audit or book a free 30-minute discovery call if you would rather talk it through first.
Keep reading
Build Better Digital Experiences.
itcroc helps businesses create modern websites, UI/UX design systems, Framer landing pages, and scalable WordPress solutions for optimal performance and growth.


