Quick answer: A build-operate-transfer agreement should settle the ending before the beginning. The twelve clauses that matter most cover when the center transfers, what the transfer costs, exactly what moves to you (people, entity, technology, processes and premises), and what protects you during the years your partner runs it. Anything left "to be agreed later" will be negotiated at the point where you have the least room to walk away.
The idea behind BOT is simple. A partner builds your India capability center, runs it for a period, then hands it over so you own it. The contract is where that idea holds or falls apart. Disputes in BOT engagements are rarely about day-to-day delivery. They are about the handover: the price, the people, and who owns what.
This checklist is written for CEOs, COOs and general counsel at mid-sized companies planning a first GCC in India. It is not legal advice. Use it to brief your lawyers and to test a partner's draft, and have Indian counsel review the final document.
What is a build-operate-transfer agreement?
A build-operate-transfer agreement is the master contract between you and the partner who sets up and runs your center. It covers three phases in one document:
- Build: the partner sets up the entity or business unit, premises, IT, security and the first hires.
- Operate: the partner runs delivery to agreed service levels while the team grows and matures.
- Transfer: the team, assets and, where relevant, the legal entity move to your ownership.
BOT is one of three common routes to an India center. If you are still choosing between them, compare build-operate-transfer, hybrid captive and managed services side by side first, because the contract looks very different in each. If you are weighing a center against a classic vendor contract, our comparison of GCCs and traditional outsourcing covers that decision. And if you are earlier in the process, start with the step-by-step plan for setting up a GCC in India.
Why does the BOT agreement matter more than the proposal?
Proposals describe the build. Contracts decide the transfer.
There is a built-in tension in the BOT model. The partner earns a margin for every month it operates the center, so a vague end point gives it a commercial reason to keep operating. Three years in, the team knows your products, your customers depend on it, and the partner is still the legal employer. If the transfer terms are open at that stage, your bargaining position is weak.
A good partner removes that tension at signing by writing the end point, the price and the mechanics into the contract. The table below shows what weak and strong wording look like in the areas that cause the most trouble.
| Clause area | Weak wording | Strong wording |
|---|---|---|
| Transfer trigger | When both parties agree | A fixed date or measurable readiness criteria |
| Transfer price | To be negotiated at transfer | A formula fixed at signing |
| People | Reasonable efforts to transfer staff | Named scope, offer terms and a consent process |
| IP | IP passes to client on completion | Client owns work product from day one |
| Exit | Termination for breach only | Early-transfer and step-in rights defined |
Clauses 1 to 4: what should a BOT agreement say about the transfer itself?
1. Transfer trigger
State when the transfer happens. There are two workable forms: a calendar date, or readiness criteria such as headcount reached, service levels held for a set number of months, and a local leadership team in place. Many contracts combine the two, with a date window and criteria that can bring it forward.
Red flag: "at a time mutually agreed" with no date and no criteria.
2. Transfer price and fee formula
Agree how the transfer is priced before anything is built. Common structures include a fixed fee, a fee per transferred employee, a multiple of monthly billing, or a fee that steps down the longer the operate phase runs. The structure matters less than the fact that both sides can calculate the number on the day they sign.
Red flag: a transfer fee defined as "fair market value" with no method attached.
3. What transfers
List it. A complete schedule covers people, the legal entity (if the engagement includes one), technology and licenses, processes and documentation, and premises or the lease. Shared services that the partner provides across several clients, such as a network operations center or a shared specialist, usually do not transfer, so the contract should say how you replace them.
Red flag: a single line saying "the operations" will transfer.
4. Employee transfer mechanics
People are the asset. Employees cannot simply be assigned from one employer to another, so the agreement should describe the process: who makes the offers, on what terms, how tenure and accrued benefits are recognized, and what happens with anyone who declines.
Red flag: no mention of continuity of service or benefits for the people moving.
Clauses 5 to 7: what protects the asset you are paying for?
5. Non-solicitation, in both directions
You should not hire the partner's dedicated team outside the agreed transfer route. The partner, in turn, should not move your trained people to other accounts during the operate phase or rehire them after the handover. Put both restrictions in writing, with a time limit and a named scope.
Red flag: a non-solicit that binds only you.
6. IP and work product
Everything the team produces for you (code, documents, designs, process maps, knowledge base content) should belong to you from the moment it is created, not at transfer. The partner's own pre-existing tools and methods stay with the partner, with a license for you to keep using anything your operation depends on.
Red flag: IP that vests in you only "upon completion of the transfer".
7. Data protection and security standards
Name the standards the center must meet, such as ISO 27001, and the controls you require: access management, device policy, network separation, background checks and incident notification windows. Add your right to audit.
Red flag: security described as "industry standard" with nothing specific behind it.
Clauses 8 to 10: how should the operate phase be governed?
8. Service levels and service credits
The operate phase can last years. Define a small number of measurable service levels, how they are reported, and what credits apply when they are missed. Make clear that service levels continue to apply during the handover period, when attention tends to drift.
Red flag: service levels that are "targets" with no consequence.
9. Pricing model and margin transparency
Most BOT engagements are priced as operating cost plus a provider margin. Published provider estimates put that margin at 10% to 25% of operating cost, and the figure varies with scope and scale. Whatever the number, the agreement should say what counts as cost, how salary increases and new hires are approved, and whether you can see the underlying figures. Open-book pricing makes the eventual transfer far easier, because you already know what the center costs to run.
Red flag: a blended rate per head with no view of salaries, and annual increases at the partner's discretion.
10. Governance and step-in rights
Set the review rhythm: operational reviews weekly or monthly, executive reviews quarterly. Give yourself approval rights over senior hires and a say in key role changes. Then define step-in rights, meaning the conditions under which you can take direct control of delivery, such as sustained service failure or the partner's insolvency.
Red flag: governance described as "regular meetings" with no named forum or decision rights.
Clauses 11 and 12: how does a BOT agreement end?
11. Staged transfer and transition services
A transfer does not have to happen in one day. Moving by function or by geography, with each stage starting only when the last one is stable, lowers the risk for regulated or customer-facing work. One digital health platform took over a team that had grown from 30 to 155 people this way, transferred by geography and function with no break in service.
The agreement should also cover transition services after the handover: which support the partner continues to provide (payroll, IT, facilities, recruitment), for how long, and at what price.
Red flag: a single transfer date with no fallback and no support afterward.
12. Early exit and termination
Plans change. You may be acquired, or want ownership sooner than planned. The contract should let you call an early transfer on a defined notice period and fee, and should set out what happens on termination for cause on either side. In every exit scenario, you need continued access to your data, your documentation and your people for long enough to keep the service running.
Red flag: termination that leaves the team, the knowledge and the premises with the partner.
How SSGSERV handles BOT agreements
We have run build-operate-transfer engagements since 2016, when we built our first GCC from scratch for a UK hardware maintenance company. Our approach follows the same order as this checklist:
- The end point is agreed at signing. A date or clear readiness criteria go into the contract on day one.
- The center is built to be handed over. Entity, processes and documentation are set up in a form you can own.
- Transfers happen in stages. Each function or location moves when the previous one is stable, with service levels tracked throughout.
- We step out cleanly. Shared services end at handover, and anyone who stays with SSGSERV is redeployed.
You can read the full method on our page explaining how a GCC transfer works. Our GCC setup services in India are built for mid-sized companies setting up a first center of 25 to 200 people, and delivery is audited to ISO 9001, ISO 27001 and CMMI Level 3.
Frequently asked questions
How long does a build-operate-transfer agreement usually run?
Providers commonly quote full BOT cycles of 18 to 36 months, though estimates vary. The right length depends on when you want ownership and how complex the work is. Our own engagements have ranged from two years to ten, and regulated work usually benefits from a longer, staged handover.
Who employs the team during the operate phase of a BOT?
The partner does. It is the legal employer, runs payroll and carries the employment obligations until the transfer. That is why the employee transfer mechanics in clause 4 need to be written down at the start.
Can the transfer price be fixed when the BOT contract is signed?
Yes, and it should be, at least as a formula. A fixed fee, a per-employee fee or a step-down schedule can all be calculated in advance.
What happens if we want to take over the center early?
That depends entirely on whether the agreement includes an early-transfer right. If it does, you give notice, pay the agreed fee and start the handover. If it does not, you are asking for a favor, so add the clause before signing.
Does a BOT agreement need to be governed by Indian law?
Governing law and the dispute forum are negotiated between the parties. Employment, the Indian entity and local registrations will be subject to Indian law in any case. Ask counsel in both countries to confirm the structure before you sign.
A build-operate-transfer agreement is easier to negotiate when the partner has done the handover before and can show you how it went. If you are planning a center in India and want to see how these twelve clauses look in practice, talk to our team and we will walk you through the terms we use.
Faizan Kanth founded SSGSERV with a vision to build a scalable global delivery model, connecting Bangalore, one of India's leading technology hubs, with Srinagar, an emerging center for skilled tech talent. Under his leadership, SSGSERV has grown into a specialized operations partner for global technology companies, serving clients across the United States, the Middle East, the United Kingdom, and the Philippines. With over a decade of experience across leading global technology, automotive, and business process organizations, Faizan brings deep expertise in operations management, business strategy, and market evaluation to every engagement. A postgraduate of a premier Indian management institute, he is driven by an entrepreneurial approach to solving complex operational challenges for enterprises worldwide. Beyond building SSGSERV, Faizan is focused on positioning Kashmir as a hub for Global Capability Centers, having grown the company's Srinagar delivery center to over 500 professionals and counting.









