How to Acquire a Ukrainian Defense Company

Ukrainian defense companies are usually described to acquirers in the language of the product: a drone, an interceptor, an electronic-warfare suite. That description undersells and misprices the target, because the product is the most replaceable part of what you are buying.

The practical consequence: two targets with the same revenue can be worth very different multiples depending on whether the permission stack and the engineering team come with the deal intact. The wider market picture behind these deals — capacity, funding volumes and who is already active — is set out in Ukrainian defense-tech investment, by the numbers.

In most jurisdictions this is a tax and liability question. In Ukrainian defense it is first a regulatory question, because the licences and statuses are attributes of the legal entity.

A third route sits between the two: a joint venture or contract-manufacturing arrangement that buys output and optionality without buying the company. Where that fits better than an acquisition is compared in JV or contract manufacturing, and the full set of entry routes is in the six ways into Ukraine’s defense market.

There is no single defence-M&A regulator in Ukraine. Instead, several separate gates apply depending on the parties and the target, and they run on different clocks.

Alongside competition clearance, four other gates decide whether a deal is doable at all.

• Sanctions and ownership screening. Ukrainian sanctions law, plus your own home regime, applied to the whole chain: shareholders, ultimate beneficial owners, and parties related by control. For a Defence City target the same screen is a statutory condition of its status.
• Export-control consent on technology.Under the 2026 procedure the interagency commission on military-technical cooperation and export control reviews applications for permission to alienate exclusive intellectual property rights or to sell technologies, and applications to export to third states goods manufactured with technology transferred that way. Any deal whose logic is “buy it and produce it at home” runs through this gate.
• State-secret access.Where the target handles classified information, the special permit and the regime unit around it are entity-bound and personnel-bound; a change of control engages the security service’s process rather than a corporate filing.
• Contractual consents. State defence contracts, grant agreements and partner licences frequently carry change-of-control provisions. These are found in diligence, not in a statute, and they are the most common cause of a delayed closing.

Financial and legal diligence in this sector sits on top of three checks that a generalist data room will not answer.

1. 1Does the permission stack actually exist, and in whose name. Registration, product identification, attested internal control system where relevant, permits in force and the reports on their use. How that permitting layer operates, and what the 2026 mechanism changed about it, is set out in the export mechanism explainer.
2. 2Does the company own its technology. Assignment from founders and engineers, contractor chains, open-source and third-party components, and any grant conditions that constrain transfer. Where IP is held personally or in a service company, the deal has a repair job before it has a price.
3. 3Is the evidence about the product what it is claimed to be. Field use, failure data, laboratory qualification, and the gap between them. What each type of evidence establishes is separated in what battlefield testing actually proves.

The process side of diligence — access waves, zones, red flags — is the same discipline an investor runs before a round, and the document set it resolves to is laid out in the diligence checklist.

Two features of the Ukrainian market distort the multiples an acquirer is used to reading.

The valuation mechanics themselves — which method survives contact with a defense-tech P&L, and what a buyer is really paying for — are worked through in how to value a defense-tech company, and the return profile on the other side of the table in what returns to expect.

Closing a defense acquisition is the point at which the acquired permissions start being tested against a new owner.

• Keep the registration alive and current. A registration is tied to identified goods and declared destination states. A new product line or a new export direction takes the entity back through pre-expertise, and that is a planning item rather than a formality.
• Watch the residency conditions. If the target is a Defence City resident, the annual compliance report with audited statements is due by 1 June, the qualified-income ratio has to hold through the year, and the ownership disqualifiers now include your chain. Losing status reaches back to the period the breach began.
• Retain the people who are the asset. Engineering retention, IP assignment and vesting are the substance of what you bought; the permission stack can be rebuilt in months, a team that iterates under fire cannot.
• Decide the technology-transfer question early. If the plan is to manufacture the product outside Ukraine, that is an export-control application about technology, with its own reviewing body and its own timetable, and it belongs in the integration plan rather than in a later phase.

1. 1Define the capability you are buying — production, technology, market access or team — because it decides which targets are relevant and which structure preserves the value.
2. 2Screen for hard stops first. Sanctions and ownership chain, occupied-territory exposure, state-secret handling, and grant or contract restrictions on transfer.
3. 3Test the permission stack before the financials.A clean P&L behind a broken export position is a smaller business than it looks.
4. 4Choose share or asset with the licences in view, and price the liability that comes with the choice into warranties and a holdback.
5. 5Map the approvals to a calendar. Competition clearance with its suspensory effect, any export-control consent on technology, security clearances and contractual consents run in parallel, not in sequence.
6. 6Write the integration plan into the deal. Retention, compliance reporting, registration maintenance and the technology-transfer application, each with an owner from day one.

Sellers read this sequence from the other end: the same permission stack that sets your price is what a Ukrainian founder is told to build before a sale process starts, which is the subject of how to exit a Ukrainian defense-tech investment.