GCC vs. ODC: Why You Should Own Your Offshore Capability

Labor is typically the largest component of any IT or BPO budget, and salary arbitrage — replacing high-cost onshore positions with lower-cost offshore talent — is one of the most powerful levers available to any organization. Most companies are already doing some version of this through outsourcing vendors. What many of them have not yet done is take the next logical step: bringing that offshore capability in-house through a company-owned Global Capability Center. Less than 25% of Global 2000 companies manage their own Global Capability Center while over 90% have significant offshore resources.

The difference in outcome between the two approaches is significant, and in my experience, consistently underestimated.

Getting the Terminology Right

Before we go further, a few definitions are worth establishing. A GCC (Global Capability Center) is any IT or BPO center where the resources are hired and managed directly by the organization for which the work is performed — typically in an offshore or near-shore location. A GBS (Global Business Services) model layers on top of this, describing the collection of services delivered across multiple locations, and is most commonly used when the focus is on business process operations rather than IT.

If your vendor is providing offshore resources but those people are hired and managed by the vendor — not by you — then what you have is staff augmentation or, if the vendor provides a dedicated physical space, an ODC (Offshore Development Center). These are useful arrangements, but they are fundamentally different from a GCC, and the difference matters enormously to your bottom line.

There is a trend in the published literature to suggest that if your GCC does not create innovation centers of excellence, define core enterprise strategy engines, or adhere to any number of other aspirational frameworks, then your GCC is a failure. I have seen articles claiming that 70-80% of GCCs fail because all they do is save money. If the only thing the centers I created in Romania and India did was save over $200M per year in labor costs, I would not call those GCCs a failure. Yes, we leveraged worldwide talent to do many innovative and interesting projects — but at the end of the day, every GCC is underwritten by salary arbitrage. I have never run a GCC program, or even consulted on one, where budget savings was not a top driver.

The Economics Are Not Close

Outsourced providers typically charge $25 to $45 per hour for India-based IT resources. The fully loaded average cost for the same resource in a company-owned GCC in India runs approximately $20 per hour — and in my experience, the actual savings per FTE tend to be substantially more than that initial gap once you factor in the inevitable team bloat. For a 300-person center in India, that differential alone produces $3 to $5 million or more in annual savings. The overhead costs of running your own entity — compliance filings, management infrastructure, local HR — are real but easily eclipsed by those savings.

The economics are even more pronounced in Eastern Europe. Vendor rates for Romanian IT resources typically run $55 to $80 per hour. The fully loaded cost of the same resource in a company-owned GCC in Romania is approximately $40 per hour. For a 300-person IT center, that spread translates to $9 to $24 million in annual savings. When I established MassMutual Romania, these numbers were not theoretical — they drove every decision we made about pace, scale, and location.

What You Actually Gain Beyond Cost

The financial case is compelling on its own, but three additional advantages make the company-owned model even more attractive.

Control over your organization. When a vendor manages your offshore team, they are incentivized to maximize revenue — which means maximizing headcount. Your interests and their interests are directly opposed. I have seen this play out repeatedly. At one organization I managed, the QA function was running 40 onshore QA managers and 210 outsourced offshore QA resources. When we brought that function in-house into our GCC, we delivered the same work program with 15 onshore and 108 offshore resources. That is not a marginal improvement — it is a complete restructuring of a bloated team that the outsourcer had every reason to maintain and none to shrink.

Control over attrition. High attrition is one of the most destructive forces in any offshore operation, and outsourced relationships are particularly vulnerable to it. Many Indian outsourcers run at 20% or higher annual attrition — meaning you spend a significant portion of your time and budget training the next wave of people who will leave for a competitor. When you own the GCC, you control the culture, the compensation philosophy, and the career development environment. At MassMutual India and Romania, we sustained attrition rates of 6 to 8% — roughly one-third of industry averages. That was not accidental. It was the direct result of deliberate cultural investment from day one, which I will cover in detail in Article 5 of this series.

Control over innovation. Any efficiency or process improvement in a company-owned GCC flows directly to your bottom line. In an outsourced model, the vendor captures that benefit unless you have contractually negotiated annual productivity cuts into the agreement — which many organizations have not.

The 150-FTE Threshold

The question I am most frequently asked is: when does building your own GCC make financial sense? My rule of thumb is 150 offshore resources in a single location. At that scale, the savings comfortably exceed the overhead of establishing and managing a foreign legal entity. I have created GCCs as small as 80 FTEs and seen strong outcomes, so I would not treat 150 as a hard cutoff — but I would insist on a rigorous cost/benefit analysis for anything below that number.

For organizations with fewer than 150 offshore resources, the landlording model is worth considering. This means leasing finished space and infrastructure — possibly including the legal entity and associated compliance functions — from a local company, at a higher per-seat cost but with substantially less administrative overhead. You sacrifice some economics but preserve direct management of your people, which is the most important advantage of the GCC model.

What About the Build/Operate/Transfer Model?

Some organizations prefer to partner with a vendor in a Build/Operate/Transfer (BOT) model, where the vendor builds out the entity, hires the staff, and then transfers it to the organization after a fixed operating period of one to five years. I have never been a fan of this approach. With thousands of GCCs currently in existence worldwide, there is a deep and accessible pool of experienced practitioners who have stood up centers before. Hiring a small, qualified team with that experience and executing the plan directly is faster, cheaper, and gives you control over culture from day one — which is precisely when culture needs to be established.

The expertise you need exists in the talent market. Go find it.

The Real Barrier Is Not Complexity — It Is Perception

The most consistent thing I have observed in organizations evaluating their first GCC is that executives dramatically overestimate the complexity and risk of the undertaking. The core team that established MassMutual India and MassMutual Romania grew those centers to over 2,600 FTEs in less than four years — without expensive consultants and without a BOT vendor. We used experienced practitioners, a clear plan, and top-down executive support.

Establishing a GCC is not nearly as complex, expensive, or time-consuming as most leaders fear. That fear is exactly what drives organizations to overpay for vendor arrangements they do not need. The salary arbitrage opportunity is substantial. The strategic control it returns to your organization is equally valuable. And once you have built the right culture, you will have an operation that is genuinely difficult for competitors to replicate.

In Article 2 of this series, we will get into the details of location selection — comparing India, Eastern Europe, and Latin America at both the country and city level, including the specific decisions that led us to Hyderabad and Bucharest for MassMutual's centers.