That time we told a client to leave EOR (and why they thanked us)
Most EOR engagements should keep running. Fast market entry, zero setup costs, full compliance from day one: that's what EOR is built for, and for most companies at most headcounts, it stays the right answer for a long time.
But sometimes it stops being the right answer in one specific market. And when it does, it helps to have a partner who will say so.
Last year, we sat down with the CFO of a European AI company. They'd grown from 12 to over 40 people across four countries in 18 months. We looked at the numbers together and said: you need to stop using EOR in Germany. Everywhere else, carry on.
We call this graduation: moving from renting someone else's infrastructure to building your own. It doesn't happen to every client. It shouldn't. But when the conditions line up, the economics, the IP position, the commercial reality, it's worth having the conversation.
As Tom, our CRO, puts it: "EOR is the right thing for most people most of the time. But when you get to a certain point, you should be on a different model, and the knowledge gap stops you."
What actually happened
In our experience, companies often hit the tipping point around 10-20 employees in one country. For this client, Germany came first. With employer costs running 20.7% on top of gross salary, the maths shifted faster than in Spain or France.
But cost wasn't the only driver. Two other factors pushed them towards their own entity. They were building genuinely novel AI/ML work and wanted a cleaner chain of title on their IP, with direct employment contracts for the German engineering team rather than IP travelling through an EOR layer. And they wanted to start bidding on German public sector and larger enterprise tenders, a lot of which either require a local GmbH or heavily favour one.
Speed wasn't the critical factor. What mattered was making the move smoothly and without incident. As Tom told their COO: "There is no financial gain, no matter what the spreadsheet says, from trying to do it so quickly that you end up causing problems in your own operating company."
In the end, 12 employees in Germany made the switch without incident. The same specialist who'd been with them since day one handled the whole transition.
The starting situation
Twelve employees across Germany, Spain, France, and the UK. An AI/ML company scaling fast. Mid-2024.
EOR was the right structure at that moment. This is precisely what Employer of Record services are built for: hire quickly in a new market, avoid months of legal setup, and stay compliant from day one.
Eighteen months later, the numbers had changed. 40+ employees total. 10+ concentrated in Germany. A projection of 60+ within the next 12 months. Germany had also become the company's R&D centre of gravity, and German buyers were starting to ask for a local contracting entity before they'd engage on larger deals.
The structure that was right at 12 was no longer right at 40 in Germany specifically. Elsewhere, EOR was still the right call.
The four questions we worked through
First, the economics: at what point does your own German entity cost less than EOR fees? For them, it was 8 employees. They had 10.
Second, operational flexibility: what can't you do on EOR that's starting to hurt? They couldn't modify equity vesting schedules, create custom bonus structures, or put German clients on a GmbH-issued contract.
Third, IP: what protection do you need? As Tom says: "If you've got IP, that might be something that's pretty important to you." On EOR, the legal employer is the EOR provider, not you. IP assignment still works, but it travels through an extra layer of contracts. With engineering concentrated in Germany, the client wanted direct employment relationships.
Fourth, growth trajectory and compliance maturity: what does your 12 to 24 month hiring plan look like, and does your team have bandwidth to manage German employment law internally?
For this client, all four answers pointed the same way in Germany. In the other markets, they pointed to staying on EOR. It's worth saying plainly: a mixed picture is normal and usually right. Different countries, different answers.
What we recommended
Germany: your own entity. Estimated saving of €180,000 a year, direct employment contracts, clean IP chain of title, and a GmbH name on contracts with German customers.
France: not yet.
Spain and UK: stay on EOR.
We offered to handle the German transition, including the tricky parts like Betriebsübergang compliance, and to stay on for payroll and compliance afterwards.
The client's COO responded: "We've been wondering when it would make sense to set up our own entity. The fact that you're the one raising this conversation, rather than trying to keep us on EOR indefinitely, tells us we're working with the right partner."
What the transition looked like
Planning first
Before anything moved, we built a simple model comparing current costs versus entity costs at 10, 20, and 40 employees. We mapped out a realistic path to formation, introduced them to local counsel, and assigned Tom as their single point of contact.
Tom's advice from day one was to plan, not sprint: "Never, ever decide to have an entity ASAP. You can do it quickly, just don't do it ASAP. Don't do it in too much of a hurry."
The same person who'd known their equity plans, benefits philosophy, and growth trajectory for 18 months stayed on the account. Different legal structure underneath, same relationship on top.
Handling the German complexity
German employment law has teeth. Betriebsübergang rules mean you can't just switch employers without proper consultation. Get it wrong and employees can claim constructive dismissal.
Tom coordinated the required employee meetings, information letters, and consultation periods. Every employee knew what was changing, what wasn't, and exactly how it affected them. Final payroll and entitlements reconciled holiday balances, benefits, and final payments to the last cent.
As Tom describes the job: "Having a partner that will smooth out the dents and the bumps in the road is the bit that is critical."
The numbers: 10+ employees transitioned across 4 countries. 6 moved to the client's own German entity. The remaining employees continued on EOR in Spain, France, and the UK. 8 weeks from decision to completion, not because we rushed, but because the planning front-loaded the work.
After the switch
The Germany EOR engagement ended. The Spain, France, and UK engagements didn't. Neither did the partnership.
Teamed continued with entity management for Germany, ongoing payroll and compliance, and HR advisory for the new in-house team. This is what GEMO (Global Employment Management and Operations) looks like in practice: one relationship across every structure, adjusted market by market as the situation evolves.
What changed
Every employee got paid on time, kept their benefits, and barely noticed the legal change. The company saved €15,000 per month in Germany alone. They could offer the equity vesting terms they wanted, put their IP chain of title on a clean footing, and start responding to German tenders under their own GmbH.
Six months later, their CEO introduced us to two portfolio companies. His words: "They'll tell you when to stop using them." For us, graduation means you're succeeding, not leaving.
When should you move from EOR to your own entity?
For most companies, most of the time: don't. EOR is the right answer for a long time in a lot of situations. The question is whether you've crossed into the zone where it no longer is for a specific market.
The crossover point typically sits between 8 and 15 employees in a single market. Germany's regulatory environment and employer social contribution costs, with tax wedges of 43.9% being the second-highest in the EU, mean the crossover tends to come earlier than in most European markets.
The calculation involves headcount, projected growth, entity setup and maintenance costs versus per-employee EOR fees, operational control needs, whether a local legal entity unlocks tender or customer contracting access, and how clean you need your IP chain of title.
Stay on EOR if your headcount in each market isn't near the crossover zone, or if commercial and IP factors don't independently justify the move. Move to your own entity when the numbers, operational needs, and commercial reality all point that way in a specific country. Often the right answer is mixed: own entity in one market, EOR in the others.
What happens to employees in a German transition?
In Germany, transitions are governed by Betriebsübergang (business transfer law). Formal employee consultation is required, including written notification about timing, reasons, consequences, and planned measures. Employee rights are protected, and when managed properly, employees transfer with their existing terms preserved.
Germany also has country-specific employee protection norms that make termination processes higher-risk than in many jurisdictions. Companies with more than 10 employees require justified reasons for regular termination.
Do you have to switch providers when you leave EOR?
Not with us. We can help you set up the entity, manage the transition, and keep running payroll and compliance afterwards. Same people, same systems.
This transition across 4 countries took 8 weeks from decision to completion. Timelines vary by jurisdiction. Tier 2 countries like Germany, France, and Spain typically require 4-6 months for full entity establishment, including incorporation, banking, tax registration, and employee transfer.
A mixed structure is also fine during transitions and beyond. This client established their own entity in Germany while keeping EOR in Spain, France, and the UK where headcount was lower.
A few questions worth asking
When was the last time your provider modelled whether EOR is still the right structure for each of your markets? Can they name the specialist who would handle a contested termination in your biggest country? What happens to the relationship if you set up your own entity somewhere?
If you have 8-15 employees in any European country and you've never seen the maths on entity versus EOR costs, it's worth running the numbers. Depending on the country, the crossover might already be behind you, or still comfortably ahead.
Want to see the maths on your situation? Talk to an Expert. We can show you where your crossover point is, what entity setup actually costs, and whether switching makes sense right now, or whether staying put is the better call.