For the centre decision that has not been made yet
Scale Your India Centre
An engineering director weighing a captive centre in India is really weighing two different bets. How fast the organisation needs to scale, and how much legal and governance overhead it can absorb along the way, decide the structure before any hiring plan gets written. This practice starts from that decision, then builds the hiring, governance and retention plan the chosen structure actually needs.
The structure decision behind an India centre
Entity versus managed, the ramp plan, and the governance that earns headquarters trust.
90 secSample frame · video pending01Before signing a lease or an incorporation
Entity or managed centre is the real decision.
Leadership often jumps straight to hiring plans before settling the structural question underneath them. Four questions decide which structure actually fits.
How fast do you need to reach real scale?
A managed centre can hire faster in the first year, because the legal and compliance groundwork is already built.
How much legal and compliance overhead can you absorb?
A captive entity brings tax, labour law and compliance obligations that a managed structure defers until scale actually justifies them.
Is this a multi-year commitment or a trial?
A trial or first foray favours a managed structure that can convert later. Certainty from day one favours building the entity directly.
What does headquarters actually need to trust the centre?
Governance and reporting expectations shape the structure as much as cost does, especially for regulated or security-sensitive work.
| Captive legal entity | Managed development centre | |
|---|---|---|
| Time to first hire | Slower, entity setup required | Faster, infrastructure already exists |
| Legal and compliance load | Carried directly by you | Carried by the managed partner |
| Long-term cost at scale | Lower per head at real scale | Higher per head, no entity overhead |
| Reversibility | Harder to unwind | Easier to scale down or convert |
02Agreed before the first hire
The ledger that keeps the centre honest
Centre engagements drift when structure, hiring and governance decisions get made separately instead of together. This ledger fixes what you bring, what gets built, what returns to headquarters, and what stays your decision regardless of structure.
- Your side
You bring
- Your target headcount and how fast it needs to scale
- Appetite for the legal, tax and compliance overhead of an entity
- How committed the organisation is to a multi-year India presence
- Our side
We build
- A costed comparison of captive entity against managed-centre models
- A recommendation grounded in your actual scale and timeline
- A transition path if a managed start should later convert to an entity
- Your side
You receive
- A clear, board-ready recommendation with the trade-offs stated plainly
- A model that will not need reversing once headcount scales
- A realistic cost comparison across both structures
Never leaves you
- The final decision on entity versus managed structure
- All strategic and technical direction for the centre regardless of structure
- The option to convert structures later without starting over
Where the line sitsThe honest answer sometimes favours the model that looks less permanent. A managed centre that converts cleanly later beats an entity stood up before it was needed.
03From a structure decision to a scaled centre
Four stages, each closing on evidence
Centres that stall usually skipped a stage here. Each one closes with something headquarters can act on before the next commitment is made.
Decide the structure against your actual scale
Target headcount, timeline and compliance appetite are tested against both structures before any commitment is made either way.
The structure decision, made with real numbersBuild the hiring and ramp plan
Compensation benchmarks, sourcing channels and a realistic ramp timeline are set against the local talent market, not a headquarters assumption.
A ramp plan built on local hiring realityStand up governance from day one
Reporting lines, delivery metrics and a rhythm with headquarters are established before the centre reaches double-digit headcount.
Governance connected from the first hireScale on measured retention
Headcount grows against a retention target, not just a hiring target, because a centre that cannot keep people cannot really scale.
Retention watched from the first cohort
04What actually moves the number
Four drivers, priced from the structure
Pricing follows the structure chosen and the roles being hired, not a fixed per-head rate. These four factors change the number most.
Structure chosen, entity or managed
A managed centre typically costs less to start and more per head at real scale than a captive entity does.
Target headcount and functions
Specialist or senior functions cost more to source and retain in the local market than general engineering roles.
Compliance and governance requirements
Regulated or security-sensitive work raises the governance and compliance cost regardless of which structure gets chosen.
Speed of the required ramp
A ramp compressed into months costs more per hire than one paced realistically against the local hiring market.
05Evidence and proof
Centres that scaled past their first plateau.
Centre proof is retention that held past year one and governance headquarters actually trusts. These previews carry that standard while written client approvals are collected.
Explore case studiesA structure decision that avoided an entity nobody needed yet.
Aster North planned to incorporate in India before checking the numbers. A costed comparison showed a managed start met their two-year plan at far lower risk.
- Entity overhead avoided
- Deferred until scale justified it
- Time to first hire
- Weeks, not a full quarter
A first centre that hit its year-two retention target.
Tern needed an engineering presence in India within a year. A ramp plan built on local compensation data delivered a staffed centre that held together past year one.
- Headcount at 18 months
- On plan
- Year-two retention
- Met the stated target
Headquarters stopped asking me to explain the centre every quarter, because the reporting finally answered the question before it was asked.
Sample · pending client approval
06Read this first
When a captive entity is the wrong move
Committing to an entity before scale or timeline justifies it locks in overhead the business may not need yet. The exits are marked plainly. When a centre is justified, it draws on the same India talent market and delivery discipline as any engagement here.
- Development Centers
Headcount needs are still genuinely small
A handful of roles rarely justifies a centre of either structure; a smaller managed-services engagement may fit better.
- Team extension
You need capacity now, not a structure decision
If the pressing need is engineers on a roadmap this quarter, extending the team is faster than any centre model.
- Delivery Pods
The centre already exists and just needs delivery capacity
If structure and governance are settled and the gap is delivery, a delivery pod fits better than a centre engagement.
| Shape | Best when | You direct | We carry |
|---|---|---|---|
| Structure assessment | Entity versus managed is still undecided | The final structural decision | A costed comparison and recommendation |
| Centre build | The structure is chosen and hiring can start | Culture, roles and priorities | Hiring, ramp and governance setup |
| Managed centre | Speed matters more than owning the entity | Delivery priorities and standards | The entity, compliance and infrastructure |
07Straight answers
Asked before ground gets broken in India.
01What is the difference between this and your development centers page?
That page covers a managed-services model for running a centre without incorporating your own entity. This page is the decision layer above it, covering whether a captive entity or a managed structure fits your scale.
02How long does it take to set up a captive entity in India?
Incorporation and compliance groundwork typically take a few months before the first hire can start. A managed centre can begin hiring sooner, which is often why organisations start there and convert later.
03What is realistic attrition for an India centre?
It varies by function and city, and the honest number is set against your specific roles rather than a generic industry figure. Retention planning starts with that number, not after it becomes a problem.
04Can a managed centre convert into our own legal entity later?
Yes, and that path is common. Starting managed defers the compliance overhead until headcount and commitment genuinely justify incorporating directly.
05How is compensation benchmarked for the centre?
Against current local market data for the specific functions and seniority you are hiring, not a headquarters number translated at an exchange rate. Retention depends on getting this right early.
06What does headquarters actually need to see from the centre?
Reporting on delivery, attrition and cost against plan, at a rhythm agreed before the centre scales past its first cohort. Governance built in from day one avoids retrofitting trust later.
07What does setting up a centre cost?
It follows the structure chosen, target headcount and the functions being hired. A managed start typically costs less upfront than incorporating an entity before scale justifies it.
08Our centre already exists but has stalled. Can you help?
Yes, a stalled centre is usually a retention or governance problem rather than a hiring one. The diagnosis starts with attrition data and where headquarters reporting is actually breaking down.