English only · Odia translation in progress

Chapter 3: How Others Built It — Indian States That Made the Leap


In 1996, Hyundai Motor Company was looking for a site to build its first manufacturing plant outside South Korea. The company evaluated locations across Southeast Asia and India, eventually shortlisting sites in Maharashtra, Andhra Pradesh, and Tamil Nadu. In October 1996, Hyundai chose Irungattukottai near Sriperumbudur, on the outskirts of Chennai. The plant would begin production in September 1998 — a 17-month construction timeline that remains one of the fastest major auto plant buildouts in Indian history.

The Sriperumbudur decision was not romantic. It was a checklist. Chennai port was 40 kilometres away — close enough for CKD (completely knocked down) kit imports during ramp-up and for export shipments once production matured. SIPCOT, Tamil Nadu’s industrial development corporation, had already acquired and developed the land with roads, power connections, water supply, and effluent treatment. IIT Madras was 25 kilometres away, producing mechanical and electrical engineers who could staff a modern assembly line. The state government committed to reliable power supply — a non-trivial promise in 1990s India, where brownouts could halt a paint shop mid-cycle and ruin an entire batch of body panels. And critically, there was already a functioning auto ecosystem nearby: Ashok Leyland had been building trucks in Ennore since 1948. A web of component suppliers, tool-and-die makers, and logistics operators already existed.

Hyundai’s Sriperumbudur plant was not the beginning of Tamil Nadu’s auto industry. It was the moment an existing ecosystem reached critical mass and began to self-reinforce. The difference between that moment and the half-century of patient building that preceded it is the entire lesson of this chapter.

Five Indian states built industrial ecosystems that transformed their economies. Each took a different path. Each offers a specific, replicable lesson — not about what worked, which is easy to describe after the fact, but about the sequence in which it worked, which is the hard part. Because in ecosystem-building, as in software engineering, the order of operations matters as much as the operations themselves.


Tamil Nadu: The Auto Cluster That Took 50 Years

The Anchor

The story begins in 1948, when Ashok Leyland established its truck manufacturing plant at Ennore, north of Chennai. At the time, the choice of Madras (as Chennai was then called) was driven by port access and the British engineering tradition that had created a modest industrial base in the presidency. Ashok Leyland was a joint venture between Ashok Motors (founded by Raghunandan Saran) and Leyland Motors of the UK. The plant made commercial vehicles — buses and trucks — and it needed components: axles, springs, brake drums, castings, forgings.

Those components did not exist locally. So Ashok Leyland either made them in-house or worked with small workshops in the Ambattur-Padi industrial area to develop supplier capability. This is the first step in every ecosystem story: the anchor company creates demand that pulls suppliers into existence. In software terms, this is the initial commit — the first node in a dependency graph that will eventually contain thousands of entries.

Through the 1950s and 1960s, Tamil Nadu’s auto component base grew slowly. The License Raj constrained scale — you needed a government permit to expand capacity, and permits went to politically connected applicants, not necessarily the most capable. But the component workshops around Ambattur developed skills: precision machining, heat treatment, quality inspection. These were general-purpose manufacturing skills that could serve any mechanical industry, not just Ashok Leyland. The talent was accumulating like compound interest — invisible year by year, transformative over decades.

The Infrastructure Layer

What Tamil Nadu did that most Indian states did not was build industrial infrastructure ahead of demand.

SIPCOT — the State Industries Promotion Corporation of Tamil Nadu — was established in 1971. Its mandate was specific: acquire land, develop industrial estates with roads, power substations, water supply, and common effluent treatment plants, and offer serviced plots to manufacturers. Not subsidies. Not tax holidays (though those came later). Physical infrastructure — the boring, expensive stuff that a private company cannot build for itself because infrastructure is a public good with coordination problems.

By the time Hyundai came looking in 1996, SIPCOT had developed over 30 industrial estates across Tamil Nadu. The Sriperumbudur estate was not built for Hyundai. It was built before Hyundai. The infrastructure existed, waiting for the company that would fill it. This is a critical distinction. States that build infrastructure in response to a specific company’s request are always late. States that build infrastructure in anticipation of demand are the ones that capture investment.

The analogy to software platform design is precise. A well-designed API does not know its consumers in advance. It provides capabilities — authentication, storage, compute — that any application can consume. SIPCOT provided industrial capabilities — land, power, water, waste treatment — that any manufacturer could consume. The platform preceded the applications.

The Talent Pipeline

Tamil Nadu invested heavily in technical education. By the 1990s, the state had over 500 engineering colleges and more than 30 Industrial Training Institutes (ITIs). The quality was uneven — many engineering colleges were diploma mills with poor lab facilities — but the sheer volume ensured that manufacturers could find employable workers. An auto assembly line does not need 500 PhDs. It needs 5,000 workers who can read a drawing, operate a CNC machine, follow a standard operating procedure, and troubleshoot a jammed conveyor. The ITI system, for all its flaws, produced these workers.

IIT Madras played a different role. It did not supply line workers. It supplied the top layer — the engineers who designed the production processes, the managers who ran the plants, the R&D staff who adapted global designs for Indian conditions. A single institution cannot build a manufacturing ecosystem. But it can provide the capstone — the 1% of talent that designs the systems within which the other 99% work.

The Cascade

Once Hyundai committed, the cascade began:

  • 1996: Hyundai chooses Sriperumbudur
  • 1999: Ford Motor Company sets up at Maraimalai Nagar, south of Chennai
  • 2005: Ashok Leyland expands; Hyundai announces second plant
  • 2007: BMW opens plant at Mahindra World City, Chennai
  • 2008: Daimler India Commercial Vehicles at Oragadam
  • 2010: Renault-Nissan opens joint plant at Oragadam (400,000 vehicles/year capacity)
  • 2012: Daimler expands; multiple Tier-1 suppliers follow
  • 2019: Hyundai capacity exceeds 750,000 vehicles/year

