- GCC and GBS setups in India rarely collapse outright. They stall. Headcount lands, payroll runs, audits pass, and the mandate never actually transfers.
- Compliance failures carry a filing date, a penalty and a named owner, so they get fixed. Sequencing failures carry none of the three, which is why they run for two years without reaching a status report.
- The most common design flaw is the mandate: a center set up to cut cost gets measured on cost, and never earns the work that would justify it.
- Governance is the second. When budget and hiring decisions route back to headquarters, approvals add weeks and India's talent market simply moves on.
- Check your own markers at months 6, 12, 18 and 24. Each stage has a different failure mode and something you can look up in your own filings, attrition report or org chart.
Need help getting your India center on track? Talk to an expert!
Discover how Wisemonk creates impactful and reliable content.
Two years into an India center and still wondering why it has not become what you planned?
Most GCC and GBS setups in India do not fail loudly. They stall quietly. The headcount is there, the payroll runs, the audits pass, and the work you meant to move never moves.
That is the hard part to catch. A missing outcome does not raise a ticket.
Below: the failure drivers by cause, the mistake behind each, and a month-by-month timeline of what to check.
Why do GCC and GBS setups in India fail in the first 24 months?
Five causes, and none of them is a shortage of talent. The mandate is written as cost saving, governance keeps decisions at headquarters, leadership is hired as site administration, pay is benchmarked against stale data, and the compliance work is attempted without local experts.
The useful split is between failures that force their own resolution and failures that do not.
- Compliance failures: these carry a filing date, a penalty and a named owner. Painful, but they get fixed because somebody has to sign something.
- Sequencing failures: these carry none of the three. Nothing is late, nobody is fined, and no owner is named, so they run for two years unnoticed.
| Failure driver | The mistake | The consequence |
|---|---|---|
| Mandate | Positioning the center on cost savings rather than capability | Stagnation, loss of headquarters interest, and high attrition |
| Governance | Running the center through slow, distant approval layers | Delayed hiring cycles and a local team that stops deciding anything |
| Leadership | Hiring an administrative site manager instead of an empowered leader | Low ownership, weak alignment, and every decision bottlenecked offshore |
| Talent and pay | Benchmarking compensation against outdated data in a fast-moving market | Offers declined, heavy first-year attrition, roles open for months |
| Operations and compliance | Attempting Indian tax, SEZ and state labour registration without local experts | Delayed launch dates, compliance exposure and budget overruns |
Each of those five is worth a closer look, because the mistake and the fix are usually different people's jobs.
What goes wrong with the mandate and the operating model?
The center gets briefed as a cheaper way to do existing work, so it is measured on cost and never earns the work that would justify it. The underlying flaw is treating India as an offshore delivery mechanism rather than a strategic extension of the business.
- Cost arbitrage as the whole thesis: once the savings are banked there is no second act. The reasons companies set up a GCC in India have to include something beyond price.
- The green dashboard problem: hitting every service level on low-stakes administrative work looks like success. It is how a center stagnates while reporting green.
- Briefing it like a vendor: if you manage the center as an outsourcing contract, it behaves like one. That is the trap when you move from outsourcing to a GCC in India.
- Rigid top-down structures: conventional operating formats suppress the local initiative you set the center up to get. Captive engineering centers in India that work are the ones given a product to own.
A weak mandate is survivable if the local team can still make decisions. Usually it cannot.
How does remote governance slow an India center down?
By adding weeks to decisions in a market that does not wait. When budget, hiring and product calls all route back to headquarters, the local leader is accountable for outcomes they cannot control, and candidates accept other offers in the meantime.
- No local decision rights: parents often withhold budget and product ownership, which leaves the India lead running a team rather than a business.
- Hiring lost to approval layers: every extra week costs you candidates. Wisemonk publishes 30 to 45 days to source an India Head, and the hiring timeline in India shows where the rest of the clock goes.
- Escalation as the default: when minor decisions become a call with headquarters, the team learns to stop deciding. That habit is hard to reverse later.
- Culture read as compliance: a team that agrees in the meeting and escalates afterward is usually a governance signal, not a personality one. Work culture in India is worth reading before you diagnose it.
Governance problems show up first in hiring. Pay problems show up right behind them.
Why does the cost-arbitrage playbook stop working?
Because the saving is a one-time gain and the sponsor expects a trend. A center that has not moved from cost reduction to capability loses its executive backing, and stale pay benchmarks make the talent side fail at the same time.
- Cost per head is the wrong headline after year one: Wisemonk publishes 40 to 60% total operating savings against a US team as of September 2026. That is a starting position, not a strategy. Full model: the cost of setting up a GCC in India.
- Stale pay benchmarking: offers built on last year's data get declined in competitive hubs, and the role stays open while the plan slips.
- First-year attrition: Wisemonk publishes Bengaluru attrition at around 25%, adding 15 to 20% to real annual cost per engineer, as of September 2026. See managing attrition in India.
- Why churn compounds here: in a small center, losing a process owner removes a whole process rather than a fraction of one.
Those are strategy problems. The next set hold up a launch date.
Which compliance and location mistakes delay a launch?
The ones with their own clocks. State labour registration, employer registrations, SEZ or STPI approvals, transfer pricing and data privacy each run on a timeline you do not control, and a city picked on brand rather than talent supply produces attrition you cannot hire through.
- Labour law is state by state: rules and registrations vary by state, so a single national plan is not a plan. Start with labor and employment law in India.
- Registration clocks: Wisemonk publishes Shops and Establishments at 1 to 4 weeks per state and SPICe+ incorporation at 8 to 12 weeks, as of September 2026. See the timeline to launch a GCC in India.
- The rulebook moved: Wisemonk publishes India's four labor codes as in force from November 2025. What was consolidated is in the new labour code in India, as of September 2026.
- Monthly filings start with the first pay run: Provident Fund, professional tax and TDS do not wait for the center to be finished. The full list is statutory compliance in HR in India.
- Payroll set up late: a center that hires before its registrations are live cannot pay people in its own name. Payroll compliance in India is the sequence to get right first.
- Tax exposure before the entity exists: once the entity trades with the parent, transfer pricing comes under scrutiny. Before it exists, the exposure is permanent establishment risk in India.
- Location chosen on the wrong criteria: a Tier 1 hub without a retention plan produces attrition, and a Tier 2 city without checking niche talent supply stalls scaling. Weigh it with are Tier 2 Indian cities worth it for offshore hiring.
- IP hygiene left until later: assignment language belongs in the first contract, not the fiftieth. Protecting intellectual property when hiring in India covers the clauses.
- Unproven local partners: rushing real estate, payroll or security vendors delays launches more often than the regulator does. Compare GCC setup consultants in India before committing.
India center not landing the way you planned?
Tell us where it is stuck and we will walk the mandate, the hiring sequence and the compliance clocks with you.
What does the 24 month failure timeline actually look like?
Four stages, each with its own failure mode and its own marker you can check without asking anyone. Month 6 is administrative, month 12 is where assumptions meet the market, month 18 is where deferred decisions start costing money, and month 24 is where the parent reframes the center as a cost line.
| Stage | What typically goes wrong | What you can check yourself |
|---|---|---|
| Month 6 | Administrative setup lags. The leader seat is open and state or employer registrations are incomplete | Your own filing records, and whether the India lead has actually started |
| Month 12 | Assumptions meet the city. Attrition runs above plan, governance friction shows, and scope has not transferred | Your attrition report, and the list of processes genuinely running in India |
| Month 18 | Deferred structural decisions start costing money. Transfer pricing timing, cost per head, the seat still open | Cost per head against plan, and how long each open role has been open |
| Month 24 | The parent reframes the center as a cost line. Knowledge leaks out and new work stops routing there | Whether new work is being assigned to India without anyone having to ask for it |
None of those four markers needs a consultant to read. They sit in systems you already own.
How do you avoid these failures in the first place?
Give the center a written mandate, a leader with real budget authority, and pay benchmarks that are current. Then let people who have done it before handle the entity and compliance work, and do not hold the first hires behind the incorporation.
- Write the mandate down: name the products or processes the center will own, and the date each one transfers. An unwritten mandate is the one that never arrives.
- Empower one accountable leader: budget and hiring authority, in writing. Hire that seat early, because it is the longest-lead item in the plan.
- Benchmark pay to the current market: not to last year's data and not to the parent's assumptions about India. Re-check before each hiring round.
- Sequence compliance alongside hiring: registrations run in parallel with recruiting, not after it. The order is in how to set up a GCC in India.
- Do not block the first hires on the entity: hiring via an EOR while your India GCC is being set up keeps both clocks running, which removes the month 6 failure mode entirely.
- Agree the vocabulary internally: teams arguing about what the center is usually disagree about what it owns. Settle it with GBS vs GCC vs SSC in India.
If you would rather not carry the build yourself, global capability centers in India sets out a structure where the entity is incorporated in your name from day one and control graduates to you over time.
How can Wisemonk help you get an India center working?
Wisemonk is an India-native Employer of Record (EOR) that helps global companies hire, pay, and manage talent in India without setting up a local entity.
For a stalled center, that usually means getting people employed and paid compliantly first, so the mandate has somewhere to land.
We do not run your governance or set your mandate. Those stay with you. We carry the employment, payroll, filings and registrations underneath.
We support 300+ global clients and more than 2,000 employees across India, process $20M+ in annual payroll, and hold a 4.8/5 rating on G2. Pricing starts from $99 per employee per month as of September 2026.
Here is how we help:
- Entity setup: incorporation and the tax and employer registrations, filed in your own company's name from the first form onward.
- PEO: payroll, Provident Fund, professional tax and TDS filings run under your own registrations once the entity is live, with equipment procurement and shipping alongside it.
- Managed payroll: the India pay run and its monthly filings executed while your team keeps the entity and the HR function.
- TalentScout: post roles to a vetted India candidate community and screen every applicant against your own scorecard.
- Background verification: identity, education, employment and court record checks before somebody joins the team.
GCC setup, managed payroll and entity setup are quoted to scope.
Ready to get your India center moving?
Tell us where the build stalled and we will come back with the sequence, the compliance clocks and how fast we can have people working.
Frequently asked questions
Do GCC setups in India usually fail outright?
Rarely. The common outcome is a stall rather than a collapse. Headcount lands, payroll runs and audits pass, but the work you meant to move never moves. A missing outcome does not raise a ticket, which is why it can run for two years unnoticed.
What is the single most common reason an India center underperforms?
The mandate. A center briefed as a cheaper way to do existing work gets measured on cost, so it never earns the work that would justify it. Talent supply is almost never the constraint. The brief is.
Why does governance from headquarters slow an India center down?
Because approvals add weeks and the local market does not wait. When budget and hiring calls route back to the parent, strong candidates accept other offers, and the team learns to escalate instead of deciding. Give the India lead written decision rights.
How much does attrition add to the cost of an India center?
Wisemonk publishes Bengaluru attrition at around 25%, adding 15 to 20% to the real annual cost per engineer, as of September 2026. In a small center it hurts more, because losing a process owner removes a whole process rather than part of one.
Which compliance steps most often delay an India launch?
State-level registrations and incorporation. Wisemonk publishes Shops and Establishments at 1 to 4 weeks per state and SPICe+ incorporation at 8 to 12 weeks, as of September 2026. Both run alongside hiring, so starting them late moves your launch date.
Is a Tier 2 Indian city a safer choice for a new center?
Only if the niche talent you need is actually there. Tier 1 without a retention plan produces attrition you cannot hire through. Tier 2 without checking supply stalls scaling later. Check the specific roles, not the city's general reputation.
Can you start hiring before the Indian entity is registered?
Yes. An Employer of Record becomes the legal employer, so people can start on compliant contracts while incorporation runs in parallel. That removes the month 6 failure mode, where the plan slips because nobody could be paid yet.
Ready to build your India team?
Tell us who you're looking to hire. We'll walk you through exactly how the setup works for your company, your timeline, and your budget.
