.png)
What Governance Model Should Enterprises Use for Hiring in India?
- Saransh Garg
- 7 days ago
- 9 min read
Of the 500 plus cross border hiring mandates we've run, the single biggest reason a client's India hiring stalls at month four isn't sourcing. It's that they picked the wrong legal wrapper before they hired anyone. A company that sets up its own entity under the Companies Act, 2013 is looking at 8 to 16 weeks of incorporation and state level registration before the first offer letter goes out. A company that routes the same hires through an Employer of Record can have someone billing hours in 10 to 15 working days. The governance model enterprises should use for hiring in India determines your timeline, your liability, and your total cost of employment long before a single resume is shortlisted.
We work with HR teams at every stage of this decision, and most are choosing between models without realising the compliance consequences of each. This is exactly what we walk them through.
What Is a Hiring Governance Model and Why Does It Matter in India?
A hiring governance model is simply the legal structure under which a worker is employed. It answers one question: who is the employer of record under Indian law, and who carries the statutory liability that comes with that. In most markets this choice is straightforward. In India it isn't, because labour law here isn't one national code. It's a mix of central legislation and state level rules that shift depending on headcount, sector, and location.
An HR Manager told to "just hire five engineers in India" is rarely told that Karnataka's Shops and Establishments rules differ from Telangana's, or that crossing certain headcount thresholds can trigger obligations under multiple overlapping codes at once. Choosing the governance model enterprises should use for hiring in India before you understand this patchwork is how otherwise well run companies end up with retroactive compliance gaps in year one.
Which Governance Model Should Enterprises Use for Hiring in India Right Now?
A wholly owned entity or global capability centre makes you the direct employer, governed by the Companies Act, 2013 for incorporation and then the Code on Wages 2019, the Industrial Relations Code 2020, and the Code on Social Security 2020 for everything that follows. An Employer of Record makes the provider the legal employer while you retain full operational control, absorbing EPF, ESI, and gratuity obligations on your behalf.
A contract or staffing model places workers on an agency's payroll under the Contract Labour (Regulation and Abolition) Act, 1970, while you as the principal employer still carry certain welfare obligations. Recruitment Process Outsourcing isn't a legal employment model at all. It's a sourcing layer that sits on top of whichever model you've already chosen.
Most enterprises don't pick one model permanently. They start with an EOR or contract hiring arrangement to validate the India hypothesis, then convert to a wholly owned entity once headcount and confidence both cross a threshold, typically somewhere between 30 and 60 people.
Contract Hiring vs Full Time Hiring in India: What HR Teams Actually Need to Know
This is the distinction that trips up most first time HR buyers. Contract hiring in India means the worker is engaged for a defined scope or duration, usually through a staffing agency or EOR, without the enterprise carrying long term retention obligations like gratuity vesting or standing order protections. It's the right call when a project has a defined end date, when you're testing a new function before committing headcount, or when demand fluctuates seasonally, which is common in product engineering teams supporting quarterly release cycles.
Full time hiring means the worker becomes a permanent employee of whichever entity sits above them, whether that's your own subsidiary or an EOR acting as employer of record. Full time status triggers gratuity accrual under the Payment of Gratuity Act, 1972, EPF contributions once thresholds are crossed, and stronger termination protections under the Industrial Relations Code 2020. It's the right call for core product engineering, platform ownership, and any role where continuity and institutional knowledge matter more than flexibility.
Where Should Enterprises Hire in India? City Wise Talent and Governance Fit
Talent geography should influence your governance choice as much as compliance does. Bengaluru carries the deepest bench for platform and cloud native roles because of its global capability centre density, which means engineers there have often already worked inside enterprise governance structures similar to yours.
Hyderabad has pulled ahead specifically for data, AI, and SAP adjacent talent, helped along by sustained hyperscaler campus investment in the city. Pune and Chennai carry strong manufacturing tech and BFSI adjacent engineering talent. NCR remains strongest for enterprise SaaS and IT services talent given the concentration of services headquarters there.
An EOR gives you employment infrastructure. It does not vet the engineer. A staffing partner should do both. AnjuSmriti Global builds a technical screening layer into every placement regardless of which governance model enterprises use for hiring in India, because the legal wrapper and the hiring quality are two separate problems that both need solving.
What Does Indian Labour Law Actually Require Under Each Governance Model?
Gratuity under the Payment of Gratuity Act, 1972 accrues from day one of full time employment regardless of which entity technically employs the worker. EPF contributions under the EPF and Miscellaneous Provisions Act, 1952 become mandatory once an establishment crosses 20 employees, and that threshold applies retroactively from the date of crossing, not from a future compliance date. The POSH Act, 2013 requires an Internal Committee once headcount hits 10, and under an EOR model this obligation typically sits with the provider, though enterprises should confirm this explicitly rather than assume it.
The most common mistake we see is treating EOR as a blanket compliance shield. It removes direct employment law exposure, but it does not remove intellectual property risk. Indian courts generally require an explicit written IP assignment clause rather than assuming work created during employment automatically belongs to the company directing it. Data protection obligations under the Digital Personal Data Protection Act, 2023 also typically remain the enterprise's responsibility as data fiduciary, even when the EOR is the legal employer.
Governance Model Decision Matrix for India Hiring
Factor | Own Entity or GCC | EOR | Contract or Staffing |
Time to first hire | 10 to 16 weeks | 10 to 15 working days | 5 to 10 working days |
Headcount sweet spot | 50 plus within 18 months | 1 to 50 | 5 to 200, flexible |
Legal employer of record | You | EOR provider | Staffing agency |
IP assignment control | Direct, in your own contracts | Needs explicit clause with EOR | Needs clause with agency |
Best for | Long term GCC, IP sensitive core work | Fast entry, testing India as a hub | Project based or fluctuating headcount |
Overhead beyond salary | Company secretary, audits, filings | EOR fee per employee | Agency markup on CTC |
How We Run a Governance Led Hiring Mandate in India
Our standard advisory sits ahead of the hiring itself, a short compliance mapping session where we walk HR and legal stakeholders through which model fits their headcount trajectory, followed by a pilot hire before scaling. For most EOR and contract engagements we get the first candidate into interviews within 7 working days, with offers typically accepted within 3 to 4 weeks.
A mid sized European insurance technology company came to us wanting 12 engineers hired in India within a quarter, and their HR team had already decided on a wholly owned entity because that's what their board expected for a serious market presence. What almost went wrong was that crossing the 20 employee EPF threshold, once their existing contractors were factored in, would have triggered retroactive contribution obligations with no payroll infrastructure in place to handle it.
We restructured the engagement so the first 12 hires went in under an EOR through our HR outsourcing framework while entity incorporation ran in parallel, avoiding an estimated 9 to 11 lakh rupees in penalties and interest, with zero attrition through the transition.
What Does Each Governance Model Cost in India?
Using a mid level software engineer at 14 to 18 lakh rupees fixed CTC as the reference point, an own entity adds EPF employer contribution, gratuity accrual, incorporation cost amortised over year one, and ongoing audit and company secretary retainers. An EOR adds the same statutory contributions plus a service fee typically between 18,000 and 28,000 rupees per employee per month depending on headcount tier.
A contract or staffing model adds an agency markup of 15 to 25 percent over CTC, which usually bundles payroll administration and a replacement guarantee. Layering RPO on top of any of these adds a separate monthly retainer for volume sourcing, generally 1.5 to 3 lakh rupees.
For senior engineers at 26 to 32 lakh rupees and lead or architect level hires at 40 to 55 lakh rupees, the percentage overheads stay roughly constant, though EOR fees often shift to a flat per head rate rather than a percentage, since compliance complexity doesn't scale linearly with salary. These cost differences are exactly why the governance model enterprises use for hiring in India needs revisiting as headcount and seniority mix change, not treated as a one time decision.
AI, Cloud, and Workforce Trends Shaping Governance Choices in India
Enterprise hiring in India right now is being reshaped by three overlapping forces. First, AI adoption inside engineering teams is pushing more companies toward hybrid governance, hiring a smaller core of full time platform and architecture engineers under an entity or EOR while using contract talent for AI tooling pilots that may or may not become permanent workstreams.
Second, cloud and data roles have moved from a nice to have to a baseline expectation, and Hyderabad and Bengaluru in particular have seen sustained demand for engineers who can operate across multi cloud environments rather than a single hyperscaler stack.
Third, more Global Capability Centers (GCC) are choosing a soft launch model, running the first cohort of hires under an EOR for six to twelve months before committing to full entity incorporation, specifically to avoid the dormant entity overhead that used to be standard practice.
The governance model enterprises should use for hiring in India increasingly reflects this staged approach rather than a single permanent choice made on day one. Enterprises that treat governance as a living decision, revisited every 12 to 18 months as headcount and strategic commitment grow, consistently avoid the retroactive compliance issues we see most often in rushed entity setups.
If you're mapping out your own India hiring governance decision, we're happy to walk your HR and legal stakeholders through the same framework we use with clients. Book a governance mapping call.
Interesting Reads:
FAQs
1.Does an EOR remove all legal exposure for an enterprise hiring in India?
No. An EOR absorbs direct employment obligations like EPF, ESI, and gratuity, but IP assignment and data protection responsibilities under India's Digital Personal Data Protection Act typically stay with the enterprise. EOR solves employment law exposure specifically, not every compliance risk tied to the engagement.
2.At what headcount does a wholly owned entity become cheaper than an EOR?
Typically between 35 and 60 employees, depending on the state. Below that, incorporation, audit, and company secretary costs outweigh EOR fees. Above it, per employee EOR charges usually exceed the same overhead spread across a larger headcount under your own entity.
3.Does Indian contract labour law apply to software engineering roles?
Yes. The Contract Labour (Regulation and Abolition) Act, 1970 applies once establishment and contractor headcount thresholds are crossed, regardless of job title. Many HR teams assume it only covers manual labour, but white collar tech roles engaged through a staffing agency are covered too.
4.Can an enterprise run EOR and an entity in India at the same time?
Yes, and it's common during transitions. The key is documenting continuity of service properly, since gratuity and tenure calculations can follow the worker rather than resetting when the legal employer changes, provided the transition is structured with a clear written agreement between both parties.
5.How does POSH Act compliance differ between EOR and entity hiring?
Under the POSH Act, 2013, any establishment with 10 or more employees needs an Internal Committee. Under EOR, this typically sits with the provider, but enterprises should confirm it explicitly in the service agreement rather than assuming coverage. Under an entity, the obligation is entirely the enterprise's own.
6.What's the biggest governance mistake first time India hirers make?
Choosing the model that looks most permanent to the board rather than what matches actual headcount and timeline. Incorporating before demand is validated often means carrying dormant entity overhead for a year or more, which is exactly what makes the governance model enterprises use for hiring in India harder to unwind later.
7.Is contract hiring or full time hiring better for AI and cloud pilot projects?
Contract hiring generally fits better for time boxed pilots since it avoids long term retention obligations if the initiative doesn't scale. Once a pilot proves out and becomes a permanent function, converting the same talent to full time status under an EOR or entity is usually smoother than restarting a search.
8.Do EOR and staffing fees vary by Indian city?
The fee structure itself doesn't vary much, but underlying compensation does. Bengaluru and NCR carry the highest base salaries for comparable roles, while Hyderabad, Pune, and Chennai typically run 8 to 15 percent lower, which is why many enterprises now build talent pipelines across multiple cities rather than one.
Comments