Scaling a Belarus Team via EOR: When to Add Headcount and When to Switch to an Entity

You put your Belarus team on an EOR, and it worked — people hired fast, no entity to stand up, payroll and compliance handled while you got on with building. Now the team is growing, and a new question shows up: keep adding people through the EOR, or set up your own company?

The honest answer is that an EOR was never a permanent verdict or a stopgap. It’s the right tool for a phase of scaling, and that phase has an end — a point where owning an entity starts to make more sense. The trick is spotting yours before you overshoot it.

Here’s how to find that point, and what to do on either side of it.

Why an EOR is the right way to start — and to keep scaling for a while

Nothing about growth changes why the EOR made sense in the first place. Hiring through an EOR gets people working in weeks, with no entity, no local director, and no compliance burden landing on you. The provider is the legal employer, so payroll, taxes, and the currency and banking mechanics sit with them, not with you.

That keeps working well past your first hire. Through validation, early traction, and the first waves of growth, an EOR lets you add talent without committing capital or locking in your activity. For a lot of teams that runway lasts a good while — and there’s no prize for leaving it early.

The catch: EOR cost climbs in a straight line

There’s a structural catch, though. Every hire adds the same per-head fee, so your total cost rises in a straight line with headcount. You also don’t get a tax regime of your own — you’re paying ordinary Belarusian employment taxes through the provider, with no access to the preferential treatment an entity can unlock.

And because you don’t own an entity, your IP and any equity arrangements are handled by contract rather than held directly. None of that is a problem early on. It just means that at some size, “simple” quietly stops being “cheap” — and stops being “enough.”

The real tipping point is a crossover, not a headcount

Ask around and you’ll hear rules of thumb: switch at ten people, switch at twenty. Ignore them. The tipping point isn’t a headcount — it’s a cost crossover, and where it lands depends on your salaries, your provider’s fees, and the tax regime you’d unlock by owning an entity.

Aspect	Scaling on an EOR	Your own entity (HTP)
Cost per hire	Salary + a per-head service fee, every month	Salary + employer taxes (capped under HTP)
Fixed overhead	None — it’s rolled into the fee	Accounting, a director, reporting, an annual audit
How total cost grows	Linearly — each hire adds the full fee	Overhead barely moves; per-head cost is low and shrinks with HTP savings
Tax regime	None of your own	HTP: 0% profit tax, capped social contributions, ~5% dividends
Speed & flexibility	Hire in weeks; change course freely	Slower to set up; activity-restricted
Best when	Early, small, or uncertain	Scaling, committed, IP and tax matter

Picture two lines. EOR cost rises straight with every hire. An owned entity starts higher — there’s fixed overhead — but each additional hire costs far less, and the tax savings grow with your payroll. Sooner or later the lines cross. Everything to the left of the crossover favours the EOR; everything to the right favours your own company. The job is to find where they meet for your team, not to guess a round number.

To make it concrete: say your own HTP entity costs a few thousand BYN a month in fixed overhead — accounting, a director, reporting, the annual audit. On a well-paid team, the HTP social-contribution saving alone can run to four figures in BYN per developer, every month. That means a handful of engineers can generate enough saving to cover the entire overhead, and every hire past that point tips further in the entity’s favour. The exact figures are yours to plug in, but the shape is almost always the same: an entity looks expensive right up until a surprisingly small team makes it the cheaper option.

Why the crossover comes earlier in Belarus than the rule of thumb says

Here’s the part that catches founders out. In most countries the crossover really is somewhere around fifteen to twenty people. In Belarus it often comes sooner — because of one line on the payroll. A standard employer pays social contributions of about 34% on the full salary, while an HTP resident pays them only on a capped base.

On a well-paid engineering team, that cap is worth a four-figure sum in BYN per developer, every month — and it scales with headcount. Five developers can mean tens of thousands of BYN a year saved on that single line alone, savings an EOR simply can’t give you, because you don’t own the entity that unlocks them.

Stack the 0% profit tax and the preferential dividend rate on top — the rest of the HTP regime — and the generic “wait until twenty” heuristic often overshoots badly for a Belarus IT team. The crossover can arrive while you’re still in single or low double digits. (Figures move, so model yours on current rates.)

The signals that say “switch” — even when the math is close

Cost isn’t the only trigger, and sometimes it isn’t the first one. Switch when you’re committing to Belarus for the long term, when you want to own your IP in-country, or when you specifically need the HTP tax regime rather than simply employing people there.

There are softer signals too. You want to grant equity or options to local staff. You want a direct employer brand and your own culture, not people who technically work for someone else. You’re pulling a scattered team into one home. Any one of these can justify the move before pure cost does.

When to keep adding headcount on the EOR

The other half of the question matters just as much, and the honest answer is often “stay put.” Keep hiring on the EOR while you’re still validating, while you’re below your crossover, or while your commitment horizon is genuinely uncertain. Flexible, EOR-based scaling is exactly right when you’re not ready to plant a flag.