Each OEM (original equipment manufacturer) brought its own supply chain. Hyundai’s Korean Tier-1 suppliers — Mando (brakes), Hyundai Mobis (modules), Sungwoo Hitech (body panels) — set up plants within 50 km of the Sriperumbudur factory. Ford’s global suppliers followed. The Tier-1s brought Tier-2s. The Tier-2s brought Tier-3s. Within 15 years, the Chennai-Hosur corridor had accumulated over 1,000 auto component companies.

The current scale is staggering. Tamil Nadu accounts for roughly one-third of India’s automobile exports. The Chennai cluster’s auto component ecosystem exceeds $30 billion in annual revenue. ACMA (Automotive Component Manufacturers Association) data shows the Chennai-Hosur corridor produces over 30% of India’s auto component output. The state’s auto sector directly employs over 350,000 people, with indirect employment exceeding a million.

The Lesson

The Tamil Nadu auto ecosystem took 50 years — from Ashok Leyland’s 1948 founding to Hyundai’s 1998 production start — to reach the critical mass that triggered exponential growth. What TN had that Odisha does not:

  1. A functioning port — Chennai port handled the imports during ramp-up and the exports during maturity
  2. An educated workforce — not brilliant, but broadly literate and trainable
  3. Policy continuity — SIPCOT survived changes in government because it was institutionally embedded, not dependent on a chief minister’s personal commitment
  4. Infrastructure that preceded demand — the SIPCOT estates were built before the tenants arrived

Odisha has none of these in the minerals-to-manufacturing chain. Paradip port exists but is overwhelmingly configured for bulk cargo (iron ore, coal), not containers or finished goods. The state’s ITI system produces fewer skilled workers per capita than Tamil Nadu. Industrial infrastructure in mining districts — Keonjhar, Sundargarh, Jajpur — is minimal beyond what the mining companies built for themselves. And policy continuity on industrial development, while improving under recent governments, does not have the multi-decade institutional track record that SIPCOT represents.

The uncomfortable implication (confidence level: ~80%): even if Odisha started building the institutional infrastructure today — the SIPCOT equivalent, the ITI pipeline, the port modernization — the payoff would not materialize for 15-25 years. Ecosystem-building has no shortcut to critical mass. Every state that built one did it over decades, not election cycles.


Gujarat: From Textile Dyes to Pharma Giant

The Technical Sequence

Gujarat’s chemical and pharmaceutical dominance did not begin with a government policy document. It began with textile mills.

Ahmedabad was the “Manchester of the East” by the late 19th century. The city’s textile mills — over 60 by independence — needed dyes. Initially imported from Germany (the global leader in synthetic dyes until World War I disrupted supply chains), dyes gradually began to be manufactured locally. Small chemical workshops in and around Ahmedabad began producing basic azo dyes in the 1920s and 1930s.

This is where the technical sequence becomes important, because the chemistry of dyes and the chemistry of drugs are cousins. Both involve organic synthesis — building complex molecules from simpler precursors through controlled chemical reactions. A factory that can synthesize an azo dye can, with modest equipment upgrades and different raw materials, synthesize a sulfonamide drug. The skills transfer: reaction monitoring, distillation, crystallization, quality testing. The infrastructure transfers: reactor vessels, heating and cooling systems, waste treatment. The regulatory knowledge transfers: handling hazardous chemicals, managing effluents, ensuring batch consistency.

The sequence was: textiles → dyes → intermediates → bulk drugs → formulations → contract research.

Each step built on the capabilities of the previous one. The textile mills created demand for dyes. The dye manufacturers developed organic chemistry skills. Those skills enabled production of pharmaceutical intermediates (the molecular building blocks of drugs). The intermediates manufacturers moved into bulk drug production (active pharmaceutical ingredients). The bulk drug producers developed formulation capabilities (turning APIs into tablets, capsules, injectables). And the most sophisticated companies eventually moved into contract research and manufacturing (CRAMS) for global pharma companies.

The Vapi-Ankleshwar Corridor

The physical concentration of this ecosystem is remarkable. The Vapi-Ankleshwar corridor in southern Gujarat — roughly 100 kilometres along the Mumbai-Ahmedabad highway — contains an estimated 25,000-30,000 chemical and pharmaceutical manufacturing units. This is one of the densest industrial clusters on the planet.

GIDC (Gujarat Industrial Development Corporation), established in 1962, played the SIPCOT role. GIDC developed over 200 industrial estates across Gujarat, providing:

  • Plotted industrial land with roads, water, power, and drainage
  • Common Effluent Treatment Plants (CETPs) — critical for chemical manufacturing, where individual units cannot afford standalone effluent treatment
  • Single-window clearance for environmental and industrial permits
  • Industrial infrastructure ahead of demand — the same pattern as Tamil Nadu

The CETP provision was particularly important. Chemical manufacturing generates hazardous waste — heavy metals, organic solvents, acidic effluents. Without a common treatment facility, each small manufacturer would either invest disproportionately in treatment or (more likely) dump waste illegally. The CETPs allowed small units to operate within environmental norms at manageable cost. Whether they actually achieved adequate treatment is debatable — the Vapi area has been cited as one of the most polluted industrial zones in India — but the institutional provision of shared infrastructure enabled the cluster to form.

The Culture vs. Institution Debate

Any discussion of Gujarat’s industrial success encounters the culture argument: Gujarat’s mercantile Baniya and Patel communities have a centuries-old tradition of entrepreneurship, risk-taking, and business network formation. The Marwari and Gujarati trading communities financed India’s early industrialization. The culture of enterprise, the argument goes, is what made Gujarat different.

There is truth in this. Entrepreneurial culture provides social capital — networks of trust that reduce transaction costs, mentoring from experienced to new entrepreneurs, cultural legitimacy for business risk-taking. A young man in Vapi whose father and uncles all run chemical businesses faces lower barriers to starting his own than a young man in Koraput whose family has no business background.

But culture is insufficient without institutions. Rajasthan has Marwari entrepreneurs but not Gujarat’s industrial density. Bihar has risk-taking traders but not Tamil Nadu’s manufacturing base. The Gujarati and Marwari communities are present across India — they dominate commercial activity in Mumbai, Kolkata, and Bangalore — but the industrial clusters formed specifically in Gujarat, where GIDC provided the physical infrastructure and policy continuity provided the predictability.

