{"id":6051,"date":"2026-09-22T10:05:22","date_gmt":"2026-09-22T07:05:22","guid":{"rendered":"https:\/\/eor.by\/?p=6051"},"modified":"2026-09-30T14:35:26","modified_gmt":"2026-09-30T11:35:26","slug":"scaling-belarus-team-eor-when-to-switch-to-entity","status":"publish","type":"post","link":"https:\/\/eor.by\/ru\/scaling-belarus-team-eor-when-to-switch-to-entity\/","title":{"rendered":"\u041c\u0430\u0441\u0448\u0442\u0430\u0431\u0438\u0440\u043e\u0432\u0430\u043d\u0438\u0435 \u043a\u043e\u043c\u0430\u043d\u0434\u044b \u0432 \u0411\u0435\u043b\u0430\u0440\u0443\u0441\u0438 \u0447\u0435\u0440\u0435\u0437 EOR: \u043a\u043e\u0433\u0434\u0430 \u0443\u0432\u0435\u043b\u0438\u0447\u0438\u0432\u0430\u0442\u044c \u0448\u0442\u0430\u0442, \u0430 \u043a\u043e\u0433\u0434\u0430 \u043e\u0442\u043a\u0440\u044b\u0432\u0430\u0442\u044c \u0441\u0432\u043e\u0451 \u044e\u0440\u043b\u0438\u0446\u043e"},"content":{"rendered":"\n

You put your Belarus team on an EOR, and it worked \u2014 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?<\/p>\n\n

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 \u2014 a point where owning an entity starts to make more sense. The trick is spotting yours before you overshoot it.<\/p>\n\n

Here’s how to find that point, and what to do on either side of it.<\/p>\n\n

Why an EOR is the right way to start \u2014 and to keep scaling for a while<\/strong><\/h2>\n\n

Nothing about growth changes why the EOR made sense in the first place. Hiring through an EOR<\/a> 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.<\/p>\n\n

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 \u2014 and there’s no prize for leaving it early.<\/p>\n\n

The catch: EOR cost climbs in a straight line<\/strong><\/h2>\n\n

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 \u2014 you’re paying ordinary Belarusian employment taxes<\/a> through the provider, with no access to the preferential treatment an entity can unlock.<\/p>\n\n

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, \u201csimple\u201d quietly stops being \u201ccheap\u201d \u2014 and stops being \u201cenough.\u201d<\/p>\n\n

The real tipping point is a crossover, not a headcount<\/strong><\/h2>\n\n

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 \u2014 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.<\/p>\n\n

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

Picture two lines. EOR cost rises straight with every hire. An owned entity starts higher \u2014 there’s fixed overhead \u2014 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.<\/p>\n\n

To make it concrete: say your own HTP entity costs a few thousand BYN a month in fixed overhead \u2014 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.<\/p>\n\n

Why the crossover comes earlier in Belarus than the rule of thumb says<\/strong><\/h2>\n\n

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 \u2014 because of one line on the payroll. A standard employer pays social contributions of about 34%<\/a> on the full salary, while an HTP resident pays them only on a capped base.<\/p>\n\n

On a well-paid engineering team, that cap is worth a four-figure sum in BYN per developer, every month \u2014 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.<\/p>\n\n

Stack the 0% profit tax and the preferential dividend rate on top \u2014 the rest of the HTP regime<\/a> \u2014 and the generic \u201cwait until twenty\u201d 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.)<\/p>\n\n

The signals that say \u201cswitch\u201d \u2014 even when the math is close<\/strong><\/h2>\n\n

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<\/a> rather than simply employing people there.<\/p>\n\n

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.<\/p>\n\n

\"\"<\/figure>\n\n

When to keep adding headcount on the EOR<\/strong><\/h2>\n\n

The other half of the question matters just as much, and the honest answer is often \u201cstay put.\u201d 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<\/a> is exactly right when you’re not ready to plant a flag.<\/p>\n\n

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 \u2014 the shape of the growth is.<\/p>\n\n

You don’t have to switch all at once<\/strong><\/h2>\n\n

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.<\/p>\n\n

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 \u2014 the settled part in the entity, the experimental part on the EOR.<\/p>\n\n

If you do switch: HTP resident or standard LLC?<\/strong><\/h2>\n\n

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 \u2014 the Park’s regime<\/a> is what pulled your crossover forward in the first place, so setting up outside it would be an odd move.<\/p>\n\n

If your activity doesn’t qualify, a standard LLC is the fallback \u2014 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.<\/p>\n\n

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<\/a> rather than assuming.<\/p>\n

\n\t
\n
\n
\n
\n
\n
\n \n \n <\/svg>\n <\/div>\n

PEO<\/h3>\n <\/div>\n
Trust us to handle regulations, allowing you to focus on what truly matters\u2014driving innovation and achieving excellence.<\/div>\n <\/div>\n\t\t\t\t\t
\n
\n Try<\/a>\n <\/div>\n <\/div>\n\t\t\t\t\t <\/div>\n <\/div>\n <\/section>\n\t<\/div>\n

How to switch without disruption<\/strong><\/h2>\n\n

The fear with switching is disruption \u2014 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<\/a> keeps running without missing a single cycle.<\/p>\n\n

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.<\/p>\n\n

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

A quick way to decide<\/strong><\/h2>\n\n

Anchor on what an entity would actually cost and save \u2014 against the standard rates<\/a> you’re paying now through the EOR \u2014 then run five questions:<\/p>\n\n