How to validate an app idea before you pay for development

Validate an app idea by proving three things before you build: that the problem is real, that people already try to solve it, and that they’d switch to something better. None of that needs code, and it can save you from building the wrong thing.

Step 1: Describe the problem, not the app

Write one sentence: “[Type of person] struggles with [problem] when [situation].” If you can’t, the idea isn’t ready. “An app for restaurants” is a category. “Owners of small restaurants lose money because staff rotas live in WhatsApp” is a problem.

Step 2: Talk to ten real people

Ask how they handle the problem today, what it costs them in time or money, and what they’ve already tried. Listen for existing workarounds — a spreadsheet, paper, a group chat. A workaround means the problem is painful enough to act on.

Step 3: Look at what already exists

Search Google Play for the problem. Competitors are good news: they prove demand. Note what reviews complain about; that is your opening.

Step 4: Test interest cheaply

• A one-page website that explains the app, with a sign-up for early access.
• A clickable mock-up shown to the ten people you spoke to.
• A manual version: do the job by hand for a few customers first.

If nobody cares about a page that describes the app, building the app won’t fix that.

Step 5: Scope a lean first version

Decide the one job version one must do, for one type of user. List what you’re deliberately leaving out. A smaller first version costs less, ships sooner and teaches you more.

Step 6: Plan how you’ll know it worked

Pick a number: sign-ups, jobs completed, hours saved. Decide what result would make you continue.

Where we come in

We run a short discovery call to pressure-test the problem and scope the smallest version worth building, then give a fixed quote against a written scope. Discuss your app idea.