Customer Interviews vs MVP: How Much to Validate First?

Every founder eventually faces a version of the same question: how much customer interview validation is actually enough before it makes more sense to just start building? Too little validation risks building on an unproven assumption; too much risks using research as a comfortable way to avoid the harder, riskier step of actually committing to development. Here’s how to find the right balance.

Why This Balance Is Hard to Get Right

Interviews are genuinely useful — they’re cheap, fast, and can prevent expensive mistakes. But they also have a natural point of diminishing returns, after which additional interviews mostly confirm existing findings rather than reveal meaningfully new information. Recognizing that point, and resisting the pull to keep going past it, is harder than it sounds, especially because building carries real risk and uncertainty that continued interviewing can feel like it’s postponing.

Signals You’ve Validated Enough

• A specific problem repeats consistently across a meaningful share of your interviews.
• You understand the current workaround people use and its real cost.
• You can describe your target audience specifically, not in vague or broad terms.
• Recent interviews mostly confirm, rather than reshape, your understanding of the problem.

If most of these are true, continuing to interview is likely to produce limited additional value compared to moving toward a focused MVP, following the broader framework in how many customer interviews before building an MVP.

Signals You Haven’t Validated Enough Yet

• Interview results are inconsistent, without a clear repeating pattern.
• You can’t yet describe the target audience specifically.
• You don’t understand the current workaround or why existing options fall short.
• Each new interview still reveals genuinely new information.

If these describe your situation, continuing discovery — potentially with a narrower or adjusted audience — is likely still worth the time before committing to a build.

Matching Validation Depth to Risk

Not every idea warrants the same amount of upfront validation. A simple, cheap-to-build tool aimed at a well-understood audience might reasonably move to a small MVP test after a handful of interviews. A complex, expensive, technically ambitious product aimed at an unfamiliar audience warrants more thorough validation before committing significant development resources, since the cost of being wrong is much higher.

Product Characteristics	Recommended Validation Depth
Simple, cheap to build, familiar audience	Lighter validation, move to MVP sooner
Complex, expensive, unfamiliar audience	Deeper validation before committing to build
High technical risk (unproven AI, hardware)	Validation plus a proof of concept for technical risk
Existing customer base already requesting it	Lighter validation, existing relationship reduces risk

Avoiding the Trap of Endless Validation

A subtler risk than under-validating is using continued research as a way to avoid the discomfort of a real commitment. If you notice yourself scheduling more interviews despite recent conversations mostly repeating earlier findings, it’s worth honestly asking whether more research is genuinely needed, or whether it has become a comfortable substitute for the harder step of building — a caution echoed in when should you stop customer discovery and start building the MVP.

Building Is Also a Form of Validation

Once discovery interviews reveal a clear pattern, remember that development itself becomes the next validation step — a real MVP, used by real people, will teach you things no amount of pre-launch interviewing could. Treating the MVP as a continuation of validation, rather than the end of it, helps reduce the pressure to get everything perfectly confirmed before writing any code.

Finding Your Own Balance

There’s no universal formula, but the general principle holds across most situations: validate until a clear, repeated pattern emerges from a well-defined audience, then move to building — treating the MVP itself as the next, more expensive but more informative round of validation.

Frequently Asked Questions

Can I validate too much before starting to build?

Yes. Once interviews consistently confirm a clear, repeated pattern, additional interviews tend to produce diminishing returns, and the more valuable next step becomes building something real and learning from actual usage.

How do I know if I'm validating enough, or just avoiding building?

If recent interviews are mostly confirming what you already know rather than revealing new information, and you're still finding reasons to delay, that's often a sign discovery has done its job and further delay is about discomfort, not genuine uncertainty.

Does the amount of validation needed depend on the type of product?

Yes. Higher-risk, more expensive, or more technically complex products generally warrant more upfront validation, while simpler, cheaper-to-build ideas can reasonably move to a small MVP test sooner.

What's a reasonable amount of interview validation for most software ideas?

For most new ideas, ten to fifteen consistent interviews with a specific target audience, revealing a clear repeated pattern, is a reasonable amount before moving toward MVP scoping — though this varies with the specifics of the idea.

Should validation stop completely once development starts?

Not necessarily. Many founders continue lighter discovery conversations even after development begins, using real usage data from the early MVP to complement and refine what earlier interviews suggested.