GCC vs IT Subsidiary vs BOT(Build-Operate-Transfer) Model in India: Which Works Best for Foreign IT Companies

More than 1,700 Global Capability Centres now operate across Bengaluru, Hyderabad, Pune, Chennai, and NCR, employing nearly two million professionals. India is no longer a low-cost delivery location that companies hedge on. It is where engineering decisions get made, where AI and data science teams are built, and where companies are placing long-term strategic bets. The question foreign IT companies are actually asking in 2025 is not whether to enter India. It is which model to use and when. GCC vs IT Subsidiary India is the core decision, and the BOT model is a third path that sits between the two. Each has different implications for capital commitment, IP ownership, compliance exposure, and operational control. Getting this wrong is expensive to fix. This guide maps all three against the business profile they suit.

What Is the Difference Between a GCC, an IT Subsidiary, and a BOT Model in India?

A GCC is a captive operational unit owned by the foreign parent that provides technology, analytics, or business services internally. An IT Subsidiary is a commercial entity selling software or services externally. The BOT model India IT Company is a third-party-led setup where a service provider builds and operates the Indian entity before transferring complete ownership. The process is to setup a Private Limited Company for all the three types, but the purpose, compliance obligations, and risk profile differ significantly. These are not three types of legal entities. They are three strategic models, each of which can be structured as a Private Limited Company under the Companies Act 2013. What differs is the purpose of the entity, who runs it during setup, who the clients are, and what the transfer pricing and IP ownership implications look like. A GCC delivers services exclusively to its foreign parent. It does not sell to external Indian clients. Its revenue is an intercompany charge from the parent. An IT Subsidiary, by contrast, sells software products or IT services to third-party clients in India or abroad. The GCC vs IT Subsidiary India distinction matters enormously for how the entity is taxed, how its intercompany transactions are priced, and what regulatory approvals it needs. The BOT model is not a separate entity type at all. It is a phased delivery framework where a third-party service provider incorporates the Indian entity, staffs it, manages operations, and then transfers the entity and employees to the foreign parent after 18 to 24 months. At the point of transfer, what the foreign parent receives is a fully operational Private Limited Company with an existing team, existing compliance history, and no setup learning curve.

What Are the Legal and Regulatory Implications of Each Model?

In the GCC vs IT Subsidiary India comparison, both require a Private Limited Company incorporated under the Companies Act 2013 with 100% FDI permitted under the Automatic Route for software and IT services. The GCC has heavier transfer pricing obligations since all revenue is intercompany. The IT Subsidiary has external client contracts and commercial GST obligations. The BOT model India IT Company uses introduces a third-party entity as interim employer, which creates a separate layer of contractual and IP risk during the operate phase. For a GCC, the legal framework is relatively clean at the entity level. A Private Limited Company is incorporated, 100% owned by the foreign parent. FC-GPR is filed within 30 days of share allotment. The complication is not the incorporation — it is the intercompany service agreement. Every rupee the GCC charges its parent is a related-party transaction subject to transfer pricing under Sections 92 to 92F of the Income Tax Act (Section 161 to 164 of Income Tax Act, 2025). The pricing methodology, whether cost-plus, revenue-share, or profit-split, must be documented annually in a Transfer Pricing study and reported in Form 3CEB (Form 48 of Income Tax Act, 2025). Indian GCCs providing technology development services to foreign parents are among the most actively audited entities by the Indian Income Tax department. No overarching legislation governs GCCs, though those established in Special Economic Zones and International Financial Services Centres are regulated under the Special Economic Zones Act 2005 and the GIC Regulations respectively. Outside SEZ structures, a GCC is simply a Private Limited Company with an intercompany service model. For an IT Subsidiary, the compliance picture is different. External client contracts mean commercial GST obligations, revenue recognition under Ind AS 115, and in many cases export of services with LUT filing and SOFTEX reporting if STPI-registered. The transfer pricing obligation still exists if the subsidiary licenses technology from or pays royalties to the foreign parent, but the external revenue base gives the Indian entity more pricing flexibility and a cleaner arm’s length comparator. The BOT model introduces the Employer of Record as a legal firewall between the foreign company and Indian regulatory agencies during the build and operate phases. During the first 12 to 18 months, the BOT partner is the legal employer, absorbing compliance liability for payroll, labour law, and tax withholding. This is genuinely useful for foreign companies with no Indian expertise. The risk is in the transfer. If the BOT contract does not correctly specify IP ownership, data handling, client confidentiality, and employee transition terms from day one, the transfer phase becomes contested.

How Do the Three Models Compare on Cost, Control, and Timeline?

The GCC built independently (called the DIY or Captive model) has the highest upfront cost and longest setup timeline but full control from day one. The BOT model India IT Company uses compresses timeline to weeks for first hire and spreads CapEx over 9  to 12  months, but reduces early control. The IT Subsidiary depends on the business model but typically resembles the DIY GCC in setup cost and timeline.

