The graveyard of failed startups is full of beautifully built apps that nobody wanted. Don’t join them.
Before you spend $30-80K on building an app, spend a weekend validating whether anyone actually wants it. Here are five methods that work — ranked from fastest to most thorough.
1. The Landing Page Test (2-3 Days)
Build a single page that explains what your app does and why someone would want it. Include a “Join the waitlist” button that captures emails.
How to do it:
- Use a simple site builder or have someone build it in hours
- Write a clear headline that describes the benefit (not the feature)
- Add 3-4 bullet points explaining what the app does
- Include a signup form
Then run $200-500 in targeted ads (Google or Meta) to your ideal customer. If your conversion rate is above 5%, there’s real interest. If it’s below 2%, your messaging is wrong or the demand isn’t there.
What this proves: People will stop scrolling and express interest. That’s more signal than any survey.
2. The Concierge MVP (1-2 Weeks)
Deliver your app’s value manually before automating it. This is the most underrated validation method.
Examples:
- Building a meal planning app? Manually create meal plans for 10 people via email and charge $10/week.
- Building a matching platform? Manually match people and facilitate introductions.
- Building an analytics dashboard? Pull reports manually in a spreadsheet and send them weekly.
What this proves: People will pay for the outcome your app delivers. The automation is just scale — the value is the important part.
3. The Pre-Sale (1 Week)
Ask people to pay before you build. This is the ultimate validation.
How to do it:
- Create a Stripe payment link for a discounted “founding member” price
- Offer early access, lifetime discounts, or input on features
- Email your waitlist or post in relevant communities
If 10 people pay before you’ve written a line of code, you have a business. If nobody pays, you’ve saved yourself months of building the wrong thing.
What this proves: Real demand, not hypothetical interest. Money is the only signal that matters.
4. The Competitor Deep Dive (1 Day)
If competitors exist, that’s actually good news — it proves there’s a market. Your job is to find the gap.
Research checklist:
- Read their 1-star reviews. What do users hate? That’s your opportunity.
- Check their pricing. Is there room for a more affordable option?
- Try their product. Where does it feel clunky or incomplete?
- Search Reddit, Twitter, and forums for complaints about existing solutions.
If you can articulate “I’m building X, but better because Y” and Y is something users actually care about — you have a viable angle.
What this proves: There’s an underserved segment in an existing market.
5. The “Mom Test” Interviews (1-2 Weeks)
Talk to 20 potential users. But do it right — don’t ask “would you use my app?” (everyone says yes to be polite).
Instead, ask:
- “Tell me about the last time you dealt with [the problem].”
- “What did you do to solve it?”
- “How much time/money did that cost you?”
- “What’s the most frustrating part?”
If people describe the problem with emotion and specificity, you’re onto something. If they shrug, the problem isn’t painful enough to build for.
What this proves: The problem is real, painful, and frequent enough to justify a solution.
The Validation Scorecard
Give yourself one point for each:
| Signal | Points |
|---|---|
| 20+ waitlist signups from cold traffic | 1 |
| 5+ people completed your concierge MVP | 1 |
| 3+ people pre-paid before the product exists | 1 |
| Competitors exist with clear gaps | 1 |
| 10+ interviews where people describe real pain | 1 |
4-5 points: Build it. You have strong validation. 2-3 points: Promising, but dig deeper on the weak areas. 0-1 points: Pivot your idea or target audience before spending on development.
What Comes After Validation
Once you’ve confirmed demand, you’re ready to build. Here’s the path:
- Define your core feature — the one thing that delivers the most value (use my MVP checklist)
- Get a realistic cost estimate — see my MVP pricing breakdown
- Choose your build partner — read how to hire a dev studio — or first decide whether you need a technical co-founder
- Ship in 8-12 weeks — not 8-12 months
Have a validated idea and ready to build? Request a technical triage — I’ll scope it, price it, and tell you honestly whether I’m the right engineer for it.