Technologies we work with

What working on the Microsoft stack actually means

"We are a Microsoft partner" says very little on its own — there are many partner designations and they mean different things at different firms. Three things matter in practice.

The first row is worth checking with any partner. When the same firm sells licences and implements, it acquires an interest in a larger user count than you need. Separating the two removes the conflict.

Why Microsoft only

We are deliberately not a general-purpose integrator. To know a system beyond the average level you have to work in it daily for years, and a firm implementing five different ERPs knows each of them less well.

The downside of that choice is worth stating too. If analysis shows a different system fits you better, we will say so — but we will not implement it. Losing the project is more honest than taking on work we do not do well. Selection criteria are in how to choose an implementation partner.

Local statutory requirements

A question worth asking every vendor, and the answer is the same for any international ERP: country-specific statutory accounting is not in the base product. VAT treatment, tax invoices, registries, payroll — all of it comes from a partner localisation.

So the useful questions are not whether a localisation exists but who develops it, how many years it has been in the market, how quickly it is updated after legislative change, and what happens to it if you change partner. For a Ukrainian entity specifically, this is covered in your Ukrainian subsidiary runs 1C.

What happens if you change partner

An uncomfortable question, and one worth asking before signing rather than when it becomes relevant.

We work so the project can be handed over: the Business Central core stays standard, customisations are built as extensions, configuration is documented. Another partner picks that up faster because the core is identical everywhere.

The opposite approach — a heavily reworked solution understood only by the team that wrote it — benefits the partner and not you. When customisation is genuinely justified is set out in when AL customisation pays off.

Working with us from abroad

We are based in Kyiv and work in English and Ukrainian. For international groups the usual arrangement is a clear split: your existing partner keeps the group template and consolidation, we take the local entity and its statutory layer, and the boundary is agreed in the contract rather than discovered in month four.

How that split works in practice, including continuity questions worth asking any nearshore supplier, is covered in working with a nearshore partner.