The Most Expensive Way to Save Money

A product optimized to a fine point cannot be rejuvenated

The Most Expensive Way to Save Money

Inventor's Mind — feature essay. Third in a series with "Judgment Is the Art of Seeing With Understanding" and "The Load You Can't Name."

You have felt this, even if you have never designed anything. Something breaks too soon — the appliance that dies in five years where your grandmother's lasted forty, the phone that slows to a stop right as the new model ships — and a thought follows that feels like plain common sense: they don't build things to last anymore. And right behind it comes the second thought, the one that feels like fiscal responsibility, especially when the money is public: if we're spending taxpayer dollars, we should build things to last.

Hold onto that second thought, because it is half right, and the wrong half is one of the most expensive ideas in government.

Two airplanes, both bought with your taxes

Your taxes paid for two airplanes that make the point better than any argument could.

The first was the finest air-superiority fighter ever built — designed in the best analytical tools money could buy, stealthy, supersonic, a generation ahead of anything in the sky. The Air Force planned to buy hundreds of them. It built one hundred eighty-seven, shut the production line in 2011, and is now working out how to replace them. The second was a heavy bomber drawn in the early 1950s with slide rules and hand calculation. Seven hundred forty-four were built. It entered service in 1955, and in 2026 the Air Force cleared a program to give it new engines so it can keep flying toward its hundredth birthday — and the bomber being built to replace its newer cousins is not slated to replace it.

If durability were simply a matter of spending enough money on good enough engineering, the expensive, advanced airplane would be the immortal one. It is the other way around. The crude, cheap one is the one that won't die, and the brilliant, costly one is the one we're replacing. So whatever "spend wisely" means, it cannot mean "spend more and build to last." The two airplanes flatly refuse that lesson.

The surprising place the money actually went

Here is where the F-22's cost actually lives, because it is not where most people think.

The whole program cost about sixty-seven billion dollars. Roughly thirty-two billion of that was research and development — the cost of inventing stealth, supercruise, and sensor fusion in metal for the first time. Procurement, the cost of actually building the airplanes, was about thirty-four billion. Now do the division that matters. Thirty-two billion dollars of development, spread across the hundred and ninety-five airframes that were eventually built, means every single F-22 carries roughly one hundred sixty-six million dollars of pure thinking before a single rivet is counted.

The B-52 carried a tiny fraction of that. Its development was modest by comparison, and it was spread across seven hundred forty-four airplanes. The expensive part of the F-22 was never the titanium. It was the invention — and the invention got stranded across far too few copies. The Air Force planned for hundreds; budget pressure cut the buy to one hundred eighty-seven; and the bill for all that development simply got divided among the survivors. Cut the fleet by three quarters and you don't cut the development bill by three quarters. You just charge each remaining airplane four times as much for it. The aircraft didn't get expensive because someone was wasteful. It got expensive because we paid to invent something and then declined to build enough of it to make the invention worth the price.

That is the first clue. The waste wasn't in the engineering. It was in a decision about quantity and time that happened in a completely different room from the engineering.

The number we watch is the wrong number

The mistake underneath all of this is not technical. It is a choice about which number to look at, and almost everyone looks at the wrong one.

We measure the cost of a thing at the moment we buy it. Call it the acquisition minute — the price tag on purchase day. It is concrete, it shows up in this year's budget, and it is the number that gets you praised or fired this cycle. So that is the number we optimize. And optimizing the acquisition minute does something quietly destructive: it strips out margin. Extra structural strength, spare power, room to grow, the slack that lets a design absorb missions nobody has imagined yet — all of it costs money on purchase day and pays off only over decades. On purchase day it looks like waste. So the minute-optimizer cuts it, every time, and feels thrifty doing it.

Measure the honest way and the picture inverts. Cost per year of capability delivered — total cost divided by the service life and the work actually done — is the number that tells you whether money was well spent. By that measure the B-52, which looked expensive and overbuilt the day it was delivered, is one of the cheapest things the country has ever bought, because the bill got spread across seventy years and counting. The acquisition minute called it costly. The mission lifetime calls it a bargain. The cheap-looking choice and the actually-cheap choice are frequently opposites — and we have built an entire system that watches the cheap-looking number and calls it discipline.

Tight budgets are not the villain — but they have a blind spot

