Executive Summary: Ukraine’s decentralized, volunteer-driven surge in drones, software, and ad-hoc procurement was indispensable in 2022–23, but it is not a scalable blueprint for great-power competition. Russia and China are converging on fewer, standardized platforms, hardening them against electronic warfare (EW), and scaling production with industrial discipline. The West should adopt a hybrid model: centralized architecture and standards with distributed execution—prioritizing EW resilience, assured navigation (including fiber-optic links and onboard autonomy), interoperable C2/data layers, and predictable production. Policymakers must shift from “many prototypes” to “few families at scale,” with open interfaces that let startups plug in while primes deliver volume, certification, and sustainment.

• Speed and improvisation: A burst of small firms and volunteer networks rapidly fielded FPV and ISR drones, software, and battlefield apps when formal procurement stalled.
• Test-bed value: Government initiatives like Brave1 created a front-line proving ground for foreign and domestic tech, accelerating learning cycles and exposing design flaws early.
• Signals to allies: The model showed how “mass through software” can create effects disproportionate to cost, catalyzing allied programs like Replicator and service-level attritable UAS initiatives.

1) Electronic warfare exposes fragility. Russia’s dense EW has degraded GPS, links, and guided munitions, forcing Ukraine to burn sorties for marginal effects and to sequence strikes around EW nodes. Emerging counters—fiber-optic-tethered drones and onboard autonomy—work, but require deeper engineering and systems integration than most “assembly” teams can deliver.

2) A “zoo” of platforms drives cost and interoperability penalties. Thousands of variants optimized for micro-niches are hard to sustain, secure, and network under fire. Reported FPV hit-rates vary widely; autonomy can lift success substantially but only when fused with reliable sensing and resilient comms.

3) Adversary standardization is out-iterating improvisation. Russia has consolidated around a smaller set of strike drones (e.g., Shahed/Geran lines) and is building high-volume factories and youth pipelines for assembly, trading variety for repeatability and scale. Concurrently, Moscow fields record drone swarms while probing Ukraine’s air defenses for saturation tactics.

4) Supply-chain leverage runs through China. Beijing’s dominance in commercial UAS ecosystems and tightening export controls complicate Western replenishment and the performance parts pipeline.

Industrial discipline: Russia’s state-directed consolidation on fewer air/sea UAS, plus rapid EW upgrades, has produced “slow but steady” battlefield gains despite Ukrainian innovation spurts.
Assured navigation: Wider use of fiber-optic control and jam-resistant profiles (visual navigation, terrain-matching) is visible in Russian concepts and field reports.
Scale via commercial ecosystems: China’s parts, manufacturing know-how, and export levers shape availability and cost curves for both sides, underscoring why allied strategies must reduce single-country dependencies.

Policy: The center of gravity is shifting from “innovation theater” to industrialized, EW-resilient effects. A durable edge requires (1) program-level standardization (open mission systems, common data and control APIs), (2) assured navigation stacks beyond GNSS, and (3) predictable serial production with qualified suppliers.

Operations: Prioritize EW as a supported/ supporting arm—plan fires around enemy EW nodes; pair attritable swarms with deliberate SEAD/DEAD and counter-EW windows; enforce spectrum discipline.

Industrial base: Use primes for certification, safety-critical software, exportability, and global MRO; use OTAs and challenge-based awards to refresh subcomponents (autonomy, seekers, datalinks) on defined cycles; constrain platform families to cut sustainment tail.

Allies: Build NATO/INDOPACOM interoperability by design—common control stations, link profiles, and data schemas; leverage OCCAR/NSPA for common spares and depot strategy.

Policymakers (NSC, OSD, Congress)

• Decide on “few families at scale” for attritable air/sea/ground UxS (≤5 core lines per domain). Mandate Modular Open Systems Approach (MOSA), common UI, and data standards; require portability across vendors via government-owned interfaces.
• Harden the navigation stack with a funded roadmap: fiber-optic tethers, visual/terrain-match autonomy, LPI/LPD waveforms, and PNT diversity in Programs of Record; resource EW as a Title 10 core competency, not niche enablers.
• Shift buying vehicles from dozens of prototypes to enterprise IDIQs/MYPs with optionized lots and built-in tech-refresh slots; use DIU/AFWERX OTAs for module insertions, not entire platforms.
• De-risk China dependencies via targeted authorities (DPA Title III, Ex-Im) for motors, ESCs, RF front-ends, optics, and secure compute; align with allied export controls to avoid re-dependence.

Joint Staff & Combatant Commands

• Operationalize counter-EW sequencing: require kill-chains that open time-windows on EW nodes; pair swarms with decoys and long-range fires; institutionalize “EW+fires” rehearsal sets.
• Normalize assured-nav tactics: field fiber-optic and autonomous modes in training centers; write ROE for autonomous fallback when links/GNSS are denied.
• Reduce control-station diversity: migrate to common GCS and link profiles across services; enforce interface control documents (ICDs) in exercises.
• Use standing contracts to push upgrades quarterly (not annually) for autonomy and EW modules via existing program IDIQs and theater BPAs.

Intelligence Community

• Collection priority: adversary EW order of battle, fiber-optic drone TTPs, and autonomy stacks (sensors, training data, compute footprints); characterize factory throughput and BOM choke-points.
• Battle damage assessment for effects-at-scale: quantify mission kill from saturation raids and EW-suppression cycles (not only physical destruction).
• Declassification strategy: selectively reveal adversary EW dependencies and spoofing patterns to support allied countermeasures and procurement choices.

Defense Contractors (Specificity & Vehicles)

• EW & counter-EW layers: RTX, Northrop Grumman, L3Harris — deliver jammer/sensor suites and LPI/LPD links via program IDIQs and NATO NSPA channels; align with Army I-AMD and Navy NIFC-CA interfaces for cross-service reuse.
• Assured navigation/autonomy: Shield AI, Anduril, Palantir — field GPS-denied autonomy, onboard perception, and mission management via DIU/AFWERX/SOFWERX OTAs feeding into service enterprise agreements; demonstrate hot-swap modules against common ICDs.
• Attritable platform families: Lockheed Martin, Boeing, General Atomics, Textron — propose two-to-three core air UAS families with shared avionics and payload buses; structure MYPs with optioned block-upgrades; certify exportable variants through FMS LOAs and OCCAR workshare for Europe.
• C-UAS and directed energy integration: Kongsberg, MBDA, Saab, Epirus — deliver layered C-UAS (kinetic + HPM/laser) modules through existing BPAs and program IDIQs; ensure MOSA compliance for joint employment.
• Supply-chain reshoring: Honeywell, Collins, Microchip — stand up U.S./allied lines for motors, servos, GNSS-alt sensors, and secure micro-electronics using DPA Title III and GSA ASTRO for rapid services support.

Confidence: Medium-High — Multi-outlet corroboration on EW effects, Russian standardization/scale, and allied procurement shifts; uncertainty remains around classified hit-rate data, true production throughput, and adversary autonomy stacks.