India GCC vs Offshore Vendor vs BOT Model: Which Is Right for Your Company

Whether to build a team in India is no longer the hard question. How to build it is.

India now hosts 2,117 GCCs employing about 2.36 million people, according to the Zinnov-Nasscom India GCC Landscape Report FY26. That is close to the numbers once projected for 2030. FICCI and ANAROCK expect India to pass 2,400 GCCs by 2030.

The market is crowded and moving fast, so picking the wrong entry model can cost you a year.

The India GCC vs offshore vendor vs BOT choice shapes your hiring speed, your year-1 budget, your IP risk and how easily you can exit. We have run all three models for global buyers. This guide shares what we have seen first-hand: real cost ranges, real timelines, and the mistakes that hurt most.

Quick Answer

There is no single best model in the India GCC vs offshore vendor vs BOT decision. An offshore vendor (staff augmentation) is the fastest option. It suits teams under 40 engineers or programs shorter than 3 years. BOT fits 40–150 engineers over 3–5 years, when you want ownership without the year-1 setup pain. A captive GCC wins at 100+ engineers over 5+ years, but only if you have strong India leadership. Most companies move through all three models in order.

What Each Model Actually Means

People use these terms loosely. Here is what each one means in practice.

Offshore Vendor (Staff Augmentation)

You hire engineers through a vendor. They sit on the vendor’s payroll but work under your direction. The vendor handles payroll, PF, benefits, compliance and replacements. You pay an hourly or monthly rate.

This is the default first step for most enterprise buyers because setup cost is low, hiring is fast and exit is easy. Working with an enterprise IT staffing company in India gives you this speed without opening an Indian entity.

There is one catch: staff augmentation is not a managed service. Your team still has to manage the engineers. If you don’t have that bandwidth, the model gets expensive fast.

Build-Operate-Transfer (BOT)

A vendor builds a dedicated center for you. It hires the team, sets up the office and runs delivery. Then it hands everything over to you on a fixed date, usually in year 2 or 3.

Several things should transfer to you:

• the employees
• the office lease
• EPFO and payroll accounts
• tools
• runbooks

Some things do not transfer by default: the vendor’s bench, its recruiter network and its own proprietary tools. Negotiate those upfront. We cover each phase in our guide on how the BOT model works for a GCC.

Captive GCC

You set up your own Indian company, usually a Private Limited company, and hire engineers directly. There is no vendor layer. You own employment, compliance, the office, payroll and delivery.

A captive is the cleanest model for IP and long-term cost. It is also the hardest to run in years 1 and 2. That is why most buyers bring in GCC setup services for entity registration, leasing and leadership hiring.

India GCC vs Offshore Vendor vs BOT: Real Costs

Here is how costs compare for a 50-engineer team on an enterprise stack. The staff aug figures assume a blended rate of $80 per hour.

Two numbers in this table matter most.

The vendor margin adds up. Staff aug has no setup cost, but at 80+ engineers the margin can reach $3–4M a year. That is the point where the captive math starts to win.

Captive savings come later. By year 3, a captive saves $3.5–4M a year compared with staff aug. But it has to absorb 600K–1.1M in setup costs in year 1 first.

Supersourcing data: We looked at 12 completed BOT engagements in our portfolio. On average, BOT became cheaper than equivalent staff aug at month 28.

• Buyers who transferred at month 24 broke even by month 31.
• Buyers who stretched the operate phase to month 36 broke even by month 38.

From the deal floor: A US insurance technology company modeled all three options for a 60-engineer ServiceNow practice. The five-year NPV came out at:

• $41M for staff aug
• $29M for BOT
• $24M for a captive

The captive won on paper by $5M, but they chose BOT anyway. They didn’t have the India management bandwidth to run a captive in years 1 and 2. The best financial answer was the wrong operating answer.

For a full five-year cost model, see our breakdown of GCC total cost of ownership.

How Long Each Model Takes to Get Running

Speed is where the three models differ most.

