MVP Testing

Building and launching your minimum viable product to achieve product-market fit.

What Is an MVP?

Not: A crappy, broken product Not: Half the features you planned Not: An excuse for poor quality

Is: The minimum feature set that delivers core value and enables learning

The goal: Test your riskiest assumptions with real customers using a real product as quickly as possible.

The MVP Mindset

Common Misconceptions

❌ "MVP means low quality" ✅ MVP means focused scope with high quality

❌ "We need 50 features to launch" ✅ You need 1 feature done really well

❌ "Let's build everything then test" ✅ Launch in 4-12 weeks, iterate forever

❌ "We'll add that before launch" ✅ Launch without it, see if anyone asks

The Core Principle

Every feature you add:

• Takes time to build
• Increases complexity
• Delays learning
• Might be wrong

Better approach:

• Launch with minimum
• Let customers guide you
• Add based on real usage
• Iterate weekly

Defining Your MVP

The Single Feature Rule

Ask: What is the ONE thing this product must do?

Example: Project Management Tool

• ❌ Tasks + Time tracking + Reporting + Integrations
• ✅ Create and assign tasks. That's it.

Example: Meal Planning App

• ❌ AI recommendations + grocery delivery + nutrition tracking + social
• ✅ Generate a weekly meal plan. Done.

If you can't describe your MVP in one sentence, it's not an MVP.

Feature Prioritization

Framework: MoSCoW

Must Have (Core MVP)

• Solves the main problem
• Without it, no value
• Minimum viable

Should Have (Version 2)

• Important but not critical
• Workarounds exist
• Launch without

Could Have (Backlog)

• Nice to have
• No immediate value
• Add if easy

Won't Have (Delete)

• Not relevant
• Distraction
• Maybe never

The MVP Canvas

Fill this out before writing any code.

Building Your MVP

Timeline Goals

Week 1-2: Planning

• Finalize feature list
• Create simple designs
• Set up infrastructure
• Define metrics

Week 3-8: Building

• Core feature
• Basic UI/UX
• Authentication
• Payment (if applicable)

Week 9-10: Testing

• Internal testing
• Fix critical bugs
• Polish core flow
• Prepare launch

Week 11-12: Launch

• Soft launch to waitlist
• Gather feedback
• Fix issues
• Iterate

Goal: 12 weeks or less from start to first customers

What to Include

Always:

• Core feature (the ONE thing)
• User authentication (if needed)
• Payment processing (if charging)
• Basic error handling
• Minimal UI that works

Probably:

• Email notifications (critical ones only)
• Simple settings
• Help/support contact

Skip for now:

• Mobile apps (build web first)
• Integrations
• Advanced features
• Customization
• Social features
• Analytics dashboards
• Complex workflows

Technical Decisions

Choose boring technology:

• Use what you know
• Battle-tested frameworks
• Managed services (avoid DevOps)
• Minimal dependencies

Don't:

• Learn new framework while building MVP
• Build custom infrastructure
• Over-engineer for scale
• Optimize prematurely

Good tech stacks:

• Rails/Django: Full-featured, fast to build
• Next.js: Modern, good for SaaS
• Laravel: PHP, mature ecosystem
• Firebase + React: Minimal backend

Managed services to use:

• Vercel/Netlify (hosting)
• Supabase/Firebase (database + auth)
• Stripe (payments)
• SendGrid (email)
• Cloudinary (images)

Design Principles

Simple > Beautiful

• Function over form for MVP
• Use component library (Tailwind, Material UI)
• Focus on clarity
• Mobile responsive is must-have

Don't:

• Hire designer yet
• Spend weeks on logo
• Perfect every pixel
• Build complex animations

Do:

• Use design system (e.g., Tailwind)
• Follow platform conventions
• Make it clean and clear
• Test on mobile

Launching Your MVP

The Soft Launch

Don't: Launch to everyone on day 1 Do: Launch to small group first

Week 1: 10 customers

• People from validation
• Invited beta testers
• Hand-picked early adopters

Week 2-4: 50 customers

• If first 10 went well
• Expand slowly
• Fix issues as they arise

Week 5+: Scale

• Open to everyone
• Paid acquisition
• Content marketing

Why gradual:

• Easier to support
• Catches critical bugs
• Lets you iterate
• Builds word of mouth

Launch Channels

For your first 100 customers:

1. Your waitlist (easiest)

• Email everyone who signed up
• Personal outreach
• Explain it's early
• Ask for feedback

