.png)
Why UK Companies Are Moving From Entity to EOR in India
Setting up a wholly owned subsidiary in India costs a UK company between £18,000 and £30,000 in the first year once incorporation, FEMA compliance, statutory audit, and local legal counsel are added, and it usually takes four to six months before that entity can legally put a single engineer on payroll. This is the real reason UK companies are moving from Entity to EOR in India: the entity route front loads cost and delay before a single hire is made, and most UK companies simply do not have four months to spare.
We have run this comparison for over 40 UK clients in the last three years, including fintechs in London, SaaS teams in Manchester, and insurance firms in Edinburgh. In nearly every case, the Employer of Record (EOR) model gets the first engineer working within 10 to 15 business days, against four to six months for entity incorporation.
The Real Reason Entity Setup Is Losing Ground for UK Founders in India
London's tech hiring market has stayed tight through the last few years, and the gap between what UK companies can afford to pay and what UK engineers now expect keeps widening. A senior backend engineer in London commands £75,000 to £95,000 base today, before employer National Insurance (15% above the secondary threshold) and pension auto enrolment costs are added on top. Fintechs in London and gaming studios in Manchester have been the fastest to look at India, since both sectors need engineering capacity they cannot build purely onshore at current UK salary levels.
The old default advice UK expansion consultants gave was to set up a private limited subsidiary in India under the Companies Act, 2013. We still meet founders who assume that is the only credible way to hire in India. It is not, and for companies hiring fewer than 15 to 20 people, it rarely makes financial sense. An entity needs a registered office, a resident director, ongoing GST filings, EPFO and ESI registrations, a company secretary, and annual statutory audits, all before the UK side even manages board resolutions and transfer pricing documentation for the subsidiary.
This is also where contract hiring and full time hiring start to matter as separate decisions. Contract hiring, where an engineer works on a fixed term or project basis gives UK companies flexibility to scale a team up or down without long term statutory obligations. Full time hiring under an EOR gives the engineer permanent employee status, benefits, and retention incentives, while the compliance liability still sits with the EOR rather than the UK company.
Most UK founders we speak to assume they have to choose entity first and figure out contract versus full time later. In practice, the EOR route lets a company start with contract engineers, convert strong performers to full time roles, and only build an entity once headcount justifies it.
We saw this shift accelerate when three separate UK clients, two of them Series B SaaS companies, came to us mid way through entity incorporation, stuck on RBI reporting requirements for their initial share capital transfer, asking whether an employer of record arrangement could get engineers working while the entity paperwork finished in parallel. All three abandoned the entity plan entirely once they saw the EOR cost curve.
Which Indian Cities Have the Right Talent for UK Teams?
For UK companies building product engineering, data, or platform teams, Bengaluru and Pune carry the deepest bench strength. Bengaluru has the highest concentration of engineers with genuine SaaS product experience, which matters for UK companies building B2B software, since these engineers have usually worked inside product led environments rather than pure services delivery. Pune has strong fintech and payments engineering talent, largely because of the concentration of BFSI captives already based there, which is directly useful for London based financial services clients.
Hyderabad has become the stronger choice for data engineering, AI adoption, and cloud infrastructure roles, driven by the large global capability center presence there. If a UK client needs cloud engineers who have actually run production AWS or Azure environments at scale, rather than engineers only certified on paper, Hyderabad candidates tend to bring more hands on incident response experience. We are also seeing rising demand from UK clients for engineers comfortable working alongside AI coding assistants and automated testing pipelines, since most UK product teams now expect new hires to already understand how to review and validate AI generated code rather than write everything from scratch.
What Indian engineers for UK clients typically lack is not technical depth. It is exposure to UK specific regulatory context. For fintech clients, engineers often have not worked with FCA adjacent data handling requirements or the way UK GDPR has diverged from EU GDPR since Brexit.
We test for this directly by presenting a data handling scenario involving customer information and asking the candidate to reason through it live, rather than asking them to define GDPR from memory. Engineers who have already worked with UK or EU clients usually reason through the scenario correctly within a few minutes. Those who have not tend to give textbook answers that do not map to the real regulatory nuance UK clients care about.
Why UK Companies Are Moving From Entity to EOR in India: The Legal and Compliance Reality
The UK side of this decision is shaped less by Indian law and more by how the UK company structures the relationship. The Employment Rights Act 1996 defines UK employee protections, but it does not extend to workers based in India. The actual legal exposure for a UK company hiring in India runs through Indian labour law: the EPF and Miscellaneous Provisions Act for provident fund contributions, the Payment of Gratuity Act, and the Shops and Establishment Act relevant to the state where the entity or EOR is registered.
This is where the common mistake happens. UK companies that choose the entity route often assume that owning the Indian subsidiary outright means less compliance risk than an EOR arrangement. It is usually the opposite. As the legal employer, the UK owned entity carries direct liability for EPFO contributions, gratuity accrual under the Payment of Gratuity Act, and TDS filings, all of which require an in country payroll and compliance function that the UK head office rarely has real visibility into. We have seen UK finance teams discover, well over a year into running their own entity, that gratuity liability had been accruing on the balance sheet without anyone in London tracking it.
Under an EOR model, the provider is the legal employer of record in India and carries this statutory liability directly, while the UK company keeps full operational and technical control over the engineer's day to day work. For UK companies hiring under 20 people in India, this shifts real compliance risk off the UK company's books entirely, which is the single biggest reason UK companies are moving from Entity to EOR in India rather than the other way around.
Companies planning to eventually cross that headcount threshold and build a genuine Global Capability Centers (GCC) in India often still start on EOR and convert to an entity later, once the team and internal processes are proven.
Entity vs EOR in India: A Comparison UK Founders Can Actually Use
Here is the breakdown we walk every UK client through before they commit to either path.
Factor | Own Entity (Pvt Ltd Subsidiary) | Employer of Record (EOR) |
Time to first hire | 4 to 6 months | 10 to 15 business days |
Upfront setup cost | £18,000 to £30,000 | £0 setup fee with most providers |
Ongoing compliance cost | £15,000 to £25,000 per year | Included in the monthly EOR fee |
Minimum headcount to justify | 15 to 20+ | 1 |
Statutory liability (PF, gratuity, ESI) | Sits with UK owned entity | Sits with EOR provider |
IP ownership transfer | Direct, via employment contract | Via EOR assignment agreement, still enforceable |
Ability to convert later | Not applicable | Convert to owned entity once headcount justifies it |
Board and RBI reporting | Required annually (FEMA, FDI reporting) | None |
The break even point, based on the mandates we have run, sits around 18 to 22 engineers. Below that, the entity's fixed annual compliance cost outweighs the per head EOR fee. Above that, an owned entity or a recruitment process outsourcing arrangement built around it usually becomes cheaper per head. Most UK companies we work with are hiring 3 to 12 people in India in year one, which is exactly why EOR is winning this decision for the majority of new UK entrants right now.
How the Transition Works: Process, Timeline, and a Real Client Story
For UK clients moving to EOR, our typical timeline runs: week one for role scoping and compliance structuring with the EOR partner, weeks one through three for candidate sourcing and technical vetting, week three for client interviews, and week four for offer and onboarding. Engineers typically start within 25 to 30 days of kickoff, faster if the client already has a defined stack and interview panel ready.
One mandate worth describing: a UK based insurtech, mid size, around 90 employees, Series B, had already begun incorporating an Indian subsidiary to build a six person data engineering pod in Pune. Three months into incorporation, their FDI reporting to the RBI got delayed because their UK side company secretary had not filed the FC GPR form correctly for the initial capital infusion, a document neither their UK lawyers nor their India side agent had flagged as time sensitive. The subsidiary sat in limbo, unable to legally hire, while their product roadmap slipped.
AnjuSmriti Global moved them onto an EOR arrangement for the same six roles within three weeks, sourced and placed four of the six engineers within 35 days, and the client shelved the entity plan entirely once they saw over a year of data engineering output at roughly 40% of the fully loaded UK equivalent cost. The stalled entity incorporation was formally withdrawn six weeks later.
We test technical fit for roles like this using a take home scenario involving a broken data pipeline with a subtle schema mismatch, rather than algorithmic puzzles. It tells us far more about how a candidate debugs unfamiliar systems under UK side time pressure, and increasingly, how comfortable they are pairing with AI assisted debugging tools that most engineering teams now use as standard practice.
Contract Hiring vs Full Time Hiring in India: What Actually Costs More?
For a mid size UK company comparing India contract hiring against building the same team in London, here is what current mandates show for a typical full stack or backend engineering role.
Mid level engineer, 3 to 5 years experience: India contract rate of £14,000 to £19,000 per year all in (salary, employer PF, and EOR fee combined), against £48,000 to £58,000 per year fully loaded in London including 15% employer NI and pension contributions.
Senior engineer, 6 to 9 years experience: India contract rate of £26,000 to £34,000 per year all in, against £70,000 to £88,000 per year fully loaded in London.
Lead or architect, 10+ years experience: India contract rate of £42,000 to £56,000 per year all in, against £95,000 to £125,000 per year fully loaded in London.
The all in India figure includes base salary, employer PF contribution at 12% of basic, gratuity accrual, and the combined EOR and agency fee, typically 18% to 22% on top of gross salary, bundled into one monthly invoice so UK finance teams get a single predictable line item instead of reconciling Indian statutory filings themselves.
This is also where contract versus full time hiring becomes a real budgeting question rather than a legal technicality. Contract engineers are typically cheaper on paper and easier to scale down, but full time hires under EOR tend to stay longer and cost less to replace, since UK companies avoid repeated onboarding and ramp up time.
Most of our UK clients start new roles as contract, convert strong performers to full time after three to six months, and reinvest the resulting savings into hiring an additional engineer rather than pocketing the margin. The insurtech mandate above used its savings to fund a dedicated QA engineer it otherwise could not have justified in the London budget.
Conclusion
Over the next 12 to 18 months, expect more UK companies to skip the entity conversation entirely for their first India hire and default straight to EOR, converting to an owned entity only once they cross the 20 engineer mark. That pattern is already visible in the mandates we are running for London fintechs today, alongside growing demand for engineers who can work confidently with AI powered development tools and cloud native infrastructure from day one. The reason UK companies are moving from Entity to EOR in India is not a passing trend. It reflects UK finance teams getting sharper about front loaded compliance risk versus flexible, liability light hiring.
If you are a UK founder weighing this decision, talk to us before you file a single incorporation document. We can usually tell you within a week whether entity or EOR makes financial sense for your specific headcount plan.
Interesting Reads:
FAQs
1.Does UK employment law apply to engineers we hire through an EOR in India?
No. The Employment Rights Act 1996 governs UK based employment and does not extend to workers employed and based in India. The relationship is governed by Indian labour law instead, including the EPF Act, the Payment of Gratuity Act, and the applicable state's Shops and Establishment Act, regardless of whether the legal employer is your own entity or an EOR provider.
2.Is contract hiring or full time hiring better for a first India team?
Contract hiring gives UK companies flexibility to test roles without long term commitment, while full time hiring under an EOR improves retention and reduces repeat onboarding costs. Most UK companies start new roles as contract and convert strong performers to full time within three to six months, once the role and the person are proven to be a good fit.
3.How does RBI reporting differ between an owned entity and an EOR arrangement?
An owned entity requires ongoing FEMA and RBI reporting tied to foreign direct investment, including FC GPR filings for capital infusion and annual FLA returns. An EOR arrangement involves no FDI at all, since the UK company pays a services fee rather than injecting capital, which removes an entire layer of regulatory reporting.
4.Can we convert from EOR to our own entity later without disrupting the team?
Yes. Once headcount crosses roughly 18 to 22 people, employment contracts are transferred from the EOR to the new Indian entity, with continuity of service preserved for gratuity and leave calculations. The transition typically takes 8 to 10 weeks and runs in parallel with normal operations so the team does not lose employment continuity.
5.Which UK industries are moving fastest from entity to EOR in India?
Fintech and insurtech firms in London are moving fastest, largely because FCA adjacent compliance sensitivity makes UK finance teams cautious about adding another compliance layer through an owned subsidiary. SaaS companies in Manchester and Bristol follow closely, driven more by speed to hire than compliance concerns.
6.Does IP ownership work differently under an EOR compared to a UK owned entity?
IP assignment runs through the employment or services agreement the EOR signs with the engineer, which explicitly assigns work product to your company as the client, not to the EOR itself. This is standard and enforceable under Indian contract law, though UK legal teams should still review the specific clause before onboarding the first engineer.
7.How does an EOR handle payroll currency risk for UK companies?
Most EOR providers invoice the UK company in GBP or USD monthly and handle INR conversion and disbursement on the India side, shifting execution risk away from the UK finance team. We recommend UK clients still model a 5% to 8% currency buffer into annual budgets, since invoiced amounts can shift depending on how the provider times conversion.
8.What happens if we need to terminate an engineer employed through an EOR in India?
Termination still follows Indian labour law regardless of who the legal employer is, typically requiring notice periods of 30 to 90 days for skilled roles depending on tenure and the applicable state law. The EOR manages the legal process and documentation, but UK managers should plan around Indian notice requirements rather than UK style immediate termination.
Comments