// GCC Sales Enablement · FAQ Reference Guide
This reference covers the 35+ most common questions sales reps face when prospecting and advancing GCC conversations — with lead-in openers, answer frameworks, and bridge questions to keep momentum.
// Conversation Starters
Use these lead-in questions to surface the buyer's real pressures before pitching anything. They work on cold calls, discovery calls, and executive briefings.
// Frequently Asked Questions
Tap any question to expand the answer. Use filters to navigate by topic, or search for keywords.
A GCC — Global Capability Center — is a wholly-owned subsidiary of a parent company, set up in a lower-cost geography like India to deliver technology, analytics, finance, or operations work. The critical word is owned. Your people, your IP, your processes — run under your brand, your governance, your culture.
The GCC model has matured in India over 30+ years. Over 2,100 GCCs now operate in India, employing 2.36 million professionals. This is no longer an experiment — it is standard enterprise operating model design.
It starts as a cost play for many companies. That's legitimate — a 40–60% reduction in fully-loaded FTE costs is significant. But the companies that built GCCs 5–10 years ago for cost reasons now use them as their primary engineering, AI, and product development hubs. That's the maturity curve.
India today has 16% of global AI talent. Companies like Google, JPMorgan, and Walmart run major product and AI programs out of India — not support functions. That's the direction the model is moving.
Other geographies serve specific niches well — Eastern Europe for nearshore European time zones, Latin America for US nearshore in certain roles. But India is in a category by itself for tech-led GCCs at scale:
Talent depth: India produced 2.5 million technically skilled graduates in 2022–23. No other country comes close at that volume with English proficiency and global work culture combined.
Ecosystem maturity: The GCC model has been operating in India for 30+ years. Legal, HR, real estate, payroll, and compliance infrastructure is well-established across six major cities and a growing Tier 2 market.
Government support: Central and state governments actively provide incentives — SEZ tax holidays, T-AIM programs in Telangana, state-level subsidies — specifically for GCC setups.
The conventional wisdom was that GCCs required 500+ FTE and Fortune 500 backing. That's no longer accurate. The mid-market inflection point has arrived — companies with $500M–$5B in revenue are now establishing viable GCCs starting at 50–150 FTEs.
Three factors have changed the math: the BOT model absorbs setup risk, Tier 2 cities (Pune, Ahmedabad, Coimbatore) offer lower cost bases, and GCC-as-a-service providers like YASH handle the infrastructure so the client isn't starting from zero.
The GCC doesn't compete with your outsourcing partner — not directly, and not immediately. Think of it as a question of which work is strategic enough to own.
The deeper issue is that over time, outsourcing accumulates a hidden cost: your vendor owns the institutional knowledge, the team relationships, and the context that makes your technology work. When the contract ends or the team turns over, that knowledge disappears. A GCC stops that drain.
The functions that work best in a GCC are those with high skill requirement, stable or growing scope, and significant IP content. In practice for technology-led GCCs, that includes: software engineering, data and AI, QA and testing, cybersecurity operations, cloud engineering, SAP development, and finance shared services.
What typically stays onshore: senior product leadership and strategy, customer-facing account management, regulatory-intensive functions requiring local presence, and work requiring physical proximity to operations or customers.
This is one of the most important objections to handle carefully — and it requires a discovery question before any response. A previous failure could trace to governance problems, poor talent strategy, timezone management, scope creep, leadership gaps, or an under-designed operating model. Each of these has a different fix.
What you can say after listening: "Most GCC failures we see trace back to one of three gaps — an operating model that wasn't designed for two-sided governance, a talent strategy that didn't account for the specific skill demand in that city, or a leadership absence in India in the early months. YASH's framework addresses all three explicitly because we've seen each one play out."
Setup costs for a greenfield GCC vary significantly based on city, headcount trajectory, and what you're building — but directionally:
One-time setup investment (legal entity, facility fit-out, IT commissioning, seed hiring, compliance): typically $500K–$2M for a 50–100 FTE initial center. We also provide 0 Capex model with Pay as you go - GCC as A Service model
Ongoing operating cost for a 100-FTE tech GCC in a Tier 1 city (Bengaluru/Hyderabad) runs 40–60% below equivalent US teams on fully-loaded basis. In Tier 2 cities, that spread widens further.
Payback period: Most YASH-modeled GCCs reach payback in 18–30 months depending on ramp speed and starting headcount.
The risk concern is real for a direct greenfield setup — and that's exactly why the BOT model exists. In the BOT structure, YASH takes on the setup risk: we establish the legal entity, hire the team, commission the facility, and operate to SLAs. You receive a running GCC with people and processes already working.
For size: mid-market GCCs starting at 50–100 FTEs in Pune or Hyderabad operate on a cost base that makes the business case work even for companies under $1B in revenue. Size is no longer the barrier it was five years ago.
BOT stands for Build-Operate-Transfer. It's a three-phase model:
Build (3–9 months): YASH sets up the legal entity, leases or establishes the facility, commissions IT infrastructure, hires and onboards the seed team (typically first 25–50 FTEs). You provide strategic direction; we handle execution.
Operate (18–36 months): YASH runs the GCC under a "run-it-like-a-captive" principle — SLA-governed, with your culture and brand embedded. Scale increases to target headcount. Progressive control transfer begins.
Transfer (6–12 months): Legal entity, team, IP, assets, and processes novate to the client. The center continues without disruption post-transfer.
The honest answer: year 1 is an investment year. You're building the team, establishing process, and absorbing setup costs. The ramp is real, and anyone who tells you the GCC pays back in month 6 is not being straight with you.
Typical ROI curve under a BOT model: break-even at 18–24 months, meaningful positive ROI by year 3, compounding value in years 4–5 as the center builds institutional knowledge, AI capability, and can absorb work that would otherwise need expensive onshore hiring.
Yes — India has two primary frameworks for tech GCCs, each with material tax benefits:
SEZ (Special Economic Zone): 10-year tax holiday on export income, requires a facility commitment and 100% export mandate. Best for larger GCCs with defined infrastructure needs.
STPI (Software Technology Parks of India): Simpler registration, no land/building commitment, better for software services startups and smaller initial setups. The more common choice for mid-market GCCs.
State governments add further incentives — Telangana's T-AIM program, Karnataka's GCC Policy 2024, and others provide stamp duty waivers, power subsidies, and hiring support.
YASH's GCC services follow a phased commercial model aligned to the Value Journey: Advisory, Build, Operate, and Transform are each separately scoped. This means clients can engage YASH at any stage — not just greenfield.
Advisory: Typically a fixed-fee engagement for strategy, business case, location analysis, and TOM design. Scoped to the specific deliverables needed.
Build: Fixed-price or milestone-based, covering entity setup, facility, compliance, and initial hiring.
Operate: Monthly fee structure based on FTE count and services scope — adjusted as the GCC scales.
That is one of the primary medium-term returns. Companies with mature GCCs (3+ years) typically see a meaningful reduction in their outsourcing spend as they absorb work in-house. The GCC becomes the internal capability, and the external vendor relationship shrinks to variable or specialist work.
YASH's own position in this is worth noting: we are often the transition partner who helps build the GCC, and we remain a transformation partner for AI, SAP, and specialized programs. The GCC doesn't remove YASH from the picture — it elevates the nature of the engagement.
For a greenfield GCC via BOT, the build phase runs 3–9 months to first FTEs onboarded and delivering. The standard greenfield timeline for a fully operational center (50+ FTEs) is 12–18 months.
What makes this faster with a partner like YASH: existing legal entity infrastructure in India, established facility relationships, a talent acquisition engine already running in key cities, and pre-built compliance frameworks. You're not starting from zero.
This is addressed directly by the Operate phase of the BOT model. During operate, YASH provides embedded GCC leadership — a country head or GCC director, delivery managers, HR, and operations — for the transition period. The client provides strategic direction; we provide the India-based leadership.
Over the operate period, YASH progressively transfers decision-making authority to client-led roles. By the time transfer occurs, the GCC has its own leadership team, established processes, and doesn't depend on HQ bandwidth to function day-to-day.
The right answer depends on your headcount trajectory, skill mix, and cost parameters. The primary GCC cities and their positioning:
Bengaluru: Deepest talent pool for senior engineering and AI roles. Highest cost base, highest attrition (18–20%). Best for large-scale innovation-led GCCs (500+ FTE target).
Hyderabad: Strong tech talent, 15–20% lower cost than Bengaluru, T-AIM state support, lower attrition. Excellent for mid-size GCCs targeting scale.
Pune: Strong for engineering and manufacturing-tech. 20–30% below Bengaluru cost, 14% attrition, capped at ~250 FTE for very senior profiles.
Chennai: Strong for BFSI, automotive tech, and manufacturing. Mature talent base, stable attrition.
NCR (Gurgaon/Noida): Strong for enterprise tech, consulting-adjacent functions, BFSI. Larger lifestyle draw for senior leaders.
Ahmedabad / Tier 2 cities: Lowest cost, captive talent pools with less competition, growing infrastructure. Right for companies prioritizing retention and cost over senior talent depth.
The time zone gap is real and requires deliberate design — not just goodwill. What works in practice:
Indian GCC teams typically operate on a hybrid shift — core hours that overlap with US mornings by 2–4 hours. India-side leadership often works late to overlap with US executive hours. For US East Coast companies this overlap is more workable than for US West Coast.
The model that works best: asynchronous-first communication design, well-defined handoff protocols, and a governance cadence that doesn't require real-time alignment for routine decisions.
IP protection is actually a key argument for a GCC compared to outsourcing. Because the GCC is your subsidiary, your governance, your policies — IP protection is structurally stronger than relying on a vendor's contractual commitments.
Standard IP protection in a GCC includes: all employees sign NDAs and IP assignment clauses, role-based data access controls, secure IT perimeter (often in purpose-built tech parks), regular third-party audits from firms like Deloitte, PwC, and KPMG, and thorough background screening for all hires.
India's talent market makes scaling significantly more straightforward than in North America or Western Europe. The pipeline of STEM graduates running at 2.5 million per year means headcount growth of 20–30% annually is achievable without competing for scarce talent.
Tier 1 cities (Bengaluru, Hyderabad) support larger scale but come with more competition for senior profiles. Tier 2 cities (Pune, Ahmedabad, Coimbatore) offer more captive talent pools and lower attrition for focused skill profiles.
Most GCCs start at 25–50 FTEs and expand to 200–500+ within 3–5 years. The challenge is usually managing the capability maturity curve as scale increases, not finding the headcount.
Yes — and YASH's GCC-as-a-Service model is specifically designed for this entry point. At 20–30 FTEs, a standalone entity with full infrastructure isn't cost-effective. The GCC-as-a-Service model lets you operate within YASH's existing India infrastructure — space, HR systems, legal entity — and expand when you're ready.
India passed the Labour Codes 2020, which consolidate 29 legacy labor laws into 4 codes. For IT/tech GCCs the practical implications:
Notice periods: Typically 30–90 days, negotiated in the employment contract. This is longer than US norms but similar to European standards.
Termination: In the IT sector, performance-based exits follow structured processes similar to US practices. Unions are essentially non-existent in IT/tech environments.
Compliance: PF (Provident Fund), ESI, Professional Tax, and Gratuity are mandatory employer obligations that factor into fully-loaded FTE costs.
The "inconsistent quality" perception usually comes from one of two things: a bad experience with a staffing firm deploying commodity resources, or an offshore team that was under-spec'd for the work assigned. City and domain specificity change the picture entirely.
India has a mature, stratified talent market. Senior engineers with 10–15 years of experience who have worked at Microsoft, Google, or global banks in India are as strong as their counterparts anywhere. The question is whether your hiring criteria and compensation are targeted at that stratum.
The GCC industry-wide attrition average runs 12–18% annually. For well-managed GCCs with structured career pathing and competitive compensation, that drops to 8–11%. That's comparable to or better than US tech industry averages.
The drivers of attrition are well understood: compensation that falls behind market, limited career growth visibility, poor management quality, and lack of connection to the parent company's mission. Each of these is a design decision, not a market inevitability.
Specific retention levers that work: competitive total compensation, visible promotions on 18-month cycles, leadership visits from HQ, strong India-side people management, and a sense of meaningful work rather than task execution.
Culture is the single most underinvested element in GCC setups and the one most correlated with long-term success. The companies with the strongest GCC cultures share several practices:
Strong India-side leadership who carry the culture and are empowered to make decisions — not just execute instructions. Frequent executive visits from HQ (quarterly at minimum). Shared rituals — all-hands, recognition programs, cross-geo team events. Clear work that's meaningful, not task queues from HQ that have no visible impact.
Indian work culture has historically been hierarchical — people wait for direction rather than pushing back or taking initiative. This is changing rapidly, particularly in the post-pandemic generation of professionals who have worked in global-model companies and are accustomed to flat structures and direct communication.
The honest answer: accountability and autonomy are outputs of design, not geography. Clear role ownership, defined decision rights, and leadership that rewards judgment rather than just compliance will produce accountable, autonomous behavior in India exactly as it does elsewhere.
India has a large number of national and state holidays — typically 12–15 per year across different regions. But GCC leave policies are structured and managed with rotation planning, similar to how US companies plan around Thanksgiving and Christmas periods.
Most multinational GCCs establish a defined calendar of public holidays specific to their location, with team rotation coverage for critical functions. This is standard HR design, not an India-specific operational risk.
English is the medium of instruction across most engineering and business programs in India. In the established GCC cities, professional English proficiency is the norm at mid to senior levels — not the exception.
Many senior Indian professionals have worked in the US, UK, or Australia for multiple years and bring global work culture back with them. This creates a substantial leadership layer that communicates comfortably with US executives.
The most significant shift in the GCC model over the last 5 years is exactly this: India now holds 16% of global AI talent. The companies leading in GCC maturity are doing product engineering, ML model development, data platform ownership, and enterprise AI from India — not just IT support.
Companies like JPMorgan, Goldman Sachs, Walmart, and hundreds of others are running core product and technology programs out of Indian GCCs, not just back-office functions. The "IT support center" model is GCC 1.0. GCC 2.0 and 3.0 are capability and innovation plays.
India's Digital Personal Data Protection (DPDP) Act 2023 is India's primary data privacy framework. It aligns with the general principles of GDPR (consent, purpose limitation, data subject rights) but has some differences in implementation and enforcement mechanics.
For BFSI and healthcare GCCs handling sensitive data, the DPDP Act adds a layer of compliance obligation that requires specific IT and governance design. Cross-border data transfer rules under the Act are still being finalized through subordinate regulations.
A Special Economic Zone (SEZ) is a designated area in India where companies receive significant tax incentives — primarily a 10-year tax holiday on income from exports — in exchange for operating under specific conditions: 100% export mandate, approved facility within the SEZ boundaries, and ongoing compliance reporting.
SEZ is best suited for: larger GCCs with a defined long-term facility commitment, where the tax holiday value outweighs the operational constraints.
STPI (Software Technology Parks of India) is the simpler alternative — registration-based, no land commitment, faster to activate. Better for: early-stage GCCs, software services work, companies that need flexibility on facility choices.
For most GCCs, the right structure is a wholly-owned subsidiary (Private Limited company under Indian Companies Act). This gives full operational flexibility — the ability to hire, contract, own assets, and operate as an independent legal entity.
A branch office is simpler to set up but more restricted — it cannot independently earn revenue in India and is directly liable under the parent's balance sheet.
A liaison office is the most restricted form — only permitted for representational activities, no business operations.
India has a well-established common law legal system, directly derived from English law. Contract enforcement and commercial dispute resolution are established and predictable, particularly for IT and professional services.
The practical consideration: Indian courts can be slow for litigated disputes, which is why commercial contracts for GCCs routinely include arbitration clauses specifying a neutral arbitration forum (SIAC, ICC, or the Indian Arbitration Act). This is standard practice, not a workaround.
US-India relations are among the most stable bilateral relationships in the global technology sector. India is not China — the geopolitical risk profile is fundamentally different. India is a democratic country with a pro-trade, pro-investment posture that has been consistent across multiple governments.
The Indian government at central and state level is explicitly pro-GCC. This is a deliberate economic development strategy with cross-party support — it doesn't change with elections.
Exit from an Indian subsidiary is structured but manageable. Key obligations: statutory notice to employees (30–90 days depending on contract terms), settlement of statutory dues (provident fund, gratuity), regulatory filings with the Registrar of Companies, and winding down or novating contracts.
In a BOT model, the exit scenario at transfer is actually a designed handover — the entity novates to the client. If the client chooses not to take transfer and exits entirely, YASH's contract typically governs the wind-down process.