MVP Scope Template: Define Your Product in One Page
A practical one-page template to define your MVP scope. Includes problem statement, user stories, feature prioritization, and success metrics.
Defining the Problem
Start here. Not with features, not with technology—with the problem.
The format that works:
[Specific person] struggles with [specific problem] because [root cause]. This costs them [quantifiable impact].
Good example: "Freelance designers waste 3-5 hours per week chasing invoice payments because clients forget or ignore payment reminders. This creates cash flow stress and awkward client conversations."
Bad example: "Businesses need better productivity tools."
The bad example could describe any software ever made. The good example is narrow enough to build something specific.
Who It's For
One persona. Maybe two. Not more.
| Attribute | Example |
|---|---|
| Role | Freelance UI/UX designer |
| Experience | 2-5 years, established but not agency-scale |
| Current behavior | Sends invoices via email, follows up manually |
| Main frustration | Chasing payments feels awkward |
| Goal | Get paid faster without damaging client relationships |
If you can't describe your user this specifically, you don't know who you're building for.
What to Build (and What Not To)
Use MoSCoW. It's simple and it works.
| Priority | Meaning | Rule |
|---|---|---|
| Must have | MVP doesn't work without it | Build this |
| Should have | Important but not critical | After launch |
| Could have | Nice to have | Future version |
| Won't have | Explicitly out of scope | Don't even discuss it |
For the invoicing example:
| Feature | Priority | Why |
|---|---|---|
| Create and send invoices | Must | Core functionality |
| Automatic payment reminders | Must | Solves the actual problem |
| Accept card payments | Should | Reduces friction but not launch-critical |
| Time tracking | Won't | Different problem |
| Team accounts | Won't | Not building for teams in v1 |
The "won't have" list is as important as the "must have" list. It prevents scope creep.
Success Metrics
Before you build anything, define what success looks like. Otherwise you'll ship and have no idea if it worked.
Validation metrics (first 30 days):
| Metric | Target |
|---|---|
| Signups | 100 people |
| Activation (sent first invoice) | 30% of signups |
| Retention (sent 2nd invoice) | 50% of activated |
Business metrics (first 90 days):
| Metric | Target |
|---|---|
| Monthly revenue | €1,000 MRR |
| Conversion to paid | 5% of signups |
| Customer satisfaction | 8+ NPS |
If you hit your validation metrics, you know the product is useful. If you hit business metrics, you know it's viable.
One-Page Template
Fill this out before writing any code:
PRODUCT NAME: _________________
PROBLEM STATEMENT: [Target user] struggles with [problem] because [root cause]. This costs them [impact].
PRIMARY USER:
- Who: _________________
- Current solution: _________________
- Main frustration: _________________
MUST-HAVE FEATURES (MVP):
WON'T HAVE (explicitly out of scope):
SUCCESS METRICS (30 days):
- Signups: ___
- Activation: ___%
- Retention: ___%
CONSTRAINTS:
- Budget: €___
- Timeline: ___ weeks
Common scoping mistakes
Too many must-haves. If your MVP has more than 5 core features, it's not minimum.
No success metrics. You'll ship something and have no idea if it worked.
Vague problem statement. "Help businesses be more productive" tells you nothing about what to build.
Missing the "won't have" list. Without explicit exclusions, everything is potentially in scope.
Optimistic timelines. Whatever you think it will take, add 50%. You're not accounting for the unexpected.
Need help scoping?
We offer free 30-minute scoping calls. We'll help you sharpen your problem statement, cut features you don't need, and give you a realistic sense of timeline and cost.
No pitch, no pressure—just honest feedback on your idea.
📬 Get Engineering Insights
Practical articles on MVP development, legacy modernization, and building products that scale. Delivered to your inbox.
No spam. Unsubscribe anytime. We respect your privacy.
The Ordinary Company
Product-minded engineers helping startups build and scale. 50+ projects delivered.
Ready to Build Your Project?
Let's discuss how we can help bring your ideas to life. Free consultation, no strings attached.