The 'India 2' Trap: A Case Study from Building Paytm Soundbox
Most Indian startups fail because they build for India 1 but price for India 2. A deep case study from my time at Paytm, with the framework for getting this right.
Most Indian startups fail because they build for “India 1” but price for “India 2.”
I saw this firsthand at Paytm, and the lesson fundamentally changed how I think about product-market fit.
India 1 vs. India 2: The Two Markets
India doesn’t have one consumer market. It has (at least) two, and they behave completely differently:
India 1: The Aspirational 100M
India 2: The Emerging 200-300M
Most founders (especially IIT/IIM-educated ones like me) naturally build for India 1. We use iPhones. We think in English. We design for people who look like us. And that’s the trap.
The Paytm Soundbox Story
When I joined Paytm as Deputy General Manager, I worked on the Soundbox product team. Soundbox is a simple device: a speaker that sits on a merchant’s counter and announces each payment received aloud.
No screen. No app required. Just sound.
The User Insight
Kirana store owners in Tier 2-3 cities couldn’t read their phone screens during rush hours. They were making chai, handing over goods, managing queues, all simultaneously. The notification sound on their phone was lost in the shop noise. They needed to hear that the payment went through.
What We Built for India 1 vs. What Worked for India 2
| Feature | India 1 Design | India 2 Reality |
|---|---|---|
| Confirmation | Push notification on phone | Audio announcement on standalone speaker |
| Language | English | Hindi, Tamil, Bengali, Marathi, auto-detected |
| Setup | Download app, login, configure | Plug in and it works. Zero configuration |
| Connectivity | WiFi / 4G | Built-in SIM: works without WiFi |
| Interface | Touchscreen dashboard | No screen, just a green LED for “connected” |
The Results
Adoption
10M+
merchants using Soundbox
Retention
95%+
monthly retention rate
Revenue
Highest
margin hardware product at Paytm
The merchants didn’t care about our UI. They didn’t care about our brand. They cared that they could hear that the payment went through while their hands were busy making chai.
That’s product-market fit you can’t fake.
The Trap: Why Smart Founders Get This Wrong
The pattern is always the same:
Build for India 1
Beautiful app. English-only. Requires an iPhone. Requires a credit card. Requires tech literacy.
Price for India 2
”We need scale, so let’s price at INR 99/month.” But India 2 users can’t use the product. India 1 users won’t pay that little.
Get stuck in the middle
Too expensive for India 2. Too basic for India 1. No product-market fit. Die.
The fix isn’t to “build for both.” It’s to pick one and go deep.
The Decision Framework
| Factor | Build for India 1 | Build for India 2 |
|---|---|---|
| Goal | High ARPU, small base | Low ARPU, massive base |
| Moat | Brand, experience, premium features | Trust, distribution, operational depth |
| GTM | Digital ads, content, influencer | Feet on street, agent networks, word of mouth |
| Design | Minimal, aesthetic, feature-rich | Simple, vernacular, trust signals |
| Risk | Fickle users, high competition | Hard distribution, low initial ARPU |
| Upside | Faster revenue, easier fundraising | Massive scale, deep moat, unicorn potential |
The Lesson
If you want prestige, build for India 1. If you want a unicorn, solve a trust problem for India 2.
The biggest companies in India (Jio, UPI, Soundbox) all succeeded by solving boring, unsexy problems for hundreds of millions of people who were underserved by India 1 solutions.
The question every Indian founder should ask themselves:
Which “India 2” problem are you ignoring because it’s not sexy?
That’s where the unicorns hide.
Enjoyed this? Get more like it.
Weekly on AI product strategy and execution. No fluff.
Comments
Loading comments...