How to Test Market Demand for Your App Idea: 5 Cheap Experiments

People saying “I’d use it” costs them nothing. Testing demand means asking them to do something.

You don’t need a finished app for this. You need a page, a question, or a payment link, and a decision made before you look at the results.

Talking to people tells you the problem is real. My validation guide and my 12 interview questions cover this part. This guide is the next step: 5 cheap experiments where strangers have to act. If you’d rather work through this with me, here’s where I teach it.

Why test demand before you build?

Building is the expensive way to find out nobody wants it. A demand test costs an afternoon and a small budget.

It answers one question: will people who don’t know you act on this offer? Each experiment below tests a different action, from the weakest signal to the strongest.

Before any experiment, write down what result means build, change or stop. The “decision rule” prompt below helps.

How do you mine competitor reviews for demand?

Read the 1 to 3 star reviews of apps already solving your problem. Unhappy users tell you exactly what’s missing, in their own words.

Look for 3 things:

• Complaints repeated across many reviews
• Workarounds people describe (“I export it to a spreadsheet”)
• Features people ask for

Paste 20 to 50 reviews into the “mine competitor reviews” prompt below and let AI count them. If the same complaint shows up again and again, you’ve found a gap. If your idea already exists, this is how you find your angle.

How do you post about your idea in communities?

Ask a question, don’t pitch. Find where people discuss the problem: subreddits, Facebook groups, Slack communities, forums.

Read each community’s rules first, because moderators set their own limits on self-promotion. Then post the problem as a question: how do you handle this today? Say you’re exploring an idea.

Count what happens. Replies describing the problem in detail, and people asking to try it, are your signal.

How do you set up a landing page and waitlist?

Build one page with one promise and one button. I validate ideas in Lovable, and a rough page takes an afternoon.

The page needs:

1. A headline with the result your user wants
2. 3 short benefits
3. One button: join the waitlist
4. One honest line saying the app is in development

Be clear it’s a test. Don’t pretend an unavailable app is ready to download.

Send people to it from your community posts and your own audience. Measure one number: visitors who leave an email.

How do you run a small ad test?

Pay to send a few hundred strangers to your landing page. Strangers are the point, because your friends sign up to be kind.

An ad test checks your message, not your whole market. A low sign-up rate tells you the headline or the audience is wrong, so test 2 or 3 headlines.

Set your budget before you start. Google’s help on daily budgets doesn’t state a minimum, and daily spend reaches about twice your average daily budget. Meta sets minimums by objective, bid strategy and currency, and Ads Manager tells you when a budget is too low.

How do you pre-sell an app?

Ask people to pay before you build. It’s the strongest signal there is, because money is a real decision.

The simplest route is a Stripe Payment Link: a Stripe-hosted payment page you create without code and share by link, QR code, email or a button on your site. It handles one-time payments and subscriptions.

Using a payment link for a pre-sale is my suggestion, not a Stripe feature. Make the terms clear:

• Say the app isn’t built yet
• Give a delivery date
• Offer a full refund if you don’t deliver, or if they ask

Don’t use a card hold to keep a deposit for weeks. Stripe’s card holds typically last about 7 days.

What counts as a good result?

The result you decided on before you started. Not the one you hoped for after.

Write your rule first, with numbers. Decide how many of your first 200 visitors have to join the waitlist for you to build, how many mean you change the message, and below which number you stop. Pick numbers fitting your audience and budget, and write them down before the test starts.

Then act on it. A test you ignore is worse than no test.

An app only you will use skips all of this. It only has to help you enough to build and keep it.

What comes after a demand test?

If people act, build a small first version fast. Simple, Lovable, Complete is how I’d shape it, and what to put in your first version keeps it small. For the full path from idea to first users, read how to build an app as a non-technical founder.

Ad budgets and Stripe features checked on Google’s, Meta’s and Stripe’s own help pages on 24 October 2026.

Write a one-page landing page for an app I haven't built yet.

The problem: [in my users' words]
Who it's for: [one kind of person]
The one promise: [the result they get]

Give me a headline, 3 short benefits and one button label for joining the waitlist. Add one line saying the app is in development. Plain words, no hype. Under 120 words.

Before I run a demand test, help me decide what result means build, change or stop.

The experiment: [landing page / pre-sale / ad test / community post]
Who sees it: [audience and roughly how many]
Budget and time: [amount, days]

Ask me what I'd need to see to believe people want this. Then write 3 rules: build if, change if, stop if. Use numbers I give you, and tell me if my numbers are too small to mean anything.

Here are reviews of apps solving the problem my app solves. Group them for me.

[paste 20 to 50 reviews, ideally 1 to 3 stars]

Make 3 lists: repeated complaints, workarounds people describe, and features people ask for. Count how often each appears. Quote short phrases from the reviews. Don't add anything not in the reviews.

Draft a post for an online community about a problem I'm exploring.

The problem: [in my words]
The community: [name]
Its rules about self-promotion: [paste them]

Write it as a question to people with the problem, not as an ad. Say I'm exploring an idea. No links unless the rules allow them. Under 150 words.