Five models get compared as if they were competing products. They are five points on one axis: how much delivery management you want to own.
This is the map. Each section links to the piece that goes into it properly.
1. The four models, side by side
Staff augmentation, dedicated pods, offshore delivery centres and Build-Operate-Transfer, compared on who directs the work, typical size, who carries hiring and attrition, and where each one stops working.
→ ODC vs staff augmentation vs BOT vs GCC
2. What augmentation really costs
The rate is the visible number. The invisible one is your own engineering leads coordinating people they did not hire — plus onboarding paid again on every rotation. That is why the model stops paying long before its rate becomes uncompetitive.
→ What staff augmentation actually costs to manage
3. Build-Operate-Transfer, honestly
The model is sold as a way to get an offshore team without the risk. What decides whether it works is a clause in the first contract — transfer date, price and mechanism fixed at signature. Where those are left open, it is outsourcing with a friendlier name.
→ Build-Operate-Transfer, step by step
4. The captive entity at the end of it
A GCC is a company, not a team: entity, statutory calendar, employment obligations, facilities, hiring function, local leadership with real authority. Lowest steady-state cost per engineer, highest fixed cost — so the horizon matters more than the headcount.
5. Making it actually deliver
The failure is rarely time zones. It is decision latency, context that lives in one hemisphere, and a rota built on goodwill. Ownership of something end to end removes most of the coordination that distance makes expensive.
→ Making a distributed engineering team deliver
6. Security, IP and the data boundary
Assignment from the first commit, least-privilege access that is logged, engineers working against masked data by default, and a boundary matched to your regulator's rules rather than to a vendor's convenience.
→ Security and IP when engineering happens offshore
7. Against hiring in-house
The comparison before all the others: time to productive, retention risk, the ability to scale down, and fully-loaded cost — including the cases where hiring is simply the right answer.
→ Offshore team vs in-house hiring
Choosing, in four questions
- How long? Under a year, augmentation or a pod. Multi-year, ODC or BOT.
- Who manages? If you have delivery capacity and want control, augmentation. If you would rather buy the management, everything else.
- Permanent capability? If yes, BOT has a destination the others do not.
- What scale? Under five, augmentation. Five to fifteen, a pod. Above fifteen, an ODC. Above roughly fifty and permanent, a captive amortises.
Start one step lower on the axis than the plan assumes. Moving up is straightforward; moving back down means unwinding something.