India's Outsourcing Origins

Reference library · 983 words

Outsourcing is now so familiar a feature of the global economy that it can seem inevitable, as though work would naturally flow to wherever it is cheapest. It is not inevitable, and the Indian case shows why. Several countries in the 1980s had large numbers of educated people and low wages. Only one built a services export industry that reshaped its balance of payments. The difference lay in a combination of language, time zone, telecommunications policy, a specific accounting quirk of the late 1990s, and a handful of firms that were willing to do dull work extremely well for a very long time.

The prehistory is important. India's post independence economic policy emphasised self reliance, with a licensing regime governing what could be manufactured and imported. That regime, whatever its other effects, made computing hardware expensive and scarce. When the government pressed foreign companies to dilute their equity holdings under legislation of the 1970s, IBM chose to wind up its Indian operations in 1978 rather than comply. The immediate effect was a shortage of machines and support. The longer effect was that Indian engineers learned to maintain, program and improvise on older equipment without vendor assistance, and a domestic software and services capability grew in the space IBM left. Tata Consultancy Services, established within the Tata group in 1968, was already exporting programming services before that departure and was well placed afterward.

The first exports were people, not code

The earliest export model was labour on temporary visas. Indian firms contracted with American and European clients to supply programmers who worked on the client's premises, on the client's equipment, under the client's supervision. The Indian firm's margin was the difference between the wage it paid and the rate it billed. This was profitable but limited, and it left the Indian company with no ownership of anything except the relationship. Contemporary critics called it bodyshopping, which was fair, and it was also the only viable structure at the time, because moving data between India and a client in Ohio was extremely difficult.

Telecommunications policy is the pivot on which the whole story turns. India's domestic telephone network in the 1980s was slow to obtain, unreliable and state monopolised. Doing software work in India for a foreign client required a dedicated international data link, which was expensive and required official permission. The creation of Software Technology Parks of India from 1991, under what is now the Ministry of Electronics and Information Technology, addressed exactly this. The scheme gave exporting firms duty free import of computers, tax concessions and, crucially, high speed satellite data links provided outside the ordinary telecommunications bottleneck. Texas Instruments had already demonstrated the concept, establishing a Bangalore design centre in 1985 with its own satellite link to send chip designs back to the United States. Once bandwidth existed, the work could stay in India and only the output needed to travel.

Year 2000, call centres and the making of a sector

The Year 2000 problem was the industry's decisive commercial break. Software written decades earlier commonly stored years as two digits, and the rollover to 2000 threatened errors in banking, insurance, utilities and airline systems. Remediation was enormous in volume, mechanical in nature, unavoidably deadline driven and unattractive to expensive Western consultancies. Indian firms took a very large share of it. What they gained was less the fee than the credential. Financial institutions that had never contemplated offshore delivery had now let Indian engineers into their core systems, found the work competent and on time, and had auditable evidence of it. When the deadline passed without disaster, the relationships remained.

Business process outsourcing followed on a different logic. If a customer service call, an insurance claim or a payroll run could be handled over a data link, it could be handled anywhere the staff spoke the customer's language. India offered a large English speaking graduate population and a time zone that turned the American night into the Indian working day, allowing round the clock service. General Electric was an early and influential mover, establishing large Indian operations in the late 1990s that were later spun out; that unit's alumni founded or led a significant number of subsequent firms. Cities including Gurugram, Noida, Pune, Hyderabad, Chennai and Bangalore built the campuses, transport fleets and 24 hour infrastructure that the model needed, including the fleets of company buses that became a familiar night time sight.

The criticisms were sharp on both ends and both had substance. In client countries, offshoring became politically contentious, framed as the export of jobs, and periodically produced legislative proposals to restrict it. In India, the work drew a different complaint: that a generation of graduates was being absorbed into night shift call handling and routine data processing that developed few transferable skills and produced burnout, and that the country was selling labour rather than building products. Neither criticism was baseless. Studies of shift work and health, and the visible turnover rates in the sector, gave the second one weight.

What the origins period established, though, was durable infrastructure of a non physical kind: contracting norms, quality certification, delivery management methods, and above all the credibility that a task could be reliably completed eight thousand kilometres away. That credibility is the actual asset, and it is why the sector survived the dot com collapse of 2001, the financial crisis of 2008 and repeated visa restrictions. The uncomfortable question now is whether it survives automation. The routine transaction processing and first line support that built the industry are precisely the work that software, and more recently generative artificial intelligence systems, handle at declining cost. Indian firms have responded by moving into consulting, cloud migration, analytics and engineering services, and by arguing that clients will still need someone accountable for the outcome. Whether that argument holds is the open question, and it is being tested now rather than in some distant future.

Back to the library