Dedicated Teams
Build the team here. Own it later. Agree the terms now.
We build the team, run it, then hand you the keys — on a date agreed up front.
Building an India team yourself is slow and risky; outsourcing it permanently means the capability never becomes yours. Build-Operate-Transfer is the answer to both.
- A working India team without eighteen months of entity setup first
- An exit price known on day one rather than discovered at the end
- A capability that ends up on your balance sheet, not ours
Capabilities
What the work actually involves
Transfer terms agreed at signature
The date, the price and the mechanism are in the first contract, not negotiated at the point you want to leave.
Build
We recruit against your hiring bar, not ours, and you approve every offer. These people are being hired to eventually be yours.
Operate
We run delivery, management and statutory compliance for an agreed period — usually eighteen to thirty months — while the team matures on real work.
Transfer
Employment moves to your entity, with retention arrangements agreed in advance so the transfer does not trigger the departures it exists to prevent.
Or do not
If the strategy changes, the centre continues as a standard engagement. The option lapses without a penalty.
Entity and statutory setup
Incorporation, registrations, payroll and compliance run under our licence during the operate phase, structured from the start so the transfer is an assignment rather than a rebuild.
Transfer readiness reviews
Checkpoints through the operate phase against the handover criteria agreed at signature, so readiness is a tracked measure rather than a judgement call at the end.
Deliverables
What you are handed.
Yours to keep, and written so another team could pick them up.
Transfer terms in the first contract
Date, price and mechanism agreed at signature.
Recruitment against your hiring bar
You approve every offer. These people are being hired to eventually be yours.
A managed operate phase
Delivery, management and statutory compliance held by us while the team matures on real work.
A transfer plan with retention designed in
Engineers are told the plan when hired, so the transfer does not trigger the departures it exists to prevent.
We do not publish prices — scope drives them. Everything else, here.
- Starts with
- A term sheet covering the transfer date, price and mechanism
- Typical duration
- Eighteen to thirty months of operate, then transfer
- Who you get
- Scaled to the target org, under a Brihat delivery head
- Commercial model
- Monthly during operate, fixed transfer fee agreed at signature
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
- You want an India team eventually on your own books.
- Eighteen months of entity setup before the first commit is the blocker.
- You want the exit price known on day one.
A different approach fits better when
- You want to outsource permanently — a delivery centre is simpler and cheaper.
- Fewer than ten people. The transfer machinery costs more than it returns.
- No intention of ever incorporating in India.
Before you ask
Questions about build-operate-transfer
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