How to Validate Your App Idea Before You Spend a Single Penny on Development

The graveyard of well-built apps that nobody wanted is enormous. They had clean interfaces, smooth onboarding, thoughtful features. They had no users because the person who built them never stopped to ask whether anyone needed them.

Validation is not pessimism about your idea. It is the fastest way to prove — to yourself and to potential customers — that the idea is real. Done well, it takes two weeks. Done badly or skipped, it costs six months and thousands of pounds.

Most founders want to test whether people like their idea. That is the wrong question. Liking something is free. Paying for something is the only test that matters at this stage.

The three questions worth answering: Does the problem exist and genuinely frustrate people? Is your solution one they'd pay for? And — critically — is the price you need to charge one they'd accept? If you can get clear, honest answers to all three, you have something worth building.

Find ten people who fit your target customer profile and talk to them. Not a survey — a conversation. Ask about the problem, not about your solution. Ask how they currently handle it, how much time it costs them, whether they've tried to solve it before, and how much they'd pay to make it go away.

At least seven of the ten should describe the problem as genuinely painful before you take the next step. If they shrug and say it's a bit annoying, that's important data. If they light up and immediately ask when they can try it, that's the data you want.

A landing page that describes the product and shows a price is more informative than a survey with a thousand respondents. You want to know if someone will click 'Pay now' — not whether they'll say yes to a hypothetical question in a form.

Use Framer, Webflow, or even a well-configured Notion page. Describe exactly what the product does, show a clear price, and add a checkout button or a waitlist form. Paid waitlists — where someone puts down a small deposit to reserve access — are the gold standard. If nobody pays, the landing page is cheap. If people do, you have validation and early revenue.

Presales are underrated. If your community trusts you, tell them you're building something, describe what it does, offer a founding-member price, and ask for payment now. You can refund everyone if you decide not to build. Most won't ask for one.

The founders who skip this step usually have some fear attached to it — fear of rejection, fear of committing, fear of being held accountable. That fear is worth sitting with, because it often reveals something important about the confidence level you actually have in the idea.

There is no universal threshold, but a reasonable bar for a first MVP: ten paying customers, or a waitlist of fifty people who have put down a deposit, or consistent, unprompted expressions of real frustration with the problem you're solving.

If you reach that bar, you are ready to build. Not the full vision — the version one that solves the core problem and nothing else. The rest of the features come after you have real users telling you what they actually need.