Dedicated Teams
Your engineering centre in India, without setting up an entity
A dedicated unit in India for a programme too large for a single pod.
Standing up your own captive centre in India means an entity, a lease, a payroll, a compliance function and eighteen months before the first useful commit. For a programme that needs twenty-five engineers, that overhead is real — but so is the alternative of splitting the work across three vendors who each optimise for their own scope.
- Programme-scale capacity without an entity, a lease or a payroll
- One architecture and one standard across every workstream
- A route to owning the centre outright if the strategy changes
Capabilities
What the work actually involves
One unit, one accountability line
Multiple pods under a single delivery head, with shared architecture and one escalation path rather than a vendor per workstream.
Your brand, your process
The centre runs to your engineering standards and your security posture. Several operate under the client's own tooling and identity provider.
Statutory work handled
Employment, payroll, DPDP-compliant data handling, equipment and office are ours. You contract for output.
Scales in both directions
Adding a pod takes weeks. Reducing takes a quarter's notice — stated up front, because the exit terms are what a centre agreement actually turns on.
Transfer path built in
Any centre can convert to a captive entity under Build-Operate-Transfer. The option costs nothing to keep open.
Security controls and audit evidence
Access control, device policy, network segregation and logging run to ISO 27001 controls, with the evidence your own auditor will ask for produced as a matter of course.
Continuity and knowledge retention
Documentation, cross-staffing and recorded decisions so the centre's knowledge survives an individual leaving — the risk that decides whether an ODC is an asset or a dependency.
Deliverables
What you are handed.
Yours to keep, and written so another team could pick them up.
A dedicated unit under one delivery head
Multiple pods, shared architecture, one escalation path — not a vendor per workstream.
Your process and security posture
Several centres run under the client's own tooling and identity provider.
Statutory and facilities handled
Employment, payroll, DPDP-compliant data handling, equipment and segregated space.
Stated exit terms
Notice period and wind-down agreed at the start, because that is what a centre agreement actually turns on.
We do not publish prices — scope drives them. Everything else, here.
- Starts with
- A scoping engagement covering size, security model and exit terms
- Typical duration
- A quarter to stand up; multi-year thereafter
- Who you get
- Fifteen-plus across multiple pods, under one delivery head
- Commercial model
- Monthly, with a quarter's notice
How to decide
What the answer depends on.
Two sets of conditions. Read both against your own situation — most organisations recognise themselves in one column within a sentence or two.
This is the right call when
- A programme too large for one pod and too long for a project.
- A captive entity has been considered and the eighteen-month setup is the blocker.
- You want one architecture across every workstream.
A different approach fits better when
- Fewer than fifteen engineers — two pods will cost you less.
- You need it next month. A centre takes a quarter to stand up properly.
- Data cannot leave your premises under any arrangement.
Before you ask
Questions about offshore delivery centre
Sectors
Where this comes up most.
The regulatory context and the systems already in the building change the build. Each sector page says how.
Next step
Bring us the problem. We will bring the architecture.
A discovery call takes forty-five minutes. You leave with our read on the problem, the shape of the system we would propose, and a straight answer on whether we are the right team for it.
- No sales deck
- An engineer on the call, not an account manager
- NDA before you share anything