Why 80/20 Matters More in India
Indian founders operate under different pressure. VCs expect faster unit economics than Silicon Valley. Runway is tighter. Feature bloat costs money you don't have.
Y Combinator's Michael Seibel emphasizes this: "Early-stage founders confuse breadth with progress." Building 40 mediocre features wastes engineering months. Building 3 exceptional features gets you to PMF in half the time.
Ocado, Freshworks, and Unacademy all started hyper-focused. Freshworks launched email ticketing—one feature. Everything else was removed. That constraint forced clarity. They hit $1M ARR by month 18.
Most Indian SaaS startups follow the opposite path: launch with CRM, invoicing, reporting, analytics, mobile app, integrations. By month 6, you're maintaining code you'll never use again. Your best engineers are debugging features 2 users touch.
How to Identify Your Critical 20%
1. Measure Everything (Starting Now)
Stop guessing. Install analytics today.
For B2B SaaS, track:
- Feature usage frequency (which buttons do users click daily?)
- Time-to-value (how many clicks to first success?)
- Churn correlation (users who don't touch Feature X churn 40% faster)
- NPS drivers (ask: "Which feature matters most?" to detractors vs. promoters)
Segment by cohort. Month 1 users behave differently than month 6. Paid users use different features than free tier.
Wingify (AB testing platform) spent months analyzing usage. Discovered 60% of users never touched their "advanced segmentation" feature. Removed it. Engineering velocity doubled. Maintenance costs dropped 35%.
2. Run the Feature Audit
List every feature shipped. Grade each:
Tier 1 (Critical 20%): Users can't achieve core value without it. Examples: for Slack, message search. For GST compliance software, calculation engine.
Tier 2 (Conversion Boosters): 40% of users need it regularly. Examples: integrations that 3-5 customer segments depend on.
Tier 3 (Zombie Features): <5% monthly active users. <2% of customer questions involve them.
Your Tier 1 list should be 3-7 features maximum.
When Robinhood launched, their core 5 features were: buy stocks, sell stocks, view portfolio, set alerts, view holdings. Everything else came later.
3. Map to Business Outcomes
You need a brutal metric: revenue per engineering hour.
For each Tier 1 feature, calculate:
- Monthly revenue influenced by this feature
- Engineering hours per month to maintain/improve it
- Revenue per hour
Example math:
- Feature A: $50K monthly revenue / 10 hours = $5K per hour
- Feature B: $8K monthly revenue / 15 hours = $533 per hour
Feature A is 9.4x more efficient.
Scott Belsky calls this "outcome clarity" in The Messy Middle. Most founders optimize for activity (shipping features) not outcomes (revenue per resource).
4. Test Ruthlessly Before You Kill
Deprecating features is risky. But it's safer than maintaining them forever.
Before cutting:
1. Announce a sunset date (60 days)
2. Offer migration paths to alternatives
3. Email affected users with reasoning
4. Track requests and complaints
If <5 users complain, the feature was already dead.
If 40+ users complain, maybe Tier 2, not Tier 3.
The Non-Obvious Insight: Your 20% Changes Over Time
This kills founders. You identify your critical 20%, build it ruthlessly, then market conditions shift.
A year ago, Indian D2C brands needed inventory management as Tier 1. Now? Customer communication layers (WhatsApp integration, SMS) are Tier 1. Inventory management moved to Tier 2.
Revise your 80/20 analysis every quarter. Run new cohorts. Track feature usage drift. What mattered in Q1 might be zombie code by Q4.
SaaSBoomi (Indian SaaS newsletter) tracked this across 50 early-stage startups. 12% failed because they couldn't adapt their core feature set. 68% succeeded because they systematically deprecated features others clung to.
Implementation: The 4-Week Sprint
Week 1: Install analytics. Add event tracking to every feature. Define cohorts (user type, signup source, LTV segment).
Week 2: Run the audit. List all features. Assign tiers. Calculate revenue per engineering hour.
Week 3: Map which Tier 1 features correlate with retention, expansion, referrals. Which Tier 3 features are sapping engineering focus?
Week 4: Propose sunsets for Tier 3. Plan migration. Communicate to customers. Track impact on team velocity.
You'll likely find:
- 2-3 features driving 70%+ of outcomes
- 8-12 features no one uses regularly
- 1-2 features creating technical debt
Cut the bottom 30%. Redirect engineers to deepening the top 20%.
The Math That Changed Freshworks
Freshworks' co-founder Girish Mathrubootham has said their real breakthrough came after they cut 18 features in 2011. They had:
- Email ticketing (Core)
- Knowledge base (Tier 2)
- 18 experimental features
They killed the 18. Added 2 customer-facing features instead: better reporting and mobile access. That reallocation—from breadth to depth—took them from $200K to $1.2M ARR in 18 months.
Actionable Takeaway
This week: List your top 10 features by user count. Calculate what % of revenue they drive. If your top 3 drive <70% of revenue, you have feature bloat. Start deprecating the bottom 40%. Measure the impact on engineering velocity. Repeat quarterly.