The honest assessment (confidence level: ~70%): entrepreneurial culture is a genuine accelerant — it reduces the activation energy for ecosystem formation. But it is neither necessary nor sufficient. What is necessary is institutional infrastructure (GIDC/SIPCOT equivalent), policy predictability, and time. What is sufficient is all three of those plus either a cultural base or a sufficiently large anchor company to kickstart the supply chain. Gujarat had culture plus institutions. Tamil Nadu had institutions plus anchors.

Odisha lacks both the entrepreneurial culture argument (the state’s dominant social groups — tribal communities, agricultural OBC communities — do not have commercial traditions comparable to Gujarat’s trading castes) and the institutional infrastructure argument. This is not a cultural judgment — it is a structural observation about starting conditions. The question is whether institutional design can substitute for cultural endowment. The Tamil Nadu case suggests it can, given enough time.

The Scale

The numbers tell the story:

  • Gujarat produces approximately 33% of India’s pharmaceutical output
  • Gujarat produces approximately 40% of India’s chemical output
  • Pharma exports from Gujarat exceeded $8 billion in FY 2023-24
  • Key companies that emerged from this ecosystem: Sun Pharmaceutical Industries (founded Baroda, now India’s largest pharma company), Zydus Lifesciences (Ahmedabad), Torrent Pharmaceuticals (Ahmedabad), Cadila Healthcare, Intas Pharmaceuticals
  • The ecosystem employs over 500,000 people directly in chemicals and pharma, with indirect employment exceeding 1.5 million

The Lesson

Gujarat built its industrial ecosystem on an existing mercantile base, but the institutional choices — GIDC’s industrial estates, common effluent treatment, single-window clearance, consistent industrial policy across DMK/AIADMK-style government changes — were what enabled scale. The technical sequence (textiles → dyes → intermediates → pharma) shows how industries evolve through adjacent capabilities. Each step was a small leap, not a giant one. Nobody in 1920s Ahmedabad planned the pharma industry. Dye makers discovered that their skills transferred to drug chemistry. The ecosystem emerged through thousands of small entrepreneurial bets, not through a master plan.

For Odisha, the relevant question is: what adjacent capability steps exist from the current mining and metals base? Iron ore mining → pelletization → DRI → steelmaking is one obvious chain, and some of it exists (JSPL Angul, Tata Steel Kalinganagar). But the next steps — steel processing → component manufacturing → assembly — require a different kind of institutional design than what Odisha has built.


Karnataka: The IT Ecosystem and the Mechanics of Network Effects

The Seed

In 1985, Texas Instruments became the first multinational technology company to set up a development centre in Bangalore. The choice was driven by a specific set of factors, none of which had anything to do with state government policy:

  1. Climate: Bangalore’s year-round moderate temperature (average 24°C) reduced air conditioning costs — a non-trivial factor when every square foot of office space needed climate control for sensitive electronic equipment
  2. IISc (Indian Institute of Science): Founded in 1909, IISc was India’s premier research institution, producing doctoral-level scientists and engineers. TI needed research talent, not line workers.
  3. Existing defense/aerospace base: Hindustan Aeronautics Limited (HAL, established 1940), Bharat Electronics Limited (BEL, 1954), and ISRO’s Satellite Centre (1972) had already created a community of engineers working on complex systems. These engineers were potential recruits or collaborators.
  4. English-speaking, educated workforce: Karnataka’s education system, while not as large as Tamil Nadu’s, produced graduates who could communicate with American clients and read technical documentation
  5. Lower costs than Mumbai or Delhi: Office rents, engineer salaries, and living costs were 30-50% lower than the established metro cities

Notice what is absent from this list: state government industrial policy. Unlike Tamil Nadu’s deliberate SIPCOT infrastructure or Gujarat’s GIDC estates, Karnataka’s IT ecosystem began with a market actor — Texas Instruments — making a rational location decision based on existing conditions. The government’s role came later.

The Domestic Pioneers

The multinational entry coincided with domestic companies making pivots that would define the industry.

Wipro, founded in 1945 as Western India Vegetable Products Limited (a company that sold cooking oil from sunflower and safflower seeds), began its IT pivot in the early 1980s under Azim Premji. The company started by manufacturing minicomputers in collaboration with Sentinel Computer Corporation of the US, then moved into IT services. By 1990, Wipro’s IT revenues exceeded its consumer products business.

Infosys, founded in Pune in 1981 by N.R. Narayana Murthy and six colleagues with Rs 10,000 of capital, relocated to Bangalore in 1983. The reasons were similar to TI’s: talent availability, lower costs, and the emerging technology community. Infosys would become the poster child of Indian IT — its IPO in 1993 was one of the first tech listings on the Indian stock exchange.

These domestic companies did something that multinationals would not: they invested in building the talent pipeline. Infosys established one of the world’s largest corporate training centres at Mysore — 337 acres, capable of training 14,000 employees simultaneously. Wipro built similar training infrastructure. The companies were, in effect, building the workforce that the education system was not producing fast enough. This is an underappreciated form of ecosystem investment — the anchor companies did not just consume existing talent, they created new talent and released it into the ecosystem (through attrition, if nothing else).

The Exogenous Shock

Two external events turbocharged the ecosystem:

1991 liberalization: India opened its economy, removed most industrial licensing requirements, and allowed foreign investment. For IT services, this meant multinational companies could set up wholly-owned subsidiaries in India (previously restricted) and Indian companies could freely access international clients. The licensing shackles that had constrained scale were removed.

Y2K (1997-2000): The Year 2000 problem — the fear that legacy software would crash when dates rolled from 1999 to 2000 — created massive demand for programmers who could review and fix millions of lines of COBOL, Fortran, and mainframe code. India had the programmers. The work was routine but voluminous, and it could be done remotely. Indian IT companies — particularly in Bangalore — ramped up hiring by tens of thousands. Y2K was the demand shock that pushed the ecosystem past critical mass.