Notice periods are the factor most buyers underestimate. Senior engineers in India usually serve 60–90 days’ notice. That includes SAP leads, Salesforce architects and ServiceNow CTAs.

Red flag: Watch for a vendor promising a ServiceNow CTA or SAP S/4HANA architect in under 30 days. Either they are overstating the candidate’s seniority, or they are asking the candidate to skip their notice period. You inherit both problems.

From the deal floor: A DAX-listed automotive company started a captive setup in January 2023. Their target was 40 engineers by December, but they reached only 18 by then. Several things went wrong:

• Their GCC Head, hired from TCS, quit in month 7.
• Entity registration took 11 weeks instead of 6.

They finally hit 40 engineers in month 19. By then, their program had slipped by two quarters.

IP, Compliance and Control: Who Carries the Risk?

In the India GCC vs offshore vendor vs BOT comparison, risk moves from the vendor to you as you move toward a captive.

IP ownership. In staff aug, engineers are vendor employees. Under Section 17 of the Indian Copyright Act, the employer is the default owner of their work. Here, that employer is the vendor, and contract language in the MSA alone is not enough to change it. The fix is to get a signed IP Assignment Deed from each engineer on day one. The same rule applies during a BOT’s operate phase. On top of that, the transfer agreement must hand over all assigned IP. In a captive GCC, engineers are your own employees from the start, so standard employment contracts cover IP.

Compliance. With staff aug, the vendor handles payroll, PF, ESIC and labour law. The same is true for BOT until the transfer date. With a captive, all of this becomes yours, along with ROC filings, board meetings and transfer pricing.

A captive makes you an Indian employer. All four Labour Codes came into force on 21 November 2025, and the central rules followed in May 2026. But states are still notifying their own rules at different speeds, as Khaitan & Co’s July 2026 employment bulletin shows. Budget for a local compliance team from day one. Anyone who calls Indian entity compliance “straightforward” has never run an Indian payroll.

Transfer pricing is the other big item. Read our guide on transfer pricing for GCCs before you set intercompany rates.

Attrition: The Cost Nobody Budgets For

Attrition is where the India GCC vs offshore vendor vs BOT choice has consequences buyers don’t expect. Typical annual rates look like this:

• Staff aug: 11–15% a year. The vendor pays for replacements, so it has a strong reason to retain people.
• BOT, operate phase: 13–18%. The team knows a transfer is coming, and that uncertainty drives exits.
• BOT, transfer window: a spike to 18–28%. This is the riskiest period in any BOT.
• Captive, years 1–2: 20–28%. You are a new brand with no culture yet, and you pay every replacement cost.
• Captive, year 3 and beyond: settles at 10–14%.

Supersourcing data: Our GCC Benchmark 2026 covered 340 engagements. In the 90 days around a BOT transfer, attrition averaged 23%, against 13% in the year before. Buyers who negotiated a 6-month vendor retention clause saw only 11%.

How to keep your team through a BOT transfer:

1. Announce the transfer at least 6 months ahead. Engineers who hear about it through rumours leave faster.
2. Offer retention bonuses tied to 12 months of service after transfer. ₹3–5 lakh per senior engineer is typical, and it works.
3. Share the post-transfer org chart early. Unclear reporting lines are the top reason people leave.
4. Have the vendor backfill any exits for 6 months after transfer, at its own cost.

When Each Model Wins

The right answer depends on your stage. Here is how to match the India GCC vs offshore vendor vs BOT options to your situation.

Choose an Offshore Vendor (Staff Augmentation) When…

• You need engineers in under 60 days.
• You need fewer than 40 engineers. Below that size, the vendor margin costs less than running your own setup.
• Your internal team can manage delivery, QA and escalations.
• Your program runs for less than 3 years. BOT and captive only pay back after about 2.5–3 years.
• This is your first India engagement and you want to learn with lower risk.

From the deal floor: A US healthcare SaaS company needed 25 Salesforce Health Cloud developers for an 18-month program.

• BOT was ruled out because 12–16 weeks to the first engineer would have used up 20% of their runway.
• They went with staff aug instead and had all 25 developers productive in 14 weeks.
• They delivered the program on time.

