From MVP to V2: How to Plan Your Product's Next Stage

Shipping the MVP is the beginning, not the end. What you do in the 60–90 days after launch largely determines whether the product becomes a business or stays a side project.

Need to define your product scope? Use our interactive Feature Prioritizer to filter your absolute must-haves, or apply for a complimentary Free MVP Scope blueprint designed by our Senior Architect.

The most common mistake is treating V2 as a bigger version of V1: add more features, polish the UI, expand scope. This is usually wrong. V2 should be driven by what users actually did with V1.

The Post-MVP Review (Week 1–2 After Launch)

Before planning V2, do a structured review:

Quantitative questions:

• What is your activation rate? (% of signups who completed the core action)
• What is your Day 7 retention?
• Where do users drop off in the onboarding funnel?
• Which features are actually being used?
• What is your NPS?

Qualitative questions:

• What are users asking for in support?
• What did churned users say when you called them?

This data — not your gut — should drive V2 priorities.

The Three Categories of V2 Work

Category 1: Fix the Broken Parts

Things that do not work well enough for users to succeed. Always first.

Common MVP issues: confusing onboarding, core flows with too many steps, performance problems, broken mobile experience.

Fix before adding. A user who cannot successfully use existing features will not care about new ones.

Category 2: Deepen the Core Value

Every product has a core loop. V2 should make that loop faster, more powerful, and more reliable.

Ask: *"What would make the thing we do best, 2x better?"*

Category 3: Add Features Users Are Asking For

Look at support requests and user interviews. Find the feature that appears in 5+ separate conversations. Build that — not features that would impress potential investors.

How to Prioritize: The RICE Framework

Score each potential V2 feature:

• Reach: How many users will this affect in the next 3 months?
• Impact: How significantly will this improve their experience? (1–10)
• Confidence: How confident are we this will work? (%)
• Effort: How many weeks to build?

RICE Score = (Reach × Impact × Confidence) / Effort

Higher score = higher priority. This removes intuition and focuses your team on features with the highest return on engineering time.

The Biggest V2 Trap: The Feature Wish List

After launch, investors, advisors, and users will all tell you what to build. Within 2 weeks you will have a 50-item list.

The trap is treating every item equally. Filter for:

Features that improve retention

Features that drive expansion revenue

Features that reduce churn friction

Revenue-impacting features always beat nice-to-haves.

The 30-Day Hold Rule

Unless something is broken, wait 30 days before committing to major V2 features. Early feedback is noisy. The loudest user in week one is not always the segment that will retain or pay. Tag every request by user type, lifecycle stage, and business impact before it becomes a roadmap item.

Give more weight to users who activated, returned, and paid. Their requests tell you how to deepen value. Requests from people who never reached the core action are usually onboarding or positioning problems, not feature gaps.

When You Have Reached a Meaningful Milestone

• NPS has increased from V1 to V2
• Day 30 retention has improved
• At least 3 users describe the product as "essential"
• You have a repeatable acquisition channel that brings in new users without manual founder effort

These signals indicate you are ready to invest in growth, not just product iteration.

---

Written by Milad Kalhur *Founder & Chief Architect at Needmvp* Milad has designed, architected, and shipped over 40+ web applications for Y Combinator founders and VC-funded startups. Having pioneered the 3-week fixed-price MVP model, he actively consults on software development efficiency, database modeling, and high-performance serverless architecture.