SolisReach
← Journal
MVP & Product5 min read

When a landing page and a waitlist beat a working prototype

Written by the SolisReach team

We build MVPs for a living, and a meaningful share of our best advice to early-stage founders is: don't build one yet. A well-crafted landing page with a genuine call to action, paired with a small amount of paid traffic, tests demand faster and cheaper than a working prototype for a specific but common category of early-stage idea.

When this actually applies

This works best when the core open question is "does anyone want this," not "can we build this" or "will this specific workflow feel good to use." If the technical feasibility is already proven (you're not testing whether the technology works, you're testing whether the market exists), a landing page test answers the actual open question without spending build budget on something that might turn out nobody wants.

What a real test looks like, not a vanity metric

A landing page collecting email signups alone is a weak signal, since an email address costs a visitor nothing. We push clients toward a real commitment: a refundable deposit, a specific "notify me and I'll pay $X when it launches" pledge, or a detailed application form that takes real effort to complete. The friction is the point: it filters out casual interest from genuine intent.

What we actually build for this kind of test

A single, well-designed page: a clear explanation of the product, a specific value proposition, and a genuine commitment mechanism, built in one to two weeks rather than the six to ten weeks a working MVP would take. Paired with a small, targeted ad budget aimed at the actual target audience, not a broad audience, this produces a real read on demand within three to four weeks total.

A real example from a client

A founder came to us wanting a full two-sided marketplace app for a niche service booking category. We built a landing page and ran $2,000 of targeted ads over three weeks instead. The page converted at 1.8 percent to a real deposit, well below what the founder needed to justify the build, and they redirected the idea before spending the $40,000-plus a full MVP would have cost. That's not a failure story, it's exactly what the test was for.

When we push back and recommend building instead

If the core question is about the actual experience of using the product, not just whether people want the outcome it promises, a landing page can't answer that, and a real prototype is the right call even at higher cost. The test has to match the actual open question, and getting that match wrong wastes time either way.

What the ad spend itself teaches you, beyond the conversion number

Running even a small, targeted ad budget against a landing page teaches a founder something a pure customer discovery process can't: which specific messages and audience segments actually generate interest, at what cost, and how that cost compares to what the eventual business model could plausibly support. This is real, usable data for whatever comes next, whether that's building the product or pivoting the idea.

We tag every landing page test with detailed campaign-level tracking specifically so this data survives past the test itself. A founder who redirects the idea can still walk away with a genuinely useful map of which messaging and audience combinations performed best, which is worth carrying into whatever they build next, even if it isn't the same product.

Running even a small, targeted ad budget against a landing page teaches a founder something a pure customer discovery process can't: which specific messages and audience segments actually generate interest, at what cost, and how that cost compares to what the eventual business model could plausibly support.

How long we let a test run before calling it

Three to four weeks is usually enough to get a statistically meaningful read at a modest ad budget, provided the targeting is genuinely narrow rather than spread thin across a broad, undifferentiated audience. Running a test longer than this without a clear signal either way is usually a sign the targeting or messaging needs to change, not that the test simply needs more time to mature.

We set this timeline explicitly with a founder before the test starts, along with what result would count as a clear yes and what would count as a clear no, specifically so the decision at the end isn't made in the moment under whatever emotional pull the founder happens to feel that week.

What a genuinely ambiguous result actually means

Not every test comes back with a clean yes or no. A conversion rate that's neither clearly strong nor clearly weak is its own useful signal, usually meaning the offer or targeting needs refinement before the underlying demand question can be answered cleanly, rather than meaning the whole idea is a wash. We treat an ambiguous result as an invitation to run one more focused iteration, adjusting a single variable, rather than either declaring victory prematurely or abandoning the idea on inconclusive data.

Founders sometimes want us to just tell them whether an ambiguous result means go or no-go, and the honest answer is usually that it means neither yet. A second, sharper test focused on the specific variable most likely to be muddying the first result is almost always worth the extra one to two weeks before making a real capital allocation decision off it.

The discipline to run that second test, rather than forcing a premature conclusion from ambiguous data, is often the difference between a founder who makes a good decision and one who makes a fast one. We'd rather add two weeks to a validation timeline than watch a founder commit real capital based on a result that genuinely didn't say anything conclusive either way.

What happens to the waitlist itself, regardless of outcome

Everyone who signs up during a landing page test deserves a real follow-up email once the decision is made, not silence. If the answer is yes, that list becomes the first cohort of actual users, already warm and already told they'd hear back, which is a genuinely valuable head start on the launch a founder would otherwise have to build from zero. If the answer is no, a short, honest note explaining that the idea didn't validate and thanking people for their interest costs almost nothing and preserves goodwill for whatever that founder builds next.

We've seen founders skip this step because the test failed and the instinct is to move on quietly, but a waitlist that gets ghosted is a small, avoidable reputational cost, particularly for a founder who's likely to launch something else eventually and may want to email some of these same people again. Closing the loop, even briefly, is cheap enough that there's no real reason not to.

Why we insist on a real ad budget instead of organic-only signups

A founder who only shares a landing page with their own network and existing followers gets a signal that's contaminated by pre-existing goodwill, not a read on whether a cold, unfamiliar audience actually wants the product. Even a modest paid budget, a few hundred dollars, gets the page in front of people with no prior relationship to the founder, which is a much closer approximation of what real customer acquisition will eventually look like.

This matters most for founders who have an engaged personal audience already, since it's easy to mistake a warm network's polite support for genuine market demand. We push every client toward at least some cold traffic in the mix specifically so the eventual conversion number reflects something closer to reality, not just how many favors a founder can call in from people who already like them.

Start a project

Want this applied to your site?

We run a Core Web Vitals and SEO audit before quoting any performance marketing engagement, and we're happy to share what we'd find on yours.