Teams in a similar spot can hire Salesforce developers in India on the same model. For a side-by-side view, read our GCC vs staff augmentation comparison.

Choose BOT When…

• You want a captive eventually, but not the year-1 pain.
• Your target is 40–150 engineers over 3–5 years.
• You don’t have an India country head or GCC Head yet.
• Your program can wait 90–120 days for the first engineer.
• You want the vendor to be accountable for delivery, not just headcount.

From the deal floor: A DAX-listed industrial manufacturer went BOT with Supersourcing in 2021 for an SAP S/4HANA brownfield migration. The team was 65 consultants in Bangalore. The vendor ran delivery for 28 months, and the transfer closed in Q2 2026. At transfer, the client inherited:

• a 71-person team
• a Bangalore lease locked at 2021 rates
• three years of runbooks and onboarding material

Their setup fee was $280K. A similar captive built from scratch at 2026 rates would cost $1.4M or more.

Choose a Captive GCC When…

• You plan for 100+ engineers over 5+ years.
• Your IP cannot sit with a vendor, even with IP Deeds in place. Regulated data and defence-adjacent work are typical examples.
• You can hire a GCC Head, an HR lead and a finance and compliance lead.
• Your India team needs its own career ladder, equity and internal mobility.
• You already run a BOT and the transfer date is getting close.

Red flag: Don’t register the entity before you hire a GCC Head. Our GCC Benchmark 2026 shows that buyers who do this take an average of 7 extra months to reach full capacity. Strong RPO services can help you fill leadership and first-wave roles faster.

The Path Most Companies Actually Take

In theory, you pick one model. In practice, most buyers move through all three:

• Year 0–1: Staff augmentation. Learn to manage offshore delivery and test the talent market for your stack.
• Year 1–2: Start a BOT. The vendor builds a dedicated center while you hire India leadership.
• Year 3–4: Transfer to a captive. The team, lease and EPFO accounts move into your entity. Keep the vendor on for niche skills and demand peaks.

Each stage builds the skills the next stage needs. Buyers who jump straight to a captive often slide back into depending on a vendor.

Supersourcing data: We looked at our clients who crossed 50 engineers in India.

• 67% started with staff aug.
• 21% started with BOT.
• 12% started with a captive.

Of that captive-first group, 8 out of 12 brought in a vendor within 18 months to cover capacity gaps.

What Most Teams Get Wrong

Most teams treat the India GCC vs offshore vendor vs BOT decision as a cost question. It is really a capability question. The cheapest five-year model fails if you can’t run it in year one. Buyers also make three expensive mistakes:

• signing BOT deals without a fixed transfer date
• skipping per-engineer IP Deeds
• ignoring the attrition spike at transfer

Each one costs more than the margin they were trying to save.

The other common mistake is choosing a city for its rent instead of its talent. Pick a city based on your stack:

Our guide on how to choose a GCC location goes deeper.

How to Check a BOT Vendor’s Track Record

Many vendors claim BOT experience, but few have actually completed a transfer. Run these five checks before you sign.

1. Ask for completed transfer references, not ongoing ones. Get the names of the client GCC Heads who managed each transfer. Then call them.
2. Ask for their transfer checklist. A real one covers employee consent, EPFO transfer, lease novation, tool offboarding and knowledge transfer. Expect 40 or more line items.
3. Ask for attrition numbers from their last transfer window. If they can’t give you a specific number, they have never managed a transfer.
4. Ask which entity type they used at transfer. Experienced vendors answer right away, explain why they chose it, and name the CA firm that handled it. “It depends” is a dodge.
5. Check the MCA registry. Search the named client’s India entity on mca.gov.in. If there is no entity, there was no transfer.

What Your BOT Transfer Clause Must Cover

The transfer clause is the most important page in a BOT agreement. If it is vague, you end up in a tense negotiation in month 30, and that never favours the buyer.

Your clause should list everything that transfers at no extra cost:

