Business strategy
3 App Demand Tests Before You Spend Weeks Building
Clicks, waitlist signups and prepayments answer different questions. Compare 3 founder examples before choosing a demand test for your app.
An ad gets clicks. A waitlist fills up. A prospective customer pays for something you haven't finished. Each result can help you decide what to build, but each answers a different question.
3 interviews in our library, with Dan Vykhopen, Caleb Dean and Roger Chen, make those differences concrete. If you're planning an app launch, their examples can help you choose a test that addresses your biggest uncertainty before you spend weeks building.
A Click Tests the Pitch
In our Roger Chen analysis, the Lobby founder describes filming a mockup and running it as an ad. His team uses the response to help choose what to market and build.
That is a way to investigate whether people respond to a proposed experience. A clickable prototype can then reveal problems in the flow before those interactions are built into the product.
The limit is what the person has actually done. Clicking an ad leaves price, continued use and payment unresolved. You can learn that a pitch attracts attention while still needing a test of the business behind it.
For your own idea, write down the decision the ad result would change. You might be choosing between 2 use cases or checking whether the core interaction is understandable. Give the test that specific job.
An Email Shows Interest You Can Follow Up
Dan Vykhopen's Massive story shows the risk of reading too much into a list. He describes collecting tens of thousands of email addresses, then finding that very few people even signed up for the launched app.
An email address gives you a way to reach someone. It leaves open whether they remember the offer, still have the problem or want it at the price you eventually charge.
The practical question is what you do with that access. An invitation to try a small version can teach you more. So can a conversation about why someone signed up and what they currently do to solve the problem.
Dan would spend the early validation period looking for payment. That is his conclusion from Massive's experience. A waitlist can still be useful for managing access or finding research participants, provided you keep those purposes clear.
A Payment Tests an Offer
Our Caleb Dean analysis describes a landing page with a Stripe link for Runify before the app existed. Some visitors joined the waitlist, while others paid an early fee.
A buyer accepted a particular offer strongly enough to part with money.
That is useful evidence, with conditions. A small prelaunch payment leaves the future subscription price, product experience and renewal decision untested. A founder still has to deliver the promised value and learn whether people keep using it.
If you try a prelaunch offer, make the unfinished state, delivery expectations and refund terms clear. Choose an offer you can honor while you learn.
Choose the Question Before the Metric
| Your uncertainty | A possible test | What you still need to learn |
|---|---|---|
| Does anyone understand or want this interaction? | Ad showing the proposed experience, followed by a prototype | Price acceptance and continued use |
| Can I find people willing to try it? | Signup and a specific invitation to participate | Whether they show up, use it and pay |
| Will someone buy this particular offer? | Clearly described paid pilot or prelaunch offer | Delivery, repeat use and renewal |
These are proposed uses of the examples. We have not run a comparison establishing one best sequence.
For a paid consumer app, you may already understand the interaction and need to test the price. For a new social experience, seeing people use the prototype together may be the more urgent question. Choose the next piece of evidence that can change your decision.
The Superwall launch-and-sell playlist includes the original interview links and shorter audio analyses. As you listen, ask what the founder knew at each step, what they had actually measured and which question they still had to answer. That's more transferable than the size of the eventual exit or launch.