Every Indian household runs on agents.
The property agent who finds the flat. The CA who files the return. The passport agent who knows which form goes in which window. The RTO agent who turns a four-day ordeal into a Tuesday afternoon. The pandit who picks the muhurat. The neighbour who knows which school form still needs to be submitted in hard copy.
This is not an inefficiency. It is the default UX for navigating complexity in India.
The AI question, then, is not whether Indians will adopt agents. They already have. The question is what rails these agents will run on.
I am using “agent” deliberately. In India, an agent is the person who helps you navigate a messy system. In AI, an agent is software that can reason, use tools, and act. The interesting question is what happens when the second starts absorbing the work of the first.
I was invited to a meetup last month by M2B, who runs a small but sharply curated gathering of people thinking about consumer AI in India. The format is a fireside chat without the fireside — no moderator in the formal sense, no slides, no panel, just an opening hypothesis from the host and four or five invitees who do not arrive polite. What follows is roughly how that evening went. The arguments are theirs; the names are not.
The debate
We had taken over the back room of a coffee place in Indiranagar that was loud enough to argue in and quiet enough to hear each other. Six of us around a table built for four — M2B, four invitees, and me. Filter coffee in glasses. Karthik had his laptop closed. Lakshmi was the only one not on her phone.
M2B had brought the five of us together because she wanted to pressure-test a strong opinion she had been forming. She opened.
“Here is what I keep coming back to,” she said. “ChatGPT can explain a school admission policy to a parent. It cannot tell that parent what the school will actually accept at the counter. That gap is what I want to argue about tonight.”
She took a sip of her coffee.
“My hypothesis is that the next decade of Indian consumption gets reshaped by AI — and India has to own enough of the rails underneath that consumption to keep the value here. Not building everything from scratch. But sovereign infrastructure where it matters — Indian-language models, India-specific personalisation, agents tuned to how Indians actually transact in healthcare, education, finance, welfare. The US and China are not letting their consumption layer ride on someone else’s infrastructure. India should not either. So the question I want to argue out — what does that look like, sector by sector?”
She looked around the table.
“Each of you has a different lens. Tell me where you think the opportunity actually lives.”
Arjun, sitting opposite me, went first. He was already nodding before she finished.
“I am Arjun. I run Saathi — a personalised AI tutor for Indian school kids. CBSE, ICSE, state boards, in Hinglish, with longitudinal memory of how each child learns. So I have skin in this argument.”
He leaned forward.
“I agree with M2B’s framing — sectoral, personalised, India-specific. But I would push harder on daily habit. The consumer AI products that win in India are the ones the user opens every day. Education is a daily habit. So is fitness, journaling, mental-health support. The deepest user understanding in this country will come from products that sit inside a kid’s evening routine or an adult’s morning. Saathi sees a child every day for six years. That is not the same kind of personalisation ChatGPT does.”
He paused.
“ChatGPT’s memory will eventually know your kid likes chess and writes in British English. After six years Saathi knows your kid keeps confusing similar-triangle ratios with congruence, gives up on geometry word problems after thirty seconds, learns better from worked examples than theory, and is exam-anxious in math but not in science. That is a completely different depth of user model. It is what makes hyper-personalisation in M2B’s frame real, and it is what general-purpose chatbots will not bother to build.”
Priya had been watching this with the slightly amused expression of someone whose objection was waiting in line. She set her phone face-down on the table, which she did when she was about to make someone work.
“I am Priya. I closed a consumer-AI fund last quarter and I have spent the last ninety days saying no to founders. My lens is unit economics. I am with Arjun that retention compounds — that part is right. But the cheque-writing question is different. At Indian ARPUs, I need the next user to cost almost nothing to serve. Otherwise this becomes services with a chatbot on top.”
She held up a finger.
“My concern with the sectoral-agents framing is specific. When AI is bolted onto a workflow that still needs per-transaction fulfilment, the unit economics break. Pure-AI products undercut you on cost — ChatGPT will do half of the bureaucracy or insurance or healthcare advice for free. And the high-trust premium does not stay where you think it stays. The family CA is not just standing still while AI commoditises his low-end work. He is bolting ChatGPT to his own desk to do faster first drafts, push more volume through the same junior team, and offer concierge service at the top. The boutique end gets cheaper and faster too. So the squeezed middle gets squeezed harder, not softer. M2B’s agents-for-every-sector idea — beautiful as a thesis — only works in the cells where the AI does most of the work and the human professional cannot absorb AI as a productivity layer to defend their flank. I am not seeing many of those cells in India yet.”
Karthik had been listening with the specific stillness of someone preparing to take apart what had just been said. He didn’t lean in. He just started talking.
“I am Karthik. I run retrieval and tool-use evaluations at a foundation-model lab. I want to be clear up front — I am not the frontier-models-will-eat-everything caricature. Curation matters. I will not pretend otherwise.”
He paused. I thought he was done. He wasn’t.
“My disagreement with M2B is about sovereignty. I do not think the knowledge graph is the moat. The model does not need to know Indian bureaucracy or jyotish permanently. It just needs to pull the right context at the right time — from public APIs, government data feeds, scraped databases, whatever is available. And that layer gets better every quarter. Indian founders building hand-curated knowledge graphs are, in my view, building moats that get commoditised in 18 to 24 months once enough of the workflow knowledge is exposed via APIs. I do not think India needs to build the whole stack. Build the application. Use the global models. That is where the money is.”
Lakshmi had been waiting. She set her glass down and looked across the table at M2B, not at Karthik.
“I am Lakshmi. I work on digital public infrastructure. My lens is different from the other three.”
She took a sip of her coffee.
“M2B is partly right about sovereignty but for the wrong reason. India does not need sovereign AI because of geopolitics. India needs public AI rails for the same reason it needed UPI — because without them, private operators cannot reach the bottom of the pyramid. Public language models, public ASR for Bharat languages, public document standards. Private operators competing on experience on top. The pitch I would put on the table is not India builds its own ChatGPT. It is India builds its own UPI for AI. That is the architecture that worked for payments and will work for AI.”
She looked around the room.
“My worry about every sector M2B named — healthcare, education, finance — is the same. The consumer AI conversation is being captured by Silicon Valley product frames that ignore the citizen at the bottom of the pyramid. Whatever you build for the top 200 million is fine. But it is not the country.”
The table sat with that for a moment. M2B turned to me.
“Nitin. You have been quiet. What is your version?”
I took my time. I had been thinking about how to put it.
“I think you are all partly right and arguing past each other. There is more than one consumer AI here. You are each describing a different one. Can we name them and see if that helps?”
Arjun put his cup down. “Let’s try it.”
“Start with the obvious. ChatGPT, Gemini, Claude. Public knowledge, general-purpose conversation, shallow personalisation that learns you write in British English and prefer numbered lists. Call it Layer A. Indian founders should not chase Layer A — at least not yet. Global players are too far ahead and the building blocks are becoming commodities.”
Karthik picked it up before I could go further. “Agreed on that. And I would add — there is a layer next to A that is also foundation-lab territory but is being built right now, not already built. Generic task completion. Operator-style browser agents, Claude-style computer use, Gemini-style agentic browsing — the model plus a browser plus a few hours of compute, completing generic tasks where the world is clean. Documented APIs. Standard workflows. Predictable interfaces. Book a flight on a documented portal, fill a form, move money through a clean fintech API. That layer belongs to the foundation labs. Same reason — Indian founders should not chase either, at least not right now. Call that Layer C.”
“Skipping B?” I asked.
“On purpose. B is Arjun’s,” said Karthik.
Arjun smiled. “Go on, Nitin. You try it.”
“Layer B is specialised conversation with deep personalisation. Narrow domain, deep on both axes — the domain and the user. Not you write in British English. This Grade 8 kid keeps confusing similar-triangle ratios with congruence, gives up on geometry word problems after thirty seconds, learns better from worked examples than theory. ChatGPT will never bother building that depth on either axis for an Indian curriculum. Saathi is the canonical example,” I concluded.
Arjun nodded. “So Layer B is where I sit. The moat is both the curriculum-deep world-curation and the longitudinal user model. Subscription business, because the user comes back daily and the marginal cost of the N+1th query is near zero. That tracks.”
“So now we go to Layer D?” asked Arjun. “Who wants to try?”
“Layer D is what Karthik just gestured at the boundary of when he described Layer C. Generic task completion is foundation-lab territory because the workflow knowledge is in the API. Domain task completion is not, because the workflow knowledge is fragmented, lived, and operational. Bureaucracy. Ritual. Claims navigation. Admissions paperwork. The moat is the same kind of asset as Layer B — user-curation plus domain-curation — plus an extra layer of operational curation. The agent acts on the user’s behalf, end to end,” said M2B.
I built upon M2B’s thoughts and said, “And one thing I want to land before Karthik comes back to push on it. Inside Layer D, the moat has a half-life, and the half-life varies enormously across bets. Bureaucracy is on a decaying moat — assume Passport Seva eventually exposes a clean API for renewal personalised by applicant type. Student. Senior citizen. NRI. Minor. Maybe a 5-year window before the moat shrinks to operational variance plus fulfilment. But ritual timing — muhurat, panchang, regional commentarial traditions — has a durable moat. No government will ever expose a panchang API. A ritual agent can compound the curation moat for decades. Where the data is public, the algorithm open-source, or the knowledge commonplace, the moat decays. Where the data is private, the algorithm proprietary, or the knowledge fragmented and lived, the moat compounds. Pick your Layer D bet by half-life.”
Priya cut in. “And the pricing follows from the action, in both layers. The user pays per outcome in D, not per month, because the thing they are buying is the thing that got done, not access to the chat. That’s the unit-economics break I was groping at earlier — it’s not about which layer has better margins, it’s that B and D are structurally different businesses. Subscription versus per-outcome. Different cap tables, different exit shapes. They aren’t comparable on the same axis.”
“Yes. Exactly, let’s whiteboard this!” said M2B.

