MVP Scoping Checklist

A short checklist to help founders define what belongs in v1 and what to cut.

The biggest killer of early-stage startups isn't bad code or lack of funding—it's feature creep. Founders often delay launch by months (or years) trying to build a "complete" product, only to realize users don't care about 80% of what they built.

An MVP (Minimum Viable Product) is not a "beta" or a "prototype." It is the smallest version of your product that delivers core value to the user. If it doesn't solve the problem, it's not viable. If it has bells and whistles, it's not minimum.

The Golden Rule of Scoping

"If the app can function without it, cut it."

Your goal is to learn, not to impress. You can always add features later. You can never get back the time you spent building features nobody uses.

The V1 Feature Checklist

Use this checklist to ruthlessly prune your backlog.

1. Authentication & Accounts

Build This (V1)

  • Social Login: Apple (required by iOS) and Google.
  • Delete Account: Required by Apple App Store guidelines.
  • Log Out: Basic session management.

Cut This (Wait for V2)

  • Custom email/password with complex validation rules.
  • Two-Factor Authentication (unless you are a bank).
  • "Forgot Password" flows (Social login solves this).
  • Social graph imports (Sync contacts).

2. Onboarding

Build This (V1)

  • Value Prop Slider: 3 screens explaining what the app does.
  • Permissions Priming: Explain why you need notifications/location before asking.
  • Paywall: Show pricing early (if subscription-based).

Cut This (Wait for V2)

  • Complex personalization quizzes (unless core to the product).
  • "Invite Friends" forced loops.
  • Interactive tutorials with tooltips.

3. Settings & Profile

Build This (V1)

  • Basic Profile: Name and Avatar.
  • Legal Links: Terms of Service & Privacy Policy (Webviews are fine).
  • Support: A simple `mailto:` link to your email.

Cut This (Wait for V2)

  • Dark Mode toggle (just respect system settings).
  • Custom notification sounds.
  • Public profiles (unless it's a social network).
  • Badges, levels, and gamification stats.

4. Monetization

Build This (V1)

  • In-App Purchases: Monthly and Yearly subscriptions.
  • Restore Purchases: Required by Apple.
  • RevenueCat: Use a wrapper to handle the receipt validation logic.

Cut This (Wait for V2)

  • Referral systems with rewards.
  • Gift cards or promo codes UI.
  • Cryptocurrency payments.
  • Web-based billing (Apple forbids linking to it).

The "Wizard of Oz" Strategy

The most powerful secret in MVP development is the "Wizard of Oz" technique: Make it look automated on the front end, but do it manually on the back end.

  • Don't build an Admin Panel. Use your database viewer or a tool like Airtable/Retool to manage users and content.
  • Don't build automated email flows. Send welcome emails manually or use a simple trigger until volume becomes unmanageable.
  • Don't build moderation tools. Handle "Report Content" flags via a support email alert.

When is it ready to launch?

Your MVP is ready when it can complete the "Happy Path" without crashing. The Happy Path is the single most common user journey that delivers value.

If a user can sign up, perform the core action (e.g., book a ride, edit a photo, send a message), and pay you—ship it.

Need help scoping?

Scoping is an art. If you're struggling to cut features, I can help.Book a call and we can define your MVP together in 15 minutes.