The platform wars are over. The platforms won.
Anduril's $20B Lattice contract with the Army and Palantir's $1.3B Maven expansion settled the enterprise C2 question. At the theater and echelon level, software-defined platforms backed by cloud infrastructure and venture-funded engineering velocity will dominate the next decade. Defense primes that tried to compete with legacy systems wrapped in modern UI lost those deals and will keep losing them.
Stop fighting the battle you already lost. Start fighting the one you can win. The enterprise C2 layer belongs to Anduril and Palantir. The tactical edge layer, the software that runs on the operator's hardware when the enterprise platform cannot reach them, is still open. And it is where operators actually make decisions.
The layer below the platform is where the value moved
Enterprise platforms assume connectivity, dedicated compute, and trained support staff. The tactical edge has none of these reliably. A team in a building with degraded comms, consumer hardware, and no program office support needs AI that runs locally, mesh networking that works across whatever links are available, evidence capture that ties every detection to source data, and a mission lifecycle that the team controls.
A fundamentally different problem than what Lattice solves. Lattice fuses intelligence from connected platforms into an operational picture. EdgeLance generates intelligence from local sensors on disconnected hardware and decides what to share upward. The enterprise platform is the consumer of that intelligence. The edge layer is the producer. Owning the producer gives you influence over what the consumer sees.
The $42.6 billion software-defined warfare market is not one market. It is two: the enterprise layer (owned) and the tactical edge layer (open). The next C2 acquisition will not be a platform that competes with Lattice. It will be the edge layer that feeds it.
Why building the edge layer internally always fails
Every major defense prime has attempted to build tactical edge software internally. The results follow a pattern: 18-24 months of development, a team of 20-30 engineers building to a requirements document, a product that works in the lab but not in the field, and an operator community that rejects it because it was designed by enterprise architects who optimized for the wrong user.
The design decisions that make edge software work for operators are not in any requirements document. Ephemeral missions with cryptographic wipe. Duress PIN with decoy unlock. NVG mode at 0.01 brightness with green monochrome. ROE-bounded response options. Wearable readiness scores that stay with the team lead. These features come from understanding what an operator needs under fire, not from a program office's concept of operations.
Internal builds also face a structural incentive problem. At a services company, every engineer building product is an engineer not billing to a customer contract. At a prime, every product development dollar competes with funded program work. The organizational incentive is to build the minimum viable product and move on. The result is software that checks compliance boxes without earning operator trust.
The acquisition math
Consider two paths to owning the tactical edge layer.
**Path A: Internal build.** Staff 20 engineers for 24 months. Total cost: $8-12M in loaded labor. Result: a v1 product with no operator validation, no SOF credibility, no patent protection, and design decisions made by committee. Timeline to first SOF deployment: 36+ months from start. Probability of operator adoption: low, based on historical precedent.
**Path B: Acquire.** Purchase a company that has already built 68+ services, designed for SOF workflows, filed patent provisionals on the core mechanisms, and built the system with operational intuition that enterprise engineers do not have. Cost: $30-75M depending on timing. Result: a working product designed for operator trust, running on consumer hardware, integrated with ATAK and Lattice, protected by emerging IP. Timeline to first deployment: months, not years.
The internal build costs less upfront but delivers less value over a longer timeline with higher risk. The acquisition costs more upfront but delivers a working, validated, IP-protected product immediately. For a prime with $10B+ in revenue, the acquisition cost is a rounding error. The strategic value of owning the tactical edge layer, the piece that makes the entire portfolio relevant in the software-defined battlefield, is not.
The board narrative that works
Defense primes facing the board after losing C2 deals need a narrative that is not 'we will catch up.' That narrative has failed for five years. The narrative that works is: 'We are not competing on platform. We own the tactical edge layer that every platform needs but none of them have built. Our ISR assets collect. Our radios transmit. Our enterprise systems visualize. And our edge layer processes, manages, and curates the intelligence that flows between them.'
That story requires owning the edge layer. Not building it someday. Owning it now, with working software, with operator validation, with patent protection, and with a team that understands the problem space. The FY2026 NDAA acquisition reforms and OTA mechanisms make acquiring and deploying non-traditional solutions faster than ever. The window to act is before the next C2 competition, not after you have already lost it.