The Art of Cutting Features
The best MVPs are ruthlessly simple. Here are 37 features you should cut—and build only after you've validated your core value.
Authentication & User Management
1. Social Login
Email/password is enough for validation. Add social later.
2. Two-Factor Authentication
Unless you're handling sensitive data, skip for MVP.
3. Forgot Password Flow
A simple email to support works initially.
4. User Profiles
Basic info only. Skip photos, bios, preferences.
5. Multiple User Roles
Start with one user type. Add roles when you need them.
6. Teams & Organisations
Validate single users first. Teams add massive complexity.
User Interface
7. Dark Mode
Nice to have. Not essential for validation.
8. Custom Themes
Focus on one good design.
9. Drag and Drop
Simple lists work. Drag-and-drop is complex.
10. Animations
Functionality first. Polish later.
11. Mobile App
Start with responsive web. Native apps can wait.
12. Offline Mode
Unless core to value prop, skip it.
Notifications
13. Push Notifications
Email is enough for MVP.
14. In-App Notifications
Dashboard updates are simpler.
15. Notification Preferences
Send what matters. Let users complain if it's too much.
16. SMS Notifications
Email only for MVP.
Search & Discovery
17. Advanced Search Filters
Basic search is fine. Add filters based on usage data.
18. Saved Searches
Let users redo searches manually.
19. Search History
Browser history exists.
20. Recommendations
Manual curation beats algorithms for small user bases.
Content & Communication
21. Rich Text Editing
Plain text or basic markdown works.
22. File Attachments
Links to cloud storage are easier.
23. In-App Chat
External tools like Intercom work great.
24. Comments
Simple feedback forms first.
25. Activity Feeds
Direct updates are clearer than feeds.
Analytics & Reporting
26. Custom Dashboards
One good dashboard is enough.
27. Report Builder
Pre-built reports only.
28. Data Export
Manual export on request initially.
29. Scheduled Reports
Send reports manually or on request.
Integrations
30. Every Integration
Build integrations users ask for, not ones you imagine.
31. Webhooks
Manual triggers work for MVP.
32. API
Unless B2D, you don't need a public API yet.
33. Zapier/Make Integration
Webhooks cover most use cases initially.
Monetisation
34. Multiple Payment Methods
Stripe/Card only for MVP.
35. Multiple Currencies
Start with one currency (probably GBP or USD).
36. Complex Pricing Tiers
Two tiers max: free and paid.
37. Annual Billing
Monthly billing simplifies everything.
How to Decide What to Cut
**The One-Question Test**:
"Will this feature change whether users will pay for the core value?"
If the answer is no, cut it.
**The Usage Test**:
Will 80%+ of users actually use this feature? If not, cut it.
**The Complexity Test**:
Does this add more than 20% to development time? If yes, consider cutting.
What You SHOULD Include
Focus MVP development on:
The one thing that solves the user's problem
Getting users to experience value quickly
Ability to pay you money
Understanding how users behave
Way for users to tell you what's wrong/missing
The Post-MVP Roadmap
After launching your minimal MVP:
**Week 1-2**: Gather feedback, fix bugs
**Week 3-4**: Add the most-requested feature
**Month 2**: Add the second most-requested feature
**Month 3+**: Continue iterating based on data
The Mindset Shift
**Instead of**: "What features should we build?"
**Ask**: "What's the minimum needed to test our hypothesis?"
**Instead of**: "Users might want..."
**Ask**: "Have users asked for this specifically?"
**Instead of**: "Competitors have..."
**Ask**: "Is this why customers choose competitors?"
Every feature you cut reduces cost, speeds launch, and focuses users on what matters. Cut ruthlessly, launch quickly, iterate constantly.