.png)
How Should You Scale an India Engineering Pod: Contractors or EOR?
- Saransh Garg
- 24 hours ago
- 9 min read
We have set up more than 40 India engineering pods for founders, and the decision that determines whether that pod survives its first year is rarely about finding good engineers. It is about choosing the right legal structure. Get an India engineering pod for Contractors or EOR decision wrong, and you either absorb 18 to 24% in avoidable statutory costs, or build a team with weak IP protection and no real retention lever, which gets expensive the day someone leaves mid project.
A 6 person pod on the wrong structure can cost a founder ₹9 to ₹14 lakh a year in compliance exposure and repeat hiring. We have watched this at seed stage startups and at well funded Series C companies expanding into India for the first time. This piece explains how we help founders make this call, with real numbers, the actual Indian laws involved, and a framework you can apply before your next hire.
Why Founders Get the Contractors vs EOR Decision Wrong
Most founders choose a structure based on however their first India hire happened to come through, often a freelancer found on referral, or an agency pitching whichever model pays them a higher margin. Neither reason reflects what your pod actually needs.
This shows up clearly in high demand cities. Bengaluru's IT sector attrition has hovered around 18 to 22% in recent years, and a contractor with no equity, no notice period, and no reason to stay past their invoice will leave the moment a better day rate appears. We have seen entire contractor based frontend teams turn over within five months once a competitor offered 15% more.
Hiring in India also looks different than it did a few years back. AI assisted development has raised the bar for senior review rather than cutting headcount needs, cloud native and platform engineering roles are in higher demand than pure application development, and global capability centres now hire almost exclusively through direct entities or EOR because larger companies have already done this compliance math. Mostly it is early stage founders building their first 5 to 15 person pod who still choose structure based on convenience alone.
There is also a timing risk. A contractor engagement that runs long, full time, and exclusive starts to resemble disguised employment under Indian law, regardless of what the contract calls it. That reclassification risk is the single most common issue we flag before a founder signs anything.
Contract Hiring and Full Time Hiring, Explained Simply
Before choosing a structure, it helps to separate two ideas founders often blend together.
Contract hiring means engaging an individual or their personal services entity against a defined scope or invoice, with no ongoing employment relationship. It suits short, bounded work such as a three month migration project. It does not automatically include statutory benefits, notice periods, or guaranteed IP assignment unless the contract explicitly covers this.
Full time hiring means the engineer becomes a genuine employee, either of your own registered India entity or of an Employer of Record acting on your behalf. This brings statutory protections such as provident fund, gratuity accrual, and a real notice period, along with stronger IP ownership by default. Full time hiring through EOR is generally the right call once a role is ongoing, exclusive, and central to your product.
Where the Right Talent for Your Pod Actually Sits
For a product engineering pod of 4 to 15 senior engineers, three cities carry the deepest bench, each with a different profile. Bengaluru has the strongest concentration of engineers with prior product company experience, useful if your pod needs people comfortable shipping fast without detailed specs. Pune carries a strong base of enterprise software engineers who excel at systems that need to stay reliable, a good fit for fintech and infrastructure pods. Hyderabad has grown quickly in cloud native and platform engineering talent, driven by large GCC buildouts, and we now place a growing share of DevOps roles out of that city.
What Indian engineers reliably bring is strong fundamentals, comfort with distributed remote workflows, and real production experience at scale. What they often lack for a founder led pod is comfort with ambiguity, since many come from environments where specs arrive fully formed. We test for this with a 45 minute unstructured problem where we deliberately withhold detail and watch what questions a candidate asks before writing any code.
The Legal Reality Behind an India Engineering Pod for Contractors or EOR
If you hire contractors directly with no registered India entity, the relevant exposure sits under the Contract Labour (Regulation and Abolition) Act, 1970 and the state level Shops and Establishments Act. Neither law was written for remote software engineers, but Indian authorities increasingly apply a substance over form test. If an engineer works exclusively for you, on your hours, using your tools, for several months, the relationship can be reclassified as employment, bringing retroactive liability under the Employees Provident Funds Act, 1952, and potentially the Payment of Gratuity Act, 1972.
If you hire through an Employer of Record (EOR), the EOR becomes the legal employer under Indian law, issues a compliant contract, and manages statutory contributions in line with the Code on Wages, 2019 and the broader Labour Codes framework now in force. You keep a direct working relationship with the engineer while the compliance liability sits with the EOR entity rather than your foreign company.
The most common mistake we see is founders assuming a contractor agreement with an IP clause is enough to protect their code. It is not, on its own. Under Indian copyright law, IP created during employment vests with the employer automatically, while IP created by an independent contractor does not vest automatically unless the assignment is precise and enforceable, ideally through a registered entity that can actually execute it. At AnjuSmriti Global, we have had to unwind two situations where a contractor held the only clean copy of a critical module and the assignment clause was contested.
A Simple Framework: Contractors vs EOR by Scenario
Your Situation | Recommended Structure | Why |
1 to 3 engineers, project ends within 6 months | Contractor, via a compliant contractual hiring agreement | Short, bounded work carries low reclassification risk |
4 to 15 engineers, ongoing product work, no local entity | EOR, via employer of record | Full statutory compliance without a lengthy entity setup |
15 plus engineers, multi year roadmap | Own entity, with EOR as a bridge for the first months | Entity costs are recovered by year two at this scale |
Senior hire, want a trial period first | EOR with a defined probation clause | Real employment relationship with a clean exit if needed |
20 plus engineers for a delivery pod | Bulk hiring via EOR or RPO | Individual contractor agreements become unmanageable at this volume |
The pattern worth remembering is that contractor structures work well for short, bounded engagements. Once a contractor relationship crosses roughly six months and becomes someone's primary, exclusive, full time commitment, which is what a real engineering pod actually is, you have drifted into territory that looks like disguised employment on paper or not.
Our Process and a Real Client Scenario
Our timeline for standing up an India pod, once structure is decided, is 3 to 4 weeks for an EOR backed team and 5 to 7 weeks if we are also setting up a registered entity in parallel. Contractor only pods move faster, in 2 to 3 weeks, though we push back on speed being the deciding factor when it leads to a structure that creates liability later. Our technical assessment for pod hires has three stages: a take home system design exercise scoped to the client's actual stack, a live pairing session testing how a candidate handles an ambiguous requirement, and a reference call focused on whether the person escalated problems early or sat on them.
A real example, details anonymised. A fintech company with roughly 80 people globally came to us with a 7 person contractor pod in Bengaluru running for over a year. Their legal counsel flagged that the arrangement looked like disguised employment, full time hours, company laptops, no other clients.
The near miss was that one contractor had never signed an updated IP assignment addendum, leaving a payments module in a legal grey zone. We restructured the pod onto EOR over five weeks, re papered every contract cleanly, and the client avoided an exposure their counsel estimated at well over 150 thousand dollars had it reached a labour tribunal. Two engineers left during the transition over compensation changes, five stayed, and that pod remains intact today, a retention outcome the original structure was never going to deliver.
Real Numbers: Cost and Salary Comparison
Backend or full stack engineer, monthly cost to the hiring company, in INR:
Level | Contractor day rate equivalent | EOR total cost (salary, employer PF, gratuity accrual, EOR fee) |
Mid, 3 to 5 years | ₹1,40,000 to ₹1,80,000 | ₹1,55,000 to ₹1,95,000 |
Senior, 6 to 9 years | ₹2,20,000 to ₹2,90,000 | ₹2,40,000 to ₹3,15,000 |
Lead or Staff, 10 plus years | ₹3,50,000 to ₹4,80,000 | ₹3,80,000 to ₹5,10,000 |
EOR typically runs 8 to 12% above raw contractor rates once you include employer PF contribution, gratuity accrual, and the EOR management fee. That premium buys compliance that removes reclassification risk, a real notice period that reduces sudden attrition, and access to benefits that pure contractor relationships cannot offer.
Most clients who move from contractor to EOR reinvest the difference into one additional senior hire rather than cutting the team, because better retention means they stop re recruiting the same seat every eight months.
Conclusion
Founders building India pods now are leaning more toward EOR from day one, largely because more legal teams abroad have become familiar with India's reclassification risk. We are also seeing a shift in what pods are being hired for, with more requests for platform engineering and AI assisted development review roles rather than pure feature delivery. If you are weighing an India engineering pod for Contractors or EOR, the honest answer depends far more on how long and how exclusive the relationship will be than on which option looks cheaper today.
Ready to scope your pod properly before you make the first hire? Talk to us here.
Interesting Reads:
FAQs
1.Does an India engineering pod for Contractors or EOR affect how quickly I can start building my team?
Contractor pods move slightly faster, often 2 to 3 weeks, since there is no employer of record onboarding step. EOR backed pods take 3 to 4 weeks, since the EOR must issue compliant contracts and register statutory benefits. The extra week generally buys meaningfully lower legal risk, so most founders find the tradeoff worthwhile once the engagement is expected to run past a few months.
2.Is a contractor pod in India legal if the engineers work full time hours exclusively for us?
It can be legal on paper, but exclusive, full time, long running contractor relationships carry real reclassification risk under Indian labour law. Authorities look at substance over form. If your contractors behave like employees in practice, the arrangement can be treated as disguised employment, which creates retroactive liability. A defined scope and shorter duration reduces this risk significantly.
3.Who owns the code written by an EOR employed engineer versus a contractor in India?
For EOR employed engineers, intellectual property created during employment vests with the employer automatically under Indian law, and the EOR contract typically reinforces this in writing. For contractors, ownership does not transfer automatically. It depends entirely on the strength of the IP assignment clause and whether the contractor can legally execute it, which is a common gap founders miss.
4.How much more expensive is EOR compared to hiring contractors in India?
EOR typically costs 8 to 12% more per month than an equivalent contractor engagement, once you include employer provident fund contributions, gratuity accrual, and the EOR service fee. In exchange, you get compliant employment status, a real notice period, and access to benefits that improve retention, which often offsets the extra cost within a year through lower attrition.
5.Can we convert a contractor into a full time EOR employee later without disrupting the team?
Yes, this is a common path. A trial period of 60 to 90 days as a contractor followed by conversion to EOR employment usually takes about a week to finalise on the employer side. The main thing to check beforehand is that the original contractor agreement does not create ambiguity around IP ownership or exclusivity that complicates the later EOR contract.
6.Does hiring through an India EOR let us offer equity from our foreign parent company?
Yes, and this works well in practice, though it needs coordination. The EOR manages Indian employment and payroll, while equity grants usually come directly from the foreign parent under its own plan, treated as separate from the local employment contract. India specific tax withholding on equity does apply, so this should be documented clearly with the employee upfront.
At what team size does it make more sense to open our own India entity instead of using EOR? Past roughly 15 to 20 engineers, setting up a private limited entity often becomes cheaper than continuing on EOR, since entity setup and compliance costs are typically recovered once headcount and payroll reach that scale. Below that size, EOR remains faster and cheaper because it avoids upfront registration and ongoing statutory filing overhead.
What happens if we need to let go of an engineer hired through EOR in India? The EOR manages the formal termination process in compliance with Indian labour law, including applicable notice periods, typically 30 to 90 days depending on seniority, and any severance owed. You manage the underlying performance decision, while the EOR executes a compliant offboarding, which is considerably cleaner than ending a long running contractor relationship abruptly.