← Insights

EOR, BPO or your own entity — what each one actually gives you

Four models, four different purchases. What each one delivers, and where each one is the wrong answer.

These four options get compared as if they were competing quotes for the same thing. They are not. They are four different purchases, and the reason comparisons between them tend to go badly is that each one assumes you have already answered a different set of questions.

What follows is what each model actually provides, stated plainly, along with the assumption it makes about you. The assumption is usually the deciding factor — more than price, and more than the feature list on anyone's website.

Your own local entity

You buy: a legal presence you control, the ability to employ directly, local credibility with customers and regulators, and no third party in your commercial relationship with your own staff.

It assumes: you already know this market will carry a real business, and you are prepared for the entity to exist for years rather than for a project.

The cost people quote is incorporation. The cost that matters is everything that follows permanently: statutory accounting, payroll, tax filings, employment-law compliance, a local director or registered agent in some jurisdictions, and the management attention of whoever ends up owning it internally. That last item is the one nobody budgets. It usually lands on a finance lead or a COO who already has a job.

An entity is the right answer more often than people think — just later than they think. It is very rarely the right first step for a two- or three-person team.

An employer of record

You buy: compliant employment of a specific person, in a specific country, without your own entity there. The EOR is the legal employer; the person works for you day to day.

It assumes: you know who you want to employ, and you know where. Both.

This is worth reading twice, because it is where most EOR disappointment comes from. An EOR is an employment mechanism, not a talent function and not an advisory one. It will not tell you whether Poland or Portugal is the better market for the skill you need, it will not find or assess the candidate, and it will not tell you whether the role is viable as one person or needs two. If you have those answers, an EOR is efficient and does exactly what it says. If you do not, you have bought a tool that is waiting on a decision you have not made — and the monthly fee starts anyway.

Watch the boundaries too: notice periods, severance exposure, benefits parity, intellectual-property assignment and misclassification risk all vary by country, and they are the terms that matter when something goes wrong rather than when it is working.

A BPO or outsourcing provider

You buy: an outcome or a process, run by someone else, usually with their own management layer, their own tooling and a service level attached.

It assumes: the work can be specified well enough to hand over, and that handing it over is genuinely what you want.

BPO is very good at what it is for. Volume, repeatability, a process that can be described in a document and measured against a target. Where it struggles is complex specialist work that needs product depth, customer context and continuity of judgement — because the provider's economics depend on interchangeable resourcing, and yours depend on the same two people still being there in eighteen months knowing what they learned in the first six.

There is also a scale floor. Two specialist roles is usually below the size that interests a provider, and what you are offered instead is either a minimum team you do not need or a shared-resource model that quietly removes the continuity you were buying.

A managed arrangement

You buy: the decisions and the people together. Someone determines the location and employment model with you, sources and assesses the individuals, arranges whichever structure fits each one, and gives you a single commercial relationship — while the people work inside your teams, on your tools, in your process.

It assumes: you can describe the capability you need. Nothing further.

This is what HBN does, and the honest reason it exists is the gap the other three leave. An entity requires conviction you have not earned yet. An EOR requires two answers you may not have. A BPO requires the work to be separable, and complex work is not. A managed arrangement is the option that starts from the requirement rather than from the infrastructure.

The trade-off is real and worth stating: there is a party between you and the employment arrangement, and you are relying on their judgement about location, model and people. That is precisely what you are buying, so it is fair to interrogate it — ask what they would recommend and why, and whether they would tell you if the answer were an entity of your own.

How to choose in one pass

The mistake that costs the most

It is not picking the wrong model. It is picking a model before defining the capability, which means the model then defines the capability — you end up with a team in the country your provider happens to operate in, at the size that suits their commercial minimum, structured the way their contract template prefers.

Write down what has to be true operationally for the work to be done well: hours of coverage, language, physical presence, product depth versus process discipline, how much the person has to sit inside your own delivery organisation. Then read the four options above against it. The choice usually makes itself.