Philippines or India: two offshore ecosystems, built for two different kinds of work

Both countries built enormous offshore industries over the last forty years, and they built them around different work. India's grew out of software and engineering contracts, where a scope is written in one place and executed in another. The Philippines' grew out of customer-facing operations, where the work happens while someone on the other end is waiting.

That difference still shapes what each ecosystem recruits for, how it manages, and what it scales well. It is a more useful question than which country has better people, and it has a clearer answer. Talent is distributed evenly across both. Ecosystems are not.

How India's offshore ecosystem was built

India's ecosystem was built around work that could be specified in one location and executed in another.

Industry histories date the first centers to 1985, when Texas Instruments and Citibank opened wholly owned operations in Bengaluru and Mumbai. We have written the era-by-era version of that story in how the offshore model got smaller every decade. What matters here is what the services industry did with it next.

Indian services firms formalized the arrangement into what Infosys named the Global Delivery Model. Industry accounts describe the traditional split as roughly seventy percent of the work performed offshore and the rest onsite with the client, with handoffs at the end of each day shift. The industry called it follow-the-sun. The time gap between India and the United States was treated as an asset. Work went out at the end of a US day and came back finished.

Four decades of that produced extraordinary depth. In its Strategic Review 2026, NASSCOM, the Indian tech-industry association, put the sector at roughly $297 billion in revenue for FY25. Its 2024 landscape report with Zinnov counts more than 1,700 Global Capability Centers in India employing over 1.9 million professionals, with engineering and R&D among the fastest-growing pieces of it.

If your work has a scope, a volume, and a clean definition of finished, that ecosystem was built for it, and nothing else in the world matches its depth.

How the Philippine ecosystem was built

The Philippine ecosystem was built around work that happens live, while someone on the other end is waiting.

Industry histories date the start to 1992, when Accenture opened a contact center in Manila. The Special Economic Zone Act followed in 1995, Sykes arrived as the first multinational BPO operator in 1997, and the sector compounded from there. By 2010 Bloomberg reported that the Philippines had passed India in call-center headcount. IBPAP, the industry association, put the sector at $38 billion in revenue and 1.82 million employees in 2024.

The founding work could not be handed off. A conversation happens in real time or it does not happen at all. So the ecosystem organized itself around being awake when the client is awake. Working United States hours became the norm rather than the exception, institutionalized down to the labor code, which requires a night differential for hours worked between ten at night and six in the morning.

That is a structural fact about an industry, and structural facts compound. Recruiting, management practice, career expectations, and family life in that sector all formed around presence inside a foreign business day. Nearly two million people have built careers on it.

Which ecosystem fits the work you are moving

The fit follows from one question: can the work be fully specified before it leaves?

Some work can. A locked procedure. A defined migration with a clean spec. High-volume processing with hard turnaround times. Engineering built to a requirements document. Handing that across a time gap is efficient, and it is the work forty years of Indian delivery infrastructure was designed to carry.

Other work cannot be specified in advance, because specifying it is most of the job. A controller who needs to ask why a number moved before the close can finish. An analyst who has to absorb the priority that changed on Tuesday morning. A coordinator holding an order desk while customers are calling. Work like that degrades every time it waits for a handoff. It needs someone in the room.

That is the same distinction that separates an embedded team from an outsourced one, and it decides more than the choice of country does.

One ecosystem was built to receive work that was already specified. The other was built to be in the room while it happens.

Why a Mini-GCC runs on the collaborative shape

A Mini-GCC runs on the collaborative shape because an embedded seat cannot be handed off at the end of a shift.

The seats are finance, operations, analytics, and executive support inside one middle-market company. The people in them join the standups, work inside the company's systems, and follow the plan that changed this morning. None of that survives a nightly package-and-return. The whole design depends on presence, which is why the environment around the seat carries so much weight. That environment is the interface between the work and the people doing it, and it is the part most offshore attempts skip.

That is why Kayana builds in the Philippines. The work our clients hand us is collaborative work, and we build where the ecosystem formed around it. We design and operate the environment the team works inside, and the design shows up in one number. Voluntary turnover across the teams we build runs 3 to 5 percent in year one. People who stay hold the context, and context is what compounds.

The category argument itself lives in the Mini-GCC model.

Quick answers

The full framework is in the book. Operational Alpha →