Officials are popping champagne over a £50 million defense contract. They claim it will create "hundreds of jobs." They want you to believe this is a win for the local economy and a spark for industrial growth.
They are wrong.
In reality, these high-profile splashes are often a mask for stagnation. They represent a fundamental misunderstanding of how modern defense technology works and how real economic value is generated. When a government official tells you that spending £50 million will create "hundreds" of new roles, they aren't describing a growth engine. They are describing an inefficiency.
The Myth of Labor-Intensive Defense
The traditional narrative of defense spending is stuck in 1944. We picture massive assembly lines, thousands of workers riveting steel, and a direct correlation between "pounds spent" and "boots on the factory floor."
That era is dead.
In 2026, the most effective defense systems are software-defined and driven by automation. If a £50 million project truly requires "hundreds" of new warm bodies to execute, it suggests the project is bogged down by legacy processes, manual labor, and outdated hardware.
True innovation is efficient. A lean team of fifty elite engineers building autonomous systems or encrypted communications protocols creates more long-term value than five hundred people maintaining a bloated, hardware-heavy platform that will be obsolete before the final check clears.
When we celebrate "job creation" in this sector, we are often celebrating the preservation of the past rather than the invention of the future. We are subsidizing overhead, not output.
The Crowding Out Effect
Every time the state directs £50 million into a specific, localized defense deal, it creates a gravity well for talent. But it isn't "new" talent.
I have watched this play out for two decades. These deals don't magically spawn engineers from the ether. They poach them. They pull the best minds away from agile startups and private-sector tech firms that are actually trying to solve global problems.
By locking these workers into a five-year government contract, we effectively freeze them in a world of bureaucratic red tape and "cost-plus" accounting. This is the Crowding Out Effect. We trade high-risk, high-reward innovation for the safety of a government-backed paycheck.
The result? The wider tech ecosystem starves so a single defense prime can hit a hiring quota that looks good in a press release.
Breaking the Cost-Plus Addiction
Most of these "landmark" deals operate under a "cost-plus" model. The contractor is paid for their costs, plus a guaranteed profit margin.
Think about the incentives there. If your profit is a percentage of your costs, you have zero incentive to be efficient. In fact, you have a financial incentive to hire more people, buy more expensive equipment, and let the project run long.
When officials brag about "job creation," they are inadvertently bragging about how much money they are letting a contractor waste. In a competitive market, a company that manages to do the same task with 20% fewer people is a hero. In the world of government defense deals, that same company is viewed as a failure because they didn't "provide enough employment."
We are prioritizing the process over the product. If the goal is national security, we should want the most lethal, efficient technology for the lowest price. If the goal is a jobs program, we should call it that—but don't pretend it's helping the defense of the realm.
The Skill Rot Crisis
The "hundreds of jobs" promised in these deals are rarely high-growth career paths.
Because these projects are often tied to specific, aging platforms, the skills required are hyper-specific and non-transferable. An engineer spending five years working on a proprietary, closed-loop legacy system for a defense contract is actually falling behind the rest of the world.
While the private sector is iterating on generative AI, decentralized networks, and advanced materials, the defense contract worker is often stuck navigating compliance documents and 15-year-old codebases.
Imagine a scenario where a mid-career software architect joins one of these "newly created" roles. They spend three years on a £50m project. When the contract ends, they find themselves in a market that has moved on without them. They haven't been "upskilled"; they’ve been institutionalized.
The Hidden Cost of "Social Value"
Modern procurement rules often require companies to demonstrate "Social Value." On paper, this sounds great. In practice, it’s a tax on efficiency.
Companies are forced to jump through hoops to prove they are hiring from specific demographics or regions, regardless of whether those are the best people for the job. This adds layers of administrative cost that have nothing to do with building a better radar system or a faster drone.
When a £50 million deal is signed, a significant chunk of that money never touches the technology. it is swallowed by:
- Compliance officers
- Contract managers
- Lobbyists
- Consultants hired to "measure" social impact
We are paying for the theater of progress, not progress itself.
Stop Asking "How Many Jobs?"
The media and the public are asking the wrong question. We shouldn't care how many people are being hired. We should care about the output per capita.
If a company can build a revolutionary defense system with ten people and a clever algorithm, that is a massive victory. It means the other 490 people are free to go build companies, fix the energy grid, or innovate in healthcare.
By obsessing over job counts, we are essentially advocating for "digging holes and filling them back in." It’s Keynesianism at its most cynical.
The Reality of Sovereign Capability
There is a legitimate argument for "Sovereign Capability"—the idea that we must maintain certain skills within our borders for national security.
But you don't build sovereign capability by subsidizing inefficient, labor-heavy contracts. You build it by fostering a competitive, high-velocity R&D environment. You build it by being the place where the world’s best engineers want to work, not the place where they go to hide in a cubicle for a guaranteed pension.
The current model creates a fragile, dependent industry that can only survive on the next £50 million "fix." It doesn't create a powerhouse; it creates a ward of the state.
The Truth About the £50m Price Tag
Let’s be honest about the math. £50 million sounds like a lot of money to the average taxpayer. In the defense world, it’s a rounding error.
A single F-35 fighter jet costs roughly £80 million. This "massive" deal that officials are touting is literally worth less than two-thirds of one airplane.
When you spread £50 million across "hundreds of jobs," plus materials, plus overhead, plus corporate profit, you realize very quickly that these roles aren't going to be high-paying, high-innovation positions. They are going to be entry-level assembly or administrative roles.
This isn't an investment in the future of British technology. It’s a temporary band-aid for a local unemployment stat.
Rethink the Win
If you want to know if a defense deal is actually good, look for the opposite of what the officials are saying.
- Is it hiring fewer people than expected? Good. That means it's efficient.
- Is the technology being sold to other countries? Good. That means it has actual market value.
- Is it being built by a company you’ve never heard of? Even better. That means the monopoly of the "Big Five" defense primes is being challenged.
The next time you see a headline about "Hundreds of jobs created by defense deal," don't cheer. Ask why they need so many people to do a job that software should be doing. Ask who is being poached to fill those seats. Ask what we aren't building because our best minds are busy filling out government timesheets.
Stop measuring success by how many people are on the payroll. Start measuring it by how much of the payroll we no longer need.
Efficiency is the only real security.
