Most buyers have no idea how many moving parts a GCC involves. When you lay this out clearly, you establish credibility immediately. Use this as the "here's what you're signing up for" frame before you explain how YASH compresses or absorbs these steps.
A standard greenfield GCC involves six distinct workstreams running in parallel. Industry average to clear all six: 12–18 months.
What functions go to the GCC? What's the target operating model? What ROI threshold justifies this? This phase produces a feasibility study, location recommendation, and financial business case. Without it, companies either overbuild (overspend) or underbuild (can't scale).
This is where most first-timers get surprised. Setting up an Indian subsidiary requires MCA registration, PAN/TAN, Shops & Establishment Act registration, and — depending on the model — STPI or SEZ status. STPI is simpler, no land commitment, suits software-led GCCs. SEZ offers a 10-year tax holiday but requires 100% export revenue and long-term real estate commitment. Always flag regulatory timelines for legal review before quoting to any client.
Site selection, lease negotiation, fit-out, IT networking, physical security (access control, CCTV, demarcated zones), server room setup, end-user computing. This workstream alone runs 4–6 months in DIY GCCs. It's the single biggest source of delay.
HR entity registration (EPFO, ESIC, Professional Tax, Labour Welfare Fund), policy framework, compensation benchmarking, payroll platform, ATS setup, background verification vendors, offer and NDA templates — then actual hiring. Senior technical roles: 8–12 weeks per cohort.
How does the GCC connect back to HQ? Who owns SLAs? What's the escalation path? The Target Operating Model (TOM) answers these questions. GCCs without a TOM look like offshore teams with no direction — this is where the "we tried this before and it failed" story usually originates.
Structured KT from the onshore team to the GCC: process documentation, shadowing, parallel run, SLA baseline-setting. This phase is where the GCC either achieves operational credibility with HQ — or gets written off as "not ready."
When a prospect says "we're thinking about a GCC," ask them which of these six workstreams they feel equipped to run internally. The honest answer tells you exactly where YASH enters the deal.
Buyers will ask "so how does this work?" You need to answer for three distinct models without confusing them — and without confusing the buyer.
YASH's flagship model and the most common entry point for mid-market clients. The key thing to internalize: BOT is not outsourcing with an exit clause. The entire trajectory is toward client ownership. YASH runs it like a captive from Day 1.
End state: A fully owned Indian subsidiary — people, IP, processes, and assets — in the client's name.
| Variant | What's Different | Best For |
|---|---|---|
| Agile BOT | Faster build phase with smaller seed team | Clients wanting to prove the model before committing |
| T-BOT | AI/SAP transformation overlay during Operate phase | Clients who want a digitally capable GCC, not just a running one |
Client owns the GCC from Day 1. YASH provides hands-on support for specific workstreams: site selection, lease, regulatory filings, talent acquisition, IT commissioning.
Some workstreams owned by YASH, others by the client — tailored allocation based on gaps. Useful when the buyer has partial India experience but needs targeted augmentation.
Client sets up their own subsidiary. High CAPEX, high management bandwidth, longest timeline. YASH can provide advisory services only.
Don't walk the buyer through all four models in one go. Pick the one that fits their situation, go deep on that one, and offer to compare alternatives only if they ask. Confusion kills deals.
This is your most powerful commercial differentiator for mid-market buyers. Know it cold.
Traditional GCC setup requires substantial upfront capital: real estate deposits, fit-out costs, IT infrastructure procurement, HR tech licenses, legal and regulatory fees — all before a single productive employee is onboarded. For a 100–150 FTE greenfield GCC, that upfront CAPEX exposure can reach $500K–$1.5M, with 12–18 months of zero productivity from the center.
YASH GCC ReadyHub eliminates this entirely.
| Item | Traditional DIY | YASH ReadyHub |
|---|---|---|
| Upfront investment | $500K–$1.5M+ CAPEX | $0 — pure OPEX from Month 1 |
| When payments begin | Day 1 of lease signing | When first team member is onboarded |
| Real estate commitment | 5–10 year lease | None — YASH's existing facilities |
| What one fee covers | Separate contracts (facility, IT, HR, payroll) | One monthly fee: workspace + IT + HR + compliance + GCC PMO |
| Legal entity timing | Must complete before hiring | Runs in parallel; team starts on YASH payroll |
"You don't pay for infrastructure you're not yet using. You pay for a running team."
The CFO's objection to a GCC is almost always: "The business case looks good in Year 3, but the Year 0 and Year 1 cash outflow is a problem." The OPEX model removes Year 0 outflow entirely and converts Year 1 to a predictable monthly cost that tracks directly to headcount.
When Finance is in the room, switch from "cost advantage" language to "cash flow profile" language. Ask: "What does your capital allocation process look like for a greenfield initiative like this?" That question surfaces whether CAPEX approval is the real blocker — and positions the OPEX model as the answer before they raise it.
Credentials matter in two specific moments: when security or data protection concerns are raised, and when the buyer is comparing you to a specialist advisory firm. Don't lead with these — use them to close confidence gaps.
Highest process maturity rating. Delivery processes are quantitatively managed and continuously optimized. Cite when asked: "How do we know quality will be consistent?"
Information security management standard. Applies to physical and information controls across all YASH GCC facilities. Cite when the buyer's security or IT team asks about data controls.
Recognized in the ISG Provider Lens Global 2025 report for both GCC Design & Setup and GCC Optimization & Enhancement. Use when buyers want analyst validation.
CMMI 5 governed infrastructure across India, co-located with customer office spaces. 20+ years of GCC experience. 1,500+ professionals currently engaged in GCC models.
| Framework | What It Covers | When to Raise It |
|---|---|---|
| DPDP Act 2023 | India's Digital Personal Data Protection Act. YASH's operating framework is built with DPDP compliance embedded. | BFSI and healthcare GCCs; any buyer with EU/US data flowing to India. |
| IP Assignment | All employment contracts include IP assignment clauses; NDA templates are standard in the HR setup workstream. | When the buyer's legal team asks "who owns what the team creates?" |
| Labour Codes 2020 | YASH's HR setup incorporates India's consolidated labour code framework — exit norms, hiring practices, compliance obligations. | When buyer's HR team asks about India employment law complexity. |
Biometric and card-based access per client zone. Separate entry from shared YASH areas.
Dedicated, segmented network per client. Not shared with other tenants. ISP-level separation available.
24/7 video monitoring. Physical guarding. Environment monitoring for server/MDF-IDF rooms.
IFMA standards. Fire NOC compliance. ISO 27001 physical controls. EHS policy and drills.
Primary GCC cities where YASH has active infrastructure: Hyderabad (Gachibowli), Bengaluru (Manyata Tech Park), Pune (Kharadi), Indore, Chennai, Gurugram, Mumbai, Noida, Jaipur. The ReadyHub model gives clients immediate access to commissioned space in primary locations — no real estate transaction to get started.
Don't lead with credentials. Lead with the business problem, then use credentials to close confidence gaps. Mentioning CMMI 5 and ISO 27001 in the first slide sounds like a brochure. Mentioning them in response to "how do we know our data is safe?" sounds like the right answer.
All regulatory claims (STPI, SEZ, DPDP Act, Labour Codes) must be reviewed by YASH's legal or compliance team before inclusion in any client-facing proposal or contract discussion.
This is your speed-to-value story. It's the single biggest practical differentiator for a mid-market buyer who can't afford 18 months of runway.
The delay isn't talent — India's tech talent pool of 1.66 million GCC professionals is ready to hire. The delay is infrastructure and administrative setup: lease negotiation (2–4 months), fit-out (3–5 months), IT commissioning (2–3 months), legal entity registration (2–4 months), HR platform setup (1–2 months). These run sequentially or with only partial parallelism when the client manages them independently.
| Traditional DIY Blocker | ReadyHub Status |
|---|---|
| Lease negotiation & deposit (2–4 months) | Eliminated — YASH leases on client's behalf or uses existing YASH space |
| Fit-out (3–5 months) | Pre-completed — enterprise-grade workspace already commissioned |
| IT infrastructure (networking, security, EUC) | Pre-deployed — client gets a dedicated, isolated network segment from Day 1 |
| Legal entity registration | Parallel-tracked — initiated while team onboards under YASH payroll |
| HR & payroll setup | Active from Day 1 — YASH's existing HR framework applied immediately |
| Seed team hiring | Accelerated — proactive talent pools mean first 25–50 FTEs available within weeks |
"We can have your first 25 people in seats, in a physically secured, network-isolated environment in India, producing output against your governance framework, in about 6–8 weeks. The legal entity catches up while the team is already working — you're not waiting for paperwork to see value."
Lead with the timeline shock, not the cost savings. Mid-market buyers are time-poor. "12–18 months to a running GCC" lands harder than "30–50% cost reduction" because the timeline is a concrete obstacle they can feel right now.
Buyers who've been burned by offshore staffing are specifically afraid of getting "bodies" rather than a functioning capability. Address this proactively — it's often the biggest emotional objection in the room.
Traditional offshore staffing gives you individuals. It does not give you: a defined service catalog, standard operating procedures, knowledge management, quality benchmarks, or a career pathway that retains senior talent. When the engagement manager leaves, the knowledge walks out the door. That's the failure mode most buyers have already experienced.
YASH sets up Centers of Excellence (COEs) within the client's GCC. A COE is a capability unit with:
| COE Element | What It Means in Practice |
|---|---|
| Charter | What this COE owns, is accountable for, and is measured against |
| Leadership structure | Chapter Lead → Senior practitioners → Associates — not a flat resource pool |
| Process framework | How work is done, not just what is done — survives individual attrition |
| Tooling stack | Platforms, automation tools, and AI accelerators embedded in the COE's workflows |
| Talent pipeline | Hire-Train-Deploy, Academy programs, internal certification tracks |
| Knowledge management | Institutional memory that does not walk out the door with any one person |
| Model | Full Name | What It Is | When to Use |
|---|---|---|---|
| BOT | Build-Operate-Transfer | Full capability built, run, then transferred | Starting from scratch |
| CTH | Contract-to-Hire | Resources on YASH payroll, then transfer to client | Client wants to evaluate fit first |
| HTD | Hire-Train-Deploy | YASH recruits, trains to client's stack, deploys | Niche skills with a hiring gap |
| AOG | Architect on Ground | Senior SME embedded to design and anchor the COE | COE setup phase — first 90 days |
| POD | Product-Oriented Delivery | Cross-functional agile team owning a product/capability | Platform and product teams |
| Factory | Factory Model | High-volume, process-driven output at defined SLAs | Run operations, support functions |
| COE | Center of Excellence | Full capability center with charter, process, tooling, leadership | Strategic capability build |
In discovery, ask: "When you imagine this working in three years, what does a productive day for your India team look like?" If they describe a team that designs, decides, and drives outcomes — they need a COE. If they describe a team executing tasks assigned from HQ — they're thinking staffing. Help them think bigger, then show YASH can build both and evolve one to the other.
Buyers don't buy GCCs — they buy outcomes: cost efficiency, talent access, IP ownership, competitive speed. Here's how to connect every YASH capability to the outcome the buyer cares about.
| Milestone | DIY / Traditional | YASH GCC-as-a-Service |
|---|---|---|
| First employee onboarded | Month 9–12 | Week 6–8 |
| First SLA-governed output | Month 12–15 | Month 3–4 |
| 50 FTEs operational | Month 15–18 | Month 4–6 |
| COE capability live (not just staff) | Month 24–36 | Month 6–12 |
| Break-even vs. onshore cost | Year 2–3 | Year 1–2 |
| Legal entity fully operational | Month 6–9 | Month 3–4 (parallel) |
| YASH Feature | Buyer Outcome (How to Say It) |
|---|---|
| ReadyHub pre-commissioned space | "Your team is producing output while your competitors are still negotiating a lease." |
| 0 CAPEX / OPEX model | "You preserve capital for the transformation work itself, not the plumbing." |
| COE setup, not staffing | "You're building institutional capability your company owns permanently — not renting capacity that disappears when the contract ends." |
| BOT trajectory | "In 3–4 years, you own a running Indian subsidiary with a proven team, embedded processes, and transferred IP. The alternative is perpetual vendor dependence." |
| CMMI 5 + ISO 27001 infrastructure | "Your IT governance team won't need a separate audit cycle for the India operations — our certifications cover the baseline." |
| 20+ years GCC experience / 1,500+ resources in GCC models | "You're not our pilot. You're inheriting two decades of what works and what doesn't." |
The OPEX model closes CFO objections before they're raised. Any time Finance is involved in approval, make the 0-CAPEX framing explicit and early. CFOs are conditioned to view India setups as multi-million-dollar capital programs. Reframe it as an OPEX line that scales with headcount, and you've removed the biggest financial objection before the proposal stage.
Q1. A prospect's CFO says: "We're interested in a GCC but can't justify the upfront capital in this budget cycle." Which YASH model do you pitch first, and what two specific features do you lead with?
Q2. A prospect who tried an offshore model three years ago says: "We just got bodies last time — no real capability." What's the structural difference between what YASH builds vs. what they experienced? Name at least three delivery model types in your answer.