Employer of Record vs. entity setup: the honest tradeoff

Nobody says this out loud, but Employer of Record is the right answer more often than the entity-setup consultants would like you to believe. It’s also the wrong answer more often than the EOR vendors would admit. Here’s the honest framework we walk clients through — the one that tells you which side of the line you’re on, and, more importantly, when to switch.

What each model actually gives you

An Employer of Record is a company that legally employs your workers on your behalf, in a country where you don’t have a legal entity. They handle the payroll, the taxes, the statutory benefits, the local labour-law compliance, and the paperwork. You keep day-to-day management, direction, and — critically — the working relationship. What you buy is speed, coverage, and the ability to have real employees in a country without incorporating.

An entity setup is exactly what it sounds like: you register a subsidiary in-country, open bank accounts, engage a local accounting firm, sign leases, run your own payroll. You take on the full compliance surface area, which is expensive up-front and cheap on the margin. What you buy is control, cost efficiency at scale, and the ability to do things — sign contracts, hold IP, employ executives with local equity — that an EOR structurally can’t do for you.

Signals you should EOR

• Fewer than ~15 employees in-country and no realistic 12-month plan to double that number. Below the break-even headcount, entity overhead eats the salary savings and adds a year of legal and finance work you’re not resourced for.
• You’re piloting a market and haven’t validated the demand yet. Entities are expensive to close. If there’s a 30% chance you pull out in 18 months, EOR is a strictly dominant strategy.
• Your finance team can’t absorb a new local tax and payroll surface area right now. Being technically capable of running foreign payroll and being organisationally ready are two different things. If your controller is already at 110%, adding a new country of compliance obligations is how you get a filing miss that shows up in due diligence two years later.
• Speed to a first hire matters more than a ~10% margin on salary. Entity setup takes 3-9 months in most jurisdictions. EOR gets you a signed offer letter this week.
• You need optionality on geography. If the answer to “which country do we hire in” is “probably three of them, we’re not sure which,” multi-country EOR lets you keep learning without pre-committing to entities.

Signals you should incorporate

• You’re consistently running >25 employees and the EOR fees (typically $400-800 per employee per month, before markups) have crossed the break-even math against local accounting-firm retainers.
• You need to sign local commercial contracts, hold local licences, or take on IP that must sit inside a local legal entity. EOR can’t do this — the EOR owns the employment relationship, not your business relationships.
• Executive hires with equity are demanding it. Meaningful local option grants require a local entity in most jurisdictions. If you’re losing a senior candidate over this, you’ve probably crossed the line already.
• Your tax structuring makes it worthwhile. Transfer pricing, R&D credits, and IP-holding structures are only accessible with local entities. If the tax team is talking about these, get on with it.
• Your investors are asking about it. This is a signal, not a mandate — but if a board-level investor has flagged that a hiring geography ought to have an entity, take the question seriously. They’ve seen this movie before.

The transition — where most companies overstay

The most expensive mistake we see: staying on EOR long past the break-even point because switching is annoying. The typical scenario is a company that grew from 5 to 40 employees in a country on EOR, and is now spending $250K-$400K a year on markup that would fund a local accounting firm three times over. Nobody wanted to own the transition, so it drifted.

The second most expensive mistake: incorporating too early. A 6-person team in a country where the CEO can’t yet articulate the local go-to-market ends up with a subsidiary, a local finance hire, a lease they didn’t need, and a compliance calendar that eats a founder’s Wednesday afternoon for the next decade.

The good news: neither of these is a one-way door. Companies migrate from EOR to entity, and — less commonly but still perfectly reasonable — from entity to EOR when a country is being wound down. Design for reversibility, and stop treating the decision as bigger than it is.

A practical migration playbook

When you decide to move from EOR to entity, work backwards from the payroll cutover date. Six months out: engage a local corporate services firm to file the incorporation, open bank accounts, register for tax and social security. Three months out: your finance team parallel-runs one dummy payroll cycle in the new entity. Six weeks out: transition offer letters go to every EOR-employed worker, offering identical terms under the new entity. Two weeks out: dry run the actual payroll run against a shadow account. Cutover day: your EOR closes out final pay, your entity picks up the next cycle. Nobody misses a paycheque.

Done well, this is a two-quarter project with minimal disruption. Done badly, it’s a two-year quagmire that generates more Slack messages than actual hires.

The wrong reasons to choose either model

“Everyone else in our stage is doing X” — irrelevant.

“Our CFO’s previous company used X” — anecdotally interesting, not evidence.

“The consultant told us we needed Y” — the consultant sells Y. Check their fee structure.

“We just want the cheapest option” — the cheapest option optimises for the current month, not the next 24 of them, and the maths on migration cost dwarfs the monthly delta almost every time.

Pick based on your headcount trajectory, your appetite for local surface area, and the specific things you need the legal structure to enable. Everything else is noise.