TL;DR — The 12 to cut
Dark mode · Profile pages · Notifications preference centre · Forgot-username flow · Multi-language · Referral program · Loyalty points · In-app chat · Multi-currency · Custom themes · Advanced search · Export to PDF
The 12, with reasoning
1. Dark mode
Adds 1–2 weeks of design + testing. Users at MVP scale don't care. Ship light only. Add dark when 1,000+ active users complain.
2. Profile pages (other than the user's own)
Building public profile pages adds permissions, privacy controls, edit flows, photo uploads. ~10 days of work. Skip until you have a social/marketplace dynamic.
3. Notification preference centre
"Email me about X but not Y" UI takes 5 days. At MVP, send 1 email per critical action. If users complain about volume, add unsubscribe (1 day). The full preference centre is a v3 feature.
4. Forgot-username flow
Use email as username. Done. Save 3 days.
5. Multi-language
i18n architecture, translation pipeline, RTL handling — 2+ weeks. Pick one language for MVP, add others when you have country-specific user demand.
6. Referral program
Codes, attribution, payout logic, fraud prevention — 2 weeks minimum. Build when you have 500+ users actively recommending you and you need to track it.
7. Loyalty points
Earn rules, redemption, expiry, accounting — easily 3 weeks. At MVP, your retention should come from the product, not gamification.
8. In-app chat (between users)
Real-time, moderation, notifications, attachments — 3+ weeks. Unless your core product IS messaging, route conversations through WhatsApp at first. You'll learn what messages actually need before building infra.
9. Multi-currency
Currency display, conversion APIs, tax/VAT logic — 1+ week. Pick INR (or your home currency). Add others when you have international customers asking weekly.
10. Custom themes / branding (white-label)
Theme engine, asset uploads, scoped CSS — 2+ weeks. Never build white-label until 5+ enterprise customers contractually require it.
11. Advanced search (filters, facets, autocomplete)
A search bar that does substring match is fine for <1,000 records. Build advanced search when basic search is the #1 pain point in user feedback.
12. Export to PDF / CSV
Looks simple, isn't. Pagination, formatting, async generation, download flow — 4 days. Ship CSV later when admins ask twice.
~6–10 weeks of dev. That's the difference between an 8-week MVP and a 4-month MVP. Same product utility for the first 500 users. 8-week MVP playbook →
What to do when an investor / co-founder demands one of these
Acknowledge, don't argue. "Yes, that's on the v2 roadmap. For MVP we're prioritising X because it's the value prop. We'll add this after we hit 500 paying users." 90% of the time the request fades when there's a real plan around it.
FAQ
What if my niche genuinely needs one of these (e.g. multi-language for a global edtech)?
Then it's not on the cut list for you. The point is: every feature should justify itself with "users won't pay without it" — not "competitors have it" or "would be nice".
Last reviewed: 20 April 2026.
Want this built for you?
Talk to Kashvi — 30-min call, honest assessment, no pitch deck.