The U.S. Navy is doubling down on a failure and calling it a "modernization."
Raytheon just bagged a $213 million contract to upgrade the combat systems on the Zumwalt-class destroyers. The trade press is busy echoing the press release—talking about "enhanced capabilities" and "integrated defense." They are missing the point. You don't upgrade a ship that has no mission; you just find more expensive ways to let it rust.
The Zumwalt (DDG 1000) was supposed to be the future of naval warfare. Instead, it’s a cautionary tale of what happens when you build a platform around a weapon that doesn't exist and a strategy that vanished before the first hull hit the water.
The Myth of the Multi-Mission Savior
The "lazy consensus" among defense analysts is that these upgrades are necessary to "bridge the gap" until the next generation of ships arrives. That is a sunk-cost fallacy dressed up in digital camouflage.
The Zumwalt was originally designed for land attack. It was built around the Advanced Gun System (AGS), meant to provide long-range fire support for Marines hitting a beach. Then the Navy realized the shells for those guns cost nearly $1 million each—roughly the price of a Tomahawk missile but with a fraction of the utility. So, they canceled the ammo. Now, the Navy has three ships with two massive, non-functioning "holsters" taking up the prime real estate on the deck.
The current $213 million contract is a desperate pivot to turn these ships into "blue water" strike platforms. They want to stick Conventional Prompt Strike (CPS) hypersonic missiles on them. But here is the nuance the optimists miss: putting the world's most expensive missiles on a platform with a tiny fleet size (only three ships) creates a logistical nightmare.
You aren't building a fleet. You’re building a boutique museum of "what if" technologies.
Complexity is Not a Capability
The defense industry loves to equate complexity with lethality. It’s a profitable lie.
Raytheon’s upgrade focuses on the Total Ship Computing Environment (TSCE). This is the "brain" of the ship. In theory, it integrates everything from the radar to the laundry machines into a single software architecture. In practice, it makes the ship a prisoner of its own code.
When you have a highly bespoke system like the TSCE on a class of only three ships, every software patch is a custom engineering project. There is no economy of scale. There is no "proven" codebase shared across a hundred Arleigh Burke-class destroyers.
I have seen programs like this bleed money for decades. You start with a $213 million contract for "upgrades." Two years later, that becomes a $500 million requirement for "integration sustainment." By the time the software is stable, the hardware is obsolete. It’s a treadmill designed by contractors to ensure the power never gets turned off in the boardroom.
The Hypersonic Distraction
The Navy is selling the Zumwalt upgrade as the premiere platform for hypersonic weapons. This is a classic case of the wrong solution for the right problem.
Yes, we need hypersonics to counter peer-state adversaries. No, we do not need to gut and rebuild a failed stealth destroyer to carry them.
The Zumwalt is "stealthy," but stealth is a relative term. In an era of multi-static radar, satellite-based infrared tracking, and wake detection, a 16,000-ton ship is not "invisible." It is just slightly harder to see until it opens its missile cells. Once it fires a hypersonic missile—which creates a massive thermal signature—the "stealth" advantage of the hull is effectively zero.
We are spending hundreds of millions to put high-profile missiles on a ship whose main selling point is being low-profile. It’s like buying a tuxedo so you can go blend in at a construction site. It’s a fundamental mismatch of tactical requirements.
The Wrong Question: "Can we fix the Zumwalt?"
If you look at "People Also Ask" sections or Congressional testimony, the question is always: "How do we make the Zumwalt operational?"
That is the wrong question. The right question is: "Why are we still pretending the Zumwalt matters?"
The $213 million being funneled into these combat system upgrades would be better spent on:
- Distributed Lethality: Buying more Naval Strike Missiles for the ships that actually work.
- Subsurface Dominance: Accelerating the Virginia-class payload modules.
- Attritable Systems: Developing the drone swarms that will actually win the next conflict.
Instead, we are obsessed with "fixing" a legacy mistake. We are obsessed with the "cool factor" of a ship that looks like a spaceship but functions like a paperweight.
The Reality of Integration Risk
Let's talk about the actual math of this "upgrade."
$213 million for three ships. That’s $71 million per hull just for the software and integration of the combat system. For context, you could buy a couple of brand-new F-35s for the price of "upgrading" the computers on a single Zumwalt.
And what do you get? A ship that still lacks a primary gun system. A ship that has a smaller vertical launch capacity (80 cells) than the older, cheaper Arleigh Burke destroyers (96 cells).
The math doesn't work. The tactics don't work. The only thing that works is the revenue stream for the prime contractor.
The Failure of the "Lead Ship" Mentality
The industry suffers from a delusion that if we just throw enough code at a bad hull design, we can "software-update" our way out of a physical engineering disaster.
The Zumwalt’s tumblehome hull design—where the sides slope inward—was chosen for stealth. But it also makes the ship potentially unstable in certain sea states. No amount of Raytheon’s "integrated combat systems" can change the laws of physics. If the ship can't operate safely in heavy weather while performing the high-speed maneuvers required for modern missile defense, the most advanced software in the world is just a very expensive way to record a sinking.
We see this across the board: the LCS (Littoral Combat Ship) was another "modular" dream that turned into a maintenance nightmare. We keep building "Swiss Army Knife" platforms that are too expensive to risk in combat and too specialized to use in peace.
The Brutal Truth
The U.S. Navy doesn't need "upgraded" Zumwalts. It needs to admit that the Zumwalt experiment is over.
We should be using these ships as technology demonstrators—floating laboratories to test new sensors and power systems—rather than trying to force them into a combat role they were never meant for. Trying to turn a shore-bombardment ship into a hypersonic-strike platform is a pivot born of desperation, not strategy.
Every dollar spent on the Zumwalt combat system is a dollar stolen from the shipbuilding accounts that actually provide the "presence" and "mass" the Navy claims it needs to deter a conflict in the Pacific.
Stop trying to fix the ghost. Start building the fleet that can actually fight.
The Navy isn't buying a combat system; it’s buying an excuse for why it hasn't retired these ships yet. In five years, when the next "upgrade" contract is announced because the hypersonics don't play nice with the legacy TSCE architecture, remember this: a $213 million bandage doesn't heal a fatal wound. It just hides it until the check clears.