| Layer | What it is | Example | Likely advantage |
|---|---|---|---|
| A (subscription) | General conversation, shallow personalisation | ChatGPT, Gemini, Claude | Global foundation labs |
| B (subscription) | Specialised conversation, deep personalisation | AI tutor for Indian curriculum | Indian domain players |
| C (subscription) | Generic task completion, clean workflows | Personal Assistant for Travel Booking and VISA form-filling via documented APIs. | Global foundation labs (possible disadvantage for those who expose APIs) |
| D (outcome-pricing) | Domain task/workflow completion. | Bureaucracy, ritual, claims navigation | Indian founders blue ocean (moat half-life varies) |
Karthik nodded slowly. “I buy the half-life framing. I still think you are overestimating how long some of these moats last. But at least now the argument is testable — we will know in five years which way the moats actually went.”
I let that sit. Then I went back at him with the question that had been forming all evening.
“Two-way version of your industry-collapse argument. You spent the first half hour asking whether foundation labs will stay out of the consumer agent layer. The mirror question is whether application companies should stay out of foundation models. India is building Sarvam, Krutrim, the AI India Mission. Should Indian application founders be running OSS — DeepSeek, Qwen, Llama — and competing on the application stack alone, or vertically integrating downward? China’s labs are now competitive with US labs through OSS. India’s are not yet.”
Karthik looked uncomfortable for the first time that evening, which is how I knew the question landed.
“OSS for now. Build on Llama or Qwen, fine-tune for Indian languages where needed, win at the application layer. Indian foundation-model bets are a longer-term play and not where the consumer AI money will be made in the next five years,” said Karthik.
“So Indian founders win the application layer if they can. Which is the conversation we have been having.”
“Yes.”
There was a beat. Then I gave the analogy I had been holding back.
“I have a healthcare background. Healthcare has a useful analogy. Epic and Cerner tried to expand from core EHR into specialist workflows, but radiology, oncology, cardiology and pathology systems survived because they were built for the job. Platform gravity is real, but domain workflow depth resists it. Same reason people will not ask Meta AI in WhatsApp to book their travel even though it is technically possible — they will ask MakeMyTrip’s agent, because MakeMyTrip is built for the job.”
Priya picked up her coffee, took a sip, set it down.
“Fine. I will accept the framing. The moat is the same kind of asset in B and D, action plus per-outcome pricing is what makes D a different company, maybe shaped as an aggregator of services or specialized boutique service shop, and the half-life argument makes my unit-economics question per-bet rather than per-layer. I still think Layer B is where most of my portfolio fits — subscription economics are cleaner. But I will stop arguing as if Layer D is a worse version of the same bet. It is a different bet. Multiple different bets, depending on half-life.”
Lakshmi had been silent through the Karthik exchange. Now she set her glass down.
“Bringing this back to the citizen. The Layer D we sketched could be transformative for Indians who currently overpay the neighbourhood agent. But two things worry me. Liability — when the bot misreads a date and a citizen loses a passport renewal. And vernacular access for the citizens who need this most.”
She had a way of saying bringing this back to the citizen that made you sit up. It was not aggression. It was a reminder of who was actually missing from the conversation.
“On liability — the frame exists. The insurance industry runs it today. Confidence thresholds, human review below cutoff, audit trail on every action. Liability sits with the operator, not the model. Apply that frame and the regulatory question becomes manageable,” said M2B.
“And vernacular?”
I jumped back in. This was the part I had thought about the most and was the least comfortable with.
“Honest answer — the first MVP in Layer D works in the four or five languages where Indian-language speech recognition is good enough. My own language, Konkani, is a year-three problem. These Indian language models are the precondition for Indian founders to reach beyond the top 200 million.”
Lakshmi looked at me for a long beat. She does this. It is not approval. It is filing.
“So you are saying the agents compound on top of public rails, funding Indian language models and curated APIs?”
“Yes. Without the public rails, Layer D reaches the urban top 200 million and stops. With them, it has a path beyond.”
“That is the answer I wanted to hear from you.” She actually smiled when she said this. Then: “Fine. I will accept the thesis. We will see whether the public rails get built in time.”
M2B leaned forward.
“Then let’s land this. If the frame is right, what does each of you see as the opportunity in your sector at each layer? I want to know whether this generalises or whether it is sector-specific.”
Karthik went first. “Healthcare. Layer B is winnable on Indian medicine traditions — homeopathy, ayurveda, and the way Indian patients actually describe symptoms — plus longitudinal patient memory. Durable moat, because Indian medical curation stays specialised. Layer D — claims navigation, post-discharge follow-up, the messy reimbursement flow. Per-outcome on the claim recovery.”
Arjun jumped in. “Education. Layer A is homework help, kids already use ChatGPT. Layer B is Saathi. Layer D is admissions, scholarships, board-exam paperwork. Admissions may decay as UGC data improves. Board paperwork probably stays fragmented longer.”
Priya was nodding now. “Finance. Layer C surprised me — fintech APIs are clean enough that foundation labs probably eat it. Layer D is the Indian opportunity I had been mispricing. Insurance claims, unusual tax filings, ESOP paperwork, loan restructuring, NRI compliance. Durable moats, because Indian financial regulation will not simplify on a five-year horizon.”
Lakshmi added, “Welfare. Layer B is a scheme-eligibility advisor that knows the citizen’s situation, language, district, family composition. Layer D is the agent that handles the long tail — escalations, knowing which BDO office requires which affidavit. Interesting twist on half-life — the good outcome in welfare is the public layer maturing. Layer D operators here should want their static moat to decay. Long-term defensibility is operational variance and experience design, not workflow knowledge.”
M2B was writing on a napkin.
“So the matrix: for every sector that matters — healthcare, education, finance, welfare, and the obvious others — Indian founders should be careful with A and C, and focus harder on B and D. Inside D, the half-life decides whether the bet is a ten-year window or a thirty-year business.”
“Yes,” I said. “And the public-rails point applies to Layer D in every sector. Without those, Layer D reaches the urban top 200 million and stops. With them, it reaches the country.”
Lakshmi looked across at M2B. “Which brings us back to the reframe I put on the table early. Your sovereignty argument is a public-infrastructure argument. The sovereign building blocks you want are the rails. The private layer competes on experience, sector by sector, layer by layer.”
M2B set down her pen. She thought about it for a beat.
“You did say it early. I dismissed it as too narrow at the time. But what the room has built tonight is exactly that — India builds its own UPI for AI, with private operators competing in Layers B and D on top. It is not what I came in with. It is a sharper version. I will take it.”
That was the closest thing to a closing point the evening produced. Not consensus on which bet wins, but consensus on the shape of the opportunity: a four-layer matrix of sectors and layers, with Indian founders winning some cells and losing others, moats decaying or compounding depending on whether the public layer eventually catches up, and a public-infrastructure layer underneath that decides how far any of it reaches.
Karthik went back to his laptop. Lakshmi paid the bill, which M2B tried to argue about and lost. We walked out into Indiranagar; the clouds were ready to burst.
The frame
India’s consumer AI conversation collapses different things into one. That collapse produces bad strategic advice — funding Layer A wrappers and ignoring everything else.
The moat in the layers where Indian founders can win is the same kind of asset — curated knowledge the foundation model does not have. User-curation. Domain world-curation. Operational curation. Not different moats. The same moat applied at different depths and in different sectors. Moat half-life is the test. Where the data is public, the algorithm open-source, or the knowledge commonplace, the moat decays as public rails mature. Where the data is private, the algorithm proprietary, or the knowledge fragmented and lived, the moat compounds.
M2B’s question was the right one — what does this look like, sector by sector? The answer the room landed on is a matrix. Picking knowledge moats by half-life and services where unit-economics fit. That is the agent economy — not one giant assistant, but many specific agents that scale the behaviour Indians already pay humans for.
India does not need a ChatGPT moment. It needs the rails underneath it, and the operators on top.
The model is the reasoning layer. The company is the operating layer. The public rails decide how far it reaches.
India does not need to invent a consumer AI behaviour. It needs to scale the one it already has.

















