Running an Offshore Development Center in Belarus After Launch: KPIs, Governance, and Retention

Clients who set up an offshore development center with us ask a lot of questions at the start: how to hire, which model to pick, how soon the team can begin. Six months in, the questions change. The team is complete, releases are going out, and someone in finance wants to know whether the center is worth what it costs.

That turns out to be hard to answer. Headcount and hours are easy to report but say little about value. Problems with morale usually stay hidden until a senior engineer resigns, and by that point a couple of colleagues may already be interviewing elsewhere.

Below we cover the period after launch: which numbers to track, how to split decisions between headquarters and Minsk, and how to keep your strongest people, including the parts that work differently in Belarus.

What Changes After Launch

While the center is being set up, nearly all the effort goes into hiring. Once it’s running, the work shifts to managing the team, and the risks shift with it. If you’re still at the earlier stage, our page on offshore development centers in Belarus describes the available models, including dedicated teams and build-operate-transfer.

Some patterns come up again and again in centers we support:

• The Minsk team gets a steady stream of tickets but never owns a piece of the product. Senior engineers find this dull and start looking around.
• Managers at headquarters and the local lead both give instructions, and engineers aren’t sure whose priorities come first.
• Engagement slips gradually. Nobody runs a survey or holds regular one-to-ones, so the first sign of trouble is a resignation letter.

None of these needs a big programme to fix, but the routines that prevent them are much easier to start in the first few months than after people have already left.

KPIs Worth Tracking

Keep the scorecard short. In our experience, five to eight numbers that leadership actually looks at each month do more good than a large dashboard. We usually group them into delivery, team health and cost.

Delivery

Most engineering teams start with the DORA metrics, which look at how fast changes get to production and how often they cause problems once they’re there. The DORA guide to software delivery metrics lists five: change lead time, deployment frequency, failed deployment recovery time, change fail rate and deployment rework rate.

For an offshore team, we’d add sprint predictability, meaning the share of planned work that actually ships, and the number of defects found by customers. We’d leave out lines of code, hours logged and story points per person. Once people know they’re being counted, these numbers stop meaning much.

Team Health

To judge whether the team will hold together, look at voluntary attrition over a rolling 12 months and split it into leavers you wanted to keep and those you didn’t. Time to fill open roles and the offer acceptance rate are useful too, because both get worse when your salaries fall behind the market.

A quarterly pulse survey of three to five questions is usually enough to catch problems early. The SPACE framework for developer productivity argues that satisfaction and well-being should sit alongside output measures, since they tend to show where output will go next.

Cost and Ownership

For cost, calculate the fully loaded cost per engineer: payroll, taxes, equipment, provider fees and the management time spent on the team. Compare it with what the same role costs at headquarters. Our 2026 benchmarks for Belarus IT salaries can help you check whether your pay levels are in line with the market.

It’s also worth tracking how much of the roadmap the ODC delivers on its own, from design to release, compared with tasks passed over from headquarters. In centers that are doing well, this share goes up year after year. When it stays the same, the team is usually being treated as extra capacity rather than as part of the product organisation.

A Sample Scorecard

Area	KPI	What good looks like	Review
Delivery	Change lead time	Measured in days, not weeks, and improving	Monthly
Delivery	Change fail rate	Stable or falling	Monthly
Team	Regretted attrition (12 months)	Low and stable, set against your own baseline	Quarterly
Team	Pulse survey score	No sharp drops quarter to quarter	Quarterly
Cost	Cost per engineer vs. HQ	Within the target ratio agreed at launch	Quarterly
Ownership	Roadmap items owned by the ODC	Growing over time	Twice a year

Use the first 90 days to collect a baseline. Targets set before you have your own numbers tend to be either too easy or impossible.

Governance: Who Decides What

Decision Rights

Time zones get blamed for a lot, but in the centers we work with, slow decisions usually come down to nobody knowing who has the final word. If engineers can’t tell who approves a hire or a salary increase, they escalate everything to headquarters and wait.

A RACI table fixes most of this. For every type of decision it shows who does the work, who signs off, who should be consulted and who just needs to know. Atlassian’s guide to RACI charts has a ready template. Cover at least hiring, salary reviews, promotions, architecture decisions, release approval, performance problems and exits.

Belarus adds one more step. When the team is employed through an EOR or a partner, formal decisions such as pay changes, disciplinary measures and dismissals have to be made by the legal employer under Belarusian procedures. Put the employer into the RACI as a separate party, so managers at headquarters know where their authority ends.

Operating Rhythm

Most of the governance happens in a handful of regular meetings. This schedule works well for the teams we support:

• Weekly: a delivery sync between the local lead and product owners, mainly about blockers.
• Monthly: a review of the KPIs, plus an update on hiring and attrition.
• Quarterly: a business review with headquarters leadership, the local lead and your provider, covering the roadmap, budget and salary market.
• Annually: a compensation review, a look at the team structure and a decision on whether the current model still makes sense.

Try not to let these slip. When a review keeps getting moved, the issues end up discussed in private chats where nothing gets decided.

The Local Lead

