How to validate an app idea before you spend a dollar

The most expensive way to test an idea is to build it. Here are five ways to get real signal first, none of which require production code.

You can validate an app idea in about a week, without writing code, by testing one thing: whether a specific group of people will give you their time, their email, or their money to solve the problem. Four cheap tests do it — problem interviews, a landing-page smoke test, a clickable prototype, and a request for a small commitment.

Validation tests behavior, not opinions

The trap every founder falls into is asking people if they like the idea. They'll say yes — being encouraging is easier than being honest — and you'll mistake politeness for demand. Real validation looks for behavior instead, because behavior is expensive to fake. A stranger's email, a deposit, a completed task in a prototype: those mean something. "Great idea" means nothing.

Talk about the problem, not your solution

Start with problem interviews, and resist pitching. The moment you describe your app, the person starts being polite. Instead, ask about the past: "walk me through the last time this happened," "what did you do," "what did it cost you." People are accurate historians and terrible predictors, so anchor on what they've actually done, not what they say they'd do. Listen especially for anyone who's already cobbled together a workaround — that's real pain.

Put up a page and see who signs up

A landing-page smoke test turns interest into a measurable action. Describe the solution as if it exists, add one clear call to action — join the waitlist, request early access — and drive a little traffic. The signup rate, and the words people use when they sign up, tell you whether the promise lands with real strangers, not just friends being kind.

Watch five people use a prototype

A clickable prototype — screens linked together with no code behind them — lets you watch what actually happens when someone tries to reach your core value. You're testing two things: do they understand the value, and can they get to it without getting stuck. Watching a handful of people attempt the core task in silence reveals more about your idea and your UX than any survey.

Ask for something that costs them

The strongest pre-build signal is a small sacrifice: a pre-order, a refundable deposit, a paid pilot, a firm scheduled call. It's worth more than a hundred enthusiastic comments, because it cost the person something. If people love the idea but won't commit anything, that's not validation — it's a warning that the problem may not be painful enough to change behavior for.

Then act on what you learn

Validation is only useful if you'll act on it. Strong signals across tests mean proceed to scoping and a PRD. Mixed signals — real problem, wrong solution — mean pivot: keep what worked, change what didn't. Weak signals mean stop or reshape before you spend a build budget. Killing a weak idea in week one isn't failure; it's the cheapest win validation can hand you.

The full playbook is in how to validate an app idea, and it's the first step in planning an app.