• All employees who consent to move, with continuity of service for gratuity.
• The office lease, by novation, with the vendor paying any landlord consent fees.
• All EPFO and ESIC accounts for those employees.
• Tools and licences used only for your engagement.
• All runbooks, onboarding guides, architecture documents and RAID logs.
• All code repositories, CI/CD configurations and infrastructure-as-code, held in your own version control.

Also lock in these terms:

• a fixed transfer date
• a transfer fee that is $0 or capped
• 6 months of vendor-funded retention support after transfer
• a 90-day knowledge transfer overlap
• a step-in right if the vendor runs into trouble

For staff aug, the must-haves are simpler:

• per-engineer IP Assignment Deeds
• a two-way, 24-month non-solicit clause
• a 14-day substitution notice
• a replacement SLA
• a cap on annual rate increases
• a data processing agreement covering GDPR, India’s DPDP Act and CERT-In’s 6-hour breach reporting rule

For a captive, sign the lease in your own entity’s name from day one. Never sign under a vendor’s entity, even for a short time.

Decision Matrix: Which Model Fits You?

Score your situation against each row. The model with the most matches wins. If BOT and captive tie, choose BOT: year-1 risk is lower, and you end up in the same place.

Not Sure Which Model Fits? Start Here

Most buyers spend more time choosing an office furniture vendor than choosing their India engagement model. Yet this decision sets your year-1 cost, your year-3 economics, your IP position and your exit options for the next five years.

The right answer is rarely the most complex one. It is the one that matches your team’s capability, your budget and how committed you really are to India.

If you are unsure, start with staff augmentation, learn from it, then decide. If you already know you need a long-term team, you can hire dedicated development teams now and grow into a BOT later.

Want help working through the India GCC vs offshore vendor vs BOT decision for your headcount, stack and timeline? It takes a 30-minute call. No deck, just the numbers.

Book a 30-minute Enterprise Discovery Call →

Frequently Asked Questions

What is the difference between BOT and managed services?

In managed services, the vendor owns the outcome and you pay for results. In BOT, you direct the delivery and the vendor provides the operating setup. BOT ends with ownership moving to you. Managed services don’t.

What is the minimum team size for BOT to make sense?

About 20 engineers. Below that, a setup fee of 150K–400K is too large compared with the savings you get after transfer. Staff aug works better for smaller teams.

Do engineers have to agree to a BOT transfer?

Yes. In India, employees cannot be moved to a new employer without their consent. Most agree if pay and growth prospects are equal or better. Still, plan to backfill the 5–15% who say no.

What happens to gratuity when engineers transfer?

Gratuity now falls under the Code on Social Security, 2020. Your transfer clause should keep service continuous, and the new employment contracts should recognise past service dates. If continuity breaks, gratuity may become payable at transfer. Check that the vendor has been setting money aside for it.

How does transfer pricing work for a captive GCC?

Your India entity bills the parent company at an arm’s-length markup. From April 2026, eligible IT services entities can choose a single safe harbour margin of 15.5% on cost. The eligibility threshold has also been raised to ₹2,000 crore. Get a transfer pricing study done before you fix your rates.

Should a captive GCC be a Private Limited company or a branch office?

Almost always a Private Limited company. Branch offices need RBI approval and face limits on retained earnings. The difference in setup cost is small.

Can I run staff aug and BOT at the same time?

Yes, and many buyers do. A common setup is to keep the core team on BOT and use staff aug for niche skills. Just structure the contracts so the non-solicit clauses don’t clash.

How much does it cost to shut down a captive GCC?

For a 50-person center, expect 400K–900K in severance, lease break fees and wind-up costs. Under the Industrial Relations Code, establishments with 300 or more workers also need government permission to retrench staff. This is why BOT’s exit flexibility has real value.

How do I benchmark a BOT setup fee?

For 50 engineers in Bangalore, 200K–280K is a reasonable fee. If a vendor quotes above $400K for the same scope, ask for a line-item breakdown. Some vendors hide 18 months of margin inside the setup fee.