After launch, the hire that matters most is usually a strong engineering manager or site lead in Minsk. This person answers day-to-day questions, picks up on frustration before it turns into a resignation and speaks for the team at headquarters. Without a local lead, decisions wait for someone in another time zone to reply, and engineers start to feel like an external vendor.

Security and Access

Access reviews and offboarding should run on a schedule, not only after something goes wrong. Plenty of companies use the controls in ISO/IEC 27001 as a reference without going for certification. At a minimum, review access every quarter and make sure that on each employee’s last day their accounts are closed and equipment is returned.

Check, too, that the service agreement assigns the intellectual property the team creates to your company. Fixing it later, during a funding round or an acquisition, is far more awkward.

Retention: Keeping Your Best People

Why People Leave

When engineers leave an ODC in Minsk, the usual reasons are a higher offer from another foreign company, a chance to relocate, no clear path to promotion, or a feeling that the Minsk office counts for less than headquarters. In exit interviews, the last two come up more often than clients expect.

Turnover is costly. Gallup estimates that replacing an employee costs between half and twice their annual salary. For a senior engineer who knows your codebase, expect the higher end.

Compensation Reviews

Salaries in the Belarus IT market change fast enough that one review a year often leaves people underpaid for months. A lot of our clients do a full review annually and a quick market check halfway through the year to catch anyone who has fallen behind. Published salary bands also help engineers see what the next level pays.

Retention Tools Under Belarusian Law

Not every retention tool used in the US or the EU works the same way here. Deferred bonuses, training agreements with repayment terms and sign-on bonuses that have to be returned if someone leaves early can all be used in Belarus, as long as they’re written into the contract and local acts correctly. Our article on retention tools that hold up in Belarus sets out what each one requires.

Many Belarusian employers also use fixed-term contracts which have their own rules on renewal and early termination. Talk to your provider about whether they suit your team, as they affect how easily both sides can end the relationship.

Non-competes are a different matter. Most employers in Belarus can’t use them, while Hi-Tech Park residents can, on condition that they pay compensation. If this is important for your roles, see our guide to what foreign employers can enforce beyond an NDA.

Career Paths and Ownership

Pay keeps people from leaving for a better offer, but it rarely makes them want to stay for years. What tends to work is giving the Minsk team responsibility for something specific, such as a product area, a service or a group of customers. Promote team leads from within the local team instead of filling every management role at headquarters, and arrange visits in both directions now and then so engineers know who they’re working with. None of this is expensive, and engineers notice it.

Your First Year: Three Checkpoints

By day 90, you should have baseline KPIs, an agreed RACI table, a local lead in place and the results of the first pulse survey.

By month six, hold the first quarterly business review, check salaries against the market, review access rights, and look at who has left so far and why.

By month 12, run the annual compensation review, see how much of the roadmap the team now owns, and decide whether to grow the center, keep it as it is or take it over through build-operate-transfer.

When to Rethink the Model

When delivery is steady, attrition is low and the local lead is reliable, many companies start thinking about growing the center or bringing it in-house, either by taking the team over from the partner or by opening a local entity. Our article on when to scale through EOR and when to switch to an entity compares the two routes.

How EOR.by Helps

Our work doesn’t stop once the team is hired. We keep running payroll and HR administration and share salary benchmarks, so compensation decisions are based on current numbers. Through our HR consulting services, we help clients put together bonus regulations, retention schemes and local acts that comply with Belarusian law.

If you decide to take the team over, we handle the transfer as well, from new employment contracts to passing on HR records.

FAQ

What KPIs should I track for an offshore development center?

Five to eight numbers across delivery, team health and cost are usually enough. A common set is change lead time, change fail rate, regretted attrition, a pulse survey score, cost per engineer compared with headquarters, and the share of the roadmap the ODC owns.

How do I measure ODC performance without micromanaging?

Look at results for the team as a whole rather than activity per person. Delivery speed, quality and ownership say far more than hours logged or individual story points, and they’re much harder to game.

What attrition rate is normal for an ODC in Belarus?

That depends on the market, the seniority mix and how your pay compares. Instead of chasing an industry figure, set your own baseline in the first year and watch for sudden jumps, especially among senior engineers.

Who makes HR decisions in an ODC run through an EOR?

You and your local lead handle day-to-day management. Formal decisions such as pay changes, discipline and dismissal are made by the EOR as the legal employer. Our article on which company policies apply to EOR employees explains how this works.

Can I use non-competes to keep ODC engineers?

Only if the employer is a Hi-Tech Park resident, and even then compensation must be paid. For most teams, deferred bonuses, training agreements and clear career paths are more practical.

When should I move from a partner-run ODC to my own entity?

Usually when the team is stable, the local lead is strong and you expect to keep growing in Belarus for several years. Compare the cost and administrative work of each option before you decide.

Final Thoughts

Whether an ODC pays off is decided mostly in the year after launch. A short list of metrics that people trust, clear rules on who decides what and regular attention to the team’s concerns go a long way.

If your Belarus ODC has been running for a few months, get in touch with our team. We’ll look at your KPIs, governance and retention risks with you and suggest what to tackle first.