Platforms, Systems & Growth
How to Validate an App Idea Before You Spend a Euro on Development
Updated 12 July 2026 · Tech Box
Quick answer
To validate an app idea: talk to 15–20 target users about the problem (not your solution), study how they solve it today and what that costs, run a landing-page test measuring real sign-ups, simulate the service manually if possible (concierge test), and seek pre-commitments — payments, deposits, or signed letters of intent. Weeks of validation routinely save six-figure mistakes.
The most expensive sentence in software is 'people will definitely want this.' Most failed apps didn't fail at engineering — they built something nobody needed. Validation replaces confidence with evidence before the big spend. This guide gives you a validation sequence you can run in 2–4 weeks with almost no budget.
Step by step
- 1
Write the assumption you're betting on
One sentence: '[audience] has [problem] painful enough to [pay/switch/act]'. This is what you are testing — not whether people say your mockup looks nice.
- 2
Run 15–20 problem interviews
Ask about the problem, never pitch: 'Walk me through the last time you dealt with this. What did it cost you? What have you tried?' Past behavior is evidence; hypothetical enthusiasm ('I'd totally use that!') is noise.
- 3
Study the current alternatives
How do people solve this now — competitor apps, spreadsheets, WhatsApp, an assistant, ignoring it? No current spending of money or effort on the problem is a red flag; ugly workarounds are a green one.
- 4
Run a landing-page smoke test
A one-page site with your value proposition and a sign-up form, plus €200–500 of targeted ads. Conversion above ~5% from cold traffic signals real interest; collect emails for launch.
- 5
Concierge the service manually
Deliver the app's value by hand for 5–10 users — match them manually, build their reports in a spreadsheet, send updates yourself. You'll learn the real workflow and whether people value the outcome before automating it.
- 6
Ask for a commitment
Pre-orders, deposits, pilot agreements, or signed letters of intent for B2B. The moment money or reputation enters, feedback becomes honest. Ten paying pre-orders outweigh a thousand survey likes.
- 7
Decide with thresholds set in advance
Define pass/fail before testing: e.g., '8 of 20 interviewees describe this as a top-3 problem AND landing page converts 5%+ AND 5 pre-commitments'. Meeting them → scope an MVP. Missing them → pivot or stop, having spent weeks instead of a year.
Common validation traps
The four ways founders fool themselves:
- Interviewing friends and family — they love you, not your market
- Pitching instead of listening — enthusiasm you created is not demand you discovered
- Counting compliments as evidence — only behavior counts: sign-ups, time, money
- Validating the solution before the problem — a slick prototype of an unneeded product still fails
Validate first, build second — we help with both
Tech Box runs discovery sprints that pressure-test ideas before development: structured interviews, landing-page experiments, clickable prototypes for user testing, and an honest go/no-go recommendation with an MVP scope if the evidence supports building.
We would rather lose a project to honest validation than build you something the market already voted against.
Frequently asked questions
How long does it take to validate an app idea?
A rigorous validation cycle — interviews, landing-page test, and a concierge experiment — runs 2–4 weeks and costs a few hundred euros in ads, versus months and six figures for building unvalidated.
How many user interviews do I need?
15–20 interviews with genuine target users typically reach signal saturation — patterns repeat and new interviews stop surprising you. Recruit strangers from the actual audience, not acquaintances.
What is a concierge MVP?
Delivering your app's value manually for a handful of users — matching, reporting, or coordinating by hand — to test whether people value the outcome before you automate it with software.
What proves an app idea is worth building?
Converging evidence: users independently describing the problem as painful, existing spending on workarounds, cold-traffic conversion on a landing page, and pre-commitments of money or signed intent — not compliments.