Indiaās most used business software isnāt chosen - itās tolerated.
Over the past 18 months, I poured lakhs of rupees and time into building automation tools on top of WhatsApp - and failed. That failure opened up something bigger: a look into the tangled web that holds up Indiaās messaging infrastructure.
This is everything good, bad, and quietly dangerous about WhatsApp - and our growing dependence on it. Itās quite a long read.
If youāre a VC, founder, or policymaker exploring how deeply WhatsApp runs through Indiaās digital economy - or how we might build beyond it - Iād love to talk. DM me. Act 1: The Introduction
The Beauty Store Owner
In 2023, I met a cosmetic store owner in Nagpur who had accidentally invented demand forecasting.
He sells beauty products - Korean serums, Indian sunscreens, foreign moisturizers. His challenge wasnāt competition or pricing. It was more existential: his shelf space could hold maybe 200 SKUs, but his customers now wanted access to 2,000.
Ten years ago, this wasnāt a problem. A woman would walk into his store, and heād guide her. āTry this LakmĆ© sunscreen. Let me show you how to apply it.ā He hired young women specifically for this - people who could explain products, who could teach.
But Instagram changed the game. Women no longer came to his store to discover products. They came with screenshots, asking for specific Korean brands theyād seen on reels. If he didnāt have it, they left. And he couldnāt stock everything.
So he invented a system.
He joined a vendor WhatsApp group - wholesalers who posted about new products arriving in the market. When something looked promising, heād post the image to his WhatsApp status. Or heād share it in a customer group heād built over years.
Then heād wait. If even two or three people asked for the price, he knew there was demand. Heād place an order before the product even touched his shelf.
He wasnāt using WhatsApp for communication and marketing alone but turned it into a just-in-time inventory system.
This was Indiaās answer to the Shopify + Stripe stack. Discovery happened on Instagram. Demand validation happened on WhatsApp Status. Payment happened on UPI. Small businesses had discovered that consumer apps could be hacked into business tools. In this WhatsApp owns Indiaās communications layer. And unlike every other tech platform, thereās no competitor even close. Instagram competes with Twitter and YouTube. WhatsApp has... nothing.
This creates both opportunity and danger.
The Infrastructure Realization
WhatsApp isnāt a product Indians use. Itās infrastructure Indians depend on.
Infrastructure is different from products. Products are things you choose. Infrastructure is what you assume exists. You donāt think about electricity until the power goes out. You donāt think about roads until theyāre blocked.
India stopped thinking about WhatsApp years ago. Itās just... there. Assumed. Essential.
This matters because of a simple truth: when something becomes infrastructure, its problems stop being individual frustrations and start being citizen problems.
A business owner spending two hours a day manually managing WhatsApp groups isnāt just inefficient - itās a productivity tax on the entire economy.
WhatsApp work messages and personal messages in groups - itās a design failure that affects work-life balance for millions.
The question isnāt whether India needs better WhatsApp tools. The question is whether WhatsApp, as designed by Meta for Metaās goals, can ever serve as the infrastructure India needs.
To answer that, we need to understand what WhatsApp actually is - and what it isnāt.
Act 2: What WhatsApp Actually Is (And Isnāt)
The Three Variations of WhatsApp:
Most people think WhatsApp is a single app. It isnāt. Meta offers three distinct products with different users:
WhatsApp: The everyday consumer app
WhatsApp Business: A mobile app for small businesses, with profiles, catalogs, chat labels, and auto-replies to manage customer chats.
WhatsApp Business API: Not an app but infrastructure - an API (via Meta Cloud or Business Solution Partners [1]) that connects WhatsApp to CRMs or back-end systems for large-scale messaging.
Bottom line: one phone number can be linked to only one WhatsApp product at a time. If itās registered on the WhatsApp Business API, it canāt also be used on the standard app - and vice versa. Though WhatsApp has rolled out a recent workaround.
Hereās the critical part: these three āWhatsAppsā behave very differently
The consumer app and the WhatsApp Business mobile app expose full phone UIs (groups, stories, calls, broadcast lists, catalogs) that people and small shops use directly on an app.
But the WhatsApp Business API historically only supported a subset of the app features and couldnāt do many of the interactive, UI-driven fetures that make WhatsApp feel like WhatsApp. For example, you cannot create or manage groups, post WhatsApp Status, or manage channels via APIs yet.
Update: Meta has added Groups endpoints and a Calling API to the WhatsApp Business Platform. You can now automate some group actions and initiate voice calls via the API - within tight limits and platform rules. As of Oct 28, 2025 thereās still no official API to post Status Updates like the mobile app.
In short: when small businesses say āwe run everything on WhatsApp,ā they usually mean the consumer or Business mobile apps - with manual groups, broadcasts, and catalogs. True automation and scale require the Business Platform/API, which is powerful but not really designed for typical SME needs.
How WhatsApp Makes Money?
WhatsAppās business model is simple.
Meta charges per message on the WhatsApp Business API, with rates varying by country and message type (Marketing, Utility, Authentication, Service).
Businesses can reply free of charge within 24 hours of a userās message; after that, only approved templates can be sent - and those cost money.
In India, rates are about ā¹0.78 for marketing and ā¹0.11 for utility/authentication messages. Example: 10,000 marketing messages = ā¹7,800; 1,000,000 = ā¹7.8 lakh monthly.
Businesses can use the platform directly via Metaās Cloud API or through Business Solutions Providers like Gupshup, WATI, Interakt, or Twilio. BSPs add their own fees on top of Metaās, so prices include markups and platform charges.
Most WhatsApp SaaS vendors sell both software and message credits - earning largely from those markups. When Meta changes rates, profits shrink or costs rise for customers, creating instability.
The pricing volatility makes WhatsApp a shaky base for predictable business models.
Why Small Businesses Canāt Access Automation?
Hereās a paradox: The businesses that most need WhatsApp automation are the ones least able to use it.
For instance, one of the most common patterns weāve seen is business owners consistently updating their WhatsApp status each morning with details about the dayās fresh vegetables, sharing posts about new stock in their groups, and responding to customer inquiries within minutes. These actions have become almost daily rituals for entrepreneurs running their businesses on WhatsApp. Such simple automations today are not possible on the main WhatsApp mobile apps but only possible in their API version.
SME challenges of using WhatsApp Business APIs
Most small businesses in India use one phone number for everything - personal and work. But the WhatsApp Business API needs a separate, dedicated number that canāt run on the regular or Business app.
Porting the existing number would mean losing existing chats and giving up the mobile app and certain crucial features like groups management and WhatsApp status posting.
Without the WhatsApp Business API even simple automations stay out of reach for SMEs
Even with an additional number, setup is a pain. You need to link it to Meta Business Manager, create and submit message templates - all buried in Metaās dashboards.
Rise of unofficial āmodā apps
Many small businesses turn to unofficial modified versions (mods) of WhatsApp or to access automation and additional features. GBWhatsApp is the most famous unofficial app that can help you run two accounts, auto-reply, tag chats, and send follow-ups, see deleted messages - without using the official API. These tools work but violate WhatsAppās rules, risk malware or data leaks, and can lead to account bans.
Here are some top features of the WhatsApp āmodsā that are helpful for SMEs
Auto Reply: Configure automatic replies per message or contact.
Message Scheduler: Schedule messages to send at set times.
Broadcast to Multiple Groups: Send one message across several groups at once.
Multi Account Support: Use two or more WhatsApp accounts on one device.
Bypass Forward Limit: Forward messages to unlimited chats.
Always Online Mode: Keep your status showing online continuously.
Itās a messy market trading serious security and compliance risks for convenience.
The irony is almost poetic: WhatsApp became essential infrastructure because it was simple and open to everyone. Yet, the moment businesses try to do anything advanced with it, it turns into a maze.
And thereās another catch: most WhatsApp automation tools live on the web, not as mobile apps.
Why? Because if you try to launch a mobile app called āWhatsApp for Businessā or āWhatsApp Automation,ā Meta will hit you with a trademark notice, and Google Play will take it down. So every SaaS company ends up building a web dashboard instead. But the small business owners live on their mobile devices.
The Policy Uncertainty
If the problem were just technical limits, businesses could adapt- learn the rules, find workarounds, move on.
But the real instability comes from something deeper: WhatsApp optimizes for Metaās goals, not yours - and those goals change without warning.
That creates systemic unpredictability that businesses quietly pay for.
Delivery drops: In 2022ā23, marketing messages reached 90ā95% of users. By mid-2025, that fell below 75%. Meta added hidden user-level caps to fight spam - no announcement, no numbers. Businesses only found out after delivery cratered. [2]
Sudden suspensions: Accounts get blocked - sometimes permanently - for vague policy violations. The appeal process is slow, and while it runs, operations stop cold. [3]
Shifting rules: In Oct 2025, WhatsApp quietly banned all āgeneral-purpose AI chatbots.ā The term isnāt defined, leaving even compliant tools exposed. [4]
Even if you master the tech, pricing, and compliance, youāre still building on shifting ground - where Metaās priorities decide your uptime.
Why Meta Wonāt Fix This?
Hereās the uncomfortable truth: these arenāt problems Meta is trying to solve. Theyāre features of the system working as intended.
Meta is an advertising company; ads pay the bills.
Every product in their portfolio - Facebook, Instagram, Messenger, even Oculus - exists to collect data and sell ads. WhatsApp is the outlier. Itās a messaging tool that, in a different world, might have evolved like Telegram, Slack or Microsoft Teams: an open platform where developers build productivity tools, businesses customize workflows, and ecosystems flourish.
But thatās not Metaās DNA.
If WhatsApp opened up like Slack, businesses would build their own solutions. Theyād customize the experience. Theyād create value that Meta couldnāt capture. From Metaās perspective, thatās money left on the table.
So instead, WhatsApp is being slowly transformed into an ads platform. Youāre starting to see it:
Ads in WhatsApp Status (already rolling out)
Paid WhatsApp channels (in beta)
Business messaging in groups
Click to WhatsApp ads
From a pure business perspective, this makes sense. Why would Meta invest engineering resources to solve a hundred-million-dollar problem (Indian MSME productivity) when they could deploy those same resources toward a billion-dollar opportunity (WhatsApp ads)?
To put it bluntly: Meta doesnāt care about your kirana storeās inventory management problem. Not because theyāre evil, but because theyāre a trillion-dollar company optimizing for trillion-dollar opportunities.
WhatsApp will never be the open platform India needs, because Metaās business model requires it to stay closed.
Which raises an obvious question: If WhatsApp canāt serve as the infrastructure India needs, what can?
Act 3: The WeChat Dream
Indiaās WhatsApp problem isnāt unique. China faced something similar a decade ago - and solved it deliberately.
WeChat handles everything WhatsApp does, plus native payments, mini-apps, ride-hailing, food delivery, and government services. The architectural choices Tencent made are precisely what WhatsApp lacks.
Messaging Constraints.
In WeChat, businesses can send users only 4 marketing messages directly per month through service account. Beyond that, marketing messages get quarantined into a separate subscription feed/folder - visible but segregated from personal conversations.
This forces discipline. Every message must justify its existence. The result: businesses target better, users feel less harassed, and the platform maintains trust.
WhatsApp has no such limits. Businesses face tiered messaging caps (starting at 1,000 recipients daily for new accounts) but these scale automatically based on quality scores. The only real constraint is cost - and when marketing messages work, companies pay willingly. The incentive structure rewards volume, not restraint.
Data Portability
When an employee leaves a Chinese company, their WeChat relationships vanish with them- customer conversations, sales context, years of institutional knowledge, gone.
Tencent solved this with WeCom (WeChat Work), a parallel app for professional communication. In WeCom, workplace conversations belong to the company, not the employee. When someone leaves, their account transfers. Customer relationships survive.
Search for a person on WeChat in China, you see two options: their personal WeChat, professional WeCom. Same ecosystem, separate contexts. You message friends on WeChat, coordinate work on WeCom. Both feel familiar, both interoperate, neither bleeds into the other.
In 2022, WeCom has about 180 Million active users and are used by over 10 million businesses in China. [5]
India needs exactly this architecture.
The boutique store owner shouldnāt manage customer orders where his daughter sends memes. The sales team shouldnāt lose client relationships when someone quits. The contractor shouldnāt coordinate labor in the same group planning his wifeās birthday.
The solution exists. WeCom proves separating contexts without fragmenting networks is possible. But WhatsApp wonāt implement it - not because of encryption, but because of infrastructure.
WhatsAppās value to Meta isnāt in reading your messages - theyāre encrypted. Itās in the metadata around them: who you talk to, when, from where, and which businesses you engage with.
Meta has added ads to WhatsAppās Status tab, but the real value lies in metadata and business messaging, not large-scale ad placements. Linking WhatsApp, Facebook, and Instagram through Accounts Center lets Meta build a unified behavioral profile - without touching message content. [6]
Splitting personal and professional WhatsApp use would shatter that identity layer. Meta wouldnāt lose access to messages - it never had them - but it would lose the metadata correlation powering cross-platform personalization.
Keeping all communication in one place creates richer data, tighter business tracking, and a more valuable ecosystem.
Which leaves the real question: if Meta wonāt separate it, who will?
Act 4: The ONDC Model for Messaging
WhatsApp isnāt going anywhere.
Half a billion Indians wonāt switch apps. Businesses wonāt rebuild customer relationships. The network effects are too strong, the switching costs too high. Our goal should be to build optionality in the form of building ONDC-like infra for messaging. A protocol could make the platform used irrelevant.
Instead of building one mega-app to rule all of e-commerce, ONDC built the rails underneath. A seller listing on one ONDC app can be discovered by buyers on completely different apps. Orders, payments, fulfillment - all work across platforms. No gatekeepers. Just open infrastructure.
The same architecture can break WhatsAppās monopoly.
Build for one killer use case:
A messaging protocol doesnāt need 500 million users on day one. It needs 500,000 users who will pay because the protocol solves a problem WhatsApp wonāt.
For example we could start with construction contractors. They need labor coordination, site photos, payment tracking, and material orders - all over messaging. WhatsApp works, but barely. A purpose-built tool would save them hours daily.
Thatās the wedge. Once one vertical proves interoperability works, others follow - logistics, healthcare, education, government services. The network grows without forcing anyone to switch.
The protocol layer should provide the essential stuff:
End-to-end encryption standards
Message delivery guarantees
Identity verification
Cross-app routing APIs
Different apps build specialized experiences on top: One for Gen Z, one for the elderly, one for MSMEs and they should all be able to talk to each other. Same network. Different interfaces.
Just like you can email someone on Gmail from Outlook. The protocol doesnāt care. It just routes messages. Email, the web, and Bluetooth already work on open protocols.
Conclusion
WhatsApp solved Indiaās communication problem. Now India needs to solve WhatsAppās incentive problem.
That doesnāt mean banning WhatsApp or building a clone. It means creating optionality - a messaging layer where WhatsApp is one choice among many, not the only one that works.
This isnāt about nationalism or rejecting foreign technology. Itās about infrastructure resilience. No nation should have its business communication layer entirely controlled by a single foreign corporation with different incentives.
The question isnāt whether to replace WhatsApp.
The question is: What does India need to build so that WhatsAppās limitations stop being Indiaās limitations?
Thatās the conversation worth having.
If you liked this essay, consider sharing with a friend or a colleague that may enjoy it too. (If you share on socials, tag me. Iām on Twitter (X) and LinkedIn)
Shoutout to Gowri N Kishore and Krishna Hegde for reading the preview and helping sharpen the edits.
Annexure:
WhatsAppās New Marketing Message Limits Policy Change: Detailed Guide
WhatsApp Business API Account Disabled? Hereās How to Unban it!
WhatsApp changes its terms to bar general-purpose chatbots from its platform
WeChatās corporate communication tool reached 180 Million active users
You can download the Peopleās Voice report on AI opportunities for Indian SMEs, created by People+AI in collaboration with 1990 Research Labs, below.











