A Global Capability Centre (GCC) is a captive unit: your entity, your employees and your budget line, in India. That is the difference from every vendor arrangement, and it explains both the control and the overhead. In this article GCC means Global Capability Centre. In Gulf news the same letters mean the Gulf Cooperation Council.
You are taking on a company, not a team
The engineering is the smaller part of the project list.
- A legal entity. It needs incorporation, directors, a registered office and regular filings, and the filings fall due even in a quiet month. The MCA's integrated SPICe+ form bundles incorporation, a director number, PAN, TAN and provident fund and state insurance registration, according to the PIB announcement of 24 February 2020. Check the current form on the MCA portal.
- Employment obligations under Indian law, with their calendar of payments and filings. Take advice from an employment lawyer and a chartered accountant.
- Premises, and a policy on office and remote work that you decide and do not inherit.
- A hiring function for a market whose pay and notice norms differ from the parent's.
- A local leader with decision rights. If every decision is made from abroad, the centre turns into a unit that only takes orders.
- Finance and tax. Ask your chartered accountant how payments between the parent and the centre must be priced and documented.
None of it is difficult. But none of it is the engineering that justified the centre, and companies routinely plan too little time for it.
Fixed cost against cost per engineer
A GCC has the highest fixed cost and, once running, the lowest cost per engineer. The other models trade the two the other way. Price these lines for each option rather than relying on a headline break-even.
| Model | Fixed cost | Cost per engineer | Control | Commitment |
|---|---|---|---|---|
| Staff augmentation | None | Highest | Task level | Short |
| Dedicated pod | Low | High | Team level | Months |
| Offshore delivery centre | Moderate | Moderate | Process and brand | A year or more |
| GCC | High | Lowest at scale | Full | Years |
Lines to price for each: recruitment, salaries and statutory costs, premises, equipment, management time on your side, legal and accounting, and the cost of closing the unit if plans change.
Horizon matters more than headcount. A large team needed for eighteen months rarely justifies an entity, while a smaller team needed for ten years may. ODC, staff augmentation, BOT and GCC compared sets the models side by side.
How to compare cities
City rankings change each year, so compare on measures you collect for your own roles.
| Measure | How to get it |
|---|---|
| Depth of the talent pool for your specialism | Ask three recruiters for the number of senior candidates they could present within a month |
| Pay for your roles | Use a current salary survey and quotes from your recruiters |
| Attrition | Ask recruiters and peer centres what they see for your roles |
| Senior hiring | Count how many staff-level or principal engineers each city offers |
| Cost of premises and talent competition | Ask what other centres in the area are hiring for |
Large metros usually offer breadth and competition for the same people. Smaller cities may offer lower costs and steadier retention, with a thinner market for senior roles. When the centre must grow its own technical leaders, the senior market can settle the choice by itself.
Each city trades one problem for another.
Two routes to a centre
Direct setup: you hire and run it
Form the company, appoint a country lead and grow from there. You hold full control from the first day. It suits a parent that already has experience in India or an entity there.
The risk lies in the order of hiring. Either the first engineers arrive with nobody who knows the market to manage them, or a manager arrives with nothing to manage. Sorting out that gap can take the whole first year.
Build-Operate-Transfer: a vendor runs it first
Under this route a vendor stands up and operates the team inside its own company, and hands it over on terms agreed at signing. Delivery begins sooner, and you form your own company once the capability has proved itself. The BOT step-by-step guide lays out each stage.
BOT also postpones the step that is hard to reverse, the creation of your own entity, until the team has proved itself. Compare its fees with your direct-setup costs before choosing.
A first-year sequence
- Write the mandate in one page: what the centre owns, who decides and how success is measured.
- Appoint the country lead before the first engineer, with budget authority.
- Hire a founding group that covers the product, not a single skill.
- Give the centre an end-to-end area of work in the first quarter, not a list of tickets.
- Set up governance: a monthly review with the parent, a shared roadmap and a named sponsor.
- Write down the exit: how you would scale down, close or hand over, and what it would cost.
The failure nobody plans for
It is rarely cost or quality. It is mandate drift.
Picture a centre created to own a product. In its first year it is asked for maintenance help by the parent's other teams, and it says yes to prove its worth. Two years on it is a support function, and hiring is hard because experienced engineers avoid support roles.
Three structural defences help:
- Hand the centre a whole product or service early.
- Base a person with decision rights in the centre, not a coordinator.
- Measure outcomes and not tickets closed.
Managing a distributed engineering team covers the day-to-day side, and offshore engineering, security and IP covers protecting the work.
Governance that keeps the centre connected
A captive centre needs the same governance as any business unit. Settle these before the first hire:
- A sponsor in the parent with authority over budget and priorities.
- A monthly review of outcomes, hiring, attrition and spend, attended by the country lead.
- A shared roadmap, so the centre's work appears on the parent's plan and is not a side list.
- Access and security standards that match the parent's, applied from day one.
- Rotation of parent staff through the centre in both directions, which builds trust faster than reports do.
Review the mandate each year. If it has drifted, correct it while the team is still small enough to move.
When a GCC fits
| Fits | Does not fit |
|---|---|
| The capability is permanent and core | The need is a project with an end date |
| Your roadmap will keep a sizeable team busy for years | The roadmap is uncertain |
| You can name a senior leader to run it | No one in the parent will own it |
| You want hiring and culture under your control | You want delivery without running a company |
If you are unsure, an offshore delivery centre gives most of the delivery benefit without the statutory commitment. An entity built for work that proves temporary can take years to wind down.
Questions teams ask
What does GCC stand for here?
Global Capability Centre, a captive engineering or business unit. It has no link to the Gulf Cooperation Council.
How long does setup take?
It depends on hiring more than on incorporation. The legal entity can be formed through the MCA form above. Recruiting a lead and a founding group sets the pace.
Can a vendor run the centre for us first?
Yes, under a Build-Operate-Transfer contract that fixes the transfer terms at signing.
Where Brihat fits
Brihat Infotech runs an offshore delivery centre for clients, with statutory work, payroll and premises handled by Brihat, and offers Build-Operate-Transfer as the route to your own entity. Start a conversation.