MVP vs Full Product: What You Actually Need

Product-market fit (PMF) is the moment when your product solves a problem so well that users can't imagine going back to life without it. It's not a binary switch — it's a spectrum.

Marc Andreessen described it as: "The customers are buying the product just as fast as you can make it." For SaaS, I'd define it more practically: when you have users who pay, stay, and tell others without you asking.

Most MVPs don't have PMF. That's fine — that's what the MVP is for. It's a tool for finding PMF, not a finished product.

The simplest way to measure PMF: ask your users, "How would you feel if you could no longer use this product?"

- Very disappointed: These are your core users. If 40%+ of respondents say this, you have PMF. - Somewhat disappointed: They like you but could live without you. You're close. - Not disappointed: They don't really need you. Back to the drawing board.

Run this survey with at least 30-50 active users. If you're below 40% "very disappointed," don't scale. Don't hire. Don't raise money. Focus entirely on moving that number up.

How do you move it up? Talk to the "very disappointed" users. What do they love? Double down on that. Talk to the "not disappointed" users. What's missing? Either fix it or accept they're not your target market.

User interviews are the most important thing you can do in the MVP stage. But most founders do them wrong.

Don't ask: "Would you use this feature?" (Everyone says yes to be polite) Do ask: "How are you currently solving this problem?" (Reveals actual behavior)

Don't ask: "Do you like the product?" (Useless validation) Do ask: "When was the last time you used the product? What were you trying to do?" (Reveals actual usage)

Don't ask: "What features should we build next?" (Users don't know what they want) Do ask: "What's the most frustrating part of using the product?" (Reveals friction)

Talk to 5 users per week. Not 5 users total — 5 per week. Make it a habit. The insights compound. After a month of weekly user interviews, you'll know exactly what to build and what to cut.

The company that iterates fastest wins. Not the one with the most features. Not the one with the most funding. The one that learns and adapts the quickest.

Ship weekly. If you're not releasing something every week, you're moving too slow. It doesn't have to be a big feature — a bug fix, a UX improvement, or a new onboarding step all count.

Measure immediately. After every release, check the data. Did engagement go up? Did churn go down? Did the "very disappointed" percentage improve?

Kill features that don't work. This is the hardest part. You spent two weeks building a feature and nobody uses it. Remove it. Don't leave dead features in your product — they add complexity, confuse users, and slow down development.

Timebox experiments. "We'll try this approach for two weeks. If it doesn't improve [metric] by [amount], we'll pivot." This prevents you from endlessly tweaking something that isn't working.

Pivoting doesn't mean your idea is bad. It means you've learned enough to aim better.

Signs you should pivot: - After 3 months, fewer than 10% of users are active weekly - Your "very disappointed" score is stuck below 20% - Users keep asking for something fundamentally different from what you've built - Your core assumption about the problem was wrong

Signs you should NOT pivot: - You haven't talked to enough users yet (minimum 30 interviews) - You've only been live for a month - A competitor launched and you panicked - One person told you they didn't like it

How to pivot well: Keep what works. The best pivots preserve your core technology and team while changing the market, the problem, or the distribution strategy. Slack started as a gaming company. Instagram started as a check-in app. They pivoted the product but kept the technology.

The hardest part of the MVP-to-PMF journey is knowing when to persist and when to change direction. There's no formula — but if you're talking to users every week and measuring honestly, you'll have the data to make the right call.

In the MVP stage, most metrics are noise. Focus on these five:

1. Weekly Active Users (WAU): Are people coming back? This is the strongest signal of value. 2. Activation rate: What percentage of signups complete the core action? If it's below 30%, your onboarding is broken. 3. Retention (Day 7, Day 30): Are users sticking around? For SaaS, D30 retention above 20% is decent; above 40% is great. 4. NPS / Sean Ellis score: Qualitative measure of product-market fit. 5. Revenue (if applicable): Are people willing to pay? Even $1 validates that the problem is real.

Don't track MRR, CAC, or LTV yet — your sample size is too small for these to be meaningful. Focus on engagement and retention. If people use your product repeatedly and tell others about it, the revenue will follow.