In software engineering terms, the ecosystem followed a classic adoption curve: slow buildup (1985-1995), trigger event (Y2K), rapid scaling (1998-2005), network effects (2005-present). By the time the Y2K spike subsided, the infrastructure — office parks, residential townships, international flights, broadband connectivity — had been built, and the ecosystem was self-sustaining.

The Government Response (Not Initiative)

Karnataka’s government did eventually act, but its interventions were reactive, not proactive. The key institutional responses:

  • STPI (Software Technology Parks of India): Established in 1991 as a central government initiative, STPI Bangalore provided satellite uplink facilities, tax exemptions (100% tax holiday on export profits), and a single-window clearance for IT companies. This was infrastructure that addressed a specific bottleneck — international data connectivity in the pre-broadband era.
  • IT parks: Electronics City (developed by Keonics, Karnataka’s electronics development corporation, starting in the late 1970s) and later ITPL (International Tech Park Limited, a joint venture with Singapore, opened 2000) provided the physical infrastructure — built office space, power backup, water, connectivity — that IT companies needed.
  • Policy stability: Successive Karnataka governments — across party lines — maintained the policy environment for IT. No government tried to impose new levies on software exports or restrict IT company operations. This negative discipline — the restraint from harmful action — is often more valuable than active support.

The parallel to Tamil Nadu’s SIPCOT is instructive. Both states provided institutional infrastructure. But Tamil Nadu built infrastructure proactively (before the companies arrived), while Karnataka built infrastructure reactively (after the companies demonstrated demand). Both approaches worked, but Tamil Nadu’s was faster because companies did not have to wait.

The Scale

The current numbers:

  • Karnataka’s IT/ITeS exports: approximately $60-70 billion annually (FY 2023-24)
  • IT workforce in Bangalore: 1.5-2 million professionals
  • Contributing approximately 25-30% of India’s total IT exports
  • Over 3,500 IT companies operating in Bangalore, from startups to multinationals
  • Indirect employment (transport, food, housing, retail serving IT workers): estimated 3-4 million

From TI’s 1985 development centre (roughly 50 engineers) to 2 million IT workers in 40 years. The compounding rate is extraordinary, and it follows the mathematical signature of network effects: once the ecosystem passes a threshold density, each new addition makes the ecosystem more attractive to the next addition. Companies locate in Bangalore because talent is there. Talent moves to Bangalore because companies are there. The self-reinforcing loop is identical to the one that drives platform adoption in technology markets — and it is nearly impossible to bootstrap from zero.

The Relevance to Odisha

The specific mechanics of Karnataka’s IT ecosystem are not directly transferable to mineral processing in Odisha. IT services require different infrastructure (office space, connectivity) than steel plants (land, water, power, rail). The workforce requirements are different — software engineers versus metallurgical technicians. The capital intensity is reversed — IT services are labor-intensive and capital-light, while mineral processing is capital-intensive and relatively labor-light.

But the underlying dynamics are identical:

  1. An anchor created initial demand (TI → Ashok Leyland equivalent)
  2. Talent accumulated through compounding (IISc grads + corporate training → ITI/engineering college pipeline)
  3. Infrastructure was provided (STPI, Electronics City → SIPCOT estates)
  4. An external shock accelerated adoption (Y2K → what could play this role for Odisha?)
  5. Network effects made the ecosystem self-sustaining once density exceeded a threshold

The software analogy is apt: Bangalore had a “minimum viable ecosystem” by approximately 1990 — a few anchor companies, a talent pipeline, basic infrastructure. Everything before 1990 was building toward minimum viability. Everything after was compounding on it. For Odisha’s mineral processing ecosystem, the question is: has minimum viability been reached? JSPL at Angul and Tata Steel at Kalinganagar are anchor companies. Some engineering colleges exist. Some infrastructure has been built. But the density is nowhere near the threshold where network effects would take over. The ecosystem is still in the pre-1990 phase, where each addition requires deliberate effort rather than being pulled in by the gravitational field of existing activity.


Jharkhand: The Cautionary Tale

The Pioneer

In 1907, Jamsetji Tata’s vision materialized when the first blast furnace at Jamshedpur was blown in. Tata Iron and Steel Company (TISCO, now Tata Steel) was India’s first private-sector steel plant and one of the first integrated steel plants in Asia. The location was chosen for the same reasons that make Odisha’s mining belt attractive today: iron ore from the Noamundi and Joda mines (then in undivided Bihar, now split between Jharkhand and Odisha), coal from Jharia (150 km away), water from the confluence of the Subarnarekha and Kharkai rivers, and rail connectivity via the Bengal-Nagpur Railway.

Jamshedpur was, by any measure, a spectacularly successful industrial anchor. Tata Steel survived two world wars, the Great Depression, Indian independence, nationalization threats, and market liberalization. By 2024, Tata Steel’s Jamshedpur plant has a crude steel capacity of approximately 11 MTPA — after 117 years of continuous operation and expansion. The company’s revenues from India operations alone exceed Rs 1,30,000 crore annually. It is one of the most respected industrial enterprises in the world.

And yet.

The Island

Jamshedpur is an island of industrial excellence in a sea of underdevelopment. The contrast is jarring. Within the city limits — which Tata Steel essentially built and managed as a company town — you find well-maintained roads, functional hospitals, schools that produce IIT and IIM admits, a technical university (NIT Jamshedpur), clean water supply, and reliable power. Step outside the city limits, and you are in one of the poorest, most governance-deficient regions in India.

Jharkhand as a state (carved from Bihar in November 2000) has:

  • Per capita income approximately 40% below the national average
  • The highest proportion of tribal population among major states (~26%)
  • A history of Naxalite/Maoist insurgency that has made large parts of the state ungovernable at various times
  • Mining mafia networks that have corrupted institutional processes
  • 11 chief ministers in 24 years of statehood — an average tenure of just over 2 years
  • Land acquisition conflicts that have stalled or killed multiple industrial projects

