Reversing the flow doesn’t just change where technology comes from. It changes who has to be able to talk to whom, and what each side has to be good at.
Under spin-off, the state was the origin point. It set the requirement, funded the science, owned the result, and released it downstream when it was ready. Everyone else was a recipient. The relationships were vertical and the sequence was clear.
Under spin-in, the state is the destination. The technology is already out there, already funded, already improving without anyone’s permission. The state’s job is no longer to originate. It’s to recognise, evaluate, buy and adopt — quickly enough that the technology is still current when it arrives.
Read those two paragraphs again and notice they describe different jobs.
Originating rewards patience, specification and control. You are defining something that doesn’t exist yet, so precision matters more than speed, and the ability to say exactly what you want is the core competence.
Receiving rewards speed, judgment, and a tolerance for things designed for reasons other than yours. You are choosing among things that already exist, so the core competence is recognising value in something you didn’t specify — and moving before it’s superseded.
The last seventy years produced institutions optimised for the first job. DRDC and the National Research Council on the research side. Public Services and Procurement Canada on the buying side. A small set of prime contractors sized for decade-long programs on the supply side. Those are good institutions and they were built well, for the job they were built for.
We’re now asking them to do the second job, and we haven’t changed much about how they work.
What this means if you’re building something
Two practical consequences.
The first is timing. An institution optimised for originating measures its cycle in program years, because that’s how long it takes to specify and build something new. Your product cycle is measured in release sprints. When those two clocks meet, the mismatch isn’t rudeness or indifference — it’s structural. Plan your runway on their clock, not yours, or don’t enter at all. The companies that get hurt are the ones that assume a promising conversation implies a near-term purchase.
The second is language. An institution built to specify wants a specification. It is fluent in “here is precisely what we require, scored in advance.” It is much less fluent in “here is a capability you didn’t ask for, which solves a problem you described differently.” If you lead with the second, you’re asking someone to do a translation their job doesn’t reward and their process doesn’t have a box for.
None of that means don’t try. It means know which job the person across the table was hired to do — because the reason they can’t see you isn’t that they’re not looking.
It’s that the market where they’d have found you never formed.
Next: the market that never formed.
This is drawn from my essay “The Dual-Use Dimension,” published in 2067 Journal. [Read the full piece →]