It would be easy to blame all this on penny-pinching, and that would be wrong. Scarcity is one of the great engines of ingenuity. A tight budget forces you to substitute cleverness for resources, to find the elegant answer because you cannot afford the brute one. Some of the best engineering ever done was done broke.

But constraint-driven cleverness has a specific blind spot, and it is the whole problem. A tight budget makes you brilliant at hitting today's requirement with less. It does nothing whatsoever for tomorrow's unspecified requirement — because that future need is not written into the budget, and you cannot be ingenious against a constraint nobody gave you. Scarcity sharpens you against the known and blinds you to the unknown. It produces a design optimized to a fine point against the spec on the page, with every ounce of future-proofing shaved away, because future-proofing never appeared on the page to be valued.

And a thing optimized to a fine point cannot be rejuvenated. There is no slack left to grow into. So when the need shifts — and it always shifts — you cannot upgrade the thing. You can only replace it.

How thrift builds a throwaway world

Watch the cycle close on itself, because this is the mechanism that produces the disposable world everyone complains about.

Tight-budget optimization produces an object too tightly fitted to its original spec to be upgraded. The need shifts; the object can't follow; replacement becomes the only rational move. Each replacement teaches the institution that replacement is normal — that things are not kept and grown, they are scrapped and rebought. And that lesson justifies the next tight budget: why pay for durability, why pay for room to grow, when we'll just replace the thing anyway? Which funds the next un-rejuvenatable object. Which gets replaced. Which proves the point again.

The throwaway world is not a moral failure or a decline in craftsmanship. It is the downstream, self-reinforcing output of measuring cost at the acquisition minute. Penny-wise procurement does not merely permit the replacement society — it manufactures it, one tightly-optimized, unupgradeable object at a time, and dresses the whole process up as savings.

But not all replacement is decay

Here the argument has to be honest with itself, because there is a version of "throw it away and build a new one" that is not decay at all — it is health.

Your phone is replaced every few years. So is the server in a data center, and the specific vaccine in an mRNA platform. These are thrown away on a fast cycle, and they are more adaptive than the B-52, not less. The difference is where the durable part lives. In a healthy replacement cycle, the lasting investment — the buffer, the room to grow — is built into the platform: the rack standard, the operating system, the manufacturing line, the interface everything plugs into. The platform endures for decades while the cheap, disposable unit churns. You throw away the perishable layer precisely because the durable layer underneath it was built to outlast it.

Decay replacement is the opposite. There is no enduring platform underneath, so when the need shifts you throw away the whole expensive, integrated thing — because nothing in it was built to be the part that lasts. The F-22 is decay replacement: brilliant, integral, and with no platform beneath it to carry forward, so replacing it means replacing all of it. Your phone is healthy replacement: the handset is disposable, the ecosystem is the B-52.

Same word — replacement — and opposite economics. Which means the real question is never "durable or disposable." It is which layer are you starving. Starve the disposable layer and you get healthy iteration. Starve the durable layer — the platform, the structure, the part that was supposed to outlast everything — and you get decay wearing the costume of thrift.

The disease is two offices

So what does it actually mean to spend public money wisely? Not "build it to last." Not "build it cheap and disposable." It means matching the build to the honest length of the mission — and the reason we get this wrong is structural, and it has nothing to do with engineers or tools.

Two numbers govern every durable thing. The first is how long the thing will be needed — the real life of the mission it serves. The second is how long the thing will be kept — the service life the budget commits to. In a sane system these two numbers would be reconciled by the same person in the same room. In the system we actually have, they are set in different offices by different people who never meet. An engineer or analyst forecasts the need. A budget officer, working on a two-to-four-year cycle and an election calendar, sets the service life and the buy quantity — and rotates out of the chair long before the thirty-year bill ever arrives. The person who decides how long to keep the thing will never personally feel whether that was the right call.

That gap — between the office that knows how long the thing is needed and the office that decides how long it's kept — is the disease. Not the slide rule, not the computer, not the engineer at the drawing board. The F-22 wasn't truncated by bad engineering; it was truncated by a budget decision made in isolation from the mission forecast. The two numbers never sat in the same room, so the buy got cut, the development cost got stranded, and a brilliant airplane became a cautionary tale about arithmetic.

The good news: it's fixable, and we already know how

