·4 min read
MVP Minimum Feature Set: What to Include
The M in MVP stands for minimum. Most founders include too much. Here is how to cut to the core.
The Core Feature Test
Ask for each feature: Can users get value without this? If yes, cut it.
Feature Categories
| Category | Include in MVP? | Examples |
|---|---|---|
| Core value | Yes | The one thing that solves the problem |
| Enable core | Yes | Auth, basic settings |
| Enhance value | Maybe v1.1 | Notifications, integrations |
| Nice to have | No | Dark mode, advanced settings |
| Enterprise | No | SSO, audit logs, permissions |
Typical MVP Feature Count
- •Simple MVP: 3-5 features
- •Standard MVP: 5-8 features
- •Complex MVP: 8-12 features
- •If you have 20+ features, you are overbuilding
What You Can Skip
- •User profile editing (use defaults)
- •Password change (offer reset only)
- •Multiple user roles (admin only at first)
- •Email preferences (send everything)
- •Export functionality (offer manually)
- •Search (until you have lots of content)
Cutting Exercise
- •List all features you want
- •Cut 50% immediately
- •For remaining, ask: can we validate without this?
- •Cut 50% again
- •What remains is your MVP
If you are not embarrassed by your MVP, you launched too late. Ship the smallest thing that could work.