Technology → Product → Capability
What defence is actually buying, and whether you are selling it
Are you ready to actually deliver if the MOD, or a prime, said they’d like your capability?
The demand signal right now is the loudest it’s been in decades. Iran, Ukraine, European rearmament - the opportunity is real. But opportunity and readiness are different things, and this market will make that distinction for you if you don’t make it yourself.
Defence procurement in the West is still broken, though progress is real. The problems are being acknowledged, the direction of travel is right. But we’re nowhere near solved yet. The companies that will capture this moment aren’t waiting for procurement to be fixed. They’re getting ready now, because the window - however imperfect - is real and narrowing.
Here’s what getting ready actually means.
Technology is not a product
A pattern I keep seeing across deeptech and dual-use companies: they have genuinely capable, interesting technology. The physics works. The TRL is credible.
Getting from technology to product requires something most grant cycles don’t fund or require: sustained, iterative engagement with end users throughout development. Not just a requirements capture at the start or a demonstration at the end. Real engagement, throughout, that shapes what gets built and why.
Most grant frameworks allow for end user involvement. The option is there.
What I keep seeing instead: end users brought in late, after the core architecture is set. End users are treated as validators rather than co-developers. Worse still: roadmaps shaped around what the next funding round requires rather than what operational reality demands. The technology development progresses, but the problem it’s solving drifts quietly away from what end users actually need.
By the time commercialisation becomes the focus, the gap is real. Every sales conversation is harder than it should be. The demand signal is there. The product isn’t quite meeting it.
A product is not a capability
This is the part that gets said less often, and it matters more right now than it ever has.
Defence doesn’t buy products. It buys capability.
A product meets a set of requirements and can be reproduced. A capability is what the product, or a set of products working as a system enable. Every system, subsystem, and components need to ultimately enable the required capability.
A company that has a product but hasn’t done the work to understand where it sits in the capability stack will keep having the wrong conversations. Talking about what their technology does when the customer needs to understand what operational problem it solves, at what scale, integrated with what else, qualified to what standard. Presenting features when the procurement team needs to see fit within a programme.
The demand signal from this conflict is for capability. Not technology. Not products. Capability. A louder signal doesn’t make those conversations easier. It just exposes the gap faster.
Capability has to be developed with end users, not presented to them
The companies that get this right didn’t arrive at capability conversations after the fact.
They had end users and procurement shaping their roadmap from early on. Requirements, operational context, and Iterative feedback that meant by the time the product was ready, the capability case was already understood by the people who needed to buy it.
I’ve watched companies get this wrong at every stage - startups that built for grant panels instead of operators, scaleups that hit commercialisation and discovered their product solved a problem the market had moved on from, established suppliers that could demonstrate technical capability but couldn’t articulate where they sat in the programme architecture.
The ongoing conflicts have compressed the timeline, programmes are accelerating, and supply chain positions are being set. The window to establish yourself as a credible capability provider is shorter than it was year ago. Getting end users and procurement into your development process now, if they aren’t already, isn’t optional. It’s the work.
Speed, flexibility, and capability positioning
Those are the three things that will determine who wins right now.
Speed to move before the window closes. Flexibility to iterate when operational requirements shift. And genuine capability positioning: knowing where you fit in the stack, being able to articulate it to the people making decisions, and having the development history to back it up.
One or two of those won’t be enough. You need all three.
The Iran conflict has made the opportunity real and urgent. It hasn’t made any company more ready than they were last year. These moments don’t repeat on a convenient timeline. In defence, missing this window doesn’t mean waiting months. It means waiting years.
More next month.