India Has Learned to Make. Now It Wants to Build.
A series of moves by Microsoft, Starbucks, Nothing and Autodesk suggests that India’s technology story is entering a more consequential phase, one in which engineering, intellectual property and global product ownership could matter more than assembly alone.
There was a time when India’s technology story was mostly about people.
Thousands of engineers writing code for companies thousands of miles away. Global technology companies setting up delivery centres. Business processes moving to Bengaluru, Hyderabad and Pune. Software exports becoming one of the country’s most important sources of global revenue.
Then came the factories.
“Make in India” gave the country’s technology and manufacturing ambitions a physical dimension. The pitch was to bring production home, deepen supply chains and make India a larger part of the global manufacturing map.
But the next chapter is asking a more difficult question.
What happens when India stops being merely the place where things are made and becomes the place where they are engineered, designed and owned?
There are few announcements that declare this shift outright.
Instead, the evidence is appearing in fragments.
A new AI cloud region in Hyderabad.
A global capability centre in Chennai.
A consumer technology company talking about “Engineer in India”.
An industrial software company looking at India as part of its global innovation engine.
Taken individually, these are corporate developments. Taken together, they suggest that India’s role in the global technology economy is changing again.
This time, the change is less about where work is done and more about where capability sits.
Microsoft’s latest move is a useful place to begin.
The company has launched its fourth Indian cloud region in Hyderabad, designed for AI workloads from the outset. Microsoft says 92% of Indian knowledge workers are already using AI and 40% of Indian enterprises are scaling AI deployments. The Economic Times reported on Microsoft’s Hyderabad AI cloud region.
There is an obvious interpretation. Demand for AI infrastructure in India is growing.
But there is a more interesting one.
AI may have arrived in India as software. Its next phase is going to be intensely physical.
Every AI interaction ultimately depends on machines somewhere. Compute has to be housed somewhere. Data has to travel somewhere. Electricity has to come from somewhere. Cooling has to happen somewhere.
Microsoft says its new Hyderabad region will use effectively zero water for cooling. The Economic Times reported on Microsoft’s approach to water use at the new region.
The AI economy is often discussed in terms of models and agents. Its foundations are increasingly about land, power, water, connectivity and infrastructure.
India’s AI opportunity is becoming an infrastructure opportunity.
The same distinction appears in India’s rapidly changing GCC landscape.
Starbucks has signed an agreement with Tamil Nadu to establish its first India global capability centre in Chennai, with around 800 high-value technology jobs expected initially.
Another GCC announcement might once have been little more than a jobs story.
It is harder to see it that way now.
India is expected to add 125 to 130 new GCCs in 2026, according to the figures in the source brief, with Hyderabad currently leading Bengaluru in new centres.
The interesting competition is no longer simply about which city can accommodate another thousand employees.
It is about what those employees will be allowed to own.
A finance operation is one thing. A global engineering team is another. An R&D centre is different again. A product organisation responsible for technology used across multiple markets represents an entirely different level of corporate responsibility.
This is why the evolution of India’s GCC sector matters.
The country is moving, slowly but visibly, from outsourcing work to owning work.
That distinction could eventually matter more than the number of centres themselves.
Perhaps the most revealing phrase in the entire story comes from Nothing CEO Carl Pei.
India, he has argued, needs to move beyond “Make in India” towards “Engineer in India.” Nothing is also building substantial product and R&D capability in the country.
The significance of the sentence lies in the verb.
Make tells you where something happens.
Engineer tells you where knowledge resides.
And knowledge is where the economics begin to change.
A product assembled in India creates manufacturing capability. A product engineered in India creates engineering capability. A product designed, developed and owned in India creates intellectual property.
These are different forms of value.
India has spent decades building one of the world’s largest pools of technical talent. It has built global IT services companies and become central to the operations of hundreds of multinational corporations.
The next question is whether more of that talent gets to decide what gets built, rather than simply how efficiently somebody else’s technology gets delivered.
That is a harder transition.
It requires stronger product organisations, deeper R&D, greater tolerance for experimentation and, ultimately, ownership.
But there are signs that the transition has begun.
The shift is also happening beyond software.
Autodesk CEO Andrew Anagnost has described India as an important part of the company’s global innovation engine, pointing to the country’s engineering talent and the scale of its infrastructure, manufacturing and industrial development.
That combination matters.
India is building highways, factories, cities, energy infrastructure and industrial capacity while AI, simulation and digital twin technologies are becoming more sophisticated.
For technology companies, this creates a large physical environment in which digital technologies can be tested against real-world problems.
A digital twin of a factory is useful.
A digital twin deployed while the factory is being designed and built is more significant.
AI applied to an existing industrial process is useful.
AI embedded into the engineering of a new industrial system has a different role.
This is where India’s physical expansion and its technology capabilities begin to intersect.
The country could become an important environment for industrial AI because it is simultaneously building the physical systems on which these technologies operate.
But there is a contradiction in this story.
India wants more engineers.
AI is increasingly capable of doing work engineers traditionally used to learn their craft.
Zoho founder Sridhar Vembu has warned about excessive dependence on AI coding tools, arguing that engineers risk losing their understanding of the systems they build when specifications, code, tests and documentation are increasingly handed over to AI.
The concern goes beyond coding.
Technology companies have always depended on apprenticeship.
People become experts by doing difficult work. They debug systems. They read documentation. They make mistakes. They work beside experienced engineers. They gradually develop judgement.
AI changes how much of this work gets done by people.
Companies therefore need to think about two goals at the same time.
Increase productivity.
Build expertise.
The second goal matters for India because engineering capability is becoming a larger part of the country’s economic proposition.
Tata Steel CEO T. V. Narendran has described India as receiving significant global attention as a market, manufacturing base, source of technology and talent, and strategic partner, while also emphasising the need for greater competitiveness.
This connects the seemingly unrelated announcements.
Microsoft is building infrastructure.
Global companies are expanding capability centres.
Technology companies are moving more engineering work into the country.
Industrial companies are finding new applications for AI.
Indian technology leaders are debating whether human expertise will keep pace with AI.
None of this guarantees that India will move up the technology value chain.
There are still questions around infrastructure, talent quality, research depth, capital, productivity, intellectual property and competitiveness.
But the ambition is changing.
The difference between making something and building it
For a long time, the aspiration was to make products in India.
The next aspiration is to build products from India.
There is a difference.
Making asks:
Can we produce it?
Building asks:
Can we conceive it, engineer it, design it, develop it, own it and take it to the world?
The progression looks like this:
Make. Engineer. Design. Build. Own. Export.
The sequence applies to smartphones and electronics.
It applies to software and AI.
It applies to industrial technology.
It applies to semiconductor ecosystems.
It increasingly applies to global capability centres.
The ultimate measure of India’s technology maturity may therefore not be how many global companies have operations here.
It may be how many global products, technologies and intellectual properties are created here.
That is a harder metric.
It is also a more useful one.
India has spent decades proving that global companies can operate from the country.
The next decade will test whether global companies will build their most important technologies from the country.
The difference is significant.
Make in India was about production.
Build in India is about capability and ownership.