Recently we started building some small solutions on Whatsapp through BSP. Also use it as a primary comm channel. Itās abundantly clear the limitations of WhatsApp while even building simple stuff. And the cost of messaging has increased to 0.80 in India. With delivery rates reducing businesses will need to look for another solution like RCS. This almost mimics the path brand Facebook pages took. Organic reach used to be 100% and now itās barely there
This is hands-down one of the best infrastructure analysis pieces I've read on Indian tech. The cosmetic store owner's WhatsApp-as-inventory-system story perfectly captures how consumer apps get hacked into business tools when proper B2B infrastructure doesn't exist. What really stands out is your framing of the incentive mismatch: Meta optimizes for trillion-dollar ad opportunities while Indian MSMEs need hundred-million-dollar productivity solutions. That gap explains everything - the API restrictions, the pricing volatility, the feature stagnation. The WeChat/WeCom comparison is especially powerful because it shows the solution exists and works at scale. The separation of personal and professional contexts isn't a technical challenge, it's a business model choice. Meta won't build it because unified identity metadata across contexts is more valuable than serving SME needs. Your ONDC-for-messaging proposal is the right architectural direction. Interoperability solves the 'network effects as moat' problem without requiring mass migration. Start with one vertical (construction contractors is a great wedge), prove the protocol works, let ecosystem diversity emerge. One addition I'd suggest: the protocol layer should include reputation/trust primitives from day one. WhatsApp's end-to-end encryption is great for privacy but terrible for platform-level spam control. A federated messaging protocol needs portable reputation that follows business identities across apps - otherwise every new entrant rebuilds spam filters from scratch and user experience suffers. The question isn't whether this gets built, but who builds it and whether it stays open. Government-backed infrastructure has different risks than VC-backed platforms. Both can succumb to capture. The governance model matters as much as the tehcnical architecture. Would love to see a follow-up on that.