{"id":5462,"date":"2026-06-12T15:35:41","date_gmt":"2026-06-12T12:35:41","guid":{"rendered":"https:\/\/recruitment.by\/?p=5462"},"modified":"2026-06-12T15:35:47","modified_gmt":"2026-06-12T12:35:47","slug":"how-to-set-up-odc-belarus","status":"publish","type":"post","link":"https:\/\/recruitment.by\/eng\/news\/how-to-set-up-odc-belarus\/","title":{"rendered":"How to Set Up an Offshore Development Center (ODC) in Belarus: A Step-by-Step Playbook"},"content":{"rendered":"\n

Before you start: is an ODC actually the right move?<\/strong><\/h2>\n\n\n\n

Over the last several years, we\u2019ve helped roughly 30 companies stand up operations in Belarus. The first thing we say on almost every intro call is the same: an ODC isn\u2019t always the right answer. It becomes the right answer when the alternatives stop holding up \u2014 not a day sooner.<\/p>\n\n\n\n

Here\u2019s the rough math we run during those first conversations. Hiring fewer than five engineers on project-bounded work? Contractors or an EOR will beat an ODC on speed and cost, every time. Committing to ten or more engineers, a three-year-plus horizon, and direct control over hiring, IP, and management? Now the ODC starts to make sense. In practice, the tipping point usually lands somewhere between hire eight and hire twelve. That\u2019s the moment the friction of juggling contractors quietly overtakes the fixed cost of just owning the entity.<\/p>\n\n\n\n

This playbook walks through what that setup actually looks like in 2026. We\u2019ve cut the theoretical parts. What\u2019s left is what we\u2019ve seen succeed and fail in practice.<\/p>\n\n\n\n

Why Belarus for an ODC in 2026<\/strong><\/h2>\n\n\n\n

The fundamentals of Belarus as a tech hub haven\u2019t shifted much in the last decade. The geography around it has.<\/p>\n\n\n\n

The country still produces some of the deepest infrastructure and product engineering talent in Eastern Europe, the legacy of two decades of work for EPAM, Wargaming, IBA, Viber, and a long list of product companies that flew under the radar. The talent network is still tight, even if a meaningful share of those engineers now sit in Warsaw, Vilnius, Tbilisi, Cyprus, or Serbia. For a modern ODC, that dispersion is actually useful. You can run a Belarus-registered entity that employs engineers across multiple jurisdictions, provided the contracting structure is set up right.<\/p>\n\n\n\n

The other half of the story is the High Tech Park (HTP)<\/a> \u2014 the regime that makes Belarus genuinely competitive on tax. We\u2019ll dig into it in a moment, but the short version is this: HTP-resident companies operate under a substantially lighter tax burden in exchange for staying within a defined scope of IT activities. Almost every foreign tech company setting up an ODC here pursues HTP residency, and frankly, we struggle to name a case where it didn\u2019t make sense to do so.<\/p>\n\n\n\n

The HTP framework, and why everything else hinges on it<\/strong><\/h2>\n\n\n\n

Almost every conversation we have with international clients ends up back at HTP. So it\u2019s worth understanding properly before you start moving on the setup.<\/p>\n\n\n\n

The High Tech Park<\/a> is a special tax and legal regime the Belarusian government created in 2005 to anchor the IT sector. Foreign-owned subsidiaries can apply for residency, and once granted, the company sits inside a different tax structure than the rest of the Belarusian economy. The benefits stack up quickly: corporate income tax exemptions on most qualifying activities, reduced personal income tax on employee salaries, simplified currency operations, and a clean IP assignment framework that works well for international owners. There\u2019s also an annual contribution to the HTP development fund, calculated as a percentage of revenue \u2014 that\u2019s how the system funds itself.<\/p>\n\n\n\n

The catch is scope. Your company has to operate within an approved list of IT activities. That list is broad \u2014 software development, consulting, R&D, fintech, cybersecurity, AI, and most things adjacent \u2014 but it isn\u2019t infinite. If the business model wanders outside the approved boundaries, residency is at risk. For most software-focused ODCs this isn\u2019t a real constraint. But you should go in clear-eyed.<\/p>\n\n\n\n

The official HTP site at park.by<\/a> carries the current activity list and application requirements. The English version is decent. Even so, we\u2019d recommend working with a local advisor on the actual filing.<\/p>\n\n\n\n

<\/p>\n\n\n\n

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

The setup, step by step<\/strong><\/h2>\n\n\n\n

Eight steps. Realistic timing on each.<\/p>\n\n\n\n

Step 1: Pick your legal structure.<\/strong> The vast majority of ODCs here are set up as Limited Liability Companies (LLCs). It\u2019s the simplest path, permits 100% foreign ownership, has reasonable capital requirements, and meshes cleanly with HTP residency. Joint Stock Companies and branch offices exist as options too, but unless your headquarters structure demands one of those (a regulatory wrinkle in your home country, say), LLC is the default. Budget about a week for this decision, mostly because the right answer depends on what your parent entity looks like.<\/p>\n\n\n\n

Step 2: Decide on HTP residency early.<\/strong> You can<\/em> register the entity first and apply for HTP afterward \u2014 but it\u2019s cleaner to plan both in parallel from day one. The HTP application demands a business plan, a defined activity scope, and a clear ownership structure. Working backward from those requirements will shape your incorporation paperwork. For almost every foreign company, pursuing HTP residency is the right call.<\/p>\n\n\n\n

Step 3: Prepare incorporation documents.<\/strong> The founders’ resolutions, articles of association, charter, and other basic documents. Notarized and apostilled documents, along with attested translations into Belarusian or Russian, are required when the creator is a foreign entity. Although an LLC’s minimum authorized capital is small, most ODCs commit a larger amount to show local stakeholders how serious they are. Two to three weeks is realistic here, and most of that time is just waiting on translation and apostille turnaround back home.<\/p>\n\n\n\n

Step 4: Register the entity.<\/strong> Filing happens with the local registration authority in the city where your office will be \u2014 Minsk, usually. Registration itself takes a few business days. After that, you\u2019ve got tax registration, statistical reporting, and a bank account to open. The bank account is almost always the slowest piece, since foreign-owned entities go through extra compliance review under National Bank of Belarus<\/a> rules. Plan three to four weeks total, from filing to a functioning bank account.<\/p>\n\n\n\n

Step 5: Apply for HTP residency.<\/strong> Submit the business plan and supporting documents to the HTP administration. The supervisory board reviews applications on a regular schedule. Approval generally runs four to six weeks \u2014 sometimes faster if your application is clean and the activity scope lines up neatly with the approved list. A weak business plan or a fuzzy activity scope is the most common reason for delay.<\/p>\n\n\n\n

Step 6: Set up HR and payroll infrastructure.<\/strong> This is where companies routinely underestimate the work. You need employment contracts that comply with Belarusian labor law, a payroll system that handles both local taxation and HTP-specific deductions, and a clean onboarding process for new engineers. Most foreign ODCs outsource payroll to a local provider in year one and only bring it in-house once they\u2019ve reached scale. Our outstaffing<\/a> and HR support services exist precisely for this part of the journey.<\/p>\n\n\n\n

Step 7: Hire the first team.<\/strong> Country lead first \u2014 ideally before any of the engineers. Sourcing those first hires through a local recruitment partner shortens this stage considerably, because you skip the steep learning curve of figuring out where Belarusian engineers actually look for work. Our IT recruitment service<\/a> runs this end-to-end. From kickoff to the first engineer\u2019s start date, plan on eight to twelve weeks.<\/p>\n\n\n\n

Step 8: Operationalize the office.<\/strong> Purchasing equipment, security, IT infrastructure, and deciding whether to operate a real office or go remote initially. Both the Belarusian labor code and the HTP framework explicitly support remote work, and most modern ODCs are now hybrid or remote by default. If you do want physical space, Minsk has well-developed coworking and serviced office options at sane rates.<\/p>\n\n\n\n

Realistic timeline from decision to a fully operational ODC: four to six months.<\/strong> We\u2019ve seen faster setups when every piece falls into place, and longer ones when the legal structure is unusual or the HTP application needs revision.<\/p>\n\n\n\n

What it actually costs<\/strong><\/h2>\n\n\n\n

Real cost ranges. Not estimates pulled from a brochure. These reflect what our clients have actually paid to set up Belarus ODCs in 2025 and 2026.<\/p>\n\n\n\n

Cost item<\/strong><\/td>Amount<\/strong><\/td>Notes<\/strong><\/td><\/tr>
Legal registration<\/strong><\/td>$3,000\u2013$8,000<\/td>Includes translation, apostille<\/td><\/tr>
HTP application support<\/strong><\/td>$5,000\u2013$15,000<\/td>Higher end with business plan help<\/td><\/tr>
Banking & infrastructure setup<\/strong><\/td>$2,000\u2013$5,000<\/td>One-time<\/td><\/tr>
Local advisory & accounting setup<\/strong><\/td>$5,000\u2013$10,000<\/td>First-year retainer<\/td><\/tr>
Annual HTP contribution<\/strong><\/td>1% of gross revenue<\/td>Paid quarterly<\/td><\/tr>
Ongoing accounting & payroll<\/strong><\/td>$1,500\u2013$3,000\/month<\/td>Scales with headcount<\/td><\/tr>
Office space (optional)<\/strong><\/td>$15\u2013$25\/sqm\/month<\/td>Minsk prime locations<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

Compliance and audit overhead in year two, currency conversion friction (usually 0.5 to 1 percent on each transfer), and travel for headquarters leadership to visit on a quarterly basis are a few hidden expenditures that don’t appear in first quotations but consistently appear in actual budgets. None of these are deal-breakers. But added together, they tend to run $30K to $50K a year that companies routinely forget to plan for.<\/p>\n\n\n\n

For broader benchmarking on Belarus\u2019s IT sector economics, the Belarusian state statistics service<\/a> publishes sector data that\u2019s useful for sanity-checking your assumptions.<\/p>\n\n\n\n

When an ODC is right \u2014 and when something else is better<\/strong><\/h2>\n\n\n\n

In many of our initial calls, we advise the customer not to pursue a complete ODC, at least not for the first 12 months. Here\u2019s the framing we use.<\/p>\n\n\n\n

Direct B2B contracts or an EOR arrangement outperformed an ODC on all metrics for one to five engineers working on project-based work. Setup is faster, cost is lower, and you can scale down without legal baggage. For five to fifteen engineers where you\u2019d rather not manage a foreign entity, a PEO arrangement<\/a> is usually the smart play. The PEO carries employment, payroll, and compliance while you run the engineering work.<\/p>\n\n\n\n

ODCs come into their own when you\u2019re hiring 10+ engineers, planning to operate for at least three years, and want full ownership over hiring, IP, and culture. Around that headcount, the economics flip \u2014 the per-engineer overhead of contractor or EOR setups starts to exceed the fixed cost of running your own entity.<\/p>\n\n\n\n

The cleanest route is really phased for many businesses. To test the team and the market, start with EOR or PEO. Once the long-term commitment seems genuine, move into a full ODC. We’ve guided a number of clients through this identical process, and it usually yields greater results than setting up the ODC right away.<\/p>\n\n\n\n

Five mistakes we see on repeat<\/strong><\/h2>\n\n\n\n

After enough setups, the same handful of mistakes show up again and again.<\/p>\n\n\n\n

Skipping HTP residency because the application looks complicated.<\/strong> The tax savings on a three-year horizon usually clear six figures, even for small ODCs. And the application really isn\u2019t that hard with a competent local advisor walking you through it.<\/p>\n\n\n\n

Hiring engineers before the entity is fully operational.<\/strong> We\u2019ve watched clients try to compress timelines by running recruitment in parallel with incorporation. It almost always backfires \u2014 engineers want to sign contracts before the company can legally issue them, and you end up in an awkward holding pattern.<\/p>\n\n\n\n

Considering the ODC as a remote office instead of a real subsidiary.<\/strong> Belarus has its own labor law, its own tax framework, and its own compliance culture. Using HQ policies to manage a Belarusian company is a surefire way to cause conflict with both employees and authorities.<\/p>\n\n\n\n

Underinvesting in the lead role.<\/strong> Everything that comes after is shaped by the first senior hire, including hiring practices, operational pace, and culture. Here, going cheap is without a doubt the most costly error we observe.<\/p>\n\n\n\n

Not making plans for the geographic dispersion after 2022.<\/strong> Nowadays, a sizable portion of Belarusian engineers are employed in Poland, Lithuania, Georgia, or other countries. Payroll and contracts must manage that complexity from the outset. If not, retrofitting the structure after the fact will take months.<\/p>\n\n\n\n

When to bring in a local partner<\/strong><\/h2>\n\n\n\n

The honest answer: for the parts where mistakes cost the most.<\/p>\n\n\n\n

You can handle the legal incorporation with any reputable Minsk law firm, and plenty of companies do. The harder piece to manage internally is the combination of HTP application, local HR infrastructure, and the first wave of hiring \u2014 three workstreams that all need to happen in parallel and all depend on a working knowledge of the local market.<\/p>\n\n\n\n

Specialized partners like us deal with that combination on a regular basis. We\u2019ve supported ODC setups<\/a> for dozens of clients, and we typically run the HR, payroll, and recruitment layers while a local law firm handles incorporation. If you want to talk through whether an ODC is the right move for your situation, reach out<\/a> and we\u2019ll give you a straight read.<\/p>\n\n\n

\r\n
\r\n

FAQ<\/h2>\r\n
\r\n\t\t\t
\r\n
How long does it really take to set up an ODC in Belarus?<\/div>\r\n
\r\n

Assuming a typical LLC and HTP residence, allow four to six months from the choice to an operational company. The first two months are consumed by administrative filings and legal incorporation. The following two are the first engineering hiring and your country’s lead search. Operational setup makes up the remaining portion. We’ve seen clients attempt to complete the project in less than three months, and the consequences typically manifest later as a weaker beginning team or unresolved compliance issues.<\/p>\n<\/div>\r\n <\/div>\r\n <\/div>\r\n\t\t\t

\r\n
Can a 100% foreign-owned company register under HTP?<\/div>\r\n
\r\n

Yes. Belarusian law makes this quite clear: HTP residents are permitted to have 100% foreign ownership, and foreign tech corporations frequently own subsidiaries in the park. Your activity scope, which must fall within the authorized list, is the sole significant restriction. Ownership itself isn’t where things get tricky.<\/p>\n<\/div>\r\n <\/div>\r\n <\/div>\r\n\t\t\t

\r\n
What’s the minimum team size that justifies an ODC versus alternatives?<\/div>\r\n
\r\n

About ten engineers, the horizon is from three years, with management ownership being given top attention. Anything smaller, and an EOR<\/a> or PEO setup<\/a> tends to deliver better economics. Past 15 engineers, we almost never end up recommending anything other than an ODC.<\/p>\n<\/div>\r\n <\/div>\r\n <\/div>\r\n\t\t\t

\r\n
How are employees taxed under HTP residency?<\/div>\r\n
\r\n

Employees at HTP-resident businesses pay a lower personal income tax rate than the typical Belarusian rate, increasing net compensation and making your offers more competitive in the local market. Check the current numbers at park.by<\/a> or with a local tax advisor before committing to compensation bands.<\/p>\n<\/div>\r\n <\/div>\r\n <\/div>\r\n\t\t\t

\r\n
Can engineers based outside Belarus work for the ODC?<\/div>\r\n
\r\n

Yes, and it\u2019s increasingly the norm. A Belarus-registered entity can contract with engineers based in Poland, Lithuania, Georgia, Cyprus, Serbia, and other jurisdictions through local B2B contracts. The compliance setup is more involved than employing only Belarus-resident engineers, but it\u2019s manageable \u2014 and it opens up a much wider talent pool.<\/p>\n<\/div>\r\n <\/div>\r\n <\/div>\r\n\t\t\t

\r\n
What happens to the ODC if our country lead relocates?<\/div>\r\n
\r\n

The entity keeps operating. Belarusian corporate law doesn\u2019t require any particular officer to be physically present in the country, though you\u2019ll obviously want operational continuity through whoever takes over the day-to-day. We\u2019ve helped clients navigate exactly that scenario more than once.<\/p>\n<\/div>\r\n <\/div>\r\n <\/div>\r\n\t\t\t <\/div>\r\n <\/div>\r\n