The question is sharp: how can a state that hosts India’s most iconic steel company, with 117 years of continuous operation, fail to develop a broader industrial ecosystem? Why did Jamshedpur not become Odisha’s equivalent of what Chennai became for Tamil Nadu?

Why the Ecosystem Did Not Spread

The answer has multiple layers, and each layer is instructive.

Political instability. Tamil Nadu’s SIPCOT survived changes between DMK and AIADMK governments because it was institutionally embedded — a statutory corporation with its own staff, assets, and mandate. Jharkhand’s industrial development institutions have never achieved this stability. Each new government reshuffles priorities, reassigns officials, and resets relationships with industrial investors. No company commits Rs 20,000 crore to a greenfield steel plant in a state where the chief minister might change before the foundation is poured.

Governance failure. Mining in Jharkhand has been associated with corruption, illegal extraction, and regulatory capture to a degree that even India’s tolerant norms find excessive. The “mining mafia” — a network of illegal miners, compromised officials, and political patrons — has undermined the institutional framework that legitimate industrial investment requires. When a company cannot be certain that its mining lease will be honored, that its land title will survive a court challenge, or that the local administration will not demand extralegal payments, the rational response is to invest elsewhere.

Insurgency. The Maoist/Naxalite insurgency, which was active in significant parts of Jharkhand from the 1990s through the 2010s, made rural areas unsafe for industrial investment. You cannot build a factory in a zone where armed groups levy “taxes,” attack police stations, and blow up railway tracks. The insurgency has decreased in recent years, but its legacy — damaged roads, absent administration, traumatized communities — persists.

Land acquisition. Jharkhand faces the same challenge as Odisha: the communities that sit on mineral-rich land are predominantly tribal (Adivasi), protected by constitutional provisions (Fifth Schedule) and legislation (PESA, Forest Rights Act). Acquiring land for industrial use requires consent processes that are time-consuming when followed properly and explosive when circumvented. Several high-profile projects in Jharkhand — including ArcelorMittal’s proposed 12 MTPA steel plant — were abandoned or indefinitely delayed after land acquisition conflicts.

Tribal displacement. The communities displaced by mining and industrial projects in Jharkhand were overwhelmingly tribal. Their displacement was rarely accompanied by adequate rehabilitation — resettlement colonies without livelihood options, cash compensation that was spent within years, loss of forest access that had provided subsistence. The resulting resentment fed the insurgency, which further deterred investment, which slowed development, which increased resentment. A vicious cycle with no obvious break point.

The Structural Diagnosis

In ecosystem terms, Jamshedpur is a node without a network. Tata Steel is an anchor company of world-class quality. But an anchor without institutional infrastructure, policy stability, talent pipeline, and social peace creates an enclave, not an ecosystem.

Think of it as a software analogy: Tata Steel Jamshedpur is like running a brilliant application on an operating system that keeps crashing. The application works perfectly. But it cannot scale beyond its own process because the OS — governance, law enforcement, land administration, education, infrastructure — is unreliable. Every new application (factory) that tries to start encounters the same OS failures and either crashes or never installs.

Tamil Nadu’s “operating system” — SIPCOT, the court system, the police, the revenue administration, the education system — was good enough. Not great. Not incorrupt. But functional and predictable. Companies could reasonably expect that a factory built today would still be operating in 20 years, that employees could send their children to school, that electricity would mostly work, and that the government would mostly honor its commitments. Jharkhand could not provide these assurances.

The Lesson

One anchor is not enough. Without institutional design, stable governance, and workforce investment, an anchor company becomes an enclave — a walled garden in a desert. The surrounding region does not industrialize; it merely services the enclave. Jamshedpur has excellent hospitals and schools inside the Tata Steel township. The rest of Jharkhand does not.

This is directly relevant to Odisha. JSPL Angul and Tata Steel Kalinganagar are anchor companies. They are world-class facilities. But they operate in mining districts (Angul, Jajpur) where the broader institutional infrastructure — education, healthcare, roads, governance capacity — is far below what an industrial ecosystem requires. The risk is that these plants become Jamshedpur-style enclaves: brilliant factories surrounded by underdevelopment, with value created inside the factory wall and very little spilling over.

The difference between Odisha and Jharkhand is that Odisha has had greater political stability (Naveen Patnaik’s 24-year tenure, followed by an orderly transition), lower insurgency (though Maoist activity existed in some southwestern districts), and stronger fiscal management. These are genuine advantages. But they are advantages of degree, not of kind. The institutional infrastructure deficit — the absence of a SIPCOT or GIDC equivalent, the weak ITI pipeline, the governance gaps in mining districts — is similar.

Confidence level on this assessment: ~75%. Odisha’s governance advantage over Jharkhand is real but may be narrower than it appears from Bhubaneswar. Ground-level institutional capacity in Keonjhar, Sundargarh, and Jajpur may be closer to Jharkhand’s governance reality than the state’s aggregate indicators suggest.


Chhattisgarh: The Bottom-Up Alternative

The Sponge Iron Belt

Chhattisgarh offers a completely different model — one that emerged without government planning, driven by small entrepreneurs rather than multinational anchors or institutional infrastructure.

Through the 1990s and 2000s, over 150 DRI (Direct Reduced Iron) / sponge iron plants sprang up in the Raipur-Raigarh corridor of what is now Chhattisgarh (carved from Madhya Pradesh in November 2000). Each plant was small by steel industry standards — typical capacity of 50,000-300,000 tonnes per year, requiring capital of Rs 50-200 crore. By comparison, a single blast furnace at Tata Steel Jamshedpur costs Rs 10,000+ crore.

How did this happen? The economics were straightforward:

  1. Low capital barrier: A coal-based rotary kiln DRI plant is one of the least capital-intensive routes into steelmaking. At Rs 50-100 crore for a small unit, it was within reach of local businessmen, many of them traders in iron ore and scrap who understood the metals market.
  2. Locally available inputs: Chhattisgarh sits on both iron ore (the Bailadila deposit in Dantewada, one of India’s richest) and coal (Korba coalfield). The two primary inputs for coal-based DRI were available within 200-300 km of the plants.
  3. Simple technology: Coal-based DRI technology — feeding iron ore and coal into a rotary kiln at 1,000-1,100°C — is not sophisticated. It does not require metallurgical PhDs or decades of process optimization. The technology was available from Indian equipment manufacturers, who provided turnkey installations.
  4. Growing steel demand: India’s construction boom, accelerating through the 2000s, created insatiable demand for basic steel products — TMT bars, structural sections, wire rod. DRI fed into induction furnaces and rolling mills to produce exactly these products.

