Key Takeaways:
- A Build-Operate-Transfer (BOT) engagement relies on structured operational rhythm, including task-level workflow documentation from day one and assigning an internal manager from week one.
- Major checkpoints are timed around real business cycles (like month- and quarter-end closes) to measure productivity and cost accurately.
- Transferring full ownership requires evaluating cost overhead, team maturity, internal HR/legal readiness, and strategic fit; many companies choose to remain in the “Operate” phase indefinitely to maintain flexibility without adding localized operational overhead.
- Common pitfalls include attempting to transfer before team stability is achieved, underestimating local legal entity timelines, or treating transfer as a mandatory default rather than a strategic choice.
A Build Operate Transfer proposal and a Build Operate Transfer engagement are two different documents. One describes an outcome, while the other requires a domestic manager assigned by week one, a 90-day cost review a CFO attends, and a Transfer decision built on evidence rather than a contract date.
This piece is the second document. It walks you through each phase of a real BOT engagement, the checkpoints, the ownership at each stage, and what gets evaluated at the point where you decide whether to take the team in-house.
What is Build Operate Transfer?
Build Operate Transfer (BOT) is a three-phase offshore staffing model. A partner like Connext builds and staffs your team, operates it alongside your leadership, and transfers full ownership to your entity if you choose to exercise that option. For the complete build operate transfer model breakdown, see our 2026 BOT model guide.
Why “What it Looks Like” Matters More Than “What it is”
A well-run BOT engagement runs on rhythm, a defined activity in each phase, a named owner at every checkpoint, and a decision point that only means something because of what happened in the phases before it.
The walkthrough below uses a finance back-office function, accounts payable, reconciliation, financial reporting support, as the working example. The phase structure and checkpoint types reflect how Connext runs these engagements in practice.
Phase 1: Build
The Build phase is where your domestic team does most of the early work, and Connext handles the infrastructure behind it.
| What Happens | Who Signs Off |
| Role scoping, workflow documentation at the task level, domestic manager assigned to own the relationship | COO or Ops Leader |
| Candidate sourcing, structured interviews with shortlisted candidates, final hiring decision | Ops Leader and Finance hiring manager |
| System access provisioning, destination-country compliance and EOR setup, equipment and workspace preparation | Connext and client IT |
Two things matter in this phase more than most buyers expect going in. First, documentation happens at the task level, not the job description level. A job description tells a new hire what the role covers. Task-level documentation tells them exactly how the work gets done today, which is what shortens ramp time.
Second, the domestic manager assignment is not a formality. Someone on the client side owns this relationship from day one, and that ownership does not transfer to Connext at any point in the engagement.
Phase 2: Operate
The categories tracked in this phase, productivity, quality, retention, cost per role, are not unique to any one BOT partner. What differs is whether the review cadence is built around your finance calendar or an arbitrary one.
| Milestone | Metric Reviewed | Owner |
| 30-day review | Onboarding completion, early output quality | Ops Leader |
| 90-day review | Productivity against defined targets, cost per role against the original financial model | CFO and Ops Leader |
| 90 days and onwards | Retention, attrition, capacity against the growth plan | CFO and Ops Leader |
The 30-day review sits with the Ops Leader alone, and it lands right after the team’s first month-end close, since that is the first real test of whether the task-level documentation from Build held up under a live cycle.
The 90-day review is the first point a CFO is formally in the room, and it lands at quarter-end, when cost per role and productivity can be measured against a full reporting period instead of a partial one.
From there, the ongoing cadence tracks to each subsequent quarter-end close, which is also when most finance leadership teams are already reviewing board-level numbers, so this becomes one more input into a process that already exists, not a separate check-in to schedule.
Weekly syncs and structured KPI tracking run underneath all of this, but the milestones above are set to your existing close calendar, not an arbitrary day count.
The Transfer Decision Point: What Actually Gets Evaluated
The Transfer phase is often described as an option, which is accurate, but rarely as a decision with actual criteria behind it. Here is what gets evaluated when a client reaches that point.
- Cost basis – Does owning the entity outperform continuing to Operate once legal, compliance, and infrastructure overhead are priced in, not just headline savings?
- Team maturity – Has the team reached the retention and output stability needed to run without Connext’s operational layer underneath it?
- Internal readiness – Does the client want to build or expand in-country legal and HR infrastructure, or does it make more sense to let Connext continue holding that responsibility?
- Strategic fit – Is this function becoming core enough to the business to justify full ownership, or does staying in Operate continue to serve the business better long term?
None of these four questions has a universally correct answer. A significant share of clients who begin a BOT engagement with transfer intent choose to remain in Operate once they see the actual cost and complexity of the alternative. Staying is not a lesser outcome. It is frequently the better one.
[global_section id=”102493″]Where BOT Engagements Typically Stall
Most failure points in a BOT engagement are predictable, and predictable problems are often preventable.
- Attempting Transfer before the team has stabilized – Moving to Transfer while retention and output are still finding their footing carries the instability directly into the new entity.
- Underestimating in-country legal and entity setup timelines – Establishing a foreign legal entity takes longer than most domestic leadership teams expect, and rushing it introduces compliance risk.
- Treating Transfer as a default endpoint rather than an optional decision – Engagements that assume transfer is the goal from day one tend to under-invest in making the Operate phase work well on its own terms.
- Losing institutional knowledge during a rushed handover – Process knowledge built up over the Operate phase does not transfer automatically. A rushed handover recreates the exact operational risk BOT was meant to remove.
Staying in Operate vs. Exercising Transfer
Transfer is not a single door that closes once. Companies revisit this comparison at every review cycle, and staying in Operate remains a live option each time, not a default that expires.
| Dimension | Staying in Operate | Exercising Transfer |
| Control | Client directs work; Connext manages the operational layer | Client owns and manages the entire operation directly |
| Cost Structure | Predictable co-management fee structure | Client assumes full entity operating costs |
| Compliance Ownership | Connext holds EOR and in-country compliance responsibility | Client assumes direct legal and compliance responsibility |
| Talent Management | Connext handles HR, payroll, and retention infrastructure | Client builds or expands its own HR and payroll function |
| Flexibility | Easier to scale up or down without entity-level commitment | Full autonomy, with the overhead that comes with it |
How Connext Supports Every Phase of a BOT Engagement
Connext delivers BOT through a co-managed model: you direct the work while we handle recruiting, HR, payroll, compliance, and people operations. We build dedicated teams across the Philippines, Colombia, Mexico, and India, giving you regional flexibility without establishing a local entity first.
Plus, our compliance posture is based on SOC 2 Type II and HIPAA standards. Whether your finance back-office team stays in Operate long term or moves toward Transfer, the model is built to support either outcome without forcing the decision before you are ready.
If you are past the concept stage and thinking through what this requires, schedule a conversation with us to walk through the specifics for your team.
Frequently Asked Questions
There is no fixed timeline. Some clients evaluate Transfer once the team hits sustained stability on the metrics reviewed during quarterly checkpoints. Many choose to remain in Operate indefinitely once they see it meets their needs without added overhead.
Compliance, payroll, and employment obligations move from Connext’s EOR structure to the client’s own legal entity in the destination country. The client must have that entity, or the process to establish one, in place before Transfer executes.
Partial transfers are possible depending on how the engagement is structured. This is a scoping conversation at the account level rather than a standard feature of every BOT engagement.
Transfer includes the team, but also the infrastructure built during Operate: documented workflows, systems access, compliance setup, and institutional process knowledge. Hiring directly without that infrastructure means rebuilding it from scratch.
No. Transfer is an option built into the model, not an obligation. Clients who remain in Operate continue to receive the same co-management structure, and many do so long-term because it continues to meet their needs.
