Most MVPs fail long before launch, because they never launch. The plan grows a feature at a time until it's a six-month project nobody finishes. The fix isn't working harder. It's scoping smaller, on purpose.
1. Pick one first user, not a market
“Small businesses” is a market. “Home bakers selling 10–40 cakes a week on Instagram” is a first user. The narrower the user, the easier every later decision becomes: which features matter, which words to use, where to find them.
2. Find the core loop
The core loop is the one action your user repeats that delivers value. For a trainer app it might be “log a session, see who owes money.” Write it as a single sentence. If you can't, you have two products.
3. List everything, then cut
Write down every feature you've imagined. Then, for each one, ask: does the core loop work without it? If yes, it goes on the cut list. You're not deleting it, you're parking it.
- Keep: anything the loop literally can't run without
- Cut: settings, themes, teams, integrations, analytics, mobile apps
- Fake: anything you can do by hand for the first ten users
4. Choose boring tools
The fastest stack is the one you already know. If you don't code, a form tool, a spreadsheet database and an automation tool can carry a surprising amount of a v1.
5. Plan it day by day
Give each of the seven days one goal. Day 1 is always: something deployed, even if it's ugly. Day 7 is always: real people using it.
If a feature doesn't fit in the seven days, it isn't in the MVP. That's the rule.
Shortcut
ShipMVP runs this exact process on your idea and hands you the scope, cut list, stack and seven-day plan in about a minute. Use it as a first draft, then make it yours.
Want this applied to your idea? Generate your MVP plan — free during beta.