Launch day feels like the finish line. Then the sign-ups slow down, the feature requests pile up, and you are not sure what to build next or whether anyone will stick around.
The first 90 days decide whether your MVP turns into a business. Here is a simple plan for what to measure, how to talk to users, and how to choose the next slice from evidence instead of guesses.
Days 1 to 30: get people through the path
- Onboard your first users personally. Watch them use it on a call if you can.
- Track one core metric. How many people complete the main workflow each week?
- Fix blockers fast. Anything that stops someone finishing the path is the top priority.
- Write down every request, but do not build them yet.
Days 31 to 60: find out if it sticks
- Measure return use. Do people come back the next week without being reminded?
- Talk to users weekly. Ask what they did before your product and what they would miss if it disappeared.
- Look for patterns in requests. One person asking is an opinion. Five people asking is a signal.
Already launched and not sure what to build next? I can help you pick the next slice from real usage.
Book a free scoping call →Days 61 to 90: choose the next slice
- Rank the v2 list by evidence. What blocks paying customers or new sign-ups?
- Pick one next slice, not five features.
- Decide on pricing changes based on how people actually use it.
What not to do
- Rebuild everything because the code is not "scalable" yet
- Add features because one loud user asked
- Stop talking to users once there is a dashboard
Frequently asked questions
What metrics should I track after launching an MVP?
Start with how many users complete the core workflow and how many come back. Revenue and retention matter more than page views.
When should I start building v2?
Once you have a few weeks of real usage and clear patterns in what users need. Building v2 on launch day usually means building the wrong thing.
Should I keep the same builder after the MVP?
If the work went well and the code is clean, continuity saves time. Either way, make sure you own the code so you have the choice.
Plan your next slice with real data
Whether I built your v1 or someone else did, a free call is enough to review what users are doing and scope the next four weeks.
- Free 30-minute call
- Fixed price from $7,500
- Live in four weeks
- You own the code
I take on two to three builds at a time, so start dates fill up.