Build Operate Transfer:
The Complete Guide
Most companies that need offshore engineering capacity face the same problem: hiring through a staffing firm gives you bodies without commitment, while building your own subsidiary takes years and carries full legal and HR risk from day one. The Build Operate Transfer (BOT) model sits between those two options — a specialist provider builds and operates a dedicated team on your behalf, then transfers ownership of that team to you at a point you define in advance.
01 What is Build Operate Transfer?
Build Operate Transfer (BOT) is a contractual delivery model in which a third-party provider establishes, staffs, and manages an offshore or nearshore team on behalf of a client company, with a pre-agreed option or obligation to transfer full ownership and control of that team to the client at a defined point in time.
The model originated in infrastructure project finance — governments used BOT to build highways and power plants without upfront public capital. Private firms built the asset, operated it to recoup investment, then transferred it to the state. The IT industry adapted the logic: instead of a highway, the asset is a functioning engineering team with embedded processes, tooling, and institutional knowledge.
BOT delivers an entire organisational unit — complete with management layer, HR, legal entity, office, and operational runbook — that is designed from the start to become yours.
The transfer is not an afterthought. It is the point.
02 The Three Phases Explained
Build — Months 1–6
The provider establishes the operational foundation: legal entity setup in the delivery country, recruitment to your headcount and seniority spec, office and infrastructure, process and tooling aligned to your engineering standards, and the governance framework that will govern the Operate phase. You participate directly in hiring decisions. The team built is built to your spec.
- Legal entity registration
- Recruitment to your spec
- Office & infrastructure setup
- Governance framework live
Operate — Months 6–36
The provider manages day-to-day operations — HR, payroll, employment compliance, office management, line management — while the team delivers under your product and engineering direction. You direct the work. The provider handles the overhead. This is the core commercial logic: the client captures the cost advantage of offshore delivery without absorbing the management burden before they are ready to.
- HR, payroll & compliance
- You direct all technical work
- 12–20% management margin
- Team grows on your terms
Transfer — Full Ownership
Ownership of the team transfers to you. Employment contracts are novated to your local subsidiary, office leases assigned, equipment and licenses transferred or re-purchased, IP formally confirmed as yours, and management responsibility handed to your nominated country manager or regional VP. The transfer can be a single event or a phased handover over 3–6 months.
- Employment contracts novated
- Leases & assets transferred
- IP formally confirmed
- 20–35% cost reduction
03 What Gets Transferred?
The term "transfer" is frequently misunderstood. What moves from provider to client is not a legal entity — it is operational control and employment relationships.
The provider does not transfer their own business. They transfer the team they built for you.
04 BOT vs Other Delivery Models
| Factor | BOT | Staff Augmentation | Dedicated Team | Captive Subsidiary |
|---|---|---|---|---|
| Time to operational team | 2–4 months | 2–6 weeks | 4–8 weeks | 6–18 months |
| Management burden on client | Low | High | Medium | High |
| Upfront investment | Low–medium | Low | Low | Very high |
| Long-term cost | Lowest (own team) | High | Medium | Low |
| Talent retention risk | Shared | Client | Shared | Client |
| Regulatory complexity | Managed by provider | Minimal | Minimal | Full |
| Path to full ownership | Built-in | None | None | N/A |
BOT is the only model explicitly designed to end in full client ownership. That is its structural differentiator.
05 When BOT Makes Sense
The BOT model suits organisations that meet one or more of these conditions:
BOT doesn't pay off in 6 months. The model fits companies that have committed to a permanent offshore capability, not a short-term project team. Below a 2-year horizon, a dedicated team or staff augmentation is cheaper.
Building a subsidiary in Romania or Poland requires legal fees, registration, and a country manager before a single engineer starts. BOT defers that burden to the provider. The client inherits an operational team, not a greenfield problem.
The BOT provider brings local employment law, tax, banking, and regulatory knowledge. By Transfer, the client has had 18–36 months to understand the regulatory environment before assuming full employer responsibility.
SAP support centres, Salesforce centres of excellence, Azure engineering teams, and data analytics centres of excellence all generate continuous, multi-year demand. BOT's Operate phase — 18–36 months of institutional knowledge accumulation — is structurally suited to these functions. See technology-specific details below.
COBOL mainframes, RPG/AS400, and legacy Java applications require engineers whose skills are scarce in Germany, the UK, and the US. BOT IT delivery centres in Romania, Poland, and India access these talent pools at competitive market rates. See the ODC legacy technology guide.
06 BOT for IT Delivery Centers
The BOT model is not a generic offshore team structure. When the capability being built is a permanent, specialised function centred on an enterprise technology platform — or a data stack, or a legacy codebase — BOT's structure fits more precisely than any alternative. The provider builds the team to client specification, operates it under client direction, and exits. What transfers is not just the people but the institutional knowledge they have accumulated.
SAP, Oracle, Salesforce, Microsoft, and Cloud
Enterprise platforms require a permanent, specialised workforce. SAP, Oracle, Salesforce, and the major cloud hyperscalers all generate continuous operational and development demand that outlasts any individual project. A BOT IT delivery center keeps that expertise inside a team with no other client. At Transfer, the client owns not just the employment contracts but the collective system knowledge of every engineer who has worked on their platform.
For detailed operational mechanics — team structure, governance, SAP salary benchmarks, and pricing — see the BOT model enterprise platform section and enterprise fit criteria.
Data Engineering Centers of Excellence
A data engineering center of excellence built via BOT covers the full analytics stack in one location. Partial centres — data engineers in one geography, analytics engineers in another, governance nowhere — produce fragile and ungoverned data products. The BOT model co-locates the full stack under a single management structure with a contractual path to client ownership.
For the full D&A stack breakdown with role titles and Romania salary benchmarks, see the Global Capability Center D&A section and the BOT model data platform guide.
COBOL, RPG, Mainframe, and Legacy Modernisation
Many enterprises run critical systems on technology stacks that are 20, 30, or 40 years old. These systems work. The problem is that the engineers who understand them are retiring faster than they are being replaced. BOT IT delivery centres in Eastern Europe and India access concentrations of legacy-skilled engineers whose careers overlapped with the commercial peak of these stacks.
The BOT model's structured knowledge transfer is particularly suited to legacy maintenance: the undocumented decisions, known failure modes, and batch dependencies that constitute the real operational knowledge of a mainframe estate accumulate in the BOT centre and transfer to the client at the end of the Operate phase. For the full legacy technology section — including the strangler fig modernisation pathway — see the ODC legacy guide and BOT advantages for legacy teams.
07 When BOT Doesn't Fit
If the requirement is to build a specific product over 12 months, BOT is the wrong instrument. A fixed-price project or dedicated team contract is cheaper and faster.
The overhead of a BOT structure is not economically justified below 8–10 people. A dedicated team arrangement delivers similar control without the transfer architecture.
Transfer only works if you are prepared to establish legal employer status in the delivery country. Without that plan, the transfer clause becomes unexercisable — and the model's primary financial benefit cannot be captured.
08 Typical Timeline and Costs
| Phase | Duration | What you pay |
|---|---|---|
| Build | Months 1–4 | Setup fee + early headcount costs |
| Operate | Months 4–36 | Per-head monthly fee (staff costs + 12–20% provider margin) |
| Transfer | Months 34–40 | Transfer fee + asset buyout (typically 1–3× monthly operating cost) |
At Transfer, the client's ongoing cost drops to direct employment cost plus internal overhead — typically 20–35% lower than the Operate-phase fee. For a 15-person team in Romania, this compounds to approximately €126,000/year in annual savings.
09 Key Risk Areas
Some BOT contracts define the transfer as an option rather than an obligation. The contract should specify automatic transfer or a binding election window — or the provider retains the team indefinitely under the original commercial terms.
Teams that operate well attract competing offers. Retention clauses, bonus structures, and equity mechanisms should be addressed in the operating agreement, not left to the provider's discretion.
Work product created during the Operate phase must be contractually assigned to the client at creation, not at Transfer. Standard employment contracts in many countries do not automatically resolve this — it must be explicit in the MSA.
Dependence on provider-specific tooling or management infrastructure makes Transfer harder to execute. BOT contracts should include interoperability and documentation requirements from day one.
10 Frequently Asked Questions
What does "transfer" mean in Build Operate Transfer?
Transfer refers to the handover of operational control and employment relationships from the BOT provider to the client. The client becomes the direct employer of the offshore team, takes over the office lease and equipment, and assumes full management responsibility. The provider exits the arrangement at an agreed point.
How long does a BOT engagement typically last?
Most BOT engagements run 2–4 years from contract signature to transfer completion. The Build phase takes 2–5 months; the Operate phase typically runs 18–36 months; the Transfer phase takes 3–6 months to execute. Shorter engagements are possible but reduce the economic case for the model.
Is Build Operate Transfer the same as an offshore development center?
An offshore development center (ODC) is a facility-based concept — a dedicated team working from a provider's or client's own office in a delivery country. BOT is a contractual model that governs how that center is established and who ultimately owns it. A BOT engagement usually produces an ODC. Not all ODCs are established via BOT.
Which countries are most commonly used for BOT engagements?
India dominates by volume, particularly for large enterprise teams. Eastern Europe — Romania, Poland, Ukraine, Czech Republic — is preferred by Western European companies for proximity, time zone alignment, EU membership (Romania, Poland), and GDPR compliance. The Philippines and Vietnam are growing for specific skill profiles.
How is BOT different from a captive center?
A captive center is a wholly-owned offshore subsidiary established directly by the company. It reaches the same end state as BOT Transfer — a company-owned team — but the client absorbs all setup risk, legal cost, and operational management from day one. BOT uses the provider's infrastructure to reach the same destination with lower upfront exposure.
Can the BOT model be used for SAP, Salesforce, or other enterprise platform teams?
Yes. Enterprise platform teams — SAP support and development, Salesforce centres of excellence, Azure engineering teams, Oracle Fusion implementation and support — are among the best-suited BOT use cases. These platforms generate continuous, multi-year operational demand that requires a stable, client-directed team, not rotating contractors. BOT builds that team in a delivery country with platform-specific talent depth (Romania and Poland for SAP; India for scale), operates it under client technical direction, and transfers full ownership. The institutional knowledge of your SAP configuration or Salesforce data model stays in the centre and transfers with the team.
What data engineering and analytics roles can be built in a BOT center?
A BOT data engineering center of excellence can cover the full analytics stack: data engineers (Apache Kafka, Fivetran, Debezium for ingestion), lakehouse engineers (Databricks, Snowflake, Apache Spark, dbt), analytics engineers (Looker, Power BI, Tableau, Cube.dev), data governance specialists (Collibra, Apache Atlas, Great Expectations), and ML engineers (MLflow, Amazon SageMaker, Google Vertex AI). The role mix is defined by the client's existing data platform and roadmap during the Build phase. Romania and Poland are the primary European BOT delivery countries for senior data engineering talent.
Is COBOL and legacy mainframe development available through BOT?
Yes. Romania, Poland, and India retain concentrations of COBOL-proficient engineers — a result of those markets' engineering education cycle overlapping with COBOL's active commercial period. A BOT IT delivery center in Bucharest or Krakow can build a COBOL development team for mainframe-dependent banks, insurance companies, and government agencies. The BOT model's structured knowledge transfer is particularly suited to this use case: the institutional knowledge of a specific mainframe codebase — undocumented logic, batch dependencies, edge-case behaviour — builds in the centre and transfers to the client at the end of the Operate phase.