If this were a flaw in human nature, the story would end in a shrug. It isn't. It's a flaw in how the rooms are arranged, and the proof is that the same government that produces stranded billion-dollar keepers also, in specific places, spends beautifully on exactly the right clock.

DARPA funds projects expecting most of them to fail, and throws the failures away on schedule without anyone's career ending — because failure is the expected output, not a scandal. Commercial space contracts buy outcomes instead of effort, and let contractors visibly fail while a competitor delivers. The Space Development Agency deliberately builds cheap satellites in throwaway tranches, betting that the technology will respin faster than durability could ever pay off. These are not different countries. They are different rooms in the same government, and what they share is one structural feature: somebody is authorized to retire a thing on schedule without it being treated as a failure.

That authority — the cover to say "this has served its purpose, scrap it as planned" without it becoming a headline — is the whole hinge. Where it exists, public money does both durable and disposable well, because someone can match the build to the clock and then act on the match. Where it's missing, everything drifts toward expensive keepers nobody can bring themselves to kill, and the drift gets relabeled as stewardship. The keeper is the choice nobody gets fired for. "We built it to last" is safe. "We built it cheap and scrapped it on schedule, as planned" is correct and politically radioactive — even when it's the wise use of the money.

A caution, so we don't overcorrect

One guardrail before the lessons, because the fix has its own failure mode. The authority to retire things on schedule is necessary, but it is not sufficient, because the forecast of how long a thing is needed is still a human judgment that can be wrong in either direction. Hand someone the power to retire things and let them misjudge a long mission as a short one, and they will scrap the bridge, the water system, the thing that genuinely needed to last a century. The goal is not to make retirement easy. The goal is to force the two numbers — how long it's needed, how long it's kept — into the same room, under one owner, who has to defend both at once. Easy retirement without honest forecasting is just the old disease running the other direction.

Lessons learned

"Build it to last" is not the same as "spend wisely." Durability you can't use is the most expensive waste there is, because you pay for decades to maintain a monument to a need that's already gone.

Watch the right number. The cost at purchase is the cheap-looking number; the cost per year of capability delivered is the true one. They frequently point in opposite directions, and the system is built to watch the wrong one.

Tight budgets breed cleverness about the known and blindness to the unknown. Scarcity makes you brilliant against the spec you were handed and helpless against the future you weren't — because you can't be ingenious against a constraint nobody wrote down.

The throwaway world is a budget decision, not a moral failing. Optimizing cost at the acquisition minute manufactures unupgradeable things, and the cycle pays for itself: each disposable object teaches the institution to expect the next one.

Ask which layer you're starving. Replacement is healthy when the durable buffer lives in the platform and you discard the cheap layer. It's decay when you discard the whole expensive thing because nothing was built to outlast it.

The disease is two offices. How long a thing is needed and how long it's kept are decided by different people who never reconcile their two numbers. Force both numbers into one room, under one owner who must defend them together.

The fix is authority, not money. Someone has to be allowed to retire a thing on schedule without it being treated as failure. Create the room; name the owner. DARPA and commercial space prove it's buildable — and that the same government can spend wisely the moment the rooms are arranged to let it.

Close

Your tax dollar is not wasted by being spent on something cheap, or on something built to last. It is wasted when nobody decided, honestly and in one place, how long the thing actually needed to last — and then matched the spending to that answer.

The B-52 was not cheap because it was crude. It was cheap because its mission was honestly judged to be long, and it was built, with margin to spare, to match. The F-22 was not wasteful because it was advanced. It was wasteful because we kept it on a clock its design never agreed to, cut the buy that would have justified its invention, and stranded the cost of brilliance across too few airframes. Neither was a failure of engineering. Both were a failure to put two numbers in the same room.

Spending money wisely is not a virtue you can feel in your gut, and it is not the warm reassurance of "we built it to last." It is a clock you are honest about, and a person willing to put their name on it. We will not get a thrifty government by spending less, any more than we got a durable one by spending more. We will get it the day the office that knows how long a thing is needed and the office that decides how long it's kept are finally made to be the same office — and somebody has to answer for both.

Sources: F-22 program figures from the Congressional Research Service and GAO (≈$67.3B total program; ≈$32.4B R&D; 195 aircraft built, 187 operational). Fleet-truncation history (planned 750 → 187) and stranded-R&D effect per 19FortyFive, May 2026. B-52 re-engine and B-52J redesignation per Defense One, May 4, 2026.