# IBM, Infosys, and Wipro entered Kochi. Only one emerged unscathed

Page: https://stenobird.com/podcast/daybreak-5886514/ibm-infosys-and-wipro-entered-kochi-only-one-emerged-unscathed
Text version: https://stenobird.com/podcast/daybreak-5886514/ibm-infosys-and-wipro-entered-kochi-only-one-emerged-unscathed.md
Podcast: [Daybreak](https://stenobird.com/podcast/daybreak-5886514)
Published: 2026-04-26T20:30:00+00:00
Episode link: https://share.transistor.fm/s/5a801225
Audio file: https://media.transistor.fm/5a801225/b02068c0.mp3
Processing state: not_requested
JSON: https://stenobird.com/v1/public/podcasts/daybreak-5886514/episodes/ibm-infosys-and-wipro-entered-kochi-only-one-emerged-unscathed
Duration seconds: 721

## Resource

At Kochi's Infopark, two models of the IT industry sit 500 metres apart. Infosys and Wipro: sprawling campuses, thousands of engineers, margins built on scale. IBM: a smaller hub, senior-heavy teams, focused on enterprise AI. Same city, completely different bets on the future. India's IT giants are expanding into tier-2 cities because they're cheaper. But AI is quietly making the old logic — hire more, deliver at scale — look like the wrong answer. Infosys and Wipro's stocks have nearly halved since 2021. IBM's has doubled. So what does Kochi reveal about where Indian IT is actually headed? Daybreak is produced from the newsroom of The Ken, India’s first subscriber-only business news platform. Subscribe for more exclusive, deeply-reported, and analytical business stories.

## Actions

- request_transcript: `POST https://stenobird.com/v1/public/podcasts/daybreak-5886514/episodes/ibm-infosys-and-wipro-entered-kochi-only-one-emerged-unscathed/transcription-requests` — Idempotently request low-priority transcript generation for this episode.
- read_markdown: `GET https://stenobird.com/podcast/daybreak-5886514/ibm-infosys-and-wipro-entered-kochi-only-one-emerged-unscathed.md` — Read the agent-friendly Markdown representation of this episode resource.

A page view does not enqueue transcription. Agents should invoke `request_transcript` explicitly when they need this episode processed.

## Transcript

Full transcripts are not published on public pages unless there is a clear rights basis.