How to validate an app idea before you build it: a waitlist method that measures real demand

The most expensive way to find out nobody wants your app is to build it first. A few weeks of deliberate validation costs a fraction of even a small MVP budget, and it either saves you that budget or makes you far more confident spending it.

Validation isn't about proving your idea is good. It's about finding the evidence that would change your mind, as cheaply as possible.

What you're actually testing

Every app idea rests on a stack of assumptions. Write yours down in this order, because each one depends on the one before it:

1. The problem exists for a specific group of people.
2. It hurts enough that they've tried to solve it, with time, money or workarounds.
3. They'll try something new, and specifically something like your approach.
4. They'll pay, or the product can earn money another way.
5. You can reach them at a cost that leaves a profit.

Most failed products didn't fail at step 4 or 5. They failed at step 1 or 2, and nobody checked.

Step 1: Problem interviews (week 1)

Talk to 10–15 people who match your target user. Not friends being kind, and not a survey. Conversations.

Ask about the past, not the future. "Would you use an app that…?" produces polite yeses that mean nothing. Instead:

• "Tell me about the last time this happened."
• "What did you do about it?"
• "What did that cost you, in time or money?"
• "What have you tried that didn't work?"
• "If you could wave a wand, what would change?"

You're listening for specifics: a spreadsheet they maintain by hand, a person they pay to do it, a workaround they're embarrassed about. Each of those is evidence that the problem is real and costly. Vague agreement is not.

If after ten conversations nobody describes the problem without prompting, stop or change the target user. That's the cheapest pivot you'll ever make.

Step 2: A landing page with one job (week 2)

Build a single page that states the outcome in the user's words, shows roughly how it works, and asks for one action: join the waitlist.

What makes it a real test:

• Specific promise. "Fill last-minute salon cancellations in five minutes", not "the future of beauty bookings".
• Honest status. Say clearly that it's in development and what joining means: free, invite-only, unsubscribe any time. The early-access page on this site is an example.
• One extra question. Ask which use case or feature matters most, or what they use today. The answers are your segmentation data.
• Confirmation email. A double opt-in removes typos, bots and impulse clicks. Confirmed sign-ups are a much better signal than raw ones.

Measure with plain analytics: visits by source, sign-up rate, confirmation rate. Keep the page fast and simple; a slow page measures your page speed, not demand.

Step 3: Drive the right traffic (weeks 2–4)

A waitlist only means something if the visitors resemble your future customers. Good sources:

• Communities where the problem is discussed, following each one's rules on self-promotion. Answer questions first, link second.
• Your interviewees, and who they'd introduce you to.
• Content that solves part of the problem, such as an article, a checklist or a free tool. It brings exactly the people who care, and it keeps working after launch. The app cost calculator on this site does that job for founders planning apps.
• A small paid test ($50–$200) on the platform your users actually use, to see sign-up cost per channel.

Avoid giveaways, contests and "sign up to win" mechanics. They inflate numbers with people who want the prize, not the product, and in many countries prize promotions come with legal obligations.

Step 4: Read the signals honestly

Numbers worth tracking, in rough order of strength:

Signal	What it suggests
Visitors from the right channels	You can reach the audience
Sign-up rate	The promise resonates
Confirmation rate	Interest survives a second step
Answers to your extra question	Which segment and feature to build first
People replying to your welcome email	Real engagement; book interviews with them
Referrals to friends	The problem is shared and talked about
Pre-orders, deposits or paid pilots	Willingness to pay, the strongest signal of all

Rules of thumb, not laws: if a well-targeted page converts very few visitors, rework the promise before the product. If people sign up but almost nobody confirms or replies, interest is shallow. If a specific segment converts far better than the rest, that's probably your real market.

Step 5: Ask for commitment

The strongest validation is someone giving up something: time, reputation or money.

• Time: a 20-minute call to see a prototype.
• Reputation: inviting colleagues with a referral link.
• Money: a refundable deposit, a discounted annual pre-order, or a paid pilot for a business customer.

If you take money before launch, be scrupulously clear: what they're buying, the expected timing, and a full refund if you don't deliver. Collect it through a proper payment provider with refunds enabled, and keep records.

Staying honest and legal while building hype

Excitement is good; misleading people is not, and it can create real legal exposure under consumer-protection and advertising rules in India, the UK, the EU and the US.

• Don't claim features, dates, user numbers, partnerships or awards that aren't real.
• Don't use countdown timers or "only 5 spots left" unless they're literally true.
• Don't promise rewards for referrals that you can't guarantee; "may move you to an earlier wave" is honest, "guaranteed lifetime free access" is a promise you'll be held to.
• Ask for clear consent before emailing anyone, keep only what you need, and let people delete their data. The DPDP and GDPR checklist covers the details.
• Publish a short privacy policy and terms page before you collect a single email.

Honesty is also good marketing. People who were told the truth about what they signed up for become your most forgiving early users.

From validation to version one

When the signals are strong, you'll know three things you didn't before: who exactly the first users are, which outcome they care about most, and roughly what they'd pay. That's the input to scoping an MVP properly, which in turn is what makes the build fast and the quote predictable.

When the signals are weak, you've saved months and most of a budget, and you probably learned what the real problem is.

A two-week plan you can start Monday

• Days 1–5: ten problem interviews. Write down exact phrases people use.
• Day 6: landing page in their words, with waitlist, one extra question, double opt-in, privacy policy.
• Days 7–12: share where your users already are; one small paid test.
• Days 13–14: review the numbers, email everyone who confirmed, and book five follow-up calls.

If you'd like help turning validated demand into a buildable plan, tell me about it.