1) The trap
Strategic technology invites a particular mistake: treating importance as if it were a business. A capability that would matter in a crisis can still lack a buyer with a budget, a route to deployment, or a plan that the capital raised can actually fund.
Founders in this field are often drawn by the mission, and they should be. But the mission does not make the company. The companies that last are the ones that are important and investable at the same time, and the second condition is the one that needs work.
2) Four tests, every round
At the early stage we do not expect everything to be proven. We expect the founders to know exactly what has been proven, what has not, and what this round will change. Four tests organize that conversation.
- A buyer, not an audience. Interest is not adoption. We look for an identifiable user, a budget owner and a purchasing path. A paid pilot counts. A letter of support without a budget rarely does.
- It works outside the demonstration. Performance on the bench is the beginning of diligence, not the end. We ask how the technology performs in the conditions its users actually face, and what has not yet been tested.
- A path to deployment. Integration, certification, production and support sit between a working prototype and something an operator can rely on. This is the gap where strategic hardware companies most often stall.
- Capital to a milestone. The round should reach a proof point that changes the risk materially, including in the case where adoption is slower than planned. Public-sector buying is slow; a credible plan assumes it.
3) Dual-use is a discipline, not a slogan
Commercial revenue can fund the long national-security sales cycle and reduce dependence on a single buyer. National-security demand can prove a technology in the hardest conditions it will ever face. Each strengthens the other.
But each market needs its own user, its own buyer and its own evidence. Two half-markets do not add up to one whole one. When a company describes itself as dual-use, we ask to see both sides of the case, and which side pays first.
4) What persuades us, and what does not
What persuades us is evidence with its limits stated: a named first customer with a budget, test results with the conditions attached, a team that has shipped in the domain, and a milestone that would change our view if it were reached.
What does not is the familiar substitute for evidence: a market-size slide, a demonstration staged in ideal conditions, or strategic relevance offered in place of revenue. None of these is disqualifying. None of them is enough.
5) Why we write this down
These tests are how our CAMP framework is built: Capital, Advantage, Market and People. We publish them so that a founder can prepare against the same standard we apply, whoever they know and wherever they are based.
An important technology deserves a company that can carry it. Our job is to find the founders building that company, and to be clear about what we need to see.
