.png)
Can Global Companies Build an Offshore Team in India Without Entity?
- Saransh Garg
- Jul 14
- 8 min read
Yes. Global companies build an offshore team in India without entity registration every single day, using an Employer of Record (EOR) as the legal employer of record while retaining full operational control over the work itself. India now hosts more than 2,000 Global Capability Centers (GCC) employing over 2.3 million professionals, and a growing share of new offshore builds start exactly this way, with no local entity at all, before scaling into something bigger later.
The question founders actually ask us is not "can we do this," but "how long can we run this way before it stops making sense." That is the real question this article answers.
Why Are Global Companies Building Offshore Teams in India Without an Entity Right Now?
Demand for Indian tech talent has shifted heavily toward AI, cloud, and data roles. Industry hiring data shows nearly two in three new roles created inside Indian GCCs today require AI, data science, or automation skills, and GCC hiring has stayed resilient even as broader white collar hiring has slowed elsewhere. This is the environment global companies build an offshore team in India without entity setup to compete in: speed matters more than ever, and registering an entity before you even know your final headcount can cost you three to four months you don't have.
Bengaluru remains the deepest market for product engineering, cloud, and AI/ML talent, largely because it hosts the highest concentration of GCCs in the country. But the market has gotten more competitive too. For every qualified AI engineer actively available in Bengaluru, there are typically five to eight open roles competing for that person's attention right now, which has pushed senior compensation up and stretched time to hire for niche roles considerably.
That pressure is exactly why Tier 2 cities have entered the conversation. Cities like Pune, Chennai, Coimbatore, and Vadodara now offer real cost advantages, often 15 to 20 percent lower than Tier 1 metros, along with lower attrition. Companies that assume Bengaluru is the only serious option often end up paying a premium for talent available at the same quality in Pune or Hyderabad for less.
Which Indian Cities Have the Right Talent Depth for a No Entity Offshore Build?
City choice becomes the single biggest lever for talent quality when global companies build an offshore team in India without entity backing, because there is no physical office anchoring hiring to one location.
Bengaluru leads for backend, cloud, and AI/ML roles. Hyderabad has become a genuine alternative, combining strong infrastructure with a growing mid to senior talent pool and comparatively lower attrition in several engineering domains. Pune and Chennai carry deep strength in enterprise software, QA automation, and BFSI focused engineering.
Most mid to senior engineers have already worked across at least two time zones with a US or European reporting line, and are comfortable with async documentation and distributed code review. What they typically lack, particularly candidates from traditional service delivery backgrounds, is the instinct to flag a product risk before being asked. We test for this directly by handing candidates an intentionally ambiguous problem and watching whether they ask clarifying questions or simply start building.
This is one reason AnjuSmriti Global runs a live, scenario based technical round for every mandate rather than relying on take home assignments, since AI assisted submissions are common enough now that they're no longer a reliable signal alone.
Is It Legal for Global Companies to Build an Offshore Team in India Without an Entity?
Yes. When global companies build an offshore team in India without entity registration, this is where the compliance line actually sits. The Companies Act 2013 defines when a foreign company is deemed to maintain a "place of business" in India, which is what triggers mandatory entity registration. As long as the EOR, not the foreign company, is the one issuing offer letters, running payroll under the Payment of Wages Act, and remitting Provident Fund and ESI contributions, the foreign company itself has no registration obligation.
Here is where two different hiring models come into play, and companies often confuse them. Full time hiring through an EOR means the engineer is a permanent employee with statutory benefits, notice periods, and long term retention incentives, just employed on paper by the EOR instead of your own entity.
Contract hiring, by contrast, works best for short, clearly scoped engagements under 12 months, governed by the Indian Contract Act 1872. The risk with contract hiring is that a contractor kept on for years, working full time hours under full time supervision, can be reclassified as a disguised employee under Indian labour law, which exposes the company to retroactive statutory benefit claims. We generally recommend contract hiring only for defined project work, and full time EOR hiring for anyone meant to be part of the core team long term.
The most common compliance mistake we see is a finance team signing an office lease directly in the foreign company's own name to get the team "out of a co-working space." That single move can be read as maintaining a fixed place of business, which risks triggering Permanent Establishment status under India's tax treaty network, months before the company is ready for the corporate tax exposure that comes with it. Keeping any physical lease under the EOR's name, not the parent company's, avoids this entirely.
EOR or GCC: When Should a No Entity Team Switch Models?
This is the table we build for every client once they pass ten hires, because it answers the one question that actually matters at scale.
Team Size | EOR Model (Annual Cost) | Entity or GCC Model (Annual Cost) | Cheaper Option |
1 to 10 people | EOR fee, 8 to 12 percent of payroll, no setup cost | Entity setup, roughly ₹8 to 15 lakh one time plus ₹25 to 40 lakh a year in compliance overhead | EOR, clearly cheaper |
11 to 25 people | EOR fee scales with payroll, around 10 percent | Entity fixed costs start spreading across more headcount | Usually still EOR |
26 to 40 people | EOR fee stays near 9 to 10 percent, now a large absolute number | Entity fixed costs amortize well at this size | Crossover zone, depends on the team |
40 plus people | EOR fee compounds into a significant recurring cost | Entity or GCC is almost always cheaper | Entity or GCC |
Three things shift this crossover point. A senior heavy team hits it earlier, because EOR fees are payroll percentage based, so the absolute cost climbs faster with higher salaries. A team you might wind down within 18 months should usually stay on EOR well past the crossover point, since dissolving an Indian entity is slow. And if you need an entity for reasons beyond payroll, billing Indian customers, holding local IP, the crossover conversation becomes irrelevant much sooner.
How Do Global Companies Actually Build a No Entity Offshore Team, Step by Step?
Once the model is chosen, the mechanics of how global companies build an offshore team in India without entity paperwork are fairly repeatable. Our build runs on a fixed timeline: role scoping and market benchmarking in week one, first interviews by week two, offer and EOR onboarding by week three to four, and most mid to senior hires starting by week five or six. Specialised roles, senior DevOps, certain AI/ML specialisations, typically need eight to ten weeks, since the qualified pool is smaller and strong candidates are usually already employed with long notice periods.
A mid size US SaaS company, Series B, around 80 employees globally, came to us to build a 12 person engineering pod through an EOR, planning to convert to a GCC once they crossed 30 people. Around hire nine, their finance team signed a three year office lease directly in the US entity's name without looping us in, putting the company at real risk of triggering Permanent Establishment status under the India US tax treaty.
We caught it within a week, brought in tax counsel, and restructured the lease under the EOR instead. The client hit its 12 hire target on schedule, avoided the tax exposure, and converted to a full GCC eleven months later, at 34 people, right where the crossover table above says it should.
What Does It Cost to Build an Offshore Team in India Without an Entity?
Using backend and full stack engineering as a reference, since it's the most commonly hired function in no entity builds:
A mid level engineer with three to five years of experience runs ₹14 to 20 lakh a year in base salary, with total landed cost, including employer PF and ESI contributions plus the EOR fee, around ₹18 to 25 lakh.
A senior engineer with six to nine years runs ₹28 to 42 lakh base, landing around ₹36 to 54 lakh total.
A lead or architect with ten or more years runs ₹48 to 75 lakh base, often with equity or bonus on top, landing around ₹62 to 95 lakh total.
Compared to hiring the equivalent role in the US or Western Europe, this typically lands 55 to 65 percent lower in total cost, even after the EOR fee, not the vague figure most agencies quote without showing the underlying math. Clients who save this much on a 15 person team most often reinvest it in one of two places: growing the India team faster toward the crossover point, or funding a second offshore function, most commonly QA or data engineering, using the same offshore recruitment approach rather than treating it as a separate initiative. This is, in practice, exactly how global companies build an offshore team in India without entity overhead while still keeping room to scale.
If you're planning your first India hires, or you're already past 15 people and wondering whether it's time to look at a GCC, talk to us before your finance team makes the decision for you.
Interesting Reads:
FAQs
1.Can a US or UK company legally employ Indian engineers without opening an Indian entity?
Yes. An Employer of Record becomes the legal employer for payroll, tax, and statutory compliance, while the foreign company keeps full control over the work. No registration under the Companies Act 2013 is needed unless the foreign company itself maintains a physical office or signs contracts directly in India.
2.What is the difference between an EOR and a GCC for hiring in India?
An EOR is a third party that legally employs your team on your behalf with no entity needed. A GCC is your own wholly owned subsidiary in India, built for long term, high volume hiring once you've outgrown the cost efficiency of an EOR, usually somewhere past 25 to 40 people.
3.How long does it take to hire an engineer in India through an EOR?
Most mid to senior hires start within five to six weeks from role scoping to onboarding. Specialised roles like senior DevOps or AI/ML engineering typically take eight to ten weeks, since strong candidates are usually already employed with 60 to 90 day notice periods.
4.Does using an EOR in India expose a foreign company to Permanent Establishment tax risk?
It shouldn't, as long as the EOR, not the foreign company, holds any office lease and signs employment contracts. Risk appears when the foreign parent directly leases office space or habitually signs local contracts, which can trigger Permanent Establishment status under India's tax treaty network.
5.Should we hire contractors or full time employees for our first India team?
Contract hiring works well for short, clearly scoped projects under 12 months. Full time hiring through an EOR is better for anyone expected to stay long term, since long tenure contractors risk being reclassified as employees under Indian labour law, creating retroactive compliance exposure.
6.What statutory benefits do EOR employed engineers in India actually receive?
The same as employees of an Indian entity: Provident Fund contributions, ESI where applicable, gratuity after five years, and paid leave under the relevant state Shops and Establishment Act. The EOR simply files these on the foreign company's behalf instead of the company filing them itself.
7.Which Indian cities offer the best value for a no entity offshore engineering team?
Bengaluru has the deepest AI, cloud, and product engineering talent but the highest cost and competition. Hyderabad and Pune offer comparable quality for backend, cloud, and infrastructure roles at meaningfully lower cost, while Tier 2 cities like Coimbatore and Vadodara are gaining traction for stability and lower attrition.
8.At what team size should a company consider converting from an EOR to its own Indian entity?
Most companies see the cost crossover somewhere between 25 and 40 people, depending on seniority mix, since EOR fees scale with payroll. Operational reasons, like wanting dedicated local HR or a physical office, often show up around the same 20 to 25 person range as well.
Comments