How to scope an MVP that actually ships

An MVP is not a bad version of your app. It is the smallest product that proves your core idea with real users.

Start with one user and one problem

Write a sentence: “For [user], who [problem], our app [solution].” Every feature should serve it.

Sort features honestly

• Must have: the app is pointless without it
• Should have: valuable but can follow in v1.1
• Could have: nice ideas to validate later
• Won’t have (now): write them down and park them

Buy, don’t build

Use proven services for authentication, payments, analytics and notifications.

Define success first

Decide the metrics (activation, retention, conversions) that tell you whether to continue, pivot or stop.

Plan the second release

Launch is the start of learning. Keep budget for improvements informed by real usage.

Want help scoping? Our Design Sprint is built for exactly this.