How to Validate an App Idea Before You Build It

“I would use that” is easy to say and almost impossible to build a business on. Validation gets stronger as it moves from opinions to behaviour: people describe a current workaround, give time to a prototype, join a waitlist, introduce you to a buyer, or pay for a limited version.

Begin with the problem, not the product pitch

Talk to people who plausibly have the problem. Ask how they handle it today, what triggers the frustration, what it costs them, and what they have already tried. Avoid leading questions that invite compliments. You are looking for patterns in existing behaviour.

Test the risky assumption first

Every idea has a few bets: the problem is painful, the audience is reachable, the proposed approach is understandable, and the economics work. Identify the bet most likely to make the whole project fail, then design the smallest test that can change your mind.

• Create a focused landing page with a clear promise and measure qualified sign-ups.
• Use a prototype to test the main workflow before building production code.
• Deliver the service manually to learn what software truly needs to do.
• Ask for a real commitment: a meeting, a deposit, a pilot or a referral.

Let the evidence change the scope

Validation is not a gate you pass once. It should shape what you build next. If people care deeply about one part of the flow and ignore the rest, your MVP should reflect that. The best early product is often a more specific version of the original idea.

When the signal is strong, move into a focused build using this guide to shipping an MVP in weeks.