How Much Evidence of Demand Do You Need Before an MVP?

“How many people do I need before I start building?” is one of the most common questions founders ask, and it’s also the wrong question. There’s no threshold — no magic number of email sign-ups or survey responses — that guarantees an idea is ready for MVP development. What matters is the quality and pattern of the evidence, not the count.

Here’s a more useful way to think about it.

Why Counting Sign-Ups Misleads You

A thousand email addresses collected through a paid ad campaign and a compelling headline tell you almost nothing about whether those people will use, let alone pay for, your product. Sign-ups are cheap to get and cheap to give. Treating a large number as proof of demand is one of the easiest ways to talk yourself into building something nobody actually wants.

What’s far more informative is what happens after the sign-up. Do people respond to a follow-up email? Do they show up to a scheduled call? Do they answer detailed questions about their current workaround? Each additional step someone takes, at some cost to their own time or money, tells you more than the initial sign-up ever could.

A Better Question: Does the Evidence Hold Up Under Pressure?

Instead of asking “how much evidence do I have,” ask “does this evidence survive a harder test?” You can find a detailed set of specific tests in how to test demand for a software product, but the general pattern looks like this:

1. Start with a low-commitment signal — a landing page, a survey, an ad click.
2. Add a medium-commitment step — a scheduled call, a detailed follow-up form, a request to try a manual version of the service.
3. Test a high-commitment action — a deposit, a pre-order, or a request to commit to a pilot period.

If interest holds up as commitment increases, even with a smaller absolute number of people, that’s much stronger evidence than a large pool that evaporates the moment you ask for something real.

Signals That Usually Mean You Have Enough

• A specific, describable audience keeps showing up — not “people interested in productivity,” but “solo bookkeepers managing 15+ small business clients.”
• People take a second or third action without being reminded, showing they remember and still care.
• At least some people are willing to pay something, even a small deposit or early-access fee, before the product exists.
• The problem shows up unprompted in interviews — people describe the pain point before you mention your idea.

None of these require a large sample size. A dozen strongly engaged early users in a well-defined niche is often better evidence than a few hundred passive sign-ups from a broad audience.

Signals That Mean You Don’t Have Enough Yet

• Interest is broad but shallow — lots of “sounds cool” reactions, no repeat engagement.
• Nobody is willing to commit even a small amount of time or money before the product exists.
• The people showing interest don’t share a common, specific problem or context.
• You can only get people to engage by personally pushing them — friends, family, or your own network, rather than people reached cold.

If most of these apply, it’s worth revisiting the problem statement or audience before scoping a build, following the framework in how to prove demand for a startup idea.

When to Stop Validating and Start Building

Validation has diminishing returns. Once you have a specific audience showing repeat, escalating commitment, more interviews or another landing page variant rarely teach you much more. At that point, the fastest way to learn is a focused MVP built around your riskiest remaining assumption — not further validation for its own sake.

Evidence Pattern	Recommended Action
Broad, low-commitment interest only	Keep validating, narrow the audience
Specific audience, one strong commitment signal	Consider a small MVP slice or pilot
Specific audience, multiple escalating commitments	Ready to scope MVP development
No consistent pattern despite multiple honest tests	Reframe the problem before continuing

Evidence Is a Guide, Not a Guarantee

Strong evidence of demand lowers the risk that you’re building something nobody wants — it doesn’t eliminate execution risk. Usability, pricing, onboarding, and timing still determine whether early interest converts into real, lasting usage. Evidence tells you it’s worth trying; it doesn’t build the product for you.

Frequently Asked Questions

How many sign-ups do I need before building an MVP?

There's no universal number. What matters more than volume is whether the sign-ups come from a specific, reachable audience, and whether interest holds up when you ask people to take a further step, like joining a call or making a small commitment.

Is a waitlist enough evidence to start building?

A waitlist alone is a weak signal because it costs almost nothing to join. It becomes stronger evidence when paired with a second, higher-commitment action — a paid deposit, a scheduled call, or consistent engagement with follow-up messages.

What if I can't get strong evidence no matter what I try?

Weak evidence across multiple honest attempts is itself useful information. It usually means the problem isn't painful enough, the audience is too broad, or the current framing doesn't match how people think about the problem — all worth addressing before committing to a build.

Can I have too much evidence before building?

Yes, in the sense of diminishing returns. Once you have a specific, engaged audience showing repeat interest and some willingness to commit, further validation delays learning that can only come from a working product. At that point, the smarter move is a focused MVP, not more interviews.

Does evidence of demand guarantee an MVP will succeed?

No. Demand evidence reduces the risk that you're building something nobody wants, but execution, usability, pricing, and timing still determine whether the MVP converts interest into real usage and revenue.