Introduction
Shipping the MVP is the beginning, not the end. The six months after launch determine whether you graduate from an MVP to a product-market fit or wind up with an expensive shelfware artifact. This guide covers the decisions, metrics, and operational patterns of that critical phase.
Days 1–30: stabilize and observe
The first 30 days post-launch are the stabilization phase. Expect a surge of bugs, edge cases, and feedback that never surfaced in QA. The team's only jobs are: triage issues, fix P0/P1 items fast, talk to every user who will talk to you, and instrument anything you wish you had instrumented before launch.
What not to do in days 1–30: start building new features. Pitch for a Series A. Hire aggressively. All of these are tempting and all are premature until you understand what you shipped.
- Stabilize: triage, fix P0/P1, talk to users, add missing instrumentation
- Do not start new features in days 1–30
- Do not fundraise aggressively until you understand what shipped
Days 30–60: measure and interview
With 30 days of real usage, funnel data starts to mean something. Instrument activation (did the user complete the core job within 7 days?), retention (did they return in week 2? week 4?), and qualitative signal (Sean Ellis 'very disappointed if it went away' survey on the week-2 cohort).
Run 10+ user interviews, split roughly evenly between users who stuck and users who bounced. The difference between the two groups is where your product lives. Write down every theme that emerges.
- Instrument activation, retention, and Sean Ellis 'very disappointed' score
- Run 10+ interviews: stickers vs bouncers
- Write down themes — they are the substrate for prioritization
Day 60: the first decision gate
Around day 60, you have enough signal to make the first real decision. Three credible paths: double down, pivot, or kill.
Double down if: activation ≥40% (freemium) or ≥60% (paid), week-4 retention shows stabilization (not a consistent decay curve), Sean Ellis 'very disappointed' ≥40%, and you have a clear 'why users love it' story from interviews.
Pivot if: activation is below threshold but a subset of users shows strong signal on a slightly different use case, user interviews reveal a stronger adjacent problem, or your core hypothesis was wrong in an informative way.
Kill if: no cohort shows strong signal, interview themes are contradictory, and the team's intuition after 60 days is that there is no durable demand. Fast kill beats slow death. This is a legitimate outcome.
- Double down: strong metrics + clear 'why users love it' story
- Pivot: weak core but strong adjacent signal
- Kill: no cohort signal; fast kill beats slow death
- All three outcomes are legitimate
Months 3–6: sharpen or pivot
If you chose 'double down' at day 60, months 3–6 are about sharpening the product and expanding the user base you have. Focus on activation improvements (first-time experience), retention hooks (habit formation, notifications, progress visualization), and paid conversion if you have a freemium model.
Do not aggressively expand feature scope. Every feature you add changes the product users are evaluating. Instead, improve the core jobs users are already doing. A 30% improvement in activation is worth more than any five new features.
If you chose 'pivot' at day 60, months 3–6 are about validating the new direction with another disciplined 6-week MVP cadence. The second MVP is usually cheaper and faster because much of the infrastructure carries over.
- Double-down: activation, retention, paid conversion — sharpen the core
- Do not expand scope aggressively in months 3–6
- Pivot: run another 6-week MVP on the new direction
Recognizing product-market fit
PMF is a vibe backed by metrics. Metric signals: organic growth (users bring users), 4-week retention above category benchmark, Sean Ellis score ≥40% sustained over multiple cohorts, revenue growth without paid acquisition pressure, support requests shifting from 'I'm confused' to 'I want more.'
The vibe signal is unmistakable when you see it: users are mad when the product is down, they build workflows around it, they refer other users without being asked, and the team is busy prioritizing rather than searching.
- Metrics: organic growth, strong 4-week retention, sustained Sean Ellis ≥40%
- Vibe: users mad when it's down, referrals without asking, team prioritizing not searching
- When both align: it is probably PMF
Scaling decisions after PMF
Post-PMF, the product development rhythm changes. Shorter sprints, more parallel experiments, investment in platform quality and observability, a proper product manager if you did not have one, and the beginning of a second product surface or major feature expansion.
The mistakes here are usually of ambition. Teams that ship too many features too fast post-PMF create complexity that strangles iteration speed. Stay disciplined about hypothesis-first work and pre-registered success criteria, even as the pace increases.
- Post-PMF: shorter sprints, more parallel experiments, platform investment
- Hire a proper PM if you did not have one
- Common failure: ambition-driven feature bloat killing iteration speed
Conclusion
The six months after MVP launch are the actual product-market fit hunt. Days 1–30 are stabilization and listening. Days 30–60 are measurement. Day 60 is a real decision gate: double down, pivot, or kill. Months 3–6 are sharpening or pivot validation. Teams that apply this cadence with discipline reach PMF faster and with less runway burned than teams that treat 'launch' as the finish line.