Walk through any defense-tech conference today and you’ll see dozens of startups promising to revolutionize warfare. Autonomous drones. AI-powered targeting. Software-defined everything. Venture capital is pouring billions into companies claiming they’ll transform how militaries fight.

But here’s the uncomfortable question: Can they actually do it? Can a startup with brilliant technology fundamentally change military doctrine—or are they destined to solve problems the military already knows it has?

This isn’t an academic question. It cuts to the heart of whether defense is fundamentally a demand-driven or supply-driven market—and that distinction determines whether we’re witnessing a revolution or just a very well-funded evolution.

The Thesis: Defense Is Fundamentally Demand-Driven

Defense, at its core, is shaped more by military doctrine and operational needs than by Silicon Valley-style supply-side breakthroughs.

In consumer technology, a supply-side breakthrough creates its own market. The iPhone didn’t need permission from a government committee to succeed; it simply showed consumers what they didn’t know they wanted, and the user (the buyer) made an immediate decision.

Defense doesn’t work that way because of a structural Principal–Agent problem:

• the user (the soldier) rarely equals the buyer (the procurement authority). A special operator might love a new drone, but they lack the authority to buy it at scale.
• acquisition officers care less about novelty and more about doctrine, budgets, lifecycle cost, and sustainability.

So the real question is: can a startup walk into a Ministry of Defense with something so transformative it forces the entire apparatus to rethink how it fights?

Highly unlikely.

The Case for Demand-Driven Defense

1. The Doctrine Pipeline

Military requirements don’t appear out of thin air. They come from a deliberate pipeline: doctrine development, war-games, operational experience, strategic assessments, and threat analysis. When militaries articulate requirements, they’re responding to carefully studied operational challenges.

Take counter-IED systems used in recent conflicts. That demand signal emerged from combat, was formalized by operational commands, and only then translated into technical requirements. Demand shaped supply—not the other way around.

---

2. The User vs. Buyer Disconnect

A structural disconnect exists at the heart of defense sales. In the commercial world, if you build a better mousetrap, the consumer buys it. In defense, a startup often captivates the user with supply-side innovation, but fails to satisfy the buyer. Defense has a structural split that the commercial world doesn’t: startups often win over the user but fail to satisfy the buyer.

The buyer enforces constraints that overpower user enthusiasm:

• security and compliance requirements
• supply-chain audits
• legal and export controls
• multi-year sustainment expectations

Until a startup clears these hurdles, operator enthusiasm is irrelevant. The system forces companies to conform, not disrupt.

3. The “Boring” Killer: Logistics and Sustainment

The biggest driver of conservatism is logistics. Startups build prototypes; militaries buy fleets.

A platform needs:

• 20–30 years of lifespan
• globally available spare parts
• multilingual manuals
• repairability by a 19-year-old conscript under fire

This is Logistical Aversion: militaries fear buying from a startup that may not survive long enough to support what they sell. The result is a systemic demand for longevity. Militaries aren’t buying gadgets—they’re entering institutional marriages.

4. The Stakes Argument

Militaries can’t beta-test in combat. Consequences aren’t “bad reviews”; they’re casualties.
“Move fast and break things” doesn’t survive first contact with life-or-death responsibility.

This risk environment naturally makes defense demand-driven. Technology must prove it solves a known problem before the doctrine shifts to embrace it.

The Counterview: A Nuanced Look at History

History appears to challenge this thesis. Wasn’t the machine gun a supply-side disruption? Weren’t tanks?

Not exactly.

• Machine guns existed for decades before they reshaped warfare; early doctrine didn’t know what to do with them. Only battlefield demand forced adoption.
• Tanks were dismissed as unreliable until doctrinal innovators (e.g., Blitzkrieg) demonstrated their operational value.

Supply creates possibility.
Doctrine—the demand signal—drives adoption.

The Current Paradox

If defense is so conservative, why the defense-tech boom? Why are VC-backed firms gaining traction?

Because defense isn’t monolithic. It’s a Demand-Driven Core surrounded by a Supply-Permeable Periphery.

1. The Budgetary “Valley of Death”

The core remains rigid because budgets are planned years ahead. A requirement must be validated, documented, and funded long before procurement begins.

Even if a general wants your tech today, the money may not exist until the next cycle.

This is the Valley of Death, where good technology dies waiting for the budget to catch up. This structural lag forces the market to be demand-driven. The budget cycle is the ultimate enforcer of the status quo.

2. Software as a Loophole

There is one exception where supply is beginning to drive demand: Software. Unlike a fighter jet, software can be deployed as a “feature update” rather than a new acquisition. This allows for a tighter feedback loop.

However, even here, the demand is usually for the platform that hosts the software. You can push a new AI targeting algorithm (supply) to a drone, but only because the military demanded and bought the drone (demand) in the first place.

3. Crisis Creates Openings

Geopolitical tension and lessons from Ukraine have created urgency. Crises open doors normally closed.

But this urgency is itself a demand signal: senior leaders are instructing the system to seek speed and non-traditional solutions.Proactively demanding non-traditional solutions are saught to avoid technological surprise.

Toward a Synthesis

Defense is structurally demand-driven with episodic supply-side breakthroughs.

The equilibrium is conservative —doctrine-driven procurement , but wars and major technologies create temporary windows where supply has influence. We are in such a window now. But windows eventually close; doctrine absorbs the shock; bureaucracy reasserts control.

The real question is: how much changes before the window closes?

What This Means for Founders

Accept the demand-driven nature of defense, and your strategy changes.

Don’t just build for the war—build for the bureaucracy.

The fantasy of reshaping doctrine overnight is just that: a fantasy. Successful defense companies don’t surprise militaries into changing how they fight; they solve operationally validated problems in better ways.

Be Machiavellian About Requirements

If defense is demand-driven, then Requirement Engineering is as fundamental as Software Engineering.

Great founders don’t just respond to RFPs—they help shape them. They work with stakeholders years before a program opens, influencing how requirements are written so that the demand signal mirrors their supply capability.

This isn’t manipulation. It’s strategy.

Conclusion

When a defense-tech startup pitches its revolutionary product, ask:

• Are they waiting for an iPhone moment that will never come?
• Or are they solving a high-stakes, logistical, doctrinally anchored problem the military already acknowledges?

In defense, it’s the latter that produces real impact. Innovation happens—but the customer decides which innovations matter.

The most successful innovations aren’t those that surprise militaries into changing how they fight. They are those that give militaries better tools to fight the way they know they need to fight.

The question isn’t whether innovation happens in defense. It clearly does. The question is who gets to decide what innovation matters.

And that customer is driven by doctrine.

In the end, doctrines eat startups for breakfast.