On 19 October, a user on r/indianstartups asked the question hanging over India’s AI boom: every IT startup in the country seems to be building AI agents — customer support agents, sales agents, workflow automation agents, coding agents — and raising millions doing it. How sustainable is the wave, the poster asked, when Google, Microsoft, OpenAI, Amazon and Meta are building the same thing with vastly more compute, distribution, data and enterprise relationships?
The thread drew twenty comments. The most upvoted answer was brutal in its brevity: most of these startups’ work, one commenter wrote, “can be done by direct claude or chatgpt more accurately.” Nineteen upvotes — the thread’s own verdict.
But the most interesting comment in the thread was not the dismissal. It was the defence. And it is the defence that should worry the startups most.
The engineer who builds AI agents — for himself
An engineer who builds AI agents for his own company laid out the strongest case for building them that the thread produced. His company, he wrote, is not an AI startup: “We are a tech startup that has to figure out AI to stay competitive.” In the past year his engineers have moved freely between Claude, Codex, Cursor and OpenCode, and in production they run Anthropic, OpenAI, Chinese and self-hosted models, choosing per task what works best and how well.
His reason was control. Platforms lock you in, he said — your Claude memories, for instance, are “basically owned by anthropic” with no way to sync them to a central place for the team. And he pointed to the leverage the platform owners hold: in his account, Cursor and GitHub Copilot have removed or restricted models. Building in-house, he wrote, keeps that control with the company.
It is a serious argument, made by someone doing the work. It is also, on inspection, a case for the opposite of what the startups in the thread are selling.
The reply that turned the argument around
The thread noticed. A reply to that comment took the engineer’s case apart with unusual precision: “The engineer’s comment makes a good case for building internally: control over models, integrations and company context. But that answers ‘why build?’ more than ‘why will customers buy from this startup?’”
The reply then proposed the test the whole debate had been missing. Judge a startup, it said, by a specific customer workflow: what still needs doing after the model produces an answer, who handles the exceptions, and what outcome is the customer paying for? That invites a further question, this article’s own: if the customer’s existing platform added a comparable agent tomorrow, what would they still pay the startup for?
That is the question the gold rush cannot answer with a demo. The engineer’s argument explains why a capable company builds its own agents. It says nothing about why that same company would buy one — and the engineer describes one unusually capable company. Most companies lack the engineers to build and maintain agents, and for them buying remains the attractive option. If the companies that can build are building, the startups’ customers may be the companies that cannot, or will not, build — a possibly narrower market than the fundraising suggests, and one a single company’s account cannot measure.
The money is real. So is the filter.
None of this means the wave is imaginary. Between 12 and 17 October, four Indian AI startups raised $50.6 million in a single record funding week, according to Entrackr — RapidCanvas taking a $29 million Series B for custom enterprise AI and agent applications, alongside Clueso, Parallel Loop and Shamrock AI. Inc42 data puts Indian AI startup funding at $676 million in the first half of 2026, more than four times the $162 million of a year earlier.
But the money is arriving with a filter attached. Google and Accel’s Atoms AI Cohort, which received more than 4,000 applications from Indian AI startups, dismissed about 70% of them as wrappers — AI features layered onto existing software without fundamentally reimagining workflows, in the words of Accel partner Prayank Swaroop. Five startups were selected from the more than 4,000 applicants.
Google’s Darren Mowry, who leads the company’s global startup organisation, put the warning bluntly on the Equity podcast: “If you’re really just counting on the back-end model to do all the work and you’re almost white-labeling that model, the industry doesn’t have a lot of patience for that anymore.” His advice to founders: “Stay out of the aggregator business.” The moats that survive, in his view, are “deep, wide moats that are either horizontally differentiated or something really specific to a vertical market.”
The platforms are coming for the middle
The squeeze is not only a matter of investor taste. The model providers are moving up the stack themselves: OpenAI’s Operator and ChatGPT Agent, Anthropic’s Claude Agent SDK, Microsoft’s autonomous agents inside Dynamics 365, Google’s Gemini Deep Research. The pitch, increasingly, is one platform agent instead of a shelf of point solutions.
And the infrastructure is quietly becoming portable. On 22 October, Anthropic, OpenAI, Hugging Face and Alibaba handed agent standards to the Linux Foundation’s Agentic AI Foundation — Anthropic’s Agent Skills, OpenAI’s Open Responses, Hugging Face’s OpenEnv and Alibaba’s OpenSandbox. The practical effect is that the specialist know-how an agent carries can move between runtimes. The model becomes the replaceable part; the workflow is the asset. That is good news for the engineer building in-house. It is worse news for a startup whose product is a wrapper around one provider’s model.
What survives, then?
The thread itself offers the survivors’ sketch. “Smaller agent companies can last if they own a narrow workflow, proprietary operational context, and distribution,” one commenter wrote — the defensible layer being integrations, evaluation data, compliance and reliable exception handling. Another, an IT sales worker, described the opposite end of the market from the inside: forced to sell generic AI, he wrote, with “the competition is 10,000 people doing same stuff” and no research behind it.
There is also a counter-argument the startups can make, and at least one founder is making it well. Runable, an Indian startup that raised a $21 million Series A in August, bets that the opportunity is not building software but what comes after — finding customers and growing the business. Its co-founder Umesh Kumar told TechCrunch: “In the end, a business doesn’t require Codex or Claude Code or anything. They require real outcomes.” The company says it reached a $2 million annualised revenue run rate within three weeks of launching payments. Outcomes, not agents, are the product.
That is the honest version of the pitch. It also concedes the point: the agent is not the moat. The moat is the outcome, the workflow, the retained customer — the things that survive the morning the model provider ships your feature.
The test
So the thread’s question stands, sharpened. Not whether Indian startups can build agents — plainly they can, and the funding proves the market believes it — but what a customer still pays a startup for once the model can do the demo, the platform can do the agent, and the capable customer can build it themselves.
The engineer’s comment is the thread’s best evidence, and its own reply is the verdict on it: a good case for building, not a case for buying. Until an agent startup can answer that question — what would you still be paid for if the platform added your agent tomorrow — the gold rush has a witness problem. Its most convincing witness just testified for the other side.
