EOR vs. setting up an entity: how to decide

This page compares the two paths side by side, explains the honest crossover point where an entity starts to win on cost, and gives you a clear way to choose. It describes the shape of each option rather than quoting entity setup costs or timelines — those swing too widely by country to state as one number. When you want to model a real figure, we link to a calculator that does it per country.

Last updated July 18, 2026. Jump to: The short answer · Quick definitions · Side-by-side · When an entity wins · Which to choose · What an entity involves · FAQ

The short answer

Most teams reach for an EOR first and build their own entity later, if ever. An EOR gets you hiring almost immediately in a country where you have no legal presence, and you pay per employee. Your own entity is the opposite trade: more to set up and more to run, but full control and a marginal cost that stops rising once you employ enough people there.

So the decision is rarely "which is better." It is "which fits this country, at this headcount, on this time horizon." A single hire in a market you are testing points to an EOR. A large, permanent team in one country eventually points to an entity. This page draws that line as clearly as the honest answer allows.

Quick definitions

Two plain definitions before the comparison, so the rest of the page reads cleanly.

• Employer of record (EOR). A company that legally employs a worker on your behalf, in a country where you have no entity. It holds the local contract, runs payroll, withholds tax, and administers statutory benefits, while you direct the day-to-day work. Our employer of record explainer walks through the full model.
• Your own legal entity. A company you register and run in the country yourself — a local subsidiary or branch. It makes you the direct legal employer, so you own the contracts, payroll, tax filings, and compliance, and you carry the cost of keeping it running.

The core difference is who carries the local employer role. With an EOR, a third party carries it for you. With your own entity, you carry it directly. Everything else in the comparison follows from that one split.

EOR vs. entity: a side-by-side

The table lines up the two paths across the dimensions that actually drive the decision. Costs are shown as shapes, not fixed numbers, because entity setup and overhead vary too widely by country to state as one figure.

Read the table top to bottom and a pattern appears. An EOR trades a recurring per-head fee for speed, low up-front cost, and someone else carrying the compliance. An entity trades a bigger commitment for full control and a cost that does not climb with every new hire. Neither is "cheaper" in the abstract — it depends on the numbers below.

When does an entity become cheaper than an EOR?

This is the question the decision usually rests on, and it has an honest answer: it depends on headcount, on how the EOR prices, and on the country. There is a crossover point, but it is not a fixed number that holds everywhere.

The mechanics are simple. An EOR fee is roughly per employee — it scales with the number of people you employ in the country. Your own entity carries a mostly fixed overhead — the cost of running it does not climb much as you add people. So at a small headcount, the per-employee EOR fee is easily below the fixed cost of a whole entity. As headcount rises, the EOR total keeps climbing while the entity overhead stays flat, and at some point the lines cross.

At small headcount an EOR usually wins on total cost and speed. At large, permanent headcount in one country, your own entity usually wins on marginal cost. The crossover is where those two truths meet — and it moves by country.

Where exactly it lands depends on three things. First, headcount in that one country — the more people, the more the fixed-cost entity pulls ahead. Second, how the EOR prices — a flat per-employee fee behaves differently from a percentage of payroll, which rises with salary. Third, the country itself, because both the cost of running an entity and the statutory employer costs you owe under either model vary widely.

That last point is worth making concrete. Statutory employer contributions — the on-costs you pay on top of salary either way — range from lighter to very heavy depending on where you hire. In Canada total employer tax runs roughly 8%, in Germany around 19%, and in France it can reach the high tens of percent (from our country guides, checked July 2026). Those figures do not change which model you pick — you owe them under both — but they shape the total you are modelling, and they show why a single crossover number cannot hold across countries.

Which should you choose?

With the trade-off clear, the choice comes down to a few honest signals. Match your situation to the lists below.

Choose an EOR when:

• You have no entity in the country and no near-term plan to build one.
• You are testing a market, or hiring just one or two people there.
• You need someone employed quickly and cannot wait to register a company.
• You would rather a partner carry local employment compliance and most of the liability.

Build your own entity when:

• You employ, or expect to employ, a large permanent team in a single country.
• You want full, direct control over contracts, benefits, and policies.
• You need real in-country presence — a local office, local directors, on-the-ground operations.
• You have modelled the cost and the entity’s flatter marginal cost clearly wins at your headcount.

There is also a path that uses both, in sequence, and it is the common one. You start with an EOR to hire fast and prove the market, then convert to your own entity once headcount grows enough to justify it. Handled well, the transition maps pay, title, start-date continuity, and benefits across, so the employee keeps doing the same job while the legal employer behind them changes. Starting on an EOR does not lock you out of an entity later — it buys you time to reach the point where an entity makes sense.

What does setting up a legal entity actually involve?

If an entity is on the table, it helps to know what "set one up and run it" really means. The specifics differ by country, but the categories of work are consistent.

• Registration. Incorporate the local company and register it with the relevant authorities.
• Local requirements. Meet country rules that can include a registered address, local directors or a legal representative, and minimum capital.
• Banking and accounts. Open local bank accounts and set up tax and payroll registrations.
• Payroll operation. Run gross-to-net payroll, withhold income tax and social contributions, and pay people in local currency on a local schedule.
• Ongoing filings. File taxes and statutory contributions on each deadline, and keep accounts and corporate records current as the law changes.

None of this is a one-time task. An entity is a standing commitment — the up-front setup is followed by an ongoing operating load that continues for as long as the company exists. That is the fixed overhead the crossover math weighs against the EOR’s per-employee fee. It is also why an entity earns its keep at scale and rarely below it.

Frequently asked questions

Is an EOR or your own entity cheaper?

It depends on headcount and country. An EOR charges a recurring per-employee fee, so its total rises with every hire. Your own entity carries a mostly fixed overhead that does not climb with headcount but starts with setup and ongoing costs. At a small headcount an EOR is usually cheaper overall; at a large, permanent team in one country an entity usually wins on marginal cost. The crossover point moves by country, so model it rather than guess.

How fast can you hire with each option?

An EOR can employ someone in days to weeks, because it already holds a local entity and only needs to issue a compliant contract. Setting up your own entity typically takes much longer — you have to register the company, meet local requirements, and stand up payroll before you can hire anyone. When speed matters, an EOR is almost always the faster route into a new country.

Can you switch from an EOR to your own entity later?

Yes, and many teams plan for exactly that. A common path is to start on an EOR to hire quickly, then convert workers to your own entity once headcount grows enough to justify it. The legal employer changes, so employees sign new contracts, but good planning maps pay, title, start-date continuity, and benefits across. The person keeps doing the same job while the paperwork behind their employment moves.

Do you lose control if you use an EOR?

You keep control of the work; you give up some control of the employment framework. You still set tasks, priorities, pay, and performance — the EOR does not manage the person. What the EOR owns is the legal side: its local contract sets the employment terms, and it handles payroll, tax, and compliance. If you need to shape contracts, benefits, and policies directly, that is a reason to run your own entity instead.

At what point is setting up an entity worth it?

An entity becomes worth it when its mostly fixed cost falls below what you would pay an EOR per employee across your team in that country. That usually means a sizable, permanent headcount in a single market, or a need for real in-country presence such as a local office. The exact point depends on the country and salaries, so the honest answer is to model both paths at your expected headcount before committing.

Can you use an EOR and your own entities at the same time?

Yes, and larger teams often do. You might run your own entities in the few countries where you have big, permanent teams, and use an EOR for everywhere else — the single hires, the new markets, the places an entity cannot be justified. The two are not rivals; they cover different situations. Matching each country to the model that fits it is usually cheaper than forcing one approach everywhere.