MVP scope checklist
An MVP should prove one core hypothesis — not deliver a mini version of your entire product vision. Scope discipline is what separates a 8-week launch from a 12-month stall.
Include in v1
- One primary user journey end-to-end (signup → core action → outcome)
- Authentication and basic role separation if B2B
- Essential integrations only — defer nice-to-have APIs
- Analytics on the one metric that validates your hypothesis
- Deployment pipeline and staging environment
Defer to v2
- Advanced reporting, admin dashboards, and bulk operations
- Full mobile apps — responsive web often suffices first
- Multi-language, white-label, and complex permission models
- Every edge case your sales team can imagine
Discovery sprint output
Before writing code, produce a written scope: user stories, wireframes, tech stack, timeline, and fixed-price estimate. That document becomes the contract for what "done" means.