.png)
How to Set Up a GCC in India with Employer of Record (EOR)
Updated: Aug 8
A wholly owned subsidiary in India takes 10 to 16 weeks to incorporate and requires a resident director before you can legally hire anyone. That is why more founders now ask us to help them set up a GCC in India with Employer of Record (EOR) instead. Our fastest client had a 12 person Bengaluru team drawing salaries and shipping code in 19 days, with no local entity on the books yet. That is close to the average timeline across the GCC mandates we run each year for US and European product companies.
Why Are Companies Choosing EOR Over Entity Setup for Their India GCC?
Global Capability Centers (GCC) are no longer a large enterprise habit. Thousands now operate in India, and a growing share are being opened by companies with under 500 global employees, the kind of company that would once have gone straight to a staffing vendor instead of building its own team. Bengaluru is still the default city for product and AI focused GCCs, though Hyderabad has become the stronger choice for cloud and data infrastructure roles, and Pune is picking up engineering teams that need better overlap with US time zones.
The real bottleneck isn't finding talent, it's sequencing. Registering a subsidiary through the Ministry of Corporate Affairs, followed by PF and ESI registration, state level professional tax registration, and opening a bank account that actually clears salary payments, routinely takes 10 to 16 weeks, longer still if the company doesn't already have a resident director lined up.
We have watched clients lose their best shortlisted candidates during that wait. Senior Indian engineers at the level GCCs want, typically 8 to 15 years with prior product company exposure, usually have two or three competing offers and will not sit on one for three months.
Which Indian Cities Have the Best Talent for a GCC Team?
Bengaluru has the deepest bench for product engineering, AI, and platform roles, largely because of the concentration of engineers who previously worked at product companies rather than services firms. Hyderabad has built genuine strength in data engineering and cloud infrastructure, driven by the large captive centres already anchored there. Pune offers solid backend and fintech talent at compensation usually 10 to 15% lower than Bengaluru for comparable experience. Chennai suits enterprise and SAP adjacent roles, and Delhi NCR works well for customer facing technical and sales engineering hires.
Most companies that set up a GCC in India with Employer of Record (EOR) anchor their first hires in Bengaluru or Hyderabad and expand to a second city once the team crosses 15 to 20 people.
What most Indian engineers bring to a GCC role is strong fundamentals and real comfort working staggered hours with US or European teams. What they often lack, especially candidates from services backgrounds, is product ownership instinct: the habit of questioning a spec, flagging a weak architectural decision early, and owning an outcome rather than just a ticket. We run a structured technical loop plus a live system design or code review round specifically to separate candidates who execute well from candidates who think like owners.
Is an Employer of Record Legal and Compliant for a GCC in India?
Hiring through an EOR does not remove Indian labour law from the picture, it shifts who carries the legal employer responsibility, from you to the EOR. Every employee on your India GCC is covered by the Employees' Provident Fund Act, 1952, the Employees' State Insurance Act, 1948 for eligible salary bands, and the relevant state Shops and Establishments Act governing hours, leave, and termination notice. India is also rolling out four consolidated Labour Codes, on wages, industrial relations, social security, and occupational safety, and several states have already notified parts of them, changes a foreign HQ legal team rarely tracks closely.
The most common mistake we see when a company tries to set up a GCC in India with Employer of Record (EOR) structures is treating the arrangement as pure staffing rather than genuine employment. If your India team reports directly into your product organisation, uses your systems exclusively, and has no independent relationship with the EOR beyond payroll, a loosely structured contract can invite scrutiny under the Contract Labour Act. The fix is a proper employer of record agreement, not a disguised staffing pass through, with monthly PF, ESI, and gratuity accrual demonstrably happening on your team's behalf, not just promised in a sales deck.
IP ownership deserves the same care. Under an EOR structure, the employment contract, not a services agreement, governs IP assignment, so the EOR needs strong IP assignment and confidentiality clauses that flow through to you as the beneficial employer. We build this into every India GCC contract we manage, since vague IP language has slowed down investor due diligence for clients before.
EOR vs Own Entity: Which Structure Fits Your GCC?
This is the comparison we walk every GCC client through before they commit to a structure.
Factor | Employer of Record (EOR) | Own Entity (Pvt Ltd) |
Time to first hire | 2 to 4 weeks | 10 to 16 weeks |
Upfront setup cost | Under 50,000 INR (onboarding only) | 15 to 25 lakh INR (legal, registration, compliance setup) |
Ongoing compliance | Carried by the EOR | Needs a local finance or HR function |
Ideal team size | Under 25 employees | Generally worth it above 15 to 20 employees |
Control over office, banking, branding | Limited | Full |
Best for | Testing the market, urgent hiring | Teams that have proven the business case for a multi year presence |
The pattern across our client base is consistent. Companies that start on EOR and cross 20 to 30 India employees within 12 to 18 months usually transition to their own entity, since at that scale the EOR fee starts to exceed what an in house HR and payroll function would cost. Companies that stay smaller, or are still validating whether the GCC model works for them, are almost always better off staying on EOR, since winding down an entity in India can itself take 6 to 12 months.
How Does the GCC Hiring Process Work With an EOR Partner?
Our standard sequence starts with role scoping and live compensation benchmarking, not stale salary surveys. Sourcing and technical vetting run over the next few weeks, with every GCC candidate going through a minimum two stage technical loop. Offer to joining typically takes 3 to 4 weeks for individual contributors and 5 to 6 weeks for lead or architect level hires, since senior candidates usually serve a 60 to 90 day notice period. EOR onboarding itself, contract execution, PF and ESI registration, and payroll setup, is usually complete within 5 business days of an accepted offer.
At this stage, most clients also decide between contract hiring and full time hiring for different parts of the team. Contract hiring suits a defined project, a proof of concept, or a role you are not ready to commit to long term: the engineer is engaged for a fixed term through the EOR, with clear start and end dates and no long term severance liability. Full time hiring suits core GCC roles you expect to build around for years, with statutory benefits and gratuity accrual after a year, and it tends to retain talent better since the engineer sees a real career path. Most GCCs we build use a mix: a full time core team plus contract hires for specialised or short term work like a migration project.
A recent example, details anonymised: a US healthtech company with roughly 150 global employees, fresh off a Series B, came to AnjuSmriti Global wanting a 10 person Bengaluru GCC to own their data platform and machine learning pipeline, after a generic staffing vendor produced three failed hires in four months. We ran the technical vetting ourselves, placed the first four engineers within six weeks, and had the full team of ten in place by month four.
The near miss: their previous EOR vendor had classified two senior hires past the PF wage ceiling incorrectly, which would have triggered a compliance notice. We caught it during our onboarding audit and corrected it before the first payroll cycle ran. That GCC has since grown to 22 people and is mid transition to its own entity, exactly the trajectory the table above predicts.
What Does It Cost to Set Up a GCC in India with EOR?
For a typical GCC engineering role in Bengaluru or Hyderabad, current compensation runs roughly: mid level (3 to 6 years) at 18 to 28 lakh INR fixed CTC; senior (7 to 10 years) at 35 to 55 lakh INR; lead or architect level (10 plus years) at 60 lakh to 1.1 crore INR, with the top end reserved for candidates from equivalent large tech operations in India. On top of fixed CTC, budget roughly 12% employer PF contribution on basic wages, gratuity accrual after one year, and statutory bonus where applicable.
Whether you engage a role as a contract hire or a full time employee changes this math. Contract roles are usually invoiced at a flat monthly or project rate through the EOR with no long term benefit accrual, which suits short engagements. Full time roles carry the fuller cost stack above but come with lower attrition and stronger continuity for core product work, which is what most GCCs want once they move past the pilot phase.
Our fee sits on top of the employee's gross compensation rather than being buried inside it, so clients see exactly what they pay for compliance and administration versus what goes to the employee. A 10 person GCC on EOR for the first year typically costs meaningfully less than the combined price of incorporation, a dedicated India HR hire, and outsourced compliance filings.
Conclusion
GCC work in India is shifting fast. Teams are being asked to own AI and machine learning product features rather than just support them, platform engineering and cloud native skills are in higher demand than a year ago, and more companies are pairing a lean full time core team with contract specialists for AI tooling, data governance, and security work rather than hiring everything full time up front. In live mandates right now, we are seeing more clients build their entity transition plan into the very first conversation, instead of treating it as a "figure it out later" decision, which tells us founders are getting more deliberate about this model, not less.
If you are weighing whether to set up a GCC in India with Employer of Record (EOR) or go straight to incorporation, the practical answer for most companies under 25 headcount is to start on EOR and let the team's growth trajectory make the entity decision for you.
Ready to talk through your GCC plan? Start here.
Interesting Reads:
FAQs
1.Does Indian PF law apply to employees hired through an EOR for a GCC?
Yes. PF obligations under the EPF Act apply to every eligible employee regardless of whether they sit on your entity's payroll or an EOR's payroll. The EOR registers the employee, deducts contributions, matches the employer share, and files monthly returns. What changes is who carries that administrative load, not whether the law applies.
2.Can a company run a GCC in India without any local entity at all?
Yes, and this is the most common structure for GCCs under 20 to 25 employees. The EOR becomes the legal employer for tax, payroll, and compliance, while you keep full operational control over reporting lines and output. Many clients run this way for 12 to 24 months before deciding whether a captive entity makes sense.
3.How does IP ownership work when GCC engineers are employed by an EOR?
IP ownership flows through the employment agreement, so it needs explicit clauses, not assumptions. A properly structured contract assigns all work product to the beneficial employer, meaning your company, not the EOR. Generic EOR templates sometimes leave this vague, which can slow down investor due diligence later if it isn't fixed upfront.
4.Which Indian cities have the strongest talent for AI and cloud GCC roles?
Bengaluru has the deepest overall bench for AI and product engineering talent. Hyderabad is the stronger choice specifically for data engineering and cloud infrastructure, given the large captive centres already trained there. Pune works well for backend and fintech roles at somewhat lower compensation than Bengaluru for similar seniority.
5.Should a new GCC use contract hiring or full time hiring first?
Most GCCs start with a small full time core team for roles they expect to build around long term, and add contract hires for defined projects like a migration, a proof of concept, or a short term compliance push. Contract hiring gives flexibility without long term severance exposure, while full time hiring builds continuity and retention for core product work.
6.How long does it realistically take to get a 10 person GCC team hired in India?
Through an EOR, a 10 person team typically takes 10 to 14 weeks from kickoff to fully onboarded, depending on seniority mix. Individual offers usually convert in 3 to 4 weeks for mid level roles and 5 to 6 weeks for senior roles, mainly because of standard 60 to 90 day notice periods at Indian employers.
7.What compliance mistakes do companies make when running their own India entity?
The biggest one is underestimating the recurring compliance calendar: monthly PF and ESI filings, quarterly TDS returns, annual ROC filings, and POSH Act compliance once headcount crosses ten. These are ongoing obligations, not one time tasks, and many companies only discover gaps after a compliance notice arrives, which an EOR structure is built to prevent early on.
8.When should a GCC transition from EOR to its own entity?
Most clients see the economics tip toward owning the entity somewhere between 20 and 30 employees, depending on role mix and roadmap length. Below that range, the EOR's fee usually costs less than building an equivalent in house HR and compliance function. Above it, the fixed costs of your own entity spread across enough headcount to make ownership the cheaper option.
Comments