European primes can evolve into kill web ecosystem orchestrators but only if they move faster than their current political, financial, and organizational wiring allows, and Ukraine’s war laboratory window will not stay open indefinitely.
The strategic question is deceptively simple: Can Europe’s defense primes make the transition from platform manufacturers to kill web ecosystem orchestrators?
The answer depends not on money—the money is arriving in quantities unprecedented since the Cold War but on whether entrenched industrial and political cultures can move faster than the war laboratory in Ukraine is running out of time.
Russia’s full-scale invasion has triggered the sharpest jump in European defense spending in decades. Equipment spending alone is projected to rise by hundreds of billions of euros over the next five to ten years. But this is not simply a larger version of the old demand. It is qualitatively different—driven by what Ukraine’s battlefield has demonstrated about distributed, software-driven combat at operational scale.
What Ukraine has shown, month after month since February 2022, is that the center of gravity in modern warfare has shifted. Power no longer flows primarily from the single exquisite platform—the premium fighter, the flagship warship, the armored breakthrough force. It flows from the network: sensors, shooters, and decision-aids connected across domains, where drones, counter-drone systems, electronic warfare, and battlefield software are iterated in months rather than years.
The distinction between the kill chain and the kill web is not merely conceptual. The kill chain describes a linear, sequential process—sensor to shooter—optimized around a single platform or system. The kill web describes something fundamentally different: a distributed, resilient, data-rich network in which “good enough” assets, continuously upgraded through software and payload evolution, generate combat power that no single exquisite platform can replicate or defeat. Ukraine’s long-range drone strikes into Russian airbases, the continuous adaptation of FPV tactics, loitering munitions employment, and mobile electronic warfare packages are not anomalies. They are early operational expressions of kill web logic working in practice against a peer adversary.
European primes, built to deliver the exquisite platform, are now being asked to underwrite the kill web.
The gap between those two missions is the central industrial challenge of this decade.
Ukraine has turned necessity into something close to an innovation machine. Its defense industrial base now functions as a live testbed for drones, autonomy systems, electronic warfare, and battlefield management tools under the most demanding conditions any weapons system will ever face. What distinguishes Ukraine’s innovation cycle from anything in peacetime Western procurement is the feedback loop: combat validation in weeks, iteration in days, field deployment within months.
Several dimensions of this matter directly for European industrial strategy. Ukraine’s defense technology ecosystem has demonstrated the capacity to take commercial off-the-shelf components, commercial code, and field improvisation and turn them into combat-validated products on cycles measured in weeks to months. That capability does not disappear when the shooting stops. It gets exported in software, intellectual property, and the veterans who built it.
European and NATO actors have begun institutionalizing this link. The EU Defence Innovation Office in Kyiv, emerging joint ventures, and co-production schemes are designed to pair Ukrainian innovators with European capital and industrial capacity. New EU instruments, particularly the European Defence Industry Programme—explicitly include integration of Ukraine’s industry into the EU defense industrial base, with funding earmarked for counter-drone systems, missiles, ammunition, and joint industrial projects involving Ukrainian firms.
The implication is strategic, not just commercial. Ukraine is not only a war laboratory but a prospective source of kill web building blocks—autonomous software architectures, drone designs, electronic warfare solutions—that European primes could orchestrate across the continent. But only if they choose to treat Ukraine as a core partner rather than an exotic adjunct to legacy programs.
European primes were engineered for a different era. Long acquisition cycles. Platform-centric programs negotiated with national ministries, with industrial policy and employment as design variables alongside operational capability. Their comparative advantage has been managing complex hardware programs under tight certification and security constraints. It has not been orchestrating open, fast-moving software- and data-centric ecosystems of the kind that kill web logic requires.
The structural obstacles are not minor. Listed primes remain answerable to shareholders conditioned to steady, predictable margins, not to high-risk bets on new ecosystem architectures and Ukrainian or startup partners. European markets are still carved up by national preferences, protection of industrial champions, and divergent requirements, which encourages replication of platforms rather than cross-border kill web architectures. Export controls, certification processes, and environmental and labor regulations make rapid capacity expansion and product cycling genuinely difficult, especially in munitions and energetics. And the cultural center of gravity inside most primes still runs toward the airframe, the hull, the vehicle—not toward the software stack and data architecture that define kill web performance.
The industrial operating system is still version 1.0 of the platform age. The kill web age demands version 2.0, in which primes become system-of-systems integrators, curators of open standards, and portfolio managers of many smaller contributors whose combat-validated products plug into a common architecture.
Despite the structural drag, the outline of an orchestrator role is becoming visible. The fragmented sub-prime segments, sensors, electronics, specialist services, represent exactly the consolidation opportunity where private capital and primes can drive standardization and align many small suppliers with common architectures. Combat-proven defense-tech startups, often founded by veterans with direct Ukraine experience, are increasingly finding their way into prime supply chains. The case of Occam’s AI autonomy software, tested through Ukraine’s Brave1 platform and now partnering with European primes—illustrates the pathway that is forming.
EU instruments are creating the financial architecture. EDIP and related mechanisms are earmarked for joint industrial projects, joint procurement, and innovation initiatives that bring together primes, European startups, and Ukrainian companies in shared programs. The political language around €800 billion in projected annual NATO defense spending by 2030 increasingly includes concepts like fostering innovation ecosystems alongside traditional platform procurement.
These developments are embryonic.
But they are directionally consistent with an orchestrator model in which primes control standards, interfaces, and certification while drawing Ukrainian and European innovators into a common kill web architecture rather than managing them as peripheral subcontractors.
The kill web transition is not just a strategic question. It is a race against three clocks running simultaneously.
- The battlefield clock is the most urgent. Every month, Ukrainian firms run real experiments under fire, iterating drone packages, electronic warfare configurations, and AI-enabled command tools against a peer adversary that is adapting in real time. These capabilities can be exported in software, intellectual property, and trained personnel even if physical production eventually relocates. The window during which Ukraine’s war laboratory is generating maximum innovation value will not stay open indefinitely.
- The budget clock defines the stakes. By 2030, Europe’s NATO members are projected to spend roughly €800 billion annually on defense, up approximately €300 billion from the mid-2020s baseline. A large share flows into equipment and associated services. Contracts signed in the next five to seven years will lock in architectures and supply chains for a generation. If those contracts flow into familiar platform structures with only marginal kill web adaptation, the opportunity cost is measured in decades.
- The political clock is the most unpredictable. Windows for deep EU-level integration, ambitious industrial policy, and risk-tolerant procurement open and close with political cycles in key capitals and in Brussels. The current alignment of political will and financial resources is unusual. It will not persist indefinitely regardless of what Russia does.
- The transition from platform manufacturer to kill web ecosystem orchestrator requires changes in at least four dimensions, none of them cosmetic.
The first is architectural leadership. A prime functioning as a kill web orchestrator owns and publishes open interface standards and data models across domains, air, land, maritime, cyber, space, enabling many third-party sensors, shooters, and software modules to plug into a common architecture. Internal engineering priorities shift from optimizing a single asset’s performance in isolation to managing system-of-systems resilience and reconfigurability.
The second is portfolio-style integration of diverse suppliers. This means building structured pipelines to scout, test, and integrate startups and Ukrainian firms whose products carry battlefield validation but need scaling, certification, and integration into larger architectures. It means using balance sheet capacity and political capital to drive consolidation in fragmented segments while leaving room for competitive innovation at the edges.
The third is software and data at the core. Combat power in the kill web age flows from autonomy stacks, mission management software, and battle management AI, supported by modular hardware, not the reverse. That requires developing internal capabilities for continuous integration and deployment of military software, with combat telemetry and Ukrainian lessons feeding regular updates rather than waiting for scheduled capability blocks.
The fourth is a new relationship with the state and with EU institutions. This means working with procurement authorities to design acquisition that buys architectures and services over time—not one-off platforms—and using programs like EDIP to co-invest with governments and Ukrainian partners in shared facilities, test ranges, and digital infrastructure that underpin a continental kill web.
In this model, a prime’s value lies less in owning every building block and more in curating and evolving the ecosystem that connects them.
Failure to move decisively carries three specific risks.
- Ukrainian innovation is already being courted by U.S. primes, global venture capital, and non-European defense actors who can offer capital, global market access, and integration into established architectures. If European primes do not move first, they will not move at all—the integration will happen elsewhere, and the architectural standards that result will not be European.
- The second risk is locking in sub-optimal architectures. The next decade of procurement could cement platform-centric, nationally fragmented systems that are far harder to retrofit into kill web architectures later, compounding dependence on external integrators for the software and data layer that actually determines combat performance.
- The third risk is the erosion of industrial sovereignty. Europe’s stated ambition of strategic autonomy depends on owning not just metal-bending capacity but also the software, data, and integration layer that defines kill web performance. Ceding the orchestrator role to others would hollow out that ambition regardless of how many platforms European factories produce.
European primes can become kill web ecosystem orchestrators.
But doing so fast enough requires a deliberate break with business-as-usual, supported by political decisions that reward architectural thinking and risk-taking over the comfort of incremental platform upgrades.
The necessary elements are visible: Ukraine’s war laboratory, EU-level funding and integration tools, a cohort of combat-hardened defense technology startups, and an emerging analytical consensus that the old model is insufficient.
The question is whether European primes will accept near-term disruption, reshaping portfolios, opening architectures, partnering deeply with Ukrainian and European innovators—in order to own the orchestration layer. Or whether they will cling to legacy platform models while others capture the kill web.
The stakes are not ambiguous.
This is a race not only against Russia but against competing industrial ecosystems that have already recognized what Ukraine’s war laboratory is worth.