Start with one flow, not a feature list
Most first-time founders scope an MVP as a shrunk-down version of their full product vision — a bit of everything. That's the wrong cut. The right cut is one flow: the single thing a user does that proves the idea has value. Everything else is v2.
What belongs in v1 vs v2
A concrete example — a marketplace app idea might get cut like this:
- v1: browse listings, view one listing in detail, contact the seller.
- v2: in-app messaging, saved favorites, reviews, payment processing.
v1 proves whether people want to browse and contact sellers at all — the question that actually matters before you build anything else.
Turning scope into a written spec
Once you know the one flow, write it down as: every screen it touches, every integration it needs (auth, payments, third-party APIs), and an explicit list of what's not included. That last part matters as much as the rest — it's what keeps a quote and a timeline honest. See our MVP timeline breakdown for how scope maps to time, and our cost breakdown for how it maps to price.
Why scoping upfront protects your budget
Every unscoped "quick addition" mid-build is a decision made without seeing the cost or timeline impact. A written spec doesn't stop you from changing your mind — it just makes every change a visible tradeoff instead of invisible scope creep that shows up as a blown budget three weeks later. Once your one flow is scoped, see our UI/UX design process for how we turn that spec into screens before writing any code.