Dimension	GCC (DIY/Captive)	IT Subsidiary	BOT Model
Legal entity	Private Limited Company	Private Limited Company	Private Limited Company (incorporated by BOT partner)
FDI route	100% Automatic Route	100% Automatic Route	100% Automatic Route (at transfer)
Setup timeline to first hire	3-6 Months	1-2 Months	15-20 working days
Typical cost (20 to 50 person centre)	High upfront CapEx	Moderate, spread over growth	Depends on operations of Project
IP ownership during setup	Foreign parent from day one	Foreign parent or Indian entity	Contractually defined, risk until transfer
Transfer pricing complexity	High (all revenue intercompany)	Moderate (mixed revenue)	High post-transfer (same as Captive)
Control	Full from incorporation	Full from incorporation	Limited during operate phase
DPDPA exposure	High (processes employee and client data)	High (processes client data)	Shared with BOT partner during operate phase
State incentive eligibility	Yes (GCC policies across states)	Depends on sector	Yes, post-transfer

A typical BOT project for a 20 to 50 member captive centre can range from USD 800,000 to USD 2 million over an 9  to  12 month concession period, depending on city, infrastructure setup, salaries, and service provider margins.

What Are the Transfer Pricing Risks in the GCC vs IT Subsidiary India Decision?

In the GCC vs IT Subsidiary India comparison, GCCs face the most intensive transfer pricing scrutiny because 100% of their revenue is intercompany. The Indian Income Tax department actively audits GCC service fees paid by foreign parents, particularly in technology development, analytics, and R&D, where intangible valuation is contested. IT Subsidiaries with mixed revenue face lower transfer pricing risk on the external revenue portion but still require arm’s length documentation for intercompany transactions. This is the compliance dimension that the GCC vs IT Subsidiary India debate most consistently underweights. Foreign companies evaluating the two models tend to focus on talent access and cost. The transfer pricing exposure in a GCC is an ongoing, annual obligation that only grows as the centre scales. The core question the Income Tax department asks in a GCC audit is whether the Indian entity is being fairly compensated for the services it provides to its foreign parent. A Japanese parent whose Bengaluru GCC employs 300 engineers but charges only a 5% markup on cost is an obvious audit target. The arm’s length standard requires either a cost-plus margin benchmarked against comparable Indian IT services companies, or a profit-split methodology that allocates group profits based on each entity’s contribution. For BOT model India IT Company structures, the transfer pricing complexity does not begin during the operate phase because the BOT partner is the employer and the Indian entity may not yet be fully active. It begins at transfer, at which point the entity has an established headcount, cost base, and service relationship with the foreign parent that must immediately be priced correctly and documented.

Which Model Is Right Based on Company Stage and Strategic Intent?

The GCC vs IT Subsidiary India decision depends on whether the India entity will serve internal or external clients, how much compliance risk the company can absorb during setup, and the long-term strategic importance of the India operation. The BOT model India IT Company uses suits companies entering India for the first time with a team target of 20 to 50 people who want eventual full ownership without the upfront regulatory burden. In 2025, the choice is no longer a simple control versus cost trade-off. It is a strategic architecture decision. BOT suits companies that want to avoid early cost shock while retaining a path to full ownership. Captive from day one suits companies where the GCC is a strategic moat and IP ring-fencing is non-negotiable. Light regulation environments like SaaS and consumer tech can use BOT or a direct captive. High regulation environments like fintech, healthtech, and industrial automation typically need a direct captive with strong compliance design from the outset. A practical decision framework:

Choose a GCC (DIY/Captive) when:

• The India operation will be a long-term strategic capability centre
• IP and data security are non-negotiable from day one
• The foreign parent has compliance infrastructure or an experienced advisory partner
• Team size target exceeds 100 people within two years
• The business operates in fintech, healthtech, defence-adjacent, or deep-tech sectors

Choose an IT Subsidiary when:

• The India entity will sell externally to Indian or global clients
• The business model involves licensing software or delivering managed services
• The company wants to build a commercial footprint in India’s domestic market
• Revenue-based STPI or SEZ tax benefits are being evaluated

Choose BOT when:

• The company is entering India for the first time with no local regulatory expertise
• The initial team target is 10 to 50 people with a plan to scale
• Speed to first hire is more important than day-one ownership
• The company is willing to invest in a detailed BOT contract that covers IP, data handling, and employee transition terms upfront

State GCC policies make the captive model more attractive than it was two years ago. Karnataka’s GCC Policy 2024 to 2029 targets setup of 1,000 GCCs by 2029. Gujarat launched its GCC Policy 2025 to 2030 offering employment-linked incentives and electricity duty exemptions. UP introduced its GCC Policy 2024 to capitalise on the state’s strategic location. Haryana’s GCC Policy offers 50% capital expenditure reimbursement for units in Gurugram. These incentives are available to direct captives, not to BOT structures during the operate phase.

Conclusion

The GCC vs IT Subsidiary India question has no universal answer, but it has a clear framework. GCCs suit companies building internal capability for the long term. IT Subsidiaries suit companies building commercial operations in India. The BOT model sits between the two and suits companies that want GCC ownership eventually but cannot absorb the Day One complexity of self-setup. What all three share: a Private Limited Company as the underlying legal entity, FC-GPR filing within 30 days of share allotment, annual transfer pricing documentation for intercompany transactions, and DPDPA compliance from the moment Indian personal data is processed. The model changes the path to the entity. The compliance obligations at the entity level remain. Corporate Legit Consulting LLP advises foreign IT companies on the GCC vs IT Subsidiary India decision, covering legal structure selection, Private Limited Company incorporation, FEMA and RBI compliance, transfer pricing framework design, state GCC incentive applications, and ongoing corporate and tax advisory. Reach out to Corporate Legit before selecting a model.