Both models end with you owning a GCC. What differs is when ownership starts, who carries the statutory burden, and what your counsel has to sign off on first.
Both models end with you owning an India center. That is the part people get right. The part that goes wrong is treating the choice as a cost comparison, when it is really two separate questions wearing one label: when do you want to own the entity, and how much of the operating burden do you want to carry on day one.
What each model actually is
COPO, Company-Owned Partner-Operated, means the entity is yours from the start. You hold it, the employees sit inside it, and the operating knowledge accrues to you from the first hire. A partner runs the operation alongside your team under a services agreement. There is no transfer event, because there is nothing to transfer: you already own the thing.
BOT, Build-Operate-Transfer, means the partner builds and runs the center first, then transfers operational control to you on pre-agreed terms. The transfer window we work to is 24 to 36 months. It exists because some companies cannot or should not stand up an Indian entity on day one, and the alternative to a BOT is usually not a faster COPO, it is nothing.
The naive read is that COPO is BOT with the waiting removed. That is not quite it. In a BOT, someone else carries the statutory and employment obligations during the build, which is a real transfer of risk and a real reason to choose it. In a COPO, you carry them from the beginning, which is a real transfer of control and a real reason to choose that instead.
The three questions that actually decide it
1. Can you stand up and hold an Indian entity now? Not in principle. Now, with the board approval, the capital, the directors, the registered address and the appetite for the statutory filing calendar that comes with it. If the honest answer is not for another two quarters, then the choice is between a BOT that starts now and a COPO that starts in two quarters, and that is a different comparison from the one on most vendor slides.
2. Who should carry the employment obligations during the build? In a COPO, your entity is the employer from the first hire, which means your entity holds the statutory contributions, the termination obligations and the compliance exposure. Some companies want exactly that, because the employment relationship is the ownership. Others, particularly those hiring their first eleven people in a country they have never operated in, would rather a partner carry it while the operation is proved.
3. Is there a transaction in view? This is the question that most often overrides the other two. A transfer event landing in the middle of a diligence process is a complication you can avoid entirely by sequencing around it. If a sale or a recap is likely inside the transfer window, either complete the transfer well before the process starts or choose the model that has no transfer event at all.
Where each one is the better answer
COPO tends to be right when the entity is ready or nearly ready, the function is one you intend to run permanently, the operating knowledge is the point, and nobody is optimising for a near-term exit. It is also the better answer when you have been burned by a vendor dependency before, because there is no version of COPO in which the method belongs to somebody else.
BOT tends to be right when the entity is genuinely not available yet, when the operation needs to be proved before the board will approve permanence, or when the company wants a partner to carry the first-year employment risk while a new function finds its shape. It is the pragmatic answer more often than the ideological reading of ownership allows.
The wrong answer, in both directions, is choosing on price. The cost difference between the two over a five-year horizon is smaller than the cost of choosing a structure you then have to unwind.
The legal, tax and transfer questions to settle first
None of what follows is legal or tax advice, and none of it is answerable from a web page. These are the questions to put to your counsel and your tax advisers before a model is selected, because the answers can change which model is viable rather than merely which is preferable.
Permanent establishment. Whether the arrangement creates a taxable presence, and on what basis, differs by structure and by how the services agreement is written. This is a question about your specific facts and it is worth asking early, because the answer can be structural.
Transfer pricing. An owned Indian entity providing services to a US parent needs a defensible intercompany arrangement, and it needs it from the start rather than retrospectively. This applies to COPO immediately and to BOT from the transfer.
Employee transfer mechanics. In a BOT, how the employment relationship moves at transfer is a substantive question, not an administrative one. Continuity of service, accrued statutory entitlements, gratuity treatment and whether consent is required all belong to counsel. Getting this wrong is the most common way a transfer that looked clean on paper becomes expensive in practice.
Foreign investment treatment and sectoral conditions. Requirements vary by sector, and a structure that is straightforward in one is conditional in another.
What transfers besides people. Intellectual property created in the center, the data the operation accumulates, the tooling, the process documentation and the vendor contracts all need to be named in the transfer terms. Anything unnamed at signing is a negotiation later, at a moment when you have less leverage than you do now.
How to run the decision
Decide the ownership question before the operating question. Reversing them is how companies end up with a structure that fits the first year and has to be rebuilt for the second. Then take the shortlist to counsel and tax before you take it to procurement, because their answers can remove an option and procurement cannot.
And if a transaction is anywhere in view, let its timeline set the structure rather than the reverse. That single rule prevents most of the expensive versions of this decision.