Almost every Ukrainian defence system on the market is described as battle-tested. One company using the phrase has delivered four units to a single reconnaissance team. Another has pushed eleven design revisions through two years of continuous frontline use under jamming. Read both websites and you cannot tell which is which.<\/p>\n\n\n\n
The buyer loses, because they cannot price the risk. The second company loses more, because two years of evidence earns it nothing while the claim costs nothing to make.<\/p>\n\n\n\n
So define the phrase. Six questions, and what a thin answer to each one means.<\/p>\n\n\n\n
Six Questions<\/strong><\/p>\n\n\n\n 1. Who used it, and in what role<\/strong><\/p>\n\n\n\n “Used by Ukrainian forces” covers every level of adoption from a four-unit trial upward. Ask which formation, at what echelon, and whether the system was that unit\u2019s primary tool for the task or one of three being run side by side.<\/p>\n\n\n\n Issue and trial are different things. A system issued as the standard answer to a recurring problem has been chosen over alternatives by people whose lives turn on the choice. A system a unit agreed to test has been chosen by nobody yet.<\/p>\n\n\n\n Suppliers are often bound by their customer\u2019s confidentiality and cannot name the unit. Accept that. Role, echelon and scale of issue are rarely restricted, and a supplier who will not describe those has either not thought about what a buyer needs, or is protecting a number they would rather you did not see.<\/p>\n\n\n\n 2. Over what period, and continuously<\/strong><\/p>\n\n\n\n A two-week evaluation in spring 2025 is not eighteen months of service. Ask for the date of first operational use, whether use has run continuously since, and whether the system is in service today.<\/p>\n\n\n\n You will forget the third one. Ask it anyway. Systems drop out of use and marketing copy does not follow them out, so a supplier still quoting a 2024 deployment may be quoting the last one they had. If the system is out of service, the reason tells you more than the deployment did. The threat may have moved, the unit may have reorganised, a newer variant may have replaced it. It may also have stopped working, and nobody wanted to write that down.<\/p>\n\n\n\n 3. In what electronic warfare environment<\/strong><\/p>\n\n\n\n “Contested” is not a specification. Every square kilometre of the country has been contested by someone since 2022, and the word carries no information about what the system had to survive.<\/p>\n\n\n\n Ask what jamming was present, at what point in the mission the system met it, and what happened when the link dropped. GNSS denial, communications jamming, or both at once. Continuous or intermittent. Did the system degrade, fail safe, or fall out of the sky.<\/p>\n\n\n\n The electromagnetic environment changes by sector and by month. A system that held up on one axis in 2024 is now being sold against threats that did not exist when it was designed, and performance figures quoted without the EW conditions attached give a buyer nothing they can use.<\/p>\n\n\n\n 4. What the loss and failure rate was, and whether anyone recorded it<\/strong><\/p>\n\n\n\n Ask how many units were delivered, how many still work, and how the losses split between combat loss, technical failure, operator error and EW effect.<\/p>\n\n\n\n You will often hear that nobody kept the numbers. With units under pressure and a manufacturer shipping revisions every week, that answer is plausible and usually honest. Treat it as a gap to close rather than a disqualification.<\/p>\n\n\n\n Treat the clean number with more suspicion. A 2.7 per cent failure rate quoted with no collection method behind it is worth less than “we lost about a third, and roughly half of those went to jamming.”<\/p>\n\n\n\n 5. What changed in the design as a result<\/strong><\/p>\n\n\n\n Suppliers are least prepared for this one, and it sorts them faster than the other five.<\/p>\n\n\n\n A system in field use has a revision history written by its users. Antennas move. Firmware gets rewritten after a bad EW encounter. A mount that held in the workshop shears off in a vehicle and gets redesigned. Ask for the last three changes and what forced each one.<\/p>\n\n\n\n A supplier who cannot name a single design change driven by user feedback has not had users, or has not listened to them. Either way you have learned something before signing anything.<\/p>\n\n\n\n The reverse tells you as much. Ukrainian manufacturers iterate faster than anyone else in this market, and a founder who can walk you through eighteen months of changes and the reasoning behind each is showing you something no test range produces.<\/p>\n\n\n\n 6. Who repaired it, how fast, and with what<\/strong><\/p>\n\n\n\n Most battle-tested claims die here, at the point where they have to become a procurement case.<\/p>\n\n\n\n Ask who did the repairs. In Ukraine the answer is often the unit itself, or the manufacturer\u2019s own engineers driving out with a box of parts. That produces excellent turnaround and tells you nothing about sustaining the system fifteen hundred kilometres away, with no relationship to the founder\u2019s mobile number.<\/p>\n\n\n\n Then ask about spares, mean time to repair, and documentation. Not whether documentation could be produced. Whether it exists.<\/p>\n\n\n\n What the Phrase Does Not Mean<\/strong><\/p>\n\n\n\n Combat use is not qualification testing. It answers a harder question than a test range does and answers it better, but it produces none of the environmental, safety and interoperability evidence a NATO customer has to hold on file. A system can be proven in combat and still sit years away from a qualification pack.<\/p>\n\n\n\n Combat use says nothing about production capacity. Building four hundred units in a workshop while revising weekly is a different industrial problem from building four hundred to a fixed configuration, to a schedule, with a warranty and a documented supply chain. Some manufacturers have made that jump. Many sit earlier on the curve than their marketing suggests, and a buyer who knows which can plan around it.<\/p>\n\n\n\n Combat use does not travel between threat environments. Performance against one jamming profile on one axis is evidence about that profile and that axis.<\/p>\n\n\n\n Combat use expires. A record built in 2023 describes a threat picture that has changed twice since. Ask when the evidence was generated, not only whether it exists.<\/p>\n\n\n\n Asking Without Insulting Anyone<\/strong><\/p>\n\n\n\n Founders in this market sometimes hear these questions as scepticism about their war. Say plainly that they are not. A Western procurement organisation is obliged to hold this file, and a buyer who cannot build it cannot proceed however good the system is.<\/p>\n\n\n\n Most founders take that well. The good ones start collecting the evidence from the next unit they issue, rather than reconstructing it under pressure eight months later.<\/p>\n\n\n\n A supplier who answers four of the six well is early, not weak, and the two gaps become a work programme. The answer that should stop a process is the confident one that collapses on the second question.<\/p>\n\n\n\n TriSovereign’s Read<\/strong><\/p>\n\n\n\n The market has a vocabulary problem and it costs both sides money. Buyers discount every claim by the same amount because they cannot sort the strong from the weak, which penalises the manufacturers holding real evidence for their competitors\u2019 vagueness.<\/p>\n\n\n\n More marketing will not fix that. A shared standard of proof will, applied by enough buyers that manufacturers start recording against it from the first unit they issue. Unit, duration, EW conditions, failure data, iteration history, sustainment. Six questions, asked in that order, every time. Manufacturers who can answer them will find procurement conversations get shorter. The rest will at least know what to start writing down tomorrow.<\/p>\n\n\n\n <\/p>\n","protected":false},"excerpt":{"rendered":" Almost every Ukrainian defence system on the market is described as battle-tested. One company using the phrase has delivered four units to a single reconnaissance team. Another has pushed eleven design revisions\u2026<\/p>\n","protected":false},"author":2,"featured_media":62,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[4],"tags":[],"class_list":["post-60","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-defense-tech"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t