What is a Global Capability Center, and why were you locked out of one?

Ask a middle-market CEO what a GCC is and you'll usually get a shrug. Ask a Fortune 500 CFO and you'll get a tour. Somewhere in Manila or Bengaluru, her company runs an office full of accountants, engineers, and analysts who have worked for it for a decade. The building rarely shows up in the annual report. The advantage shows up everywhere else.

What a Global Capability Center is

A Global Capability Center, or GCC, is an offshore operation that a company builds and owns itself. The people are the company's own employees. The work is core work: financial reporting, engineering, data and analytics, risk, customer operations. Despite the offshore address, nothing about it is a call center.

The older industry name is a captive center, and captive is the operative idea. The team serves one company. It holds that company's context, learns its systems, and gets better at its specific work every year. An accountant in a bank's GCC learns that bank's close process, then its reporting quirks, then the judgment calls behind them. A decade in, she is one of the people who knows how the place actually runs.

The scale of this is easy to miss because the centers are deliberately unglamorous. NASSCOM, the Indian tech-industry association, counts more than 1,700 GCCs in India alone, with over 1.9 million professionals inside them. Hundreds of the Global 2000 run one. JP Morgan runs tens of thousands of skilled operators in centers like these, and the work is real work for the parent company: closing books, managing risk, building software. The centers cluster where deep talent lives: Bengaluru, Hyderabad, Manila, Cebu, Warsaw, Mexico City.

The difference between a GCC and outsourcing

The difference is ownership. An outsourcing firm sends you work done by its own employees, on its own systems, spread across its whole client list. A GCC is your operation. The people work for you, sit inside your processes, and answer to your standards.

That one difference drives everything else. A vendor's economics reward throughput across many clients. A captive team's economics reward depth in one. When an outsourcing contract ends, the learning leaves with the vendor. When a GCC team closes the books for the twelfth quarter in a row, the learning stays in the company, and the thirteenth close is faster than the first.

This distinction explains a lot of middle-market disappointment with offshore work. What most companies have been offered under that word is the vendor model, without the ownership that makes the enterprise version compound. That failure has its own anatomy, and we wrote it up in why most offshore staffing fails.

What it takes to build one

Building a traditional GCC is an enterprise-scale project, and the bill arrives before the leverage does. The standard build requires:

• A legal entity in the host country, stood up and kept compliant by local counsel.
• Real estate in a market the company has never operated in.
• A local HR function covering hiring, payroll, benefits, and employment law.
• A management layer on the ground to run the center day to day.
• A multi-year plan, because the ramp from signed lease to productive operation is measured in years.

Every line on that list is fixed cost. Spread across a thousand seats, fixed cost becomes a rounding error. Spread across a dozen seats, it swallows everything the model was supposed to save. That math decided who got GCCs and who didn't. Nobody kept the middle market out on purpose. The overhead did it.

The model was proven twenty years ago. The price of admission was being enormous.

Can a middle-market company have one?

For most of two decades, the honest answer was no. A $75M company can't amortize a foreign entity, a building, and a standing management layer the way a bank with ten thousand offshore seats can. The structure stayed where the scale was.

Here is the part worth sitting with. The valuable part of a GCC was always the architecture: embedded people, owned context, capability that compounds quarter after quarter. The entity, the real estate, and the management layer were only the wrapper it came in. The wrapper was what cost so much.

The wrapper is what has changed. That same architecture can now be built at middle-market scale, without the entity, the real estate, or the multi-year build. We call the rebuilt version a Mini-GCC, and what a Mini-GCC looks like in practice is its own story.

Kayana creates Mini-GCCs for PE-backed middle-market companies. We design and operate the environment the team works inside, and the design shows up in one number: voluntary turnover runs 3–5% in year one across the teams we build. People who stay carry the context. Context is what compounds.

Quick answers

The category argument continues in the Mini-GCC model. The full framework is in the book. Operational Alpha →