The Indian Enterprise Context
India is not a market to be localised into. It is a context so distinct — in its languages, its regulatory environment, and its enterprise culture — that intelligence infrastructure built for another context will always be insufficient here.
- ◆Twelve languages as a design requirement, not a localisation project
- ◆WhatsApp as enterprise infrastructure
- ◆Data residency and the DPDP Act
- ◆The India opportunity and why it must be built by people who understand it
The language requirement.
An intelligence layer operating in India must speak twelve languages with regional fluency — not translate from English into Hindi, but think in Hindi, in Tamil, in Telugu. The distinction is not linguistic. It is commercial. A sales agent that translates is a worse sales agent than one that converses. Orin speaks. It does not translate.
WhatsApp as the primary channel.
India has more than 500 million WhatsApp users. For the majority of Indian enterprises, WhatsApp is not an optional channel — it is the primary one. Customer communication, vendor coordination, internal operations: WhatsApp is where the work happens. An AI layer that treats WhatsApp as an add-on has misunderstood the Indian enterprise.
Regulation and data residency.
The Digital Personal Data Protection Act represents a shift in the Indian regulatory landscape. Data residency — processing customer data in India, on Indian infrastructure — is becoming a legal requirement, not a preference. Intelligence infrastructure built on foreign cloud providers will face increasing compliance friction. Building in India, for India, is the only durable answer.
The decade ahead.
India is building the largest enterprise transformation the world will see in the next decade. The organisations that will lead it are the ones investing now in intelligence infrastructure built for this specific context — not waiting for global platforms to catch up with it. The opportunity is here. The window to build it properly is now.