Build Operate Transfer vs Dedicated Team: Which to Choose
Build Operate Transfer and the dedicated team model are closer to each other than either is to staff augmentation. Both give you a structured offshore team working under your technical direction. Both use a provider to manage operations. Both offer more stability and cohesion than individual contractor placements.
The difference is fundamental: in a dedicated team engagement, the provider never exits. In a BOT engagement, the provider's exit is the point.
That single distinction drives every other difference — in cost structure, in contract terms, in team retention dynamics, and in what the engagement looks like five years from now.
Quick answer: Choose BOT if you intend to own the team eventually and your horizon is 2+ years. Choose a dedicated team if you want a stable, provider-managed team indefinitely with no intention to take on employer responsibility in the delivery country.
Quick Comparison
| Factor | Build Operate Transfer | Dedicated Team |
|---|---|---|
| Provider exit | Yes — at Transfer | No — provider remains indefinitely |
| Client owns team at end | Yes | No |
| Time to operational team | 3–5 months | 4–8 weeks |
| Management model | Provider manages ops, client directs work | Same |
| Long-term cost | Lower post-Transfer | Permanent margin |
| Minimum viable horizon | 24+ months | No minimum |
| Team size fit | 8–80+ people | 3–50 people |
| Regulatory complexity | Managed by provider, transferred to client | Managed by provider, stays with provider |
| Best for | Building permanent offshore capability | Stable long-term team without ownership intent |
What Is a Dedicated Team Model?
In a dedicated team arrangement, the provider assembles a team exclusively for one client and manages it for the duration of the engagement. The team works under the client's technical direction — same as BOT — but the employment relationship, office, and operational management remain with the provider permanently.
The client does not become the employer. The provider does not exit. The arrangement continues indefinitely, renewed or adjusted by agreement, until the client decides to terminate.
What dedicated teams are good at:
- Stability without ownership complexity — you get a committed team without becoming a foreign employer
- Shorter time-to-team than BOT — no Build phase setup; providers draw from existing bench or fast-track recruitment
- Flexibility — easier to scale up or wind down than a BOT structure with contractual milestones
- No Transfer planning — the engagement ends when you choose, with agreed notice period
What dedicated teams are not good at:
- Long-term cost efficiency — provider margin is permanent, unlike BOT where it disappears at Transfer
- Creating genuine ownership — the team is always the provider's, which affects how team members identify with the client
- Negotiating leverage over time — the provider retains the employment relationship, which gives them structural leverage if the commercial relationship deteriorates
What Is Build Operate Transfer?
In a BOT engagement, the provider builds an offshore team to the client's specification, operates it through a defined period, and then transfers full operational ownership — employment contracts, office, equipment, and institutional knowledge — to the client at a pre-agreed point.
The provider exits. The client becomes the direct employer. The team becomes part of the client's own organisational structure.
For a full explanation, see What is Build Operate Transfer?
Key Differences
The exit question
This is the defining structural difference. In a dedicated team model, the provider is a permanent participant in the commercial relationship. The team is their asset, staffed by their employees, housed in their office. The client is the customer.
In BOT, the provider is a temporary participant with a contractually defined exit. The client is building toward ownership. The provider's role diminishes as the client's ownership increases.
This is not just a philosophical distinction. It shapes:
- Retention dynamics: Dedicated team employees know they work for the provider. They may be redeployed to other clients. They may leave for the provider's own projects. BOT team employees know they work for one client and that this relationship may lead to direct employment by that client — a stronger retention incentive.
- Pricing power: In a dedicated team, the provider can adjust commercial terms at renewal because the client has limited leverage — leaving means losing the team. In BOT, the Transfer removes that leverage permanently.
- Team identity: A BOT team, built for one client and managed toward Transfer, typically develops stronger identification with the client's mission than a dedicated team, which may serve multiple clients over the provider's portfolio rotation.
Contract structure
Dedicated team contracts are simpler: a master services agreement, a statement of work defining the team, and a commercial schedule. Renewal is annual or biennial. No Transfer provisions required.
BOT contracts are more complex: MSA plus phase schedules for Build, Operate, and Transfer; employment framework agreement; Transfer mechanics; IP assignment provisions. See Build Operate Transfer Contract for the full structure.
The added complexity of a BOT contract is the price of the ownership right. It is worth it if ownership is the goal. It is unnecessary overhead if it is not.
Setup time
Dedicated teams can be assembled in 4–8 weeks for teams of 5–15 using the provider's existing bench and fast-track recruitment. BOT's Build phase takes 3–5 months because it is building an organisational unit from scratch — office, legal structure, governance framework — not just placing individuals.
For clients with urgent headcount needs, the dedicated team model is faster. For clients planning 6+ months ahead, the BOT Build timeline is not a constraint.
Cost Structure Over Time
This is where the decision often becomes clearest.
Assume a 20-person senior engineering team, 48-month engagement horizon.
| Period | Dedicated Team | BOT |
|---|---|---|
| Month 1–3 | Lower — no setup fee | Higher — Build phase fees |
| Month 4–36 | Per-head rate + permanent margin | Per-head rate + provider margin |
| Month 37–48 | Per-head rate + permanent margin | Direct employment cost only |
| Total 48-month cost | Higher by 12–20% vs BOT | Lower — margin eliminated at Transfer |
| Total 60-month cost | Higher by 20–30% vs BOT | Increasingly lower |
The dedicated team is cheaper to start and more expensive to sustain. BOT costs more to start (Build phase) and less to sustain (post-Transfer). The crossover typically occurs at Month 26–32 depending on team size and provider margin.
Companies that are certain they will run the engagement beyond 36 months almost always find BOT cheaper in total cost of ownership. Companies uncertain about the horizon beyond 24 months often prefer the dedicated team's flexibility, even at higher long-term cost.
Ownership and Control
Both models give the client technical control — sprint planning, architecture, code quality, product direction. The provider manages people operations in both.
The difference is in ultimate ownership:
Dedicated team: If the commercial relationship breaks down, the provider retains the team. The client loses the people, the institutional knowledge, and the operational history. Rebuilding takes months. This is the structural risk of permanent provider ownership.
BOT: Post-Transfer, the client owns the team. If the relationship with the former provider deteriorates, the client has already exited. There is no hostage situation.
For core engineering functions where the team holds critical product knowledge, this ownership distinction is significant. For less critical or project-specific functions, it matters less.
Team Stability and Retention
Both models produce more stable teams than staff augmentation, because the team is built as a unit rather than assembled from individuals.
The difference is in retention incentive:
In a dedicated team, the provider employs the team. The provider can redeploy team members to other clients, offer them roles in other engagements, or lose them to the provider's own internal mobility. The client has no direct control over these decisions.
In a BOT engagement, the team is built for one client and the employment relationship will eventually transfer to that client. Team members who value stability and the prospect of direct employment by a recognisable company have a stronger reason to stay. BOT engagements consistently report lower attrition than equivalent dedicated team arrangements — typically 10–15% annually vs 20–30% for dedicated teams at comparable seniority.
When to Choose a Dedicated Team
Use the dedicated team model when:
- You do not intend to become an employer in the delivery country. Transfer requires the client to establish a local legal entity and manage employment directly. If that is not feasible or desired, BOT's Transfer phase is unexecutable — a dedicated team is the right model.
- Your horizon is under 24 months. The economics of BOT require you to reach Transfer to recoup the setup cost. If the engagement is likely to terminate before Month 24, a dedicated team is cheaper.
- You need the team operational in under 8 weeks. BOT's Build phase cannot be compressed below 10–12 weeks without compromising hire quality. If speed is the primary constraint, a dedicated team using an established bench is faster.
- The team is small (under 8 people). BOT governance overhead is not justified below this threshold. A dedicated team arrangement with a lighter contract structure is more appropriate.
- The function is non-core. For QA, IT support, or back-office functions where deep product knowledge and long-term team stability matter less, the dedicated team model delivers adequate results at lower complexity.
When to Choose BOT
Use Build Operate Transfer when:
- Your intention is to own the team. BOT is the only model with a built-in ownership path. If permanent ownership is the goal, the dedicated team model is the wrong vehicle.
- Your horizon is 3+ years. BOT's total cost of ownership over a multi-year period is materially lower than a dedicated team, because provider margin is eliminated post-Transfer.
- The team is a core engineering function. Product engineering, platform teams, data capabilities — functions where deep knowledge accumulation and low attrition produce a compounding performance advantage — benefit from BOT's ownership incentives.
- You are entering a new delivery country and want managed setup. BOT's Build phase uses the provider's operational infrastructure to establish the team without the client absorbing full setup risk.
- You want to build toward a Global Capability Center. BOT is the fastest path from zero to a company-owned GCC. See What is a Global Capability Center? for how these typically evolve.
Frequently Asked Questions
Can a dedicated team engagement convert to BOT later?
Yes, but it is a significant contractual restructure. The parties need to agree a Transfer date, establish the Transfer mechanics (employment novation, lease assignment, asset transfer), and amend the commercial terms to include a Transfer fee. It is cleaner to structure the engagement as BOT from the start if Transfer is the eventual goal.
Is a dedicated team cheaper than BOT?
In the short term (under 24–30 months), yes — no setup fees and no Transfer fee. Over a longer horizon, BOT is cheaper because provider margin is eliminated post-Transfer. The total cost crossover typically occurs between Month 26 and Month 32.
Who owns the IP in a dedicated team engagement?
IP ownership in a dedicated team engagement should be explicitly assigned to the client in the MSA — it is not automatic. Standard provider employment contracts may assign IP to the provider's entity. This must be contracted out. The same applies to BOT, but BOT's more complex contract structure typically gives it more explicit attention.
What notice period is standard for terminating a dedicated team?
Notice periods for dedicated team terminations typically range from 60 to 180 days, depending on team size and contract terms. This allows the provider time to manage the team's transition (redeployment or redundancy) and the client time to arrange continuity. BOT termination before Transfer follows similar logic, with additional Transfer execution provisions.