← Archive

India Tech: Reach Is Abundant, Revenue Per User Is Not

by ·July 24, 2026·9 min read·India
इस निबंध का पूरा हिंदी अनुवाद अभी तैयार नहीं है — नीचे का लेख अंग्रेज़ी में है। चित्रों के लेबल और साइट का बाकी हिस्सा हिंदी में दिख रहा है।

A common way to describe India's technology market is by its size: a very large number of people, most of them now online, most of them on mobile.

That description is accurate and not very useful, because it leads to the wrong conclusion — that a product which works elsewhere can be brought here and priced a bit lower.

The more useful description is about shape. The addressable audience is enormous, and average willingness to pay is a small fraction of what a product designed for wealthier markets assumes. Those two facts together do not describe a big version of a familiar market. They describe a different problem, one where the unit economics have to be rebuilt from the ground up rather than discounted into place.

The shape of the market, honestlyPeople reachablevery largeAveragewillingness topaymuch lowerPrice sensitivityvery high
Figure 1.The opportunity is genuine and the unit economics are unforgiving. A product designed for high willingness to pay does not become an India product by discounting it — the whole cost structure has to be different.

Why importing a product rarely works

Products built first for high-income markets tend to optimise for revenue per user: charge more, serve fewer, let margin do the work. Support is expensive per customer because customers are few and valuable. Features assume good connectivity and recent hardware.

Applying that to a market where the realistic price point is a small fraction of the original breaks several things at once.

Support costs stop working. If a service earns very little per user per month, it cannot afford much human support per user. Everything must be self-service or automated, which is a design constraint from the first day rather than a scaling optimisation.

Infrastructure costs matter enormously. At low revenue per user, the cost of serving a request is a meaningful share of what that user generates. Efficiency is not a nice-to-have.

Feature assumptions break. Devices are more varied and often older. Connectivity fluctuates. An application that assumes a stable connection and a recent phone excludes a large share of the people it is trying to reach.

Language is not a translation layer. A large majority of potential users are more comfortable in a language other than English. Treating that as a localisation task added late produces a product that technically supports a language and is not really built for it.

The companies that have succeeded at genuine scale here generally did not adapt a foreign model. They designed around volume and thin margins from the beginning, which is a harder engineering problem and a very different business plan.

A stack with a public layer in themiddleApps and services people useState-built rails: identity,paymentsCheap data and cheap devices
Figure 2.India's distinguishing feature is not the size of its market but that foundational digital infrastructure was built as public utility rather than by private platforms. That changes who captures value.

The part that is genuinely distinctive

The feature that most distinguishes India's technology landscape is not the market size. It is that a layer of foundational digital infrastructure was built as public utility rather than emerging from private platforms.

Digital identity, and especially real-time payments, were built as rails that any provider can plug into. In most large markets, equivalent infrastructure is privately owned, and whoever owns it collects a fee on essentially all activity flowing through it.

This changes the economics in a specific way. Where payments infrastructure is private, a substantial share of transaction value goes to the intermediary. Where it is a shared utility operating at very low cost, that value stays distributed among the businesses using it, and payments become something close to free.

Two consequences follow.

It lowers the barrier for new entrants. A small business can accept digital payments without negotiating with a card network. This has visibly changed commerce at the smallest end of the market, which is where most Indian economic activity actually happens.

It changes what can be aggregated. Aggregation theory predicts that whoever controls the interface to demand captures value. When a critical piece of that interface is a public utility with mandated interoperability, the aggregation opportunity moves elsewhere — to whoever owns the customer relationship, rather than to whoever owns the pipe.

Whether this model exports is a live question. Several countries are studying it. It is worth noting honestly that public infrastructure of this kind brings its own trade-offs — questions about privacy, exclusion of people the system fails to recognise, and the concentration of a different kind of power in state hands. These are real and unresolved, not details.

Which business models survive hereDoes it work at very large scale?Volume plays:ads, payments,commerceHard: needs bothNiche, smallPremium niche:real but limitedDoes it need high per-user revenue?
Figure 3.Models that need meaningful revenue per user struggle unless aimed at a narrow premium segment. Models that monetise volume thinly — payments, advertising, commerce take-rates — fit the market's actual shape.

What actually works commercially

Given the shape of the market, the business models that fit are reasonably predictable.

Thin monetisation of very large volume. Advertising, payments take-rates, commerce commissions, lending. Each user contributes little; the numbers work because there are a great many of them.

Premium niches, honestly sized. There is a genuine segment with high willingness to pay, and businesses serving it can be excellent. The mistake is projecting that segment's size from the total population — it is a market of tens of millions, not hundreds, and plans built on the larger number disappoint.

Serving businesses rather than consumers. Firms will pay for things that reduce cost or increase revenue in ways individuals will not, and the gap between Indian and global pricing narrows considerably for software sold to businesses.

Building for global customers from India. The long-established services model, and increasingly product companies selling worldwide while operating here — which sidesteps the domestic pricing constraint entirely.

The pattern worth noticing across all four: none of them involves charging Indian consumers directly for much. That is not pessimism about the market. It is the arithmetic of a place where reach is abundant and per-user revenue is scarce — the exact inverse of the assumption most product playbooks are built on.

Dr Nadeem Khudboddin Shaikh
Dr Nadeem Khudboddin Shaikh
Ex–Wells Fargo · Ex–Goldman Sachs · Columbia University alumnus