The result was bottom-up industrialization. No SIPCOT. No GIDC. No government master plan. Hundreds of entrepreneurs, individually making rational economic bets, collectively building an industrial cluster.

The Costs

But the Chhattisgarh model came with severe costs that any honest account must confront.

Environmental devastation. Coal-based DRI is one of the most polluting industrial processes in India. The rotary kilns emit particulate matter, sulfur dioxide, carbon monoxide, and volatile organic compounds. The Raipur-Korba belt has some of the worst air quality in the country. The Central Pollution Control Board has repeatedly flagged the cluster. Respiratory diseases — silicosis, chronic obstructive pulmonary disease, asthma — are endemic among plant workers and nearby communities.

Groundwater contamination from improperly disposed char (the waste residue from DRI kilns) and ash has affected drinking water sources in surrounding villages. This is not a hypothetical future risk. It is a documented current reality.

Labor conditions. Sponge iron plants are notorious for poor labor practices. Workers — many of them migrant laborers from Odisha, Jharkhand, and Bihar — operate in extreme heat (kiln temperatures exceed 1,000°C, ambient temperatures near the kiln reach 50-60°C), often without adequate safety equipment. Wages are low — Rs 8,000-15,000 per month for kilnwork, roughly half the wage at an integrated steel plant. Unionization is rare. Safety incidents — burns, falls, equipment failures — are underreported because workers fear dismissal.

This is the dark side of bottom-up industrialization. When the state does not set and enforce environmental and labor standards, the gap is filled by the market’s natural tendency toward cost minimization. The cost savings from lax environmental compliance and poor labor standards are, in a competitive commodity market, the difference between profitability and bankruptcy for marginal producers. The incentive structure pushes toward the bottom.

Quality ceiling. Coal-based DRI produces sponge iron with relatively high levels of gangue (impurities from the coal ash) and inconsistent metallurgy. Steel made from this route — typically in small induction furnaces rather than electric arc furnaces with full refining capability — is adequate for construction-grade TMT bars but unsuitable for automotive, appliance, or high-specification applications. The Chhattisgarh cluster is locked into the lowest-value segment of the steel market.

This is a form of a poverty trap applied to industrial development. Low capital → simple technology → low-quality product → low margins → insufficient surplus for technology upgrades → continued low quality. Breaking out of this trap requires either external capital infusion (a large company acquiring and upgrading the plants) or regulatory pressure that forces technology upgrades (which would bankrupt the marginal producers and consolidate the industry).

Partial Relevance for Odisha

The Chhattisgarh model is partially relevant to Odisha for two reasons.

First, it demonstrates that large-scale industrialization can happen without mega-projects, multinational anchors, or government master plans. Hundreds of small entrepreneurs, making individual bets of Rs 50-200 crore, collectively built more steelmaking capacity than some countries have. The entrepreneurial energy required is significant but different in kind from the institutional capacity required to attract a Hyundai or Tata Steel greenfield.

Odisha already has elements of this model. The sponge iron belt around Jharsuguda and Sambalpur hosts dozens of small DRI plants and induction furnaces. But the same pathologies apply — pollution, poor labor conditions, low product quality.

Second, it demonstrates the limits of bottom-up industrialization without institutional guardrails. The environmental and social costs of the Chhattisgarh model are severe, and they fall disproportionately on the poorest communities. A state that pursues this model without simultaneously building environmental regulation capacity and labor inspection capability is externalizing costs onto populations that cannot resist.

The honest conclusion (confidence level: ~85%): the Chhattisgarh model shows that entrepreneurship can work without mega-projects, but only if accompanied by effective environmental and labor regulation. Without guardrails, bottom-up industrialization degenerates into a race to the bottom on environmental and labor standards. Odisha should learn from the entrepreneurial energy but reject the regulatory vacuum.


What Successful Ecosystems Have in Common

Lay the five cases side by side — two successes (Tamil Nadu, Gujarat), one later success (Karnataka), one cautionary tale (Jharkhand), and one mixed result (Chhattisgarh) — and the common factors emerge with clarity:

1. An Anchor Company or Institution

Every ecosystem started with an anchor that created initial demand for suppliers, workers, and infrastructure.

  • Tamil Nadu: Ashok Leyland (1948)
  • Gujarat: Ahmedabad textile mills (19th century)
  • Karnataka: Texas Instruments (1985) plus domestic pioneers (Wipro, Infosys)
  • Jharkhand: Tata Steel (1907)
  • Chhattisgarh: No single anchor — distributed small entrepreneurs

The anchor is necessary but not sufficient. Jharkhand had the best anchor in Indian industrial history and still failed to build an ecosystem. The anchor creates the seed. Everything else determines whether the seed grows.

2. Institutional Infrastructure Before Demand

This is the factor that separates success from failure most reliably.

  • Tamil Nadu: SIPCOT built industrial estates before companies arrived
  • Gujarat: GIDC provided plotted land, CETPs, and utilities across 200+ estates
  • Karnataka: STPI and Electronics City provided IT-specific infrastructure (reactive, but still present)
  • Jharkhand: No equivalent institution achieved scale or continuity
  • Chhattisgarh: No institutional infrastructure — entrepreneurs built their own (with resulting externalities)

The pattern is clear. In game theory terms, industrial infrastructure is a coordination game. No single company will build a road because the road benefits all companies. No single company will build a wastewater treatment plant because treatment capacity is a public good. A state institution that solves these coordination problems — by building the roads, the treatment plants, the power substations — unlocks collective investment that no individual actor would make.

