1. Home
  2. Blog
  3. Apps

I have an app idea: how to validate it before building

Before paying for development, learn how to test your app idea with customer interviews, a waitlist page, prototypes and presales, without writing code.

Apps

Validating an app idea means proving, on a small budget, that a specific group of people has a frequent problem and is willing to change habits, or pay, to solve it. You can test this before writing a single line of code, using conversations, prototypes and real offers. The point of validation is to find out quickly if the idea does not hold up, while finding out is still cheap.

Separate the problem from the solution

Most app ideas arrive as a solution: "an app that connects X with Y". Before testing the solution, write down the problem behind it in one sentence that could be proven wrong:

Small barbershop owners lose appointments every week because customers book over messaging apps and forget to show up, and today they deal with it by sending reminders by hand.

Notice the parts: a defined audience, a concrete problem, a frequency and the workaround people use today. If you cannot fill in those four points, you do not yet know what you are validating.

Next, list the assumptions that must be true for the business to work. For example: the problem happens often, owners are bothered enough to switch tools, their customers will accept booking through an app, and someone will pay for it. Test the riskiest assumption first, the one that brings everything else down if it turns out to be wrong.

Talk to people the right way

Interviews are the cheapest tool and the most misused. The usual mistake is pitching the idea and asking whether the person would use it. Almost everyone says yes to be polite, and that tells you nothing.

The rule is to ask about what people have already done, not what they would do. Compare:

Weak questionBetter question
Would you use an app that reminds customers of their appointment?When did a customer last miss an appointment? What did you do?
How much would you pay for this?How much do you spend today, in tools or time, dealing with this?
Do you think this is a good idea?What else have you tried? Why did you stop using it?
Would this feature be useful?Can you show me how you manage your schedule today?

The best signals appear when people describe workarounds: spreadsheets, manual reminders, group chats, a staff member assigned to the task. A workaround shows the problem is real and that people already spend effort on it.

Talk to people outside your own circle. Friends and family want to support you and will skew their answers. Keep going until the stories start repeating, and write down exact phrases, because they become ad copy and landing page text later.

Tests that measure behavior

Conversations reveal the problem. To find out whether people want your solution, you need tests where they do something, not just say something. Here are options, from cheapest to most involved:

  1. Waitlist page: a page with a clear value proposition and a button to join the list. Drive visitors with a small ad budget or by sharing it in communities where your audience gathers.
  2. Presale or deposit: offer founder pricing to anyone who pays upfront. Money is the most honest signal there is.
  3. Concierge MVP: deliver by hand what the app would do. In the barbershop example, you would send the reminders yourself for a few weeks to three or four shops.
  4. Wizard of Oz: a simple interface in front and a person doing the work behind it, without users knowing it is not automated.
  5. Clickable prototype: screens built in a design tool and tested with real users while you watch where they get stuck.

Set the success criterion before running the test. An example with hypothetical numbers: "if fewer than 15 out of 500 page visitors leave their contact details, the proposition or the audience is wrong". The right threshold depends on your business. What matters is deciding in advance, so you do not reinterpret the result afterward.

Strong signals and misleading ones

Not every positive reaction counts as validation. Separate what matters from what only looks like it does.

Strong signals:

  • Someone pays, even a small amount, or leaves a deposit.
  • Concierge users keep using it and complain when you are late.
  • People recommend the solution to others without being asked.
  • Prospects ask when they can start and push to get in early.

Misleading signals:

  • Compliments and "what a cool idea".
  • Likes, comments and followers.
  • Positive survey answers about future use.
  • Enthusiasm from friends, family and fellow founders.

If after several attempts you only have signals from the second list, the idea needs to change before it becomes code.

When to move on to an MVP

With strong signals in hand, it is time to think about the MVP: the smallest version of the product that delivers the main outcome to a specific audience. For the barbershop, that might be booking and automatic reminders only, with no loyalty program, no in-app payment and no marketplace of barbers.

Before hiring developers, be clear on:

  • Who the first audience is and how you will reach them.
  • What the core flow is, from first visit to the result.
  • Which metric will tell you whether the MVP worked, such as weekly usage or conversion to paid.
  • What stays out of the first version, in writing.

Mistakes that defeat the purpose

The most common missteps are spending months listening without ever asking for a commitment, testing with an audience that is too broad, and moving the success criterion so the result looks good. Another one is validating the problem and assuming your solution is the right one without testing it.

At Bridgemoon, which invests in startups and also becomes a partner in digital businesses, validation is one of the first things we look at in an app idea. It says more about a product's chances than any feature roadmap.

Frequently asked questions

Should I protect my idea before telling people about it?

Ideas on their own are generally not protected by law; what you can register is a trademark and, later, rights over the software you build. Keeping the idea secret usually hurts more than it helps, because it prevents the conversations that show whether it has value. Register the brand when the name is settled and focus on executing well.

How much does it cost to validate an app idea?

Mostly it costs time: interviews, building a page and running a concierge service by hand. Cash spending tends to be limited to a page builder, a prototyping tool and a small ad budget to bring in visitors. That is a fraction of the cost of building an app nobody uses.

What if validation comes back negative?

A negative result is information that saved you money. Go back to the conversations and look at what failed: the audience, the problem, the proposition or the price. Plenty of good products come from an adjustment after a bad test, and some ideas need to be dropped, which is also a good use of validation.