What Is an MVP — and Who Actually Decides If It Works?

The Misconception at the Heart of Most Product Failures

MVP. Minimum Viable Product. Three words that almost every founder can define and almost none can correctly apply.

The popular interpretation goes something like this: build the smallest possible version of your product, release it, and see what happens. And while that is not entirely wrong, it misses the most important question entirely.

Minimum viable for whom?

Most founders — and virtually every enterprise innovation team — answer this question themselves. They sit in a room, debate features, cut the list down, and declare the resulting specification "the MVP." Then they build it, release it, and discover that their definition of minimum viable bears no resemblance to what their customers actually needed to engage with.

The Noodle Investments Framework has a different answer. Minimum viable is defined by the customer. Full stop.

This article is about how you find that definition — and how you move from first users to fundable, production-grade product in a structured sequence.

What Is an MVP? (Phase 0)

In the Rapid Validation System, MVP work begins at Phase 0 — the direct translation of your Traction Test results into a buildable product specification.

Phase 0 is not a product. It is a translation exercise. You take three inputs:

• The sign-up data and persona signals from your Traction Test
• The qualitative answers from your signal questions form
• The behaviours of your earliest users once they gain access

And from these, you derive the smallest possible product surface that solves the acute, validated pain for the specific, validated persona — without adding anything they did not ask for.

The temptation to build more is almost irresistible at Phase 0. Resist it.

Who Decides Product-Market Fit?

Let us be precise about this, because it is the source of enormous confusion.

You do not decide Product-Market Fit. Your investors do not decide it. Your advisors do not decide it.

Your customers decide it — through their behaviour, not their words.

The classic signals of genuine PMF are well-documented but worth naming precisely:

• Retention: Users come back without prompting. They build the product into their workflow.
• The 40% Test: When surveyed, more than 40% of active users say they would be "very disappointed" if the product disappeared. (Sean Ellis's benchmark, still the most reliable proxy.)
• Organic referral: Users tell colleagues without being asked, incentivised, or nudged.
• Resistance to churn: When you try to remove a feature or increase price, users push back with genuine urgency — not polite protest.
• Usage depth: Users explore more of the product over time, not less.

Notice what is absent from this list: positive feedback in demos, high NPS scores from people who haven't actually used the product, and investor enthusiasm. These are lagging indicators of narrative quality, not leading indicators of market fit.

From Traction Test to MVP: The Pivot-to-Build Decision

Your Traction Test ended with one of two outcomes: a pivot signal or a PMF signal. If you reach Phase 0 MVP, you have a PMF signal.

The first task is adaptation — translating the traction data into product decisions. Concretely:

• Persona signals tell you which user to build for first (not all of them — one)
• Pain language from signal questions becomes your onboarding copy, your support documentation, and your in-product prompts
• Urgency signals tell you how fast you need to move and how aggressive you can be with your early access offers

FOMO-driven early access is your primary acquisition mechanism at Phase 0. You have a list of warm, qualified early sign-ups from your Traction Test. These people raised their hands. Now you convert them into users with an offer that rewards their early commitment:

• Personal onboarding calls with the founder
• Exclusive founding member pricing locked for life
• Direct input into the product roadmap
• Founding cohort community access

The goal is not to gift value — it is to create a founding cohort dynamic where early users feel invested in the product's success. When they feel ownership, they become advocates. When they become advocates, you get organic growth before you spend a pound on paid acquisition.

Detecting and Adapting to User Behaviour

This is where most enterprise teams and many first-time founders make their second critical error. They ship Phase 0, watch a dashboard, and measure what they planned to measure.

The Rapid Validation System says: watch what you did not plan to measure.

What features do users navigate to first — and is it the one you expected? Where do they drop off? Which flows do they complete quickly and which ones cause friction? What do they ask in support tickets, and what language do they use? What do they do instead of what you designed?

These unplanned behaviours are your product roadmap. Your job at Phase 0 is not to build what you planned. It is to detect the emergent pattern of what users actually do, and adapt your product surface to reduce friction in those paths.

Tools like session recording, heatmaps, and in-product event tracking are not optional at this stage. You are running an experiment, not a business — and experiments require measurement.

Phase 1: Tweaking What Works

Phase 1 begins when you have enough user behaviour data to identify which parts of your product are generating retention and which are generating drop-off.

The work of Phase 1 is surgical: fix the friction, amplify the delight, and do not add net-new features until the core loop is clean. This is often described as "ironing out the kinks" — but that undersells the strategic discipline required.

Your North Star Metric should be defined before Phase 1 begins. This is the single number that, if it grows week-on-week, tells you the business is working. Not revenue (too early). Not sign-ups (too shallow). The metric should capture value delivery — for example: "number of users who completed a full workflow in their first week."

Every Phase 1 product decision should be evaluated against the North Star. Does this change move the number? If not, deprioritise it.

Phase 2: Adding Production Features

Phase 2 begins when your core loop is stable, retention is demonstrably healthy, and your North Star Metric is trending positively.

Now you can layer in the infrastructure of a real product:

• Payment gateways — converting your founding-member free tier to a paid product; implementing billing, invoicing, and subscription management
• Authentication and security hardening — production-grade identity management, data protection, compliance groundwork (GDPR, SOC 2 if relevant)
• Integrations — connecting to the tools your users already use (the ones that surfaced in your signal questions)
• Admin and reporting — giving buyers (not just users) visibility and control, which is critical for B2B retention
• Support infrastructure — ticketing, knowledge base, onboarding flows

Phase 2 is where you begin looking like a product company, not a prototype.

Phase 3: Production-Grade Product

Phase 3 is the crossing of the threshold from "impressive startup" to "investable business." The product is stable, scalable, and defensible. Your unit economics are real — you know your CAC, your LTV, your payback period, and your gross margin.

This is also where your legal hygiene must be complete: incorporation in the appropriate jurisdiction, IP assignment agreements from all founders and early contributors, co-founder agreements formalised, and cap table clean.

Do not walk into a VC conversation with loose ends here. Investors will find them in due diligence, and they will use them to reprice your round.

Pitch Deck V2: VC-Ready

Pitch Deck V2 tells the full story:

• Problem — validated through discovery, proven by traction
• Solution — built and used by real customers
• Traction — retention data, North Star Metric trends, PMF signals
• Market — TAM/SAM with real conversion data backing the assumptions
• Business model — with live unit economics
• Team — your founding narrative and unfair advantages
• The ask — specific raise amount, use of funds, 18-month milestone roadmap

SAFE Agreements and Closing with Investor FOMO

For early-stage raises, Simple Agreements for Future Equity (SAFEs) are the standard instrument. They are founder-friendly, fast to execute, and avoid the complexity of priced rounds before you have sufficient data to justify a valuation negotiation.

The FOMO close is real — and ethical. When you have genuine PMF signals, real retention, and a clean deck, the best thing you can do is create legitimate urgency: a close date, a round cap, and a clear reason why the investors in the room are getting terms that later investors will not.

Investors understand momentum. A founder who knows exactly where they are going — and has the data to prove they are already moving — is a founder worth backing.

The Rapid Validation System: End-to-End

Two weeks from raw idea to Pitch Deck V0. Three weeks with one pivot. Four with two. Then through MVP phases to VC-ready in weeks, not months.

Enterprises take six to eighteen months on the same journey and rarely learn faster the second time. First-time founders take six to nine months and learn through pain. Seasoned founders take a month.

The difference is not intelligence. It is structure, sequencing, and the discipline to let the customer — not the founder — define what success looks like.