An offshore development center (ODC) is a dedicated software or IT team that a vendor employs and manages for one client. A global capability center (GCC) is a dedicated offshore or nearshore center that runs business functions for one company, under that company's direction. A captive center is a GCC the company owns and runs itself. Build-operate-transfer (BOT) is a model where a partner builds and runs a center, then hands it over to the company.
The right model depends on who owns the local entity, who employs the team, who directs the work and when, if ever, ownership moves to you.
Key takeaways
- ODC and GCC describe what a center does. Captive, BOT, hybrid and partner-run describe who owns it.
- Only 11% of companies planning a GCC expect to launch fully captive, according to ISG. New centers lean toward BOT or partner-run setups.
- In Latin America, the BOT operate phase runs three to five years in a typical deal, and ISG has found that not every BOT ends in a transfer.
- A partner-run GCC gives you control of hiring and the work without owning the entity, and it’s the fastest model to launch.
- Many companies start with a partner and move to their own entity later.
The two questions behind every offshore model
ODC, GCC, captive center and BOT answer two separate questions: what the center does, and who owns and runs it. The first question splits ODCs from GCCs. An ODC focuses on software and IT work, while a GCC can run almost any business function, from finance and customer support to data and engineering. Ownership sets captive centers, BOT, hybrid GCCs and partner-run GCCs apart.
To compare them, look at four things:
- Who owns the entity? The entity is the local company the team works under. It holds the lease and signs the contracts.
- Who employs the team? The employer issues employment contracts and runs payroll.
- Who directs the work? The company directing the work sets the priorities, standards and performance metrics.
- When does ownership change? Some models move the center to your own entity at a set point, and others never do.
What is an offshore development center (ODC)?
An offshore development center (ODC) is a team in another country that works only on your projects, while a vendor employs the team and runs its office and HR.
Most ODCs handle software development, testing and IT support. Because the vendor owns the entity, ownership stays with the vendor unless your contract includes a path to transfer. You set priorities for the projects the team takes on, and the vendor manages hiring, payroll and day-to-day operations.
An ODC fits companies that need a dedicated software or IT team fast and don’t want to set up a foreign entity. The tradeoff is control: the people, the office and much of the knowledge the team builds belong to the vendor. Pricing tends to follow headcount. When a vendor employs the team, contracts may use pricing per full-time team member, like other managed services.
What makes a center a GCC?
A center is a GCC because of its relationship with your business. Your company directs the work, sets the standards and keeps the knowledge the team builds.
A GCC can run almost any function, from technology and finance to customer support, data and back office work. The entity behind the team can belong to you or a partner, and that choice separates the next three models. For the full definition, see what a global capability center is.
Captive centers: full ownership from day one
With a captive center, your company owns everything from day one: the entity, the office, payroll and local compliance. It gives you the most control over IP, governance and culture.
It also takes the longest to set up and needs the most upfront investment, since you build everything yourself. ISG notes that captive centers suit companies with experience operating internationally or an existing leadership presence in the target country. Fewer new GCCs start this way. ISG research shows only 11% of companies planning a GCC expect to launch fully captive.
Build-operate-transfer: partner first, ownership later
In a build-operate-transfer (BOT) model, a partner builds and runs a center for you, then transfers the team, infrastructure and processes to your own entity at an agreed point.
Until the transfer, the partner owns the entity and employs the team, while you direct the work. BOT has become a common way to start. Deloitte's 2025 Global Business Services Survey notes that companies use BOT as a market entry strategy before moving to their own operations, and Haynes and Boone describes it as a common and growing way to build a GCC in Latin America.
The three phases of build-operate-transfer (BOT)
- Build: The partner forms the legal entity, sets up the site and recruits the team.
- Operate: The partner runs day-to-day operations while you direct the work and the team grows. In Latin America, this phase runs three to five years in a typical deal.
- Transfer: Agreed employees, infrastructure and processes move to your own entity, through a pre-agreed purchase of the partner's assets or shares.
The transfer terms need the most care. ISG flags transfer timing and keeping key leaders as the areas to plan for, and notes that pricing runs at a premium during the operate phase.
From 0 to 400 employees: a transfer in practice
A global insurance service provider partnered with MicroSourcing to build its Philippine workforce while establishing its own local entity.
Build - MicroSourcing provided the recruitment, employment and workplace infrastructure needed to launch the GCC, helping the client scale from zero to 400 employees in less than one year.
Operate - MicroSourcing managed employment and operational support while the client directed the team's work and continued establishing its own entity and facilities.
Transfer - Once the client's entity and facilities were ready, MicroSourcing coordinated the transfer of employees, assets and processes to the client's independent operations, without disrupting business delivery.
After the transfer, MicroSourcing continued supporting the client's growth through an ongoing recruitment partnership.
How a fast start BOT works
A fast start BOT lets your team begin work before your own entity exists. The partner hires your team as the employer of record, and the team starts working for you right away. You set up your own entity, office and local compliance in the background, then move the team over when everything is ready.
This matters because setting up an entity yourself takes time. Registering a foreign company in the Philippines takes about 78 days, according to the World Bank’s 2025 Business Ready report, and that’s before you secure office space and meet local compliance rules. Meanwhile, headquarters wants the team working now.
"One of the biggest challenges we see is the gap between when a business needs its team operational and how long it actually takes to establish a presence in a new market. Those timelines don't always align.
What we've found is that businesses don't necessarily have to choose between moving quickly and building something they own long term. They can start building their team while the foundations for their own operations are still being put in place.”
- Haidee Enriquez, CEO of MicroSourcing Group
Hybrid and partner-run GCCs: two ways to share the work with a partner
A hybrid GCC is a center you own and direct, with a partner providing pieces such as facilities, recruitment or operations. ISG describes it as company ownership combined with outside expertise, used by companies that want to own their capability while reducing early setup risk.
A partner-run GCC, also called GCC as a service, reverses that ownership. The partner builds and runs a dedicated center, owns the entity and employs the team. You direct the work, approve every hire and set the performance metrics. Moving the team to your own entity later is optional.
From the outside, this can look like an ODC, since a partner employs the team in both. But a partner-run GCC can run any business function, and you decide who joins the team and how it works.
EagleView Technologies started with a pilot team of 41 people in the Philippines and grew to more than 1,300 employees across multiple business functions, while keeping direct control of its processes.
How the models compare
Many companies move from one model to another as they grow, starting with a partner and moving to their own entity once the team is established.
|
Model |
Who owns the entity? |
Who directs the work? |
Ownership changes |
Speed to launch |
Best fit |
|
Offshore Development Center (ODC) |
Vendor |
You, at the project level |
Only if your contract converts it |
Fast |
Dedicated software or IT teams without a foreign entity |
|
Captive Center |
You |
You |
You own it from day one |
Slowest |
Companies with international experience planning a long-term center in one country |
|
Traditional BOT |
Partner, then you |
You |
At an agreed transfer point |
Medium |
Companies that want to own the center but need a partner to get it running |
|
Hybrid GCC |
You |
You |
You own it from day one |
Medium |
Companies that want ownership but not the work of hiring and running a site |
|
Partner-Run GCC |
Partner |
You |
Optional, when you’re ready |
Fastest |
Companies that want to direct the work without setting up a local entity |
|
Traditional Outsourcing |
Vendor |
Vendor |
Never |
Fast |
Standardized processes the vendor can run on its own terms |
GCC vs. ODC vs. Captive Center vs. BOT: Common Comparisons
-
GCC vs. ODC
The biggest differences are scope and who manages the team.
An ODC handles software and IT work, and the vendor runs hiring and day-to-day management. A GCC can take on any business function, with your company approving hires and setting how the team works.
If you need a software team and don't mind the vendor managing it, an ODC can be enough. If the work is core to your business, a GCC gives you more control. Connective made this switch. After working with a vendor team in India, it moved to a MicroSourcing team in Manila in 2019, starting with 12 compliance staff and growing to more than 40. The team uses Connective’s own security setup and reports directly to Connective’s managers.
“There's a big difference between having people work on your projects and having a team that really knows your business. When they're working directly with your managers, they get to know how things work, why decisions are made and what matters to the business. You don't get quite the same understanding when there's a vendor sitting between you and the team.
- Haidee Enriquez, CEO of MicroSourcing Group
-
GCC vs. Captive Center
A captive center is one way to own a GCC. Every captive center is a GCC, but a GCC can also be hybrid, partner-run or built through BOT. In a captive center, you own the entity from day one.
-
GCC vs. BOT
BOT is a path to owning a GCC. A partner builds and runs the center first, then transfers it to your entity, so you end up with a GCC you own.
-
ODC vs. BOT
Both start with a partner employing the team. A BOT includes a planned transfer to your entity, while an ODC stays with the vendor unless your contract converts it.
-
Captive Center vs. Outsourcing
A captive center keeps the team, processes and knowledge inside your company. Outsourcing hands a defined process to a vendor that runs it with its own staff and methods. ISG draws the line between efficiency and capability: outsourcing works well for standardized, repeatable work where scale drives savings, while a captive center or other GCC suits work you want to build and own.
How to choose the right model
“Few organizations operate at the extremes of full captivity or full provider control; most position themselves somewhere along a continuum of shared risk and distributed decision ownership."
- Stanton Jones, Distinguished Analyst, ISG
ISG suggests weighing two things: how much startup risk you want to hand to a partner, and how much direct control you need over IP, tooling and governance from day one.
In practice, that comes down to a few questions:
|
Question |
If yes, consider |
|
Do you need to own the entity from day one? |
A captive center or hybrid GCC |
|
Do you want to own it eventually, but not yet? |
BOT, or a partner-run GCC with the option to transfer |
|
Does the team need to start within weeks? |
A partner-run GCC or fast start BOT |
|
Is the work limited to software or IT? |
An ODC, or a GCC if you want more control |
|
Will the team run finance, customer support or several functions? |
A GCC, under any ownership model |
|
Is this your first time running a team in another country? |
A partner-run, BOT or hybrid model to reduce early risk |
Why more companies start with a partner
New GCCs are more likely than older ones to start with a partner. ISG research shows planned centers lean toward BOT or partner-run setups, while many existing centers were built from scratch. Demand is growing too: 43% of companies using onshore or outsourced teams today plan to move to a dedicated offshore center within the next year.
Partners also stay involved after launch. ISG found that two-thirds of GCCs plan to increase their use of outsourcing as they expand, and more than a third expect to raise their spending on outsourced services by over 10% within a year.
Not sure which model fits?
If you're weighing your options, MicroSourcing's global capability center services let you launch under MicroSourcing's entity today, then transition the team to your own operations when you're ready.
FAQs
How long does each model take to launch?
A partner-run GCC is the fastest, because the partner's entity, site and recruiters are already in place. With MicroSourcing, a team can launch in as little as 6-8 weeks. A fast start BOT can be just as quick, since your team starts under the partner's entity. An ODC is also fast. A traditional BOT or hybrid model takes longer, and a captive center takes the longest, since you have to set up your own entity, office and compliance first.
Can you switch from one model to another?
Yes. Many companies start with a partner-run GCC or an ODC and move to their own entity later through a transfer. Agreeing early on which employees and assets move, and when, makes the switch smoother.
Does every BOT end in a transfer?
No. ISG has found that not all BOT arrangements transfer ownership as planned. Without clear milestones and a firm intent to bring the center in house, a BOT can turn into a long-term managed service.
Which model gives you the most control?
A captive center gives you full ownership of the entity, IP and operations. A partner-run GCC can give you the same control over hiring, priorities and performance without owning the entity, since the partner handles employment and local operations.