Odisha does not have an institution playing this role for mineral-based manufacturing. IPICOL (Industrial Promotion and Investment Corporation of Odisha Limited) exists, but it has not developed the kind of systematically built-out, widely distributed industrial estate network that SIPCOT or GIDC created. The industrial areas that exist — Kalinganagar, Angul — are largely single-company developments, not ecosystem-enabling platforms.

3. Policy Continuity Across Governments

Tamil Nadu’s SIPCOT survived 50 years of alternating DMK-AIADMK governments. Gujarat’s GIDC survived changes from Congress to Janata to BJP governments. Karnataka’s IT-friendly policies survived transitions between Congress, Janata Dal, and BJP. In every case, the industrial policy framework was treated as infrastructure — something that persists regardless of who is in power — rather than as a political program that changes with each election.

Jharkhand’s failure on this dimension is definitive. Eleven chief ministers in 24 years means that no industrial policy survived long enough to be tested, let alone to produce results. Every new government reset relationships, reshuffled bureaucrats, and restarted planning processes.

Odisha has an unusual advantage here. Naveen Patnaik’s 24-year tenure (2000-2024) provided extraordinary policy continuity — the kind of stability that typically requires institutional embedding rather than personal leadership. The test comes now: will industrial development policy continue with the same parameters under the new government, or will it reset? The early signals (continued pursuit of existing MoU commitments, retention of some key bureaucratic positions) are cautiously positive, but it is too early to be confident. Policy continuity under a long-serving leader is not the same as institutional continuity that survives leadership change. The latter is what SIPCOT represents, and Odisha has not yet built that.

4. A Talent Pipeline

Tamil Nadu: 500+ engineering colleges, 30+ ITIs, IIT Madras at the apex. Gujarat: Commercial acumen was the talent; technical skills came from the Gujarati diaspora returning from Africa and UK, plus local engineering colleges. Karnataka: IISc, IIIT-B, and corporate training centres (Infosys Mysore). Jharkhand: NIT Jamshedpur, XLRI — excellent institutions, but too few for ecosystem-scale demand, and graduates mostly left the state. Chhattisgarh: No systematic talent pipeline — relied on migrant labor.

The talent question for Odisha is acute. The state has some engineering colleges (CET Bhubaneswar, NIT Rourkela, IIIT Bhubaneswar, VSSUT Burla) and several ITIs. But the pipeline is insufficient in both volume and quality for industrial ecosystem building. NIT Rourkela produces excellent graduates — who overwhelmingly leave Odisha for jobs in Bangalore, Hyderabad, and Pune. The state produces talent that it cannot retain because the jobs do not exist. But the jobs do not exist partly because the talent is not there. This is the talent chicken-and-egg problem, and breaking it requires either a massive anchor commitment (as Infosys did with its Mysore campus) or a government-led training initiative scaled to ecosystem requirements.

5. Twenty to Fifty Years of Patient Building Before Critical Mass

This is the factor that nobody wants to hear, but every case confirms.

  • Tamil Nadu auto: Ashok Leyland 1948 → Hyundai critical mass 1998 = 50 years
  • Gujarat chemicals: Textile dyes 1920s → Pharma dominance 1990s = 70 years
  • Karnataka IT: TI 1985 → Self-sustaining ecosystem 2005 = 20 years (the fastest, because IT has lower capital requirements and faster compounding than physical manufacturing)
  • Jharkhand: Tata Steel 1907 → still no ecosystem 2025 = 118 years and counting (because the other four factors were absent)

The minimum viable timeline for building a physical manufacturing ecosystem — steel, chemicals, auto components — appears to be 20-30 years under favorable conditions (institutional infrastructure, policy continuity, talent pipeline all in place) and indefinitely long under unfavorable conditions (Jharkhand).

This has profound implications for Odisha. If the state began building the institutional infrastructure today — a properly resourced industrial development corporation, systematic ITI expansion, port modernization for finished goods, governance reform in mining districts — the earliest realistic date for achieving ecosystem critical mass in mineral-based manufacturing would be 2045-2055. That is not pessimism. That is the empirical range from every comparable case.


What Odisha Has, What It Lacks, and What Could Change

What Odisha has:

  • The raw material anchor. 28% of India’s iron ore, 51% of bauxite, 98% of chromite, 24% of coal reserves. No Indian state has a more complete mineral endowment. This is the equivalent of Ashok Leyland in 1948 or the Ahmedabad textile mills — the anchor around which an ecosystem could form.
  • Two world-class steel plants. JSPL Angul and Tata Steel Kalinganagar are not Chhattisgarh-style DRI kilns. They are integrated, modern, globally competitive facilities. They could serve as anchor companies for a broader ecosystem.
  • Political stability. Twenty-four years of single-party governance, followed by an orderly transition. This is better than Jharkhand, though not yet as institutionally embedded as Tamil Nadu’s cross-party policy continuity.
  • Fiscal discipline. Odisha consistently ranks among India’s most fiscally disciplined states. Mineral revenue provides a revenue cushion that most states lack. This gives the state government fiscal space to invest in infrastructure without borrowing recklessly.

What Odisha lacks:

  • Institutional infrastructure for manufacturing. No SIPCOT or GIDC equivalent at the scale or quality needed. Industrial areas exist (Kalinganagar, Angul, Jharsuguda) but they are company-specific developments, not ecosystem platforms with the roads, CETPs, workforce housing, and utilities that a cluster of 500 companies would need.
  • A talent pipeline at scale. The engineering colleges and ITIs exist but do not produce the volume or skill profile that ecosystem-building requires. More critically, the best graduates leave the state because the ecosystem does not yet exist to employ them.
  • Policy continuity that survives leadership change. Naveen Patnaik’s 24 years were a gift of stability, but it was leader-dependent stability. Whether industrial policy will maintain course under new leadership, and under future leadership changes beyond that, is the open question. Institutional continuity — the SIPCOT model — has not been built.
  • Patience. Democratic politics operates on 5-year election cycles. Ecosystem-building operates on 20-50 year timelines. No chief minister earns electoral rewards for infrastructure investments whose payoff arrives two or three elections later. This is the deepest structural challenge, and it is not unique to Odisha — it is the fundamental tension between democratic accountability and long-term infrastructure investment.

