Europe.

A market that buys to a written standard

European defense procurement is the most proceduralised environment we operate in. The award routes are set in law, the timelines are published, and an unsuccessful bidder has real standing to challenge. That has a consequence foreign suppliers routinely underestimate: the quality of the compliance response matters as much as the quality of the capability, and a technically superior offer that misses a formal requirement gets excluded rather than corrected.

The upside is that the process is knowable. Nothing about a European competition should be a surprise.

Three operational pictures

The eastern flank is a persistent surveillance and indications-and-warning problem along a land frontier, run at a tempo that does not relax, against an adversary with electronic warfare capability that has to be designed around rather than assumed away.

The Mediterranean and the Atlantic approaches are a maritime domain awareness problem with a search-and-rescue obligation attached — vessels in distress, irregular crossings, fisheries enforcement and smuggling all in the same water, often in the same track picture.

The interior is a border, infrastructure and event-security problem, where the counter-uncrewed-aircraft mission has moved in a very short time from a specialist concern to a standing requirement at airports, ports, energy sites and any large public gathering.

Interoperability is a requirement, not a preference

A European customer is rarely buying a standalone capability. They are buying something that has to feed an alliance picture and accept tasking from it. Standard message formats, standard imagery metadata, standard dissemination paths — these are specified, tested and enforced.

We design to that from the start because retrofitting it is expensive and because a system that only produces a proprietary output has quietly made its owner dependent on the supplier who built it. That is the opposite of what we sell.

Counter-UAS, specifically

Small uncrewed aircraft over European critical infrastructure have gone from an incident to a pattern. The operational problem is not detection alone. It is detection, tracking, identification and a legally defensible response, in airspace full of legitimate traffic, near people, where most kinetic options and many electronic ones are unavailable.

That makes the integration harder than the sensors. The system has to reach the person authorized to decide, with enough confidence to act and enough record to justify it afterward. We build the chain, sustain it, and train the operators — on our equipment or on equipment the customer already owns.

How programs get bought

National tenders, alliance-level acquisition through NATO’s support agency, and direct commercial sale each apply depending on the customer and the funding line. Most programs of consequence carry industrial participation expectations, which means the teaming arrangement is part of the bid rather than an implementation detail.

For a non-European supplier the realistic routes are a specific technical contribution inside a larger national program, or a niche where domestic industry is not positioned. Attempting to displace a national champion on price is not a strategy.

What we are usually asked for

Sensor and exploitation capability integrated onto airframes already in service. Ground segment and fusion architecture that connects collection to the existing operations room. Counter-UAS detection and defeat at fixed sites, sustained and trained. And the instructors and analysts to make all of it operate at the standard the customer is measured against.