It’s also the better call if Belarus is one of several countries you hire in, if you want to keep your activity open rather than tie it to a business project, or if you’re simply not ready for entity overhead, ongoing compliance and an annual audit. Growth on its own isn’t a reason to switch — the shape of the growth is.

You don’t have to switch all at once

The choice isn’t strictly one or the other. Plenty of companies run a hybrid: an entity for the committed core team in Belarus, and an EOR alongside it for new hires they’re still sizing up or for people in other countries. The entity captures the tax savings on the staff you’re sure about, while the EOR keeps the speed and flexibility for everything still in flux.

It’s a practical way to get the best of both. You don’t have to move every last person the day you incorporate, and you don’t have to keep paying EOR fees on a stable core just because a few roles are still uncertain. Split the team along the line of commitment, not the calendar — the settled part in the entity, the experimental part on the EOR.

If you do switch: HTP resident or standard LLC?

If you cross the line, there’s a second choice: what kind of entity. For a qualifying IT team an HTP resident is usually the point — the Park’s regime is what pulled your crossover forward in the first place, so setting up outside it would be an odd move.

If your activity doesn’t qualify, a standard LLC is the fallback — simpler and unrestricted, but without the tax breaks. It’s worth reading a full tax-and-cost comparison of the two before you commit, because the gap between them is large.

Either way, the first practical step is confirming your activity qualifies for HTP at all, which is worth checking with someone who does it day to day rather than assuming.

How to switch without disruption

The fear with switching is disruption — people, pay and IP all moving at once. It doesn’t have to feel that way. The heart of a clean transition is moving your people from the EOR’s employment onto your new entity while their payroll keeps running without missing a single cycle.

Contracts and IP get reassigned to your entity in the same move, so nothing about ownership is left ambiguous. Tenure carries over, people keep working, and from the team’s side it should feel like an administrative change rather than an upheaval.

The rest is sequencing: standing up the entity, securing HTP admission if that’s the route, and handing over accounting and reporting so nothing falls through the gap. With one provider across both stages, it’s a handover, not a rebuild.

A quick way to decide

Anchor on what an entity would actually cost and save — against the standard rates you’re paying now through the EOR — then run five questions:

• Is your headcount near the crossover you’d model for your salaries?
• How firm is your commitment to Belarus — months, or years?
• Do you need to own IP in-country or grant equity to local staff?
• Does your activity qualify for the HTP regime?
• Are you ready for entity overhead, compliance and an annual audit?

Mostly “not yet, uncertain, keep it flexible”? Keep scaling on the EOR. Mostly “yes, committed, IP and tax matter”? It’s time to set up your own entity.

FAQ

Is there a headcount where an EOR always stops making sense?

No single number fits everyone — it depends on salaries, provider fees, and whether you’d qualify for the HTP regime. For a well-paid Belarus IT team the crossover often comes earlier than the usual fifteen-to-twenty rule, sometimes in single or low double digits. Model it on your own figures rather than trusting a benchmark.

Can I move people from the EOR to my own entity without re-hiring them?

Yes. A proper transition moves your people onto the new entity as a handover, with tenure and terms carried over, rather than firing and re-hiring. Handled well, it’s an administrative change for the team, not a disruption.

Will switching interrupt anyone’s pay?

It shouldn’t. The whole point of sequencing the move is that payroll runs continuously — people shift from the EOR’s books to your entity’s without missing a cycle. Continuity is the first thing to plan for.

What happens to our IP when we switch?

IP and contracts are reassigned to your new entity as part of the move, so ownership sits cleanly with your company. Under an EOR your IP is already assigned to you by contract; switching just formalises it inside your own entity.

Can I run an EOR and an entity at the same time?

Yes, and many companies do. A common hybrid is an entity for the committed core team in Belarus and an EOR for new hires or new markets you’re still testing. The two aren’t mutually exclusive.

Do I lose the EOR’s speed once I have an entity?

For hiring into the entity, yes — that’s ordinary employment, not the plug-and-play speed of an EOR. It’s exactly why some teams keep an EOR alongside the entity for fast or experimental hiring while the core sits in the company.

How long does the switch take end to end?

Setting up an entity and, if relevant, securing HTP residency runs in weeks to months, depending on your documents and the review. The people-and-payroll transition is planned around that, so it lands as a scheduled handover rather than a scramble.

Roughly what does an entity’s fixed overhead cover?

The recurring pieces are accounting and reporting, a director, statutory filings, and — for a company with foreign investment — an annual audit. It’s a largely fixed cost that barely grows as you add people, which is exactly why the per-head economics keep improving with scale.

Let eor.by find your switch point

We run EOR teams and we set up entities — HTP and standard — so we’re not trying to nudge you from one to the other. We’ll model your crossover on your real salaries and headcount, tell you honestly whether you’re there yet, and handle whichever side of the line you’re on.

Talk to eor.by and we’ll show you where your switch point sits — then either keep scaling your team, or set up your entity and move everyone across without a hitch.