What could change the calculus:

Artificial intelligence and automation may reduce the talent barrier significantly. If a steel plant can operate with 30% fewer skilled workers because AI handles process optimization, quality control, and predictive maintenance, then Odisha’s talent pipeline deficit becomes less binding. If AI-driven design tools allow local engineers to achieve in 5 years what previously took 15 years of accumulated experience, the compounding timeline compresses.

Green hydrogen could redefine the energy economics of steelmaking in ways that favor Odisha. If steel production shifts from blast furnace (requiring imported coking coal) to hydrogen-based direct reduction (requiring renewable electricity + water), Odisha’s combination of iron ore + solar/wind potential + water availability could make it a globally competitive location for green steel production without the need for an existing industrial ecosystem. The technology is not proven at scale yet, and the costs remain prohibitive (confidence level on green hydrogen transforming Odisha’s steel economics by 2035: ~25%; by 2045: ~55%).

These possibilities are explored in later chapters. For now, the lesson from Tamil Nadu, Gujarat, Karnataka, Jharkhand, and Chhattisgarh is stark: industrial ecosystems are built, not announced. They require anchors, institutional infrastructure, talent, policy continuity, and decades. Odisha has the anchors. Everything else remains to be built.


Sources

  1. Hyundai Motor India Limited. “History — Hyundai in India.” Hyundai Motor India, Chennai. https://www.hyundai.com/in/en/hyundai-story/history

  2. SIPCOT (State Industries Promotion Corporation of Tamil Nadu). “About Us — Industrial Complexes.” Government of Tamil Nadu. https://sipcot.tn.gov.in

  3. ACMA (Automotive Component Manufacturers Association of India). “Indian Auto Component Industry Performance FY 2023-24.” ACMA, New Delhi. https://www.acma.in/auto-component-industry-overview

  4. IIT Madras. “Annual Report 2023-24.” Indian Institute of Technology Madras, Chennai. https://www.iitm.ac.in

  5. GIDC (Gujarat Industrial Development Corporation). “About GIDC — Industrial Estates.” Government of Gujarat. https://www.gidc.gov.in

  6. IBEF (India Brand Equity Foundation). “Pharmaceutical Industry in India.” IBEF, 2024. https://www.ibef.org/industry/pharmaceutical-india

  7. Sun Pharmaceutical Industries. “About Us — Company History.” Sun Pharma, Mumbai. https://www.sunpharma.com

  8. Nasscom (National Association of Software and Service Companies). “IT-BPM Industry in India — Strategic Review 2024.” Nasscom, New Delhi. https://nasscom.in

  9. Texas Instruments India. “History — 35 Years of Innovation in India.” Texas Instruments, Bangalore. https://www.ti.com/about-ti/innovation/india

  10. Wipro Limited. “Our History.” Wipro, Bangalore. https://www.wipro.com/about-us/

  11. Infosys Limited. “Infosys History — From Founding to Global Leadership.” Infosys, Bangalore. https://www.infosys.com/about/history

  12. STPI (Software Technology Parks of India). “About STPI — Establishment and Mandate.” Department of Electronics and IT, Government of India. https://www.stpi.in

  13. Tata Steel Limited. “Heritage — 117 Years of Steelmaking.” Tata Steel, Mumbai. https://www.tatasteel.com/about-us/heritage

  14. Government of Jharkhand. “Jharkhand — Industrial Policy 2021.” Department of Industries, Ranchi. https://jharkhand.gov.in

  15. Central Pollution Control Board. “Assessment of Sponge Iron Plant Clusters in India.” CPCB, New Delhi. https://cpcb.nic.in

  16. Ministry of Steel, Government of India. “Annual Report 2023-24 — Sponge Iron Production Data.” https://steel.gov.in

  17. IPICOL (Industrial Promotion and Investment Corporation of Odisha). “Industrial Infrastructure — Odisha.” Government of Odisha. https://www.ipicol.in

  18. NITI Aayog. “State Health Index and Fiscal Health Index.” Government of India. https://niti.gov.in

  19. Ministry of Education, Government of India. “All India Survey on Higher Education (AISHE) 2023-24 — Engineering Colleges by State.” https://aishe.gov.in

  20. JSPL (Jindal Steel and Power Limited). “Operations — Angul Integrated Steel Plant.” JSPL, New Delhi. https://www.jindalsteelpower.com

  21. Tata Steel Limited. “Kalinganagar Plant — Expansion Plans.” Tata Steel, Mumbai. https://www.tatasteel.com/kalinganagar

  22. HAL (Hindustan Aeronautics Limited). “History — Establishment and Growth.” HAL, Bangalore. https://hal-india.co.in

  23. SIAM (Society of Indian Automobile Manufacturers). “Automobile Exports from India — State-wise Data.” SIAM, New Delhi. https://www.siam.in

  24. Mines and Geology Department, Government of Odisha. “Mineral Resources of Odisha.” https://minesodisha.gov.in

  25. India Semiconductor Mission. “Vision for India’s Semiconductor Ecosystem.” Ministry of Electronics and IT, Government of India. https://indiasmiconductormission.in

  26. International Energy Agency. “The Future of Hydrogen — Seizing Today’s Opportunities.” IEA, Paris. https://www.iea.org/reports/the-future-of-hydrogen

  27. Keonics (Karnataka State Electronics Development Corporation Limited). “Electronics City Bangalore — History.” Government of Karnataka. https://www.keonics.in

  28. NIT Rourkela. “Placement Report 2023-24.” National Institute of Technology Rourkela. https://www.nitrkl.ac.in

  29. SAIL Rourkela Steel Plant. “About RSP — History and Capacity.” Steel Authority of India Limited. https://sail.co.in/rourkela-steel-plant

  30. Reserve Bank of India. “State Finances — A Study of Budgets 2024-25.” RBI, Mumbai. https://www.rbi.org.in

Source Research

The raw research that informs this series.