2. Direct outreach

• People you interviewed
• LinkedIn connections
• Industry contacts
• Warm introductions

3. Communities

• Reddit (relevant subreddits)
• Indie Hackers
• Hacker News (Show HN)
• Product Hunt
• Twitter
• LinkedIn posts
• Industry Slack/Discord

4. Cold outreach

• If you have clear ICP
• Personalized emails
• LinkedIn messages
• Offer discount for early adopters

The Launch Message

Template:

"We built [product] for [customer type] who struggle with [problem].

After talking to 50+ [customers], we learned [key insight].

So we built [solution description].

Early access is open. [Link]

We're looking for feedback and early customers. First 100 get [benefit/discount].

Who's interested?"

Keys:

• Lead with problem, not features
• Mention validation (builds credibility)
• Clear CTA
• Incentive for early adopters
• Ask for feedback

Measuring Success

North Star Metric

Pick ONE metric that matters most:

For different business types:

• SaaS: Weekly active users
• Marketplace: Transactions completed
• E-commerce: Orders per month
• Content: Engaged readers
• Social: DAU/MAU ratio

Your north star should:

• Reflect real value delivered
• Be measurable
• Connect to revenue
• Be improvable

Essential Metrics

Acquisition:

• Signups per week
• Conversion rate (visitor → signup)
• CAC (customer acquisition cost)
• Traffic sources

Activation:

• % completing onboarding
• Time to "aha moment"
• % using core feature
• Feature adoption rates

Retention:

• Day 1, 7, 30 retention
• Monthly churn rate
• Usage frequency
• Session length

Revenue:

• MRR (monthly recurring revenue)
• ARPU (average revenue per user)
• LTV (lifetime value)
• LTV/CAC ratio

Referral:

• Referral rate
• Viral coefficient
• NPS (net promoter score)

Setting Targets

Week 1-4: Activation

• 50%+ complete onboarding
• 30%+ use core feature daily
• 60%+ have "aha moment"

Week 5-12: Retention

• 40%+ return day 7
• <10% churn monthly
• 3+ sessions per week

Week 13-24: Growth

• 20%+ MoM growth
• LTV/CAC > 3x
• 10%+ come from referrals

Dashboard Setup

Use simple tools:

• Mixpanel (user analytics)
• Amplitude (product analytics)
• Google Analytics (traffic)
• Stripe (revenue)
• Notion (everything else)

Track weekly:

• Signups
• Active users
• Retention
• Revenue
• Churn

Review monthly:

• Cohort analysis
• Channel performance
• Feature usage
• Customer feedback

Gathering Feedback

The Early Customer Interview

After they've used product for 1 week:

Questions:

1. "What were you hoping to accomplish?"
2. "Were you able to do it?"
3. "What was confusing?"
4. "What's missing?"
5. "Would you recommend this? Why/why not?"
6. "What would make this a must-have?"

Listen for:

• Actual usage patterns
• Unexpected use cases
• Friction points
• Feature gaps
• Competitive alternatives

Feedback Channels

In-app:

• Feedback button (make it obvious)
• NPS survey (30 days in)
• Feature request form
• Bug report form

Direct:

• Email responses
• Scheduled check-ins
• Support conversations
• Social media mentions

Passive:

• Usage analytics
• Heatmaps (Hotjar)
• Session recordings
• Error logs

Processing Feedback

After 50 users:

1. Categorize:

• Bugs (fix immediately)
• UX issues (prioritize)
• Feature requests (evaluate)
• Praise (note what's working)

2. Look for patterns:

• 40%+ mention = critical
• 20-40% = important
• <20% = interesting but not urgent

3. Decide:

• Fix (this week)
• Roadmap (next month)
• Backlog (someday)
• Won't do (explain why)

Iteration Strategy

The Weekly Cycle

Monday:

• Review last week's metrics
• Analyze feedback
• Prioritize issues

Tuesday-Thursday:

• Build/fix
• Test internally
• Deploy to production

Friday:

• Customer interviews
• Plan next week
• Document learnings

Goal: Ship improvements weekly

What to Iterate

Always prioritize:

1. Critical bugs
2. Onboarding friction
3. Core feature improvements
4. Retention issues
5. New features

Don't optimize too early:

• Signup flow (unless broken)
• Pricing page
• Performance (unless bad)
• SEO
• Brand/design

The Build Trap

Warning signs:

• Adding features no one asked for
• "We'll launch when it's perfect"
• Building instead of talking to customers
• Ignoring feedback because "we know better"

Reality check questions:

• Did a customer ask for this?
• Will it improve key metrics?
• Can we test without building?
• What will we learn?

Achieving Product-Market Fit

What Is PMF?

Marc Andreessen: "Being in a good market with a product that can satisfy that market"

Sean Ellis test: "How would you feel if you could no longer use this product?"

• 40%+ say "very disappointed" = PMF

Rahul Vohra's PMF score:

• Survey: % who'd be "very disappointed" without product
• Track quarterly
• 40%+ = PMF achieved

Signs You Have PMF

✅ Customers are telling their friends ✅ Organic growth is accelerating ✅ You're struggling to keep up with demand ✅ Retention is strong (>40% monthly) ✅ NPS is 30+ ✅ CAC is profitable ✅ People are asking for features ✅ Competitors notice you

Signs You Don't Have PMF

⚠️ Growth requires constant pushing ⚠️ Churn is high (>10% monthly) ⚠️ Users don't refer others ⚠️ Meh responses ("it's fine") ⚠️ Low engagement ⚠️ Need to explain value constantly ⚠️ Building features no one uses

Getting to PMF

Focus on:

1. Retention first - If they don't stick, nothing else matters
2. Core value - Make one thing amazing
3. Ideal customer - Narrow your focus
4. Feedback loop - Talk to users weekly

Typical timeline:

• 6-12 months for B2C
• 12-24 months for B2B

Don't scale before PMF. Fix the product first.

Common MVP Mistakes

Mistake 1: Building Too Much

❌ 6-month build, perfect product ✅ 2-month MVP, iterate monthly

Cost: Wasted time, might build wrong thing

Mistake 2: Launching Too Late

❌ "Just one more feature..." ✅ "Launch, see what people actually want"

Rule: If you're not embarrassed, you waited too long

Mistake 3: Ignoring Metrics

❌ "Feels like it's going well" ✅ "40% retention, 5% MoM growth"

Set up analytics from day 1

Mistake 4: Feature Creep

❌ Adding features to make everyone happy ✅ Focusing on must-haves for best customers

Say no to most feature requests

Mistake 5: Not Talking to Customers

❌ Building in isolation ✅ Weekly customer conversations

Talk to 5-10 customers every week

Mistake 6: Premature Scaling

❌ Hiring team, buying ads before PMF ✅ Staying lean until retention is solid

Don't scale a broken product

MVP Launch Checklist

Before launch:

• [ ] Core feature works reliably
• [ ] Onboarding is clear
• [ ] Payment processing tested (if applicable)
• [ ] Analytics implemented
• [ ] Feedback mechanisms in place
• [ ] Support email set up
• [ ] Privacy policy + terms
• [ ] Mobile responsive
• [ ] Critical bugs fixed
• [ ] Beta testers approved it

Launch week:

• [ ] Email waitlist
• [ ] Post in communities
• [ ] Personal outreach
• [ ] Monitor closely for issues
• [ ] Respond to all feedback

First month:

• [ ] Talk to 20+ users
• [ ] Track all key metrics
• [ ] Ship improvements weekly
• [ ] Document learnings
• [ ] Iterate based on data

Resources

Analytics:

• Mixpanel (product analytics)
• Amplitude (user analytics)
• PostHog (open source)
• Hotjar (heatmaps)

Feedback:

• Intercom (customer messaging)
• Typeform (surveys)
• Canny (feature requests)

Building:

• Vercel (hosting)
• Supabase (backend)
• Stripe (payments)
• Tailwind (CSS)

Books:

• The Lean Startup by Eric Ries
• Traction by Gabriel Weinberg
• Inspired by Marty Cagan
• The Mom Test by Rob Fitzpatrick

What's Next?

After MVP is launched and getting traction:

1. Improve retention - Make product sticky
2. Find PMF - Achieve 40%+ "very disappointed"
3. Optimize onboarding - Get users to "aha moment"
4. Scale acquisition - Pour fuel on fire
5. Build team - When you can't keep up
6. Raise funding - If growth requires capital

Remember: Most successful companies started with a simple MVP. Focus on solving one problem really well, for one customer type, then expand.

You've validated:

• ✅ Problem exists
• ✅ Solution works
• ✅ People will pay
• ✅ Unit economics work
• ✅ Product delivers value

Now: Build the company.