<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd" xmlns:googleplay="http://www.google.com/schemas/play-podcasts/1.0"><channel><title><![CDATA[Gray Matters: Mission Matters Podcast]]></title><description><![CDATA[The Mission Matters podcast explores the intersection of technology, national security, and startups through in-depth conversations with early-stage founders and government technologists. Each episode reveals the opportunities, technical challenges, and innovations shaping the future of national security, offering insights from those on the front lines of technological evolution and national defense.]]></description><link>https://maggiegray.us/s/mission-matters-podcast</link><image><url>https://substackcdn.com/image/fetch/$s_!hspO!,w_256,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F29289b07-737d-48e5-ba9c-13d291c93276_1024x1024.png</url><title>Gray Matters: Mission Matters Podcast</title><link>https://maggiegray.us/s/mission-matters-podcast</link></image><generator>Substack</generator><lastBuildDate>Sat, 21 Nov 2026 03:50:19 GMT</lastBuildDate><atom:link href="https://maggiegray.us/feed" rel="self" type="application/rss+xml"/><copyright><![CDATA[Maggie]]></copyright><language><![CDATA[en]]></language><webMaster><![CDATA[maggiegray@substack.com]]></webMaster><itunes:owner><itunes:email><![CDATA[maggiegray@substack.com]]></itunes:email><itunes:name><![CDATA[Maggie Gray]]></itunes:name></itunes:owner><itunes:author><![CDATA[Maggie Gray]]></itunes:author><googleplay:owner><![CDATA[maggiegray@substack.com]]></googleplay:owner><googleplay:email><![CDATA[maggiegray@substack.com]]></googleplay:email><googleplay:author><![CDATA[Maggie Gray]]></googleplay:author><itunes:block><![CDATA[Yes]]></itunes:block><item><title><![CDATA[🎙️ Ep 33 - Defending Taiwan: A Strategy to Prevent War with China | Eyck Freymann]]></title><description><![CDATA[How to deter war with China over Taiwan?]]></description><link>https://maggiegray.us/p/ep-33-defending-taiwan-a-strategy</link><guid isPermaLink="false">https://maggiegray.us/p/ep-33-defending-taiwan-a-strategy</guid><dc:creator><![CDATA[Maggie Gray]]></dc:creator><pubDate>Tue, 10 Nov 2026 20:15:19 GMT</pubDate><enclosure url="https://api.substack.com/feed/podcast/224357184/71912876ba4ccbaa35ac0856077139a1.mp3" length="0" type="audio/mpeg"/><content:encoded><![CDATA[<p>How can we deter a future conflict over Taiwan? On the newest <strong><a href="https://www.linkedin.com/company/mission-matters-podcast/">Mission Matters Podcast</a></strong> episode (links in comments), <strong><a href="https://www.linkedin.com/in/matt-kaplan-86107a177/">Matt</a></strong> and I sit down with <strong><a href="https://www.linkedin.com/in/eyck-freymann/">Eyck Freymann</a></strong> to discuss the evolving U.S.-China-Taiwan relationship, the challenges of deterring Chinese aggression, and the technologies that could shape a future conflict in the Indo-Pacific.</p><p class="button-wrapper" data-attrs="{&quot;url&quot;:&quot;https://maggiegray.us/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe now&quot;,&quot;action&quot;:null,&quot;class&quot;:null}" data-component-name="ButtonCreateButton"><a class="button primary" href="https://maggiegray.us/subscribe?"><span>Subscribe now</span></a></p><p><br>On the episode, we discuss:</p><p><br>&#127481;&#127484; <strong>Why Taiwan matters:</strong> The strategic importance of Taiwan goes far beyond semiconductors, and its future has enormous implications for the U.S. alliance system in the Indo-Pacific.<br>&#9876;&#65039; <strong>Deterrence and gray-zone warfare:</strong> Why China may prefer a gradual campaign of economic coercion, cyberattacks, and other sub-threshold activities over a conventional military invasion.<br>&#128640; <strong>Emerging defense technologies:</strong> The critical roles of autonomous maritime systems, resilient communications, integrated air defense, and AI in a potential conflict over Taiwan&#8212;and why the lessons from Ukraine don't always translate to the Pacific.<br>&#127981; <strong>The defense industrial base:</strong> Why the U.S. and its allies need to rethink defense production and build integrated, allied supply chains to compete with China's manufacturing capacity.<br><br>One of my biggest takeaways from the conversation was Eyck's argument that <strong>deterring a Chinese invasion of Taiwan is both possible and achievable&#8212;but deterring an invasion alone isn't enough.</strong> The U.S. also needs a strategy for responding to the growing range of coercive activities that fall below the threshold of conventional warfare.<br><br>As always, please reach out if you or anyone you know is building at the intersection of technology and national security. And please fill out the form below if you are interested in working in defense tech (in or out of the <strong><a href="https://www.linkedin.com/company/shieldcap/">Shield Capital</a></strong> portfolio).</p><p>You can listen to the podcast on <a href="https://open.spotify.com/episode/4RN2nZGy3MmJSLfUMYAL9s?si=VHRb8myYSXKShCZ4L1ZxcA">Spotify</a>, <a href="https://youtu.be/sZevaB-o_gY">YouTube</a>, <a href="https://podcasts.apple.com/us/podcast/defending-taiwan-a-strategy-to-prevent-war-with/id1807120572?i=1000801048611">Apple</a>, the Shield Capital <a href="https://shieldcap.com/episodes/eyck-freymann">website</a>, or right here on Substack.</p><p class="button-wrapper" data-attrs="{&quot;url&quot;:&quot;https://maggiegray.us/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe now&quot;,&quot;action&quot;:null,&quot;class&quot;:null}" data-component-name="ButtonCreateButton"><a class="button primary" href="https://maggiegray.us/subscribe?"><span>Subscribe now</span></a></p><p class="button-wrapper" data-attrs="{&quot;url&quot;:&quot;https://workindefensetech.netlify.app/&quot;,&quot;text&quot;:&quot;Work in Defense Tech&quot;,&quot;action&quot;:null,&quot;class&quot;:null}" data-component-name="ButtonCreateButton"><a class="button primary" href="https://workindefensetech.netlify.app/"><span>Work in Defense Tech</span></a></p><p><strong>Transcript</strong></p><p><strong>Maggie</strong> 00:45</p><p>In this episode of the Mission Matters podcast, we sit down with Eyck Freymann to discuss strategies to preserve peace and protect US interests and values in an era of systemic competition with China. On this podcast, we often discuss the kinds of technologies that we&#8217;re building to improve our national security, but we rarely dig into the details of what the adversary actually looks like and why we need these new technologies to remain competitive. So this is an episode I&#8217;m really looking forward to. I just read Eyck&#8217;s newest book, Defending Taiwan: A Strategy to Prevent War with China, and learned quite a lot about the actual tactics and situation on the ground of what it might actually look like if we had some kind of a conflict with China.</p><p><strong>Matt</strong> 01:27</p><p>In addition to his most recent book, Eyck is the author of several other books, including The Arsenal of Democracy: Technology, Industry, and Deterrence in an Age of Hard Choices, and One Belt, One Road: Chinese Power Meets the World. This conversation today covers everything from the current state of US-China-Taiwan relations, different pillars of deterrence to prevent a conflict with China, and the role that emerging technologies would play in a potential future conflict. Eyck, thanks so much for coming on the podcast.</p><p><strong>Eyck</strong> 01:56</p><p>Thanks for having me on. Let&#8217;s get into it.</p><p><strong>Maggie</strong> 01:58</p><p>Yeah, well let&#8217;s just start with a basic question. Why does China care about Taiwan, and why should America care about Taiwan?</p><p><strong>Eyck</strong> 02:07</p><p>Well, thanks for starting there. That&#8217;s the way to start. The first thing to say is that both China and America cared about Taiwan before Taiwan made semiconductors. In fact, we almost went to nuclear war over it twice, in the first and second Taiwan Straits crises. And the reason has to do first and foremost with Taiwan&#8217;s geographic position. Taiwan sits right in the center of the first island chain, which is an archipelago extending down from Japan all the way to Southeast Asia via Taiwan and The Philippines. There are not that many navigable waterways between those islands. That partly has to do with the topology of the seabed. It&#8217;s known as the Ring of Fire, right? There&#8217;s volcanoes. It&#8217;s a place where two tectonic plates collide. And as a result, the United States learned this geography lesson in the Pacific War and the Korean War, if our friends and partners are all astride this first island chain, then a Chinese or any other continental Eurasian navy will have a very hard time breaking out into the wider waters of the Pacific, crossing the ocean and threatening the homeland. But if China can somehow flip Taiwan and use its Pacific-facing coast as a forward base to project naval power, surface ships or submarines forward, they can effectively surround Japan. They can surround the Philippines, they can surround South Korea, and these are economies that ultimately are almost entirely dependent on imported energy, food, and other inputs to survive. So a world in which Taiwan falls by force or coercion is an unmitigated catastrophe for the entire alliance system in the region. In fact, the current status quo in our relations with Japan and the others becomes unsustainable. So that&#8217;s why China wants Taiwan for geostrategic reasons. It obviously has this enormous propaganda value for the CCP because not to retread the history in too much detail, this is the unfinished business of China&#8217;s civil war. This is the question of whether there is such a thing as one China that includes Taiwan, and whether the Chinese Communist Party is the sole legitimate government, or whether there is some second China, a free China, which is richer and more technologically advanced, and just better in a lot of ways, or whether Taiwan got separated at some point along the way. So for Beijing, this is an incredibly sensitive issue that relates to the Communist Party&#8217;s legitimacy, Xi Jinping&#8217;s personal legitimacy within the regime, and also this is this massive opportunity, because if Taiwan can be made to submit, the dominoes might very quickly fall, and then China&#8217;s pathway to national rejuvenation and eventually regional and global hegemony would be well underway.</p><p><strong>Maggie</strong> 05:15</p><p>One of the things I find really interesting is actually learning about the domestic situation in Taiwan. So can you tell us a little bit about some of the different political opinions in Taiwan about China and its relationship with China?</p><p><strong>Eyck</strong> 05:29</p><p>Well, how much time do we have? I&#8217;m kidding. I&#8217;m kidding. So, it&#8217;s hard to answer this question without drawing caricatures because Taiwan is a thriving democracy with an incredibly robust and vibrant political debate. And they understand China reasonably well because they can absorb CCP material in the original language because they&#8217;re flooded with propaganda, from every direction, because they&#8217;ve been living under threat in one form or another for the last 70-odd years, and because they&#8217;re not stupid. Like everyone else, they can see that Donald Trump is unpredictable, and they wonder what that means for their security and their personal future. So, Taiwan is divided between two basic camps that they call green and blue. The green camp is the Democratic Progressive Party, it&#8217;s the current ruling party, which basically takes the view Taiwan is an independent country. We became independent in 1949, and we&#8217;re not going to rock the boat, but we are in fact an independent country with our own distinct traditions, heritage, history, culture, and we have a place in the US-led security architecture, and the United States wants to protect us for the reasons we&#8217;ve discussed. And therefore, if we keep the Americans on board and we play our part and we are a good partner, the Americans will deter this for us, and they will not abandon us. And then there&#8217;s the Blue camp, which is the Guomindang. This is the party of Chiang Kai-shek, the party that fought the Chinese communists on the mainland in the 1930s and &#8216;40s and then decamped to Taiwan after, which sometimes gets branded as the pro-China party. That&#8217;s kind of an oversimplification. The KMT would say, &#8220;Who are we kidding?&#8221; We speak Chinese. We eat Chinese food. Most of us practice Chinese religion or Chinese philosophy in some form. Most of us have ancestry on the mainland, an ancestral hometown on the mainland. We are Chinese, right? There is one China that includes Taiwan, but for historical reasons that we all understand, there is a free part of China and an unfree part of China, and the free and unfree parts have different definitions of what the ruling framework for China ought to be. But on that basis, we can talk to the CCP. We can deliver each other&#8217;s mail. We can trade, and furthermore, the Americans may not be reliable. The Americans may not be coming. The cavalry may not be there, and if that&#8217;s the case, we don&#8217;t wanna be used as a pawn in someone else&#8217;s game, and we don&#8217;t want Beijing to get the wrong idea that we&#8217;re going to provoke a crisis. We need to do diplomacy with Beijing to reassure them that the best way to handle this is through grown-ups sitting down at a table. And now I&#8217;m caricaturing, and within each of these parties, there&#8217;s a huge range of perspectives which range from the loco-coco, independence now, dare Beijing to attack us, which is a rounding error of the population, less than ten percent, not zero, loud on Twitter, but less than ten percent. These people have blown up my DMs since I&#8217;ve written the book. And then on the other side, the loco-coco or paid off united front, unification now, we can become a glorious province of the PRC and advance Chinese communism. Basically, no one in Taiwan believes that. But plenty of people in Taiwan believe, due to China&#8217;s size and scale and geographic proximity, that some accommodation has to be had. So these two camps totally hate each other. They inhabit completely different information environments. It divides families. It divides communities. And unlike in the United States where there&#8217;s this, you could call it a deep state, or you could just call it a centrist core of technocratic professionals, which is most of our military, most of our intelligence community, a lot of our diplomatic corps, people who basically consider the partisan stuff to be noise, a distraction from the mission, Taiwan is a younger democracy, is very polarized across all of its institutions. They don&#8217;t really have nonpartisan think tanks, for example. And both sides caricature the other side and try to get the Americans, in some cases China, to intervene in Taiwan&#8217;s politics to their advantage. This is a very noisy and challenging information environment, and the reason I&#8217;m harping on this is because Taiwan&#8217;s going into an election. In 2028, January 2028, they will elect their next president, and it will probably be the incumbent, Lai Ching-te of the DPP, the green side, versus some yet to be determined KMT. And there will be a temptation for some in the United States government to just assume, well, the DPP is the pro-America party superficially, so they&#8217;re our team. And one of the arguments in the book is this stuff is way more delicate than we would think, and trying to meddle in Taiwan&#8217;s politics is more likely to backfire than to work. We should respect that the people of Taiwan can make their own choices, that they are sane and don&#8217;t want their kids to grow up under communism, and that they will make good decisions for themselves. But you have to remember that the people of Taiwan will respond to the signals they get from the United States, and if they believe that the United States does not have their back and will not be there for them, then they may decide that the only solution is some kind of negotiated surrender. And the goal of the US policy should be to back up Taiwan, whoever they happen to democratically elect, to allow this process to play out peacefully through diplomacy and not in a more violent or coercive way.</p><p><strong>Matt</strong> 11:43</p><p>So speaking of the US position on Taiwan, help us understand, like let&#8217;s suppose the US decided that the risks of conflict with China weren&#8217;t worth it, and that, whether it was the military conflict or just an economic crisis that coming to Taiwan&#8217;s defense, in an invasion or blockade scenario was just not worth the cost. Help us understand what would be the worst case scenario for the type of outcome that could lead to, from a US perspective. What would you want the US government and citizenry to have in mind, as it evaluates that decision and thinks about what its posture will be toward Taiwan?</p><p><strong>Eyck</strong> 12:31</p><p>Assuming we&#8217;re unwilling to fight?</p><p><strong>Matt</strong> 12:33</p><p>Yes.</p><p><strong>Eyck</strong> 12:33</p><p>Well, if you&#8217;re unwilling to fight, you&#8217;re choosing between bad options, because you definitely don&#8217;t wanna get backed into fighting a war that you don&#8217;t wanna fight. So if it turns into a crisis and you&#8217;re intending to fold, the more chips you have on the table when you eventually fold, the worse a position you&#8217;re in. And in other words, if you&#8217;re holding a bad hand in poker, fold early. Everyone knows that. On the other hand, the United States has maintained a, what we call this One China policy. Technically, it&#8217;s a One China policy guided by the Three Communiques, the Six Assurances, and Taiwan Relations Act. It&#8217;s a whole litany to recite, but we have this policy that has grown over half a century that we have reiterated a zillion times, and that is part of what creates stability in the region. So if we were to change our policy in an arbitrary way, it would scare the daylights out of all of our regional partners. It would make them doubt whether our promises to them, which have never really been tested, are still good, and it may invite provocations and further tests, not just from China against Taiwan, but from North Korea on the peninsula or in contested maritime space, from Russians all around the region. The Russians are out there on a regular basis harassing our Japanese friends. China may see whether it extends into the Southern Ocean. They recently fired a nuclear-capable ICBM towards Australia. So the possibility that walking away from Taiwan could actually set in motion a catastrophe that brings us in is something we can&#8217;t ignore, and that&#8217;s one of the reasons for strategic ambiguity because, frankly, different presidents have different views on this, and we don&#8217;t have a window into the heads of past presidents, and it&#8217;s possible that some of them would have fought for Taiwan and others actually wouldn&#8217;t. But maintaining the current ambiguous position seems like the wise thing to do in that scenario. But obviously you don&#8217;t want to be led to the brink and then have to walk down in a humiliating way.</p><p><strong>Matt</strong> 15:06</p><p>Yeah, I mean, in the book, you draw a really interesting historical comparison to talk about US resolve, during the Cold War, to Berlin, and the symbolic positioning that Berlin had in the Cold War, and how it&#8217;s analogous in some sense to the position of Taiwan today. I was wondering if you could explain that comparison and what we can learn from it as the US kind of continues or modifies its strategy and adapts to the new situations going forward.</p><p><strong>Eyck</strong> 15:34</p><p>So there&#8217;s lots of ways in which Taiwan is not like Berlin, that we have to get to understand the limits of the analogy, but let&#8217;s talk about the ways in which they are potentially instructive. So Berlin is this weird case at the end of the Second World War because it&#8217;s in the heart of East Germany. It&#8217;s an exclave. It&#8217;s in the heart of East Germany, but it&#8217;s divided into four parts, a Soviet sector, an American, a British, and a French. And over the course of 1945 to 1948, it is unclear whether the Soviets will do as they&#8217;ve promised at Yalta and actually allow these Eastern European countries that were liberated from the Nazis by the Red Army to elect their own leaders. And it becomes clearer and clearer that Stalin is not intending to do this, and the Western Allies decide to pursue increasing integration for their sectors in Berlin and turn it into more of a garrison. But it&#8217;s very hard to defend because it&#8217;s a pinprick on a map completely surrounded by Brandenburg and East Germany, which is controlled by the Red Army. And the Soviets believe it should be trivial to take it through blockade. In 1948, they try. And the Truman administration, with help from the British and others, decides to launch this airlift to prove our commitment. And various other contingencies are discussed that would involve the use of nuclear weapons, but the United States decides we&#8217;re not gonna go there yet, but we&#8217;ll threaten the Soviets that if you shoot the planes which are resupplying Berlin, then you&#8217;ll likely have nuclear war. And in 1948, &#8216;49, only we have nukes. So there&#8217;s lots of reasons why we would not wanna fight the Soviets, but we do happen to have nukes and they don&#8217;t. And we supplied Berlin, and it is an epic public relations victory as well as an operational success. Because not only do we supply Berlin through the winter with just a never-ending flood of planes landing, like, on the tarmac in Tempelhof, like a Swiss watch, but crowds of German schoolchildren, you know, stand and wave flags for them. And it&#8217;s clear that we are the good guys and the Soviets are the bad guys, and that we&#8217;re gonna continue this, and they give up. Now, it&#8217;s tempting to think, &#8220;Oh, awesome. So if China blockaded Taiwan, we would just do that.&#8221; Wrong. And the reason is the distances are much greater, there&#8217;s 10 times as many people, and the GDP is much bigger, and a lot of what they do is, like, industry, like making chips and things that the world needs, which is super energy intensive, and a lot of Taiwan&#8217;s energy system runs on gas, which you can&#8217;t fly in a plane. So for various reasons, it&#8217;s much, much harder to resupply Taiwan through an airlift than it was for Berlin. The other way in which the Berlin crisis is revealing is in the late &#8216;50s through 1962, under Eisenhower and Kennedy. At this point, the Soviets have nukes, and they decide to try again. And Khrushchev&#8217;s idea is, &#8220;Well, now that I have nukes, you wouldn&#8217;t dare.&#8221; And he ends up linking Berlin and Cuba, and he pushes us to the brink of a Cuban missile crisis, believing that if he stares us down over Cuba, he can also make a deal over Berlin. And that doesn&#8217;t work in part because he underestimates our willingness to go to the nuclear brink. There&#8217;s a bunch of lessons you can take from this history, but one of the big ones is Taiwan feels a bit like Berlin in this respect, and if you&#8217;re not prepared to go to the brink, you&#8217;re lost. But it is much more likely, given the fact that the US and China are nuclear powers, that Taiwan&#8217;s fate is determined by a crisis than by a war. Because if we do go to the brink, given the unimaginable stakes, it is quite possible that one side or the other just backs down with all of the reputational disaster that follows from that.</p><p><strong>Maggie</strong> 19:52</p><p>So coming back to the present, luckily today we are not on the brink, but that&#8217;s not to say that there isn&#8217;t anything happening in&#8212;</p><p><strong>Matt</strong> 20:00</p><p>We&#8217;re getting closer.</p><p><strong>Maggie</strong> 20:00</p><p>In conflict. Yeah, so can you give us what is the state today of conflict between Taiwan, China, the US, and, you know, in particular, what&#8217;s happening in the gray zone kind of beneath the threshold of a hot war?</p><p><strong>Eyck</strong> 20:17</p><p>There&#8217;s a few different levels to this. Let&#8217;s talk at the conventional military level, which is where most of your listeners are probably paying the most attention, which is this question of deterrence by denial. China&#8217;s building this capability to try to show that they could take Taiwan through an amphibious invasion. Now, an amphibious invasion will probably have multiple parts and multiple sequences. It would probably begin with cyberattacks and bombardment to soften the target, to trap some of Taiwan&#8217;s air force in their mountain hangars, maybe to disable some of their surface fleet, some of their air force. It would try to degrade Taiwan&#8217;s command and control infrastructure, probably try to take out some of their leadership, sow chaos, all of that. But then ultimately, if China wants to take Taiwan through an invasion, they have to deliver some number of tens of thousands of men across 100 miles of very challenging water, either by ships on the surface or by air. And this is very challenging to do because 10, 20, 30,000 men have to be resupplied with a whole lot of stuff, like millions of tons of stuff: vehicles, fuel, spare parts for the vehicles, medical, tents, other kinds of equipment, blood. And these things have to be, seriously, these things have to be delivered on schedule in what may turn out to be dozens or hundreds of crossings back and forth across the strait. And there&#8217;s only so many of these vessels that can do that job, and if a certain number of them are taken out of commission, damaged, destroyed, sunk, then you can have a scenario where China ends up with several thousand men on the island, but no ability to sustain them. They get massacred, and this is the worst possible outcome reputationally for China. So, the contest that the United States and its partners on one side and China on the other are engaged in on the deterrence by denial question is trying to change each other&#8217;s risk calculus or assessment of how likely it is that this could succeed. And so much of this depends on assumptions, on assumptions, on assumptions stacked on top of each other. You know, how much operational surprise do they get? How resilient is Taiwan&#8217;s communication system when certain nodes get whacked? What countries allow the US military access basing and overflight? And on and on and on. But both sides are presumably studying this with an incredible degree of granular detail, and they&#8217;re plugging it into simulations, and they&#8217;re running those simulations. They&#8217;re all probabilistic, and they&#8217;re running the simulations zillions of times and then seeing what percentage of the time it comes out with a win and with a loss. Obviously a real war, way more complex. These are not crystal balls, but just they&#8217;re indicative. And what the US and its partners are trying to do is multiply the sources of catastrophic risk that this kind of operation would face. And it&#8217;s even if Beijing has an assessment, it is something-something percent, they&#8217;re gonna have confidence intervals on that number. So it&#8217;s partly about shaping what that number is and partly about shaping their confidence intervals based on classified capabilities that you may or may not have. But that is obviously not the whole story. There is a whole other basket of activities that China&#8217;s doing to Taiwan short of kinetic attack that they hope will get Taiwan to submit without fighting. And I think obviously China would prefer to get Taiwan for free than to go through all of this cost and challenge and risk in an operation that could not possibly have 100% chance of success.</p><p><strong>Matt</strong> 24:15</p><p>Where are the conflicts in Ukraine and the Middle East instructive for how to think about deterrence in Taiwan, in the Taiwan Strait, and where are they not instructive?</p><p><strong>Eyck</strong> 24:26</p><p>Oh, that&#8217;s an interesting question. So I think the danger of over-indexing on the Ukraine case is that we assume that Xi Jinping&#8217;s personality is like Vladimir Putin&#8217;s. It&#8217;s not. It&#8217;s totally different, and his political system works differently, and that it&#8217;s a binary between whether he invades or whether he doesn&#8217;t. Let&#8217;s talk about personalities. Vladimir Putin is a risk-taker. He&#8217;s a gambler, and he&#8217;s invaded countries before. He invaded Georgia in 2008, and he got away with it. We let him get away with it. And then he took Crimea and started what was essentially a low-level war in Eastern Ukraine in 2014 that dragged on for years and years. And we also basically let him get away with it. We put sanctions on, but we did not resist what he was doing from a military point of view. So he did learn from those two experiences that he would probably not face serious military costs directly from NATO if he moved again against Ukraine. And he also revealed that that&#8217;s part of his pattern of behavior, so it should not have come as that much of a surprise when he went for the whole thing in 2022. Xi Jinping has a different personality. His whole modus operandi is different. He is more of a risk-taker when it comes to taking out threats to his rule at home, taking out rivals. But that&#8217;s because the stakes if he gets that wrong are existential for him. When it comes to moving in foreign policy, he tends to act in a much more gradual and systematic way, trying to change facts on the ground over time. Look at how he handled the South China Sea. Look at how he handled Hong Kong. In fact, he probably believes that he was extremely restrained letting the Hong Kong protests develop as they did over more than five years before he finally decided to put the kibosh on it in 2019. So everything we know about Xi Jinping&#8217;s mode of operating suggests that he would prefer a slowly tightening noose than some blitzkrieg over Taiwan. There&#8217;s also a difference between land war and maritime war, which is pretty significant. And maybe this is a separate question, but clearly drones matter a lot. Unmanned systems are changing the battlefield in Ukraine, and there will be significant read-throughs to the Indo-Pacific. But it&#8217;s just different when you&#8217;re operating across an enormous body of water, and the battle space is hundreds of times as big, and you&#8217;re routinely using either carrier-based aviation or very long-range precision missiles to deliver mass to target. Command and control, your ability to see and understand a battle space that is hundreds of thousands of square miles of size, is an entirely different technical problem than the one Ukraine and Russia are facing in their land war today. Relatively speaking, C4ISR matters much more, and the lesson from historical maritime war seems to be because of that. If you can see your enemy and deliver an effective first shot, that can be it. So maritime wars, once they start, tend to have much more decisive conclusions that come very quickly. And you can tell a story either way about what that means. But it does suggest that a lot of the things that we believe we have to build in Ukraine to protect the rest of Eastern Europe may not be exactly the things we have to build in the Pacific.</p><p><strong>Maggie</strong> 28:34</p><p>Yeah, I think you were reading my mind for the next question, which is one of the major themes, of course, coming out of the conflict in Ukraine and the Middle East is the importance of commercial space like Starlink, the importance of drones, the importance of AI for targeting, the importance of electronic warfare, et cetera. What role will some of these emerging technologies play in a future conflict, potentially in the Indo-Pacific between China, Taiwan, and other allies?</p><p><strong>Eyck</strong> 29:03</p><p>Well, immensely important role. Let&#8217;s start with the invasion scenario. So Taiwan has to... Let&#8217;s assume that Taiwan is being invaded, they&#8217;re being bombarded. They have to sustain the resilience of their command and control, so they actually know what is happening and they can coordinate their forces, and then they have to identify which are the most dangerous approaching craft, whether in the air or on the surface, and then they have to take them out with an economy of resources because Taiwan during an invasion is gonna be very hard to resupply. Ukraine has depth, they have geographic depth, and they have a land border with NATO, and Taiwan is something like one seventeenth the size. So they will have to conserve their forces and use their missiles, unmanned systems, and other fires in a much more disciplined way. So that means in a context where Taiwan doesn&#8217;t have access to Starlink, the technologies that will enable Taiwan&#8217;s armed forces to have truly resilient C4ISR are fundamental. There&#8217;s a number of reasons why Taiwan doesn&#8217;t have Starlink. One is that they don&#8217;t trust Elon, and they probably have good reasons not to trust him, given Elon&#8217;s recent comments in China. But the other thing is, unmanned systems where unmanned surface vessels are probably gonna matter relatively more. There is a maritime fight in the Black Sea. The Ukrainians have been very effective at it. But if you assume that China will generally, in invasion, try to take most of the men across the strait on slow-moving ferries, the question is how you can create risks and complications for those ferries at a relatively low cost. And an indigenized supply chain to make USVs of various sizes is, I think, 100% essential, mission-critical for Taiwan. They&#8217;re doing that. They&#8217;re ramping, and if Taiwan can do it right, they could potentially become a provider of those capabilities to others in the region. And I could go on all day about this. I think these are two of the big ones. The third is air defense. Taiwan is close enough to China&#8217;s mainland bases that they would be saturated with missile and drone strikes, just enormous strike packages against their critical infrastructure, against military targets, possibly against civilian targets. And force conservation is gonna be an incredibly important principle in absorbing that, those opening barrages. Taiwan cannot afford to expend its precious air defenses on cheap, low-value drones. And having an integrated air and missile defense system is non-negotiable for them. Probably exploring some creative counter-UAS capabilities as well. The good news is that Japan needs exactly the same thing, South Korea needs exactly the same thing, the Philippines needs exactly the same thing. So we have a basis, if we can get our act together, to create one great big allied market and create an overwhelmingly powerful demand signal for whatever producer anywhere in the world can generate these capabilities. And I&#8217;d like to see us move in that direction.</p><p><strong>Matt</strong> 33:05</p><p>Yeah, are we moving in that direction, or what are the hindrances to having a allied demand signal for these capabilities across the Indo-Pacific?</p><p><strong>Eyck</strong> 33:18</p><p>Well, I think we&#8217;re not yet at a point in the American debate where we&#8217;ve accepted that we&#8217;re just not gonna make most of this stuff ourselves. I mean, it seems obvious to me, and I argued in my previous book, The Arsenal of Democracy, that literally the only way that we can get the capabilities we would need to fight and win a war with China is gonna involve buying at least components, if not finished stuff, from Japan, Taiwan, and South Korea, &#8216;cause we can&#8217;t make anything in this country. And if we make anything, it comes in late and over budget and often poor quality. And with no offense to the many exciting defense techs that are popping up everywhere, including at Stanford, I mean, there was a wonderful Wall Street Journal piece the other day about, I think it was in the Journal, about trying to make the board game Monopoly in the United States, and the conclusion was it cost twice as much, the pieces were crap, and they had to buy the dice from China. So if you can&#8217;t make a Monopoly set, why would we think that we can become a globally competitive drone power? We&#8217;re just not going to be. But if that is true, then the implications for our strategic posture are enormous because it means you are gonna become dependent on someone else for a capability that is life and death in fighting any future war. So which of our partners are we willing to become that dependent on? And our partners are gonna ask the same question. So I think there&#8217;s an overwhelmingly strong case for involving the Japanese. But do we want the Taiwanese to play a role in this as well? We already depend on them for TSMC. We haven&#8217;t spent much of this conversation talking about chips, but, like, clearly one of the reasons we care about Taiwan is that they make all the GPUs that are powering AI. So if we&#8217;re depending on them for the GPUs, why not also depend on them for the motors or the actuators or the sensors or the other ingredients of making a drone? It&#8217;s one thing to say that on a podcast. It&#8217;s another thing for the Pentagon to put in writing, &#8220;Yeah, we&#8217;re gonna become strategically dependent on Taiwan to make drones in the United States.&#8221; But the co-production thing is the only way to do it, and this is a conversation that has to include at minimum the Indo-Pacific allies plus Taiwan, but ideally also the British, whichever European militaries are interested in being involved, because they&#8217;re struggling to make drones too, the Ukrainians, who have their own supply chain challenges, who would struggle to do bilateral cooperation with Taiwan but are totally happy to access our capital markets, and frankly the Canadians too, because if the club is that big, maybe the Canadians will come to the table. So the approach should be you get all of the allies together and you say, &#8220;We want to become an integrated block to make drones so we don&#8217;t depend on China for the drone supply chain. Who are we comfortable including in the club? Do we not wanna become more than 70, 80% dependent on any one place? Okay, fine.&#8221; What follows from that in terms of setting specifications to make parts interoperable across different kinds of unmanned systems? Who&#8217;s gonna be allowed to buy from whom? How are the co-production supply chains going to work? It just seems obvious to do the economy of scale, but actually accomplishing that is a diplomatic lift, which is easier said than done. And that is why it hasn&#8217;t happened yet.</p><p><strong>Maggie</strong> 36:59</p><p>Can you tell us what is the current state of the Chinese military&#8217;s investment in some of these emerging commercial technologies, and how do we, you know, the US and Taiwan stack up?</p><p><strong>Eyck</strong> 37:10</p><p>Well, that&#8217;s a broad question. So China is investing in a whole array of technologies. Now, how good those actually are is another question. Now, I like to say the CCP loves things that it can count, and it hates things that it can&#8217;t count. And the way that their system works is they&#8217;ll have a meeting and they&#8217;ll decide we&#8217;re gonna make X many missiles, Y many drones, Z many submarines, and then they go out and do that. In the same way that every year they have a meeting and they say our GDP is going to be 5%, and if their GDP is actually only on track to be 2%, they dig holes and fill them up again or build bridges to nowhere. That&#8217;s how their system works. These numbers are inputs, they&#8217;re not outputs. So there is this lingering question about quality that applies to everything that they do. And quality is harder to measure, and this is a source of insecurity for them.</p><p><strong>Maggie</strong> 38:16</p><p>I mean, we hear stories, right, of missile silos filled with water instead of gasoline, right?</p><p><strong>Eyck</strong> 38:21</p><p>Well, if you wanna think about, like, what levers we can pull to make Xi Jinping think twice about the assuredness of his military forces. Like, you&#8217;re not gonna make him doubt that he has X many drones, Y many missiles, Z many submarines, and you&#8217;re not going to make X plus one, Y plus one, Z plus one because they&#8217;re the Chinese Communist Party. So if you can&#8217;t beat them in quantity, you must beat them in quality, and you must inject uncertainty into his thinking about the extent of that qualitative gap, that you must show him that you lead technologically, and you must make him insecure about what that lead means, and so he doesn&#8217;t know how much quantitative overmatch he needs to compensate. That is, by the way, to put it in a different way, what we did in the last 15 years of the Cold War that beat the Soviet Union, is that starting in the second half of the &#8216;70s, heading into the &#8216;80s with a bunch of visionaries, Harold Brown and others, we decided that we would bet on going to space for a lot of our ISR, and this was not a sure bet at the time. It was a moonshot. GPS was almost canceled multiple times. And this is a whole saga which I talk about in a previous book. But the fact that we did it, and then we displayed those capabilities to the Soviets by doing deterrence patrols that shocked them, that we could just go dark and pop up someplace else, made them unsure about what it would actually take to catch up and conclude the only possible approach was arms control to rein in our capabilities. We need to do something similar for China. And arguably, if you want to get China to the table in AI arms control too, we have to do something like that. But in cyber, in other domains where quality is hard to measure, it&#8217;s very important to signal our lead when we have it. And we need to invest in the sources of our technological strength because they are marshaling a lot of resources to catch up.</p><p><strong>Matt</strong> 40:41</p><p>One major stakeholder in all this we haven&#8217;t talked about much is NATO and Europe. Obviously that&#8217;s a frequent topic of discussion and debate today. What role do you see NATO playing, especially now in deterrence in the Indo-Pacific, not just militarily, but kind of across the different pillars you talk about in the book, and especially economically? And what&#8217;s your outlook on their role in all this?</p><p><strong>Eyck</strong> 41:11</p><p>NATO remains fundamental because there is one continental scale land war that is happening in the world right now, and it&#8217;s on NATO&#8217;s eastern border. And if we don&#8217;t win it or settle it on favorable terms, it will spread. There is no doubt in my mind about that. Putin will not stop. Therefore, NATO needs to remain active. NATO members need to pay their way. More important than spending the money, they have to spend the money on the right stuff. They have to move towards more efficient co-production of the critical stuff that&#8217;s needed. They have to have a better pipeline to get the learnings from Ukraine and integrate them into European militaries. I mean, who among us really believes that if, God forbid, Putin were to roll tanks across the border, that NATO members would fight as effectively with drone warfare as the Ukrainians? I&#8217;m not convinced. Who among us believes that if North Korea were to try this, try out some of these tactics, techniques, and procedures on the South Koreans, that the South Koreans would be prepared to fight as effectively as the Ukrainians? I don&#8217;t know. So NATO has a role to play in bringing these learnings that Ukraine is acquiring and paying for in blood, to the rest of the coalition. I think NATO also has this globally stabilizing role, even if NATO allies would not be directly involved in the conflict in the Pacific, because China doesn&#8217;t want to initiate a chain of events that breaks their relation with Europe. But for reasons of geography, for reasons of politics, for reasons of economy, the European Union is not really much of a player in the Taiwan issue, and they are not part of the core coalition that would have to go toe-to-toe with China if it came down to it in the Pacific. So we should not delude ourselves, and we should also not pretend that you can just copy and paste the NATO model to the Pacific. We should be wiring together our Asian allies more effectively. I hope that&#8217;s come through in the conversation. I really think we should, and I think we can, but the way to do it is not, like, to build a cathedral and then try to wire it. You build the wiring first, and then if you want to later, you put some masonry and stained glass windows in. And so the interesting thing to me is what the US, Japan, and Australia, for example, are doing on a trilateral basis to conduct joint fires, and we&#8217;re demonstrating that in exercises like Balikatan. Bringing the UK in through the AUKUS pact, which is not just about subs, but it&#8217;s about hypersonics and all these emerging technologies. How do we fold Japan in or get Japan to a place where they can join that pact? And then because this is not an all or nothing proposition, how do we wire our respective systems so we can collaborate with the Indians where convenient, even if it&#8217;s just for ISR? How do we wire ourselves up to talk to the Vietnamese? Obviously, we will not integrate with Taiwan&#8217;s military the way we do with Australia&#8217;s, but how far can we go? Rethinking this as a sliding scale. A sliding scale or as a ladder that you can build, climb step by step, I think that kind of federated architecture is much more attractive to everyone, including us, than a NATO model, which has benefits but is also kinda cumbersome, right? Because NATO has to move by consensus. So NATO is wonderful. We gotta protect it, we have to preserve it, and in the Pacific we need to build something a little different.</p><p><strong>Matt</strong> 45:11</p><p>Yeah. One other topic I wanna make sure we went into a little bit more depth about was AI. I mean, you have an entire section of your book where you talk about the role of AI in strategic deterrence specifically. And obviously the US and China both depend on Taiwan for the most advanced chips. I think most of our listeners know about that at this point, so we don&#8217;t need to talk about that in a ton of depth specifically. And I think you wrote that 99% of NVIDIA&#8217;s most advanced GPUs are made in Taiwan. But this particular issue strikes me as one of the most confusing parts, one of the most confusing dynamics of the Taiwan scenario, just given that the government&#8217;s understanding of the role of AI is changing really fast and the models themselves are continuing to improve, like, super rapidly. So kind of across the board, and it&#8217;s a broad question, but if you were briefing US policymakers, what framework would you use to explain what role AI is gonna play in all this, especially as it&#8217;s just evolving so fast?</p><p><strong>Eyck</strong> 46:13</p><p>Okay. That&#8217;s a nice way to end. I wanna make three points. First, I wanna talk about strategic deterrence and how it&#8217;s become fuzzy in a very scary way. Next, I wanna talk about hybrid war and the gray zone. And then third, I wanna use those two things to talk about AI. The strategic deterrence used to be simple. If I have nukes and you have nukes, I can nuke you, bad for you. But if you can absorb that and nuke me back, it&#8217;s bad for me. And if both of us have a secure second strike, it&#8217;s in neither of our interests to move first. So I just explained that in 15 seconds. Tom Schelling won a Nobel Prize for explaining that and other things, and building a game theoretic architecture around it, and that was nuclear strategy basically for most of the Cold War. Now, that doesn&#8217;t end nuclear competition. We&#8217;re, you know, competing with the Soviets over intermediate range missiles and air defense, ballistic missile defense all through the end of the Cold War. But basically, in a land where strategic deterrence is nuclear deterrence and second strike capabilities exist, it&#8217;s simple. We don&#8217;t live in that world anymore because our nuclear command and control systems are now multimodal. They&#8217;re based on space-based architectures that can be attacked through all kinds of means, computer systems which can be attacked using all kinds of means, and the number of tools that you can potentially use to go after an adversary&#8217;s critical infrastructure, including chem, bio, and other things, are becoming easier to access. And as cyber enables all sides, including non-state actors, to reach into others&#8217; critical infrastructure and tinker, it raises real questions of what strategic deterrence even means in the 21st century. And that&#8217;s a very scary question, and it brings us back to some debates in the Cold War about what tactical nuclear weapons might do to strategic stability, like whether it might be tempting to use a tactical nuclear weapon that could take out just a building or a city block. Maybe it won&#8217;t be such a taboo if it can be targeted in that way. Second point, hybrid war. We are not at war with China and Russia, but we&#8217;re not at peace with them either. Hybrid war is relentless. It&#8217;s happening globally. It basically is a euphemism for acts of terrorism, and it&#8217;s happening all over the place. China cutting undersea cables in the Baltic, cutting undersea cables connecting to Taiwan, using lasers to jam satellites. Russia sending explosive packages to major German cargo airports. I mean, I could go on. This is ramping up in a number of domains simultaneously, and it&#8217;s really scary because what it is really targeting are the sinews of commerce in the commons, particularly the sea lanes through which the energy and people and supplies on which our economy depends for its lifeblood depend. And we see an example of this in Hormuz. Hormuz isn&#8217;t fully open, and it isn&#8217;t fully closed. And what do you do with that if you&#8217;re no longer in a world of binary open and closed? This is how China plans to move against Taiwan, through an all-around strangulation campaign that targets the shipping and eventually aims not to shut it down but to take it over, to dictate the terms on which it can flow. We do not yet have a doctrine for how we deal with that, and the proof that we don&#8217;t have a doctrine is that the bad guys&#8217; use of it is going parabolic. And if it continues to go parabolic, eventually basic functions of the global economy will stop working. So this is not a peripheral question. This matters just as much as deterring an invasion. Now, how does AI play in? AI just turbocharges that problem because it offers all of these ways to make trouble for other countries in ways that are actually really damaging or socially destabilizing, but hard to attribute and below the level of kinetic, actually kinetic attack. You can potentially deliver strategic effects with AI. An agent that goes rogue, &#8220;Oh, so sorry it escaped from a lab and took out your power grid. Sorry about that.&#8221; I mean, it introduces so many hundreds of scary scenarios at the same time, and we should think of it as an arms control problem from that point of view. But I think we also have to be realistic that the Chinese and the Russians think they&#8217;re winning in this fight and won&#8217;t change their minds unless they think we have big-time qualitative overmatch. So I think AI is very scary for this reason, because it makes this definition of strategic deterrence fuzzier because it intensifies the hybrid war. I don&#8217;t see a clear solution other than pacing the frontier.</p><p><strong>Maggie</strong> 51:54</p><p>Eyck, one last question to close us out. What is the thing that you most see startups and other American technology firms and policymakers most misunderstand or get wrong about the situation with Taiwan?</p><p><strong>Eyck</strong> 52:07</p><p>That we can deter Xi Jinping, that this is not a lost cause. How do I know? Because we&#8217;ve deterred him so far. The guy&#8217;s been in power for, like, 14 years. Every single day he has woken up and said, &#8220;Not today.&#8221; So if the question is, can you deter him from pressing the button? This is the big one. When the missiles fly and we&#8217;re gonna whack American bases, and we&#8217;re going to blockade the island and send the global economy into free fall, I don&#8217;t think he&#8217;s gonna press that button. Not because he wouldn&#8217;t under the right circumstances, but because the United States and Taiwan and our other friends and partners are stepping up and continue to step up so that he doesn&#8217;t see a clear pathway to success. So if that&#8217;s your definition of victory, I think we are succeeding and we can continue to succeed. What people don&#8217;t fully understand is that that is not the whole story. This hybrid gray zone question of the boundary between peace and war getting blurred and pushed, we lack a doctrine for this, and we lack an understanding of the kinds of effects we can deliver in response that will be equal and opposite and proportionate, that will make our adversaries think twice. Some of these may not be kinetic military in nature. Some of them may be economic tools. A lot of them may be cyber-related. Some of the most valuable in China&#8217;s case may be information war capabilities. But until we have a doctrine and then a set of capabilities that we can deploy in service of that doctrine, this feeling that the international architecture that holds the commons up is breaking down, that&#8217;s gonna accelerate. Our supply chains are gonna get less secure. Our societies are gonna get less resilient. And this is ultimately something that the Pentagon has to lead on by clarifying that this is a priority. But if and when they do, and I hope they do, we are gonna need industry to step up, with ideas, with innovations, with products that can be made available to the allies to respond.</p><p><strong>Maggie</strong> 54:33</p><p>Well, thank you so much for coming on the show. I think our listeners probably learned a lot about the current state of Taiwan deterrence, and all things China. So thank you so much for your time.</p><p><strong>Eyck</strong> 54:43</p><p>Thanks for having me on. This was great.</p>]]></content:encoded></item><item><title><![CDATA[🎙️ Ep 32 - Danti AI: How AI is Revolutionizing Intelligence Analysis]]></title><description><![CDATA[AI is revolutionizing intelligence analysis.]]></description><link>https://maggiegray.us/p/ep-32-danti-ai-how-ai-is-revolutionizing</link><guid isPermaLink="false">https://maggiegray.us/p/ep-32-danti-ai-how-ai-is-revolutionizing</guid><dc:creator><![CDATA[Maggie Gray]]></dc:creator><pubDate>Fri, 30 Oct 2026 18:26:23 GMT</pubDate><enclosure url="https://api.substack.com/feed/podcast/222827397/c7636fbd58cc07b5a58de9fe183d38f5.mp3" length="0" type="audio/mpeg"/><content:encoded><![CDATA[<p>AI is revolutionizing intelligence analysis. On the newest <strong><a href="https://www.linkedin.com/company/mission-matters-podcast/">Mission Matters Podcast</a></strong>, <strong><a href="https://www.linkedin.com/in/david-rothzeid-7a116961/">David</a></strong> and I sit down with <strong><a href="https://www.linkedin.com/in/jessekallman/">Jesse Kallman</a></strong>, the co-founder and CEO of <strong><a href="https://www.linkedin.com/company/dantiai/">Danti</a></strong>, to discuss how their customers like <strong><a href="https://www.linkedin.com/company/usspaceforce/">United States Space Force</a></strong> and <strong><a href="https://www.linkedin.com/company/nga/">National Geospatial-Intelligence Agency</a></strong> use AI tools like Danti to analyze intelligence faster and better than ever before.<br><br>We discuss:<br> &#127757; How analysts are using Danti around the world: from Venezuela to NATO to PACOM<br> &#128187; How Danti applies to a variety of use cases including defense, insurance, disaster response, and more<br> &#128752;&#65039; How Danti integrates and analyzes many multi-modal data sources including geospatial data, signals intelligence, social media data, and more</p><p>As always, please reach out if you or anyone you know is building at the intersection of commercial technology and national security. And, if you&#8217;re interested in working at a Shield Capital portfolio company or another national security focused startup, please fill out this <a href="https://workindefensetech.netlify.app/">form</a> to &#8220;Work in Defense Tech!&#8221;</p><p>You can listen to the podcast on <a href="https://open.spotify.com/episode/3QgqwhYuVygVFuV946IE5D?si=6Bs0U6U0TO2EH2kRUIgeVQ">Spotify</a>, <a href="https://youtu.be/1qMmDhqDJVY">YouTube</a>, <a href="https://podcasts.apple.com/us/podcast/danti-ai-how-ai-is-revolutionizing-intelligence-analysis/id1807120572?i=1000798932960">Apple</a>, the Shield Capital <a href="https://shieldcap.com/episodes/danti-ai">website</a>, or right here on Substack.</p><p class="button-wrapper" data-attrs="{&quot;url&quot;:&quot;https://maggiegray.us/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe now&quot;,&quot;action&quot;:null,&quot;class&quot;:null}" data-component-name="ButtonCreateButton"><a class="button primary" href="https://maggiegray.us/subscribe?"><span>Subscribe now</span></a></p><p class="button-wrapper" data-attrs="{&quot;url&quot;:&quot;https://workindefensetech.netlify.app/&quot;,&quot;text&quot;:&quot;Work in Defense Tech&quot;,&quot;action&quot;:null,&quot;class&quot;:null}" data-component-name="ButtonCreateButton"><a class="button primary" href="https://workindefensetech.netlify.app/"><span>Work in Defense Tech</span></a></p><p><strong>Transcript</strong></p><p><strong>Maggie</strong> 00:36</p><p>On this episode of the Mission Matters podcast, we sit down with Jesse Kallman, the co-founder and CEO of Danti AI. Danti is building the future of AI-enabled intelligence analysis. Its platform runs a team of AI intelligence analysts to answer questions by integrating and parsing through diverse data sources, including open source intelligence like social media data, geospatial intelligence like satellite and drone imagery data, sensor data, and more. Their product is used by customers across the US government, including the Space Force and National Geospatial Agency. Before founding Danti, Jesse had a long career in the defense industry across both startups and defense primes, including Northrop Grumman, Booz Allen Hamilton, Airbus, Xwing, and more. Jesse, thank you so much for joining us on the Mission Matters podcast.</p><p><strong>Jesse</strong> 01:27</p><p>Thanks for having me.</p><p><strong>Maggie</strong> 01:28</p><p>So first question, a little bit of a softball. You all of course have .ai in your URL, which is very hot these days with startups. Everywhere you look, people are talking about AI, AI agents, both inside and outside of the US government. So I wanna ask, what does AI agents for defense mean to you, and in the actual context of Danti, what all are you actually doing with AI?</p><p><strong>Jesse</strong> 01:56</p><p>Yeah, it&#8217;s a great question. We get asked about this so often. Sometimes people even laugh when they hear the phrase AI agent because it can mean so many different things to so many different people. And so from our perspective and how I think about AI agents, it&#8217;s essentially tools that can execute tasks that are sometimes quite complex, in a sequence. And so they understand how to run the sequence. They understand the steps of the sequence. They understand, based on key phrases from a person, what they&#8217;re trying to accomplish &#8212; how to actually go and do that work. And so how Danti thinks about that in the context of intelligence analysis, or just supporting war fighters overseas that just need key information, we like to bring a variety of different tradecraft and skill sets into these AI agents that understand, based on a person&#8217;s question: is this a maritime question? Are they trying to solve for a natural disaster? Is this a border issue? Or is this just a simple data request that can be solved from a summarization of 50 tweets, two news articles, and a coincidental image? And so that&#8217;s how we think about agents &#8212; tools that can go, once tasked, and execute multimodal or multidisciplinary tasks for the user.</p><p><strong>Maggie</strong> 03:10</p><p>So perhaps by design, I think your average person is not super familiar with what an intelligence analyst in the intelligence community or in the US military actually does. So can you paint a picture? What does an intelligence analyst job look like pre-Danti, and then where does Danti fit into their workflow?</p><p><strong>Jesse</strong> 03:30</p><p>Sure. So a lot of our team comes from the defense and intelligence community, and they&#8217;ve worked in many different agencies across many different disciplines. I myself have seen a variety of different disciplines, but I think it boils down to a few key things. It comes from: someone somewhere needs information for some specific purpose, and something like a request for information, or an RFI, will come in to an organization &#8212; says, &#8220;I&#8217;m looking for X,&#8221; or you&#8217;re providing a briefing to Y. And typically that analyst will, one, take that request, and based on their prior background and knowledge and their level of experience, will know: to solve this and answer this question, I have to execute these steps. I&#8217;ll typically go across a variety of different systems. So let&#8217;s say in the case of a GEOINT analyst &#8212; they&#8217;re being asked about activities in a port overseas. What they&#8217;ll typically do is, that port gives them a key buzzword, where they&#8217;ll know: okay, we have things like port boundary information. What is the actual boundary of that port? What&#8217;s encapsulated there? What other data sets? Do we have any visual imagery data sets? Are we talking unclassified, classified? Say, at the unclassified level, what data repositories do I have access to? Do I have the logins that I know, based on my background, I can now go and pull information? The next thing is more of that temporal context. When are we talking about? Are we talking yesterday, two months ago, three months ago? Is this a pattern thing, or a series over time? And they have to start to build that temporal context as well. So now they&#8217;ve got the spatial, they&#8217;ve got the temporal, and then they start sourcing. So let me pull together the key information that I have across that spatial-temporal context, and this can take days in many cases. And once they&#8217;ve pulled all that together, then they can begin the analysis work. So what&#8217;s actually happening here? What am I observing? What&#8217;s happening in the surrounding areas? And can I determine what it is this person is ultimately asking for? And if I can, I then bring that all together with supporting evidence into a report that&#8217;s then delivered. And so that&#8217;s one example of how we&#8217;ve observed it over the last many years.</p><p><strong>David</strong> 05:38</p><p>Awesome. Well, maybe taking it from the abstract level &#8212; SpaceWorks just named you a success story, I think last month. So maybe go into a little bit of detail about what you&#8217;ve been doing with Space Force and various combatant commands, and how they&#8217;re leveraging Danti today.</p><p><strong>Jesse</strong> 05:55</p><p>Yeah, great. We were happy to see that story come out on some of the great work we&#8217;ve been doing, initially across the Space Force&#8217;s TAC-SRT program. It&#8217;s since been renamed to, I believe, BATS. But&#8212;</p><p><strong>David</strong> 06:08</p><p>And what does TAC-SRT stand for?</p><p><strong>Jesse</strong> 06:10</p><p>It&#8217;s Tactical Surveillance Reconnaissance, I believe. I forget the exact terminology. But yeah, it&#8217;s supposedly for responding quickly to combat and command needs for commercial data that&#8217;s publicly available and publicly shareable with allies and partners. And some of the key use cases there are things like supporting global natural disasters, maritime activities, border conflict issues. But anywhere the US really needs to be able to provide this information at a fully unclassified level to its allies and partners in the region, so that the US can provide that information to support whatever needs there might be. And so that&#8217;s been the primary focus of that program. I think it&#8217;s been pretty revolutionary, being able to bring in so many different commercial vendors &#8212; whether they be imagery providers, analytics providers, analysis services companies &#8212; to, again, take in-turn requests that could take a week before, to maybe a couple days. And where Danti&#8217;s been supported is: now, how do we take that request and potentially automate it all the way, initially? Or how do you understand the data landscape before you go and execute those tasks? And maybe to give you a specific example, since this is recent, with US SOUTHCOM. So the earthquakes in Venezuela &#8212; that was something that Space Force supported pretty heavily. One, in providing a lot of information very quickly to local NGOs and other governments in the region. Obviously not able to provide classified information, but a lot of their requests are: what are the status of the ports? Are there slips to bring aid in via ship? What&#8217;s the status of the airport? Are the runways destroyed? What sort of hospital infrastructure &#8212; what does that look like? And so what Danti provided in that case is, an analyst at US SOUTHCOM, TAC-SRT, the Joint Commercial Operations Cell, can just come in, in natural language, type: &#8220;What are the status of the top three ports in Venezuela in the last forty-eight hours?&#8221; And the system, in a matter of seconds, will synthesize thousands of news articles, tweets, information across the Internet. It&#8217;ll cross-correlate what it finds when it determines where those ports are. I mentioned before pulling that information on the port boundaries, so understanding where the ports are. It&#8217;ll look at broadcasting ships via AIS. It&#8217;ll pull coincident imagery, so you get a visual understanding. And then it provides a simple synthesized summary that someone, in a couple clicks, can put into a briefing or PowerPoint slides and send as an email to an NGO. And so that&#8217;s what Danti provides &#8212; that ability to really automate across those different government and commercial systems and get the user directly to that end report they need.</p><p><strong>David</strong> 08:51</p><p>Maybe just tell me &#8212; but for Danti, in the case of this Venezuelan earthquake and being able to pull in a lot of information quickly, how would this otherwise go down? What are the analysts using today without Danti, or yesterday without Danti?</p><p><strong>Jesse</strong> 09:11</p><p>Yeah, I was actually there in the ops room at SOUTHCOM for some of this as well, and it was interesting to see the ops center, where you have a bunch of different teams &#8212; mostly staff from different parts of SOUTHCOM, from mission partners, other agencies &#8212; and they were fielding requests either by phone call, WhatsApp message, whatever the form, and they&#8217;re bringing that into the ops center. The ops center is typically, again, very manually going by and saying, &#8220;Okay, based on this request, who has this information? Who can get on the phone with another partner agency and bring it together?&#8221; And it was being pieced together by different commercial companies, contractors. They have a common operating picture up in the ops floor where they&#8217;re integrating different datasets to see if they could do it there. And so that&#8217;s how it&#8217;s been done. Where Danti provided value was, we showed up with a lot of automated integrations to a lot of the systems they were pulling from already, in a lot of the modalities: air traffic data, maritime data, imagery, open-source intelligence. We would simultaneously take those RFIs coming in, also type them in to see if the system could actually just spit the answer out completely automated &#8212; completely alleviating all those people having to waste time calling across their different networks to piece the information together.</p><p><strong>David</strong> 10:29</p><p>So, Jesse, maybe building off of the work that you&#8217;ve been doing with SpaceWorks, talk to us a little bit about some of the international cooperation and working with some of the combat commanders. It seems as though international partners are starting to leverage a lot more of the unclassified data that&#8217;s coming off of a lot of different capabilities, whether it&#8217;s commercial GEOINT providers or otherwise. And just how do you see the international market shaping up?</p><p><strong>Jesse</strong> 10:58</p><p>Yeah, I think that&#8217;s a great thing, and it&#8217;s probably one of the biggest growing areas we see in general right now. And maybe a more US-centric example would be &#8212; we actually did a very rapid deployment with USSOCOM, with NATO, during an exercise called Trojan Footprint this past summer, where we got contacted one morning and there was a need for equipping a lot of allied forces in Europe with information tools, but there was nothing that they could do quickly. And within two or three hours, we had a deployment available for SOCOM that allowed them, plus a number of different NATO countries &#8212; I believe it was about eight or nine &#8212; and all of their special operations forces to connect unclassified information from open source, new social, imagery, a variety of different things. And now any SOF operator in any language could come into one terminal and ask a question and get provided the entire coalition&#8217;s information in seconds. And we saw anyone from Polish and Hungarian to French forces just get dropped into our software and start running things like GEOINT, SIGINT, OSINT workflows all together. And I think, more broadly in the international market, this is a function of &#8212; most countries do not have the infrastructure the US has. They don&#8217;t have tens of thousands of highly skilled analysts sitting in offices waiting to support and answer questions and fuse information. A lot of these foreign partners know the information exists. They want control. And I think what we&#8217;re hearing from a lot of the space companies &#8212; a lot of even companies like Palantir have coined this data sovereignty thing around the world &#8212; is that all of these international organizations now, they want their own data capabilities. They want their own satellites. They want their own feeds to the key information they need, but they just don&#8217;t have the massive trained analyst force to do it. And I think that&#8217;s a great opportunity for companies like Danti, where we&#8217;re already providing a lot of that encoding of when is it the right time to use a synthetic aperture radar satellite versus a bunch of tweets, versus the beacon off a ship. And so how does someone like the Korean government or the Philippines government better leverage all of this information with an analyst &#8212; doesn&#8217;t really matter how well trained, or their background, whatsoever. They&#8217;re able to control their data environment and control their own information that&#8217;s getting out to key users.</p><p><strong>David</strong> 13:20</p><p>That&#8217;s awesome. I guess a lot of what you&#8217;re talking about, with all this data aggregation and fusing, I will say, seems a bit reminiscent of Palantir, and I do feel like they&#8217;re kind of an 800-pound gorilla across the software landscape within the department. How do you view Palantir, and where does Danti fit into the tech stack or ecosystem of tools available to end users?</p><p><strong>Jesse</strong> 13:47</p><p>Yeah, I think Palantir obviously has been around a long time, and I think they&#8217;ve done a lot of amazing work in revolutionizing how complex organizations connect silos of data and build useful applications on top of that, and coining some of these phrases like data ontologies and how do you build relationships. So I think they&#8217;ve really advanced how a lot of different applications and different folks in the community can operate. And I think where Danti fits in &#8212; we, as a company, provide capabilities, one, that help organizations do a lot of these data integrations connected in more of an automated way, where you can just tell the system what this data is. We provide a lot more in-depth, very detailed workflows for that end user, who is likely not going to use a more complex system like a Maven Smart Systems or something like that. But really, we deploy within that ecosystem. So today, we&#8217;re actually even co-deployed with Palantir in organizations like the US Army, and in that Venezuela example. We are able to feed information into those common operating pictures like a Maven Smart Systems, where those are really powerful views of the entire visual data landscape. Whereas in Danti, you&#8217;re asking an agent &#8212; essentially an analyst &#8212; to start running cross-modal workflows for you, doing a lot of fusion, doing some of that analysis, to then spit it back into those common operating pictures. So I think Palantir has laid the landscape to making a lot of those data feeds more easily integratable and common across the entire enterprise. And I think it&#8217;s paved the way for a lot of companies at the application layer like ourselves, who are doing a lot of great work, to take the last step with a lot of these organizations.</p><p><strong>Maggie</strong> 15:40</p><p>So Jesse, from the use cases you&#8217;ve been describing, it sounds like you&#8217;re able to work with a number of different combatant commands, a number of different services on different use cases, but you&#8217;re able to use one platform for all of those. So can you talk a little bit about how Danti is flexible and able to work on each of these different tasks?</p><p><strong>Jesse</strong> 16:01</p><p>Yeah. I think we talked a little bit about some of the bigger players in the space, but there&#8217;s a lot of organizations that don&#8217;t need that level of infrastructure rebuild, where, again, we can step into some of these mission partners who have a very simple... I mentioned maritime domain awareness, where they already have some of their own infrastructure, their own ecosystem of vendors. Danti will allow them, in a matter of hours or even a couple days, to completely connect that disparate information data environment, and then have someone of any skill level now be able to run the workflows of what were highly expert, 15-year subject matter experts. And now it alleviates those subject matter experts to focus on those really difficult tasks, like the ones that absolutely need a human spending hours researching and analyzing. We can now alleviate that, so we provide that data integration infrastructure layer for them. We provide all the workflows on top of it. We provide a lot of the encoded tradecraft so that, again, anyone from a mission partner that can&#8217;t spell, or doesn&#8217;t know what SIGINT means or OSINT or any of those things are &#8212; they&#8217;re able to run those workflows across those different tradecraft areas.</p><p><strong>Maggie</strong> 17:13</p><p>And then expanding that further, so CENTCOM can use this, PACOM can use this, but you also have commercial customers using this. Can you tell us about some of the commercial use cases for a tool like this?</p><p><strong>Jesse</strong> 17:24</p><p>Yeah, just like the US government has issues connecting highly disparate and very spatial, anchored-in-the-real-world datasets, so do insurance companies, so do commercial real estate companies, so do global logistics companies. And so some of the things we&#8217;ve seen are anything from, again, global logistics companies that wanna understand impacts to their facilities due to ongoing conflicts around the world &#8212; where cargo may be stuck in the seas due to conflicts outside of Iran &#8212; to even real estate investors that are trying to understand the complexities and nuances between things like foot traffic or traffic data around a location and how that relates to demographics of a local neighborhood or population changes, or even the structural information of a building, and how do you use all of that information together to help with things like real estate acquisition that today also require a team of expert brokers to pore across this information. So that&#8217;s how we think about it, where you have this anchored-in-the-real-world problem that is a huge mix of information across different disciplines, where you&#8217;re just trying to help someone use all of it interchangeably to answer whatever their key concern is.</p><p><strong>David</strong> 18:42</p><p>So maybe, it seems as though the use cases for the military are not so dissimilar from those on the commercial side. What does the setting-up process look like for a commercial vendor versus the department? Maybe we&#8217;ll circle back to the department, and you can provide the listeners some of your trials and tribulations and what it&#8217;s been like. But just curious &#8212; how have you seen the differentiation there?</p><p><strong>Jesse</strong> 19:11</p><p>Yeah, I would say, for the differentiation on the government side versus commercial &#8212; in the government landscape, there&#8217;s a lot of security restrictions, data access restrictions; there&#8217;s a lot of sensitivities into where that data can be shared. I would say it&#8217;s not extremely dissimilar to commercial, where a lot of enterprises are also thinking about how do we secure our data. There&#8217;s a big topic now around data sovereignty for both governments and enterprises. And so in the enterprise market, a typical startup, or a typical new start &#8212; a lot of times these organizations are just using our software out of the box. It&#8217;s cloud deployed. It&#8217;s got tons and tons of information around the world. They&#8217;re able to get comfortable with what the system can do before they start integrating it with their own infrastructure. So, being able to monitor global facilities to start, you just need to tell the system where the facilities are. We don&#8217;t need deep integrations with their own enterprise systems, but we&#8217;ve done other applications where insurance companies can directly either integrate or run automated exports of things like policy data, more sensitive commercial or customer information, into the system, because we deploy the system in nodes where every organization and every customer&#8217;s data stays secure locally in one environment. They have complete access and control on it. It doesn&#8217;t send data out to external AI models or anything like that. Everything is locally deployed and secured, and so they can be assured. But anyway, they can start with a more public and open system, but they can also have even their own on-prem deployed systems behind the firewall.</p><p><strong>David</strong> 20:54</p><p>Very cool. And so you&#8217;ve obviously had a decent amount of success with the military contracts. What does that look like on the networking side, and getting access to government network information and data?</p><p><strong>Jesse</strong> 21:08</p><p>Yeah, for those that listen to this that are maybe also looking at getting into deploying software at the government, it&#8217;s not an easy road. There are so many things required &#8212; from facilities clearances, authorities to operate, being able to actually have the credentials and do the deployments. We joked earlier today about even having CAC cards sometimes to be able to access certain network terminals, and sometimes the hurdle&#8217;s there. And so we&#8217;ve been around a little over three years, and we&#8217;ve been able to get through a lot of those hurdles, where great partners like the National Geospatial Intelligence Agency supported us to get our facilities clearance. So now the company itself can hold classified contracts. We can have cleared staff that can be cleared to go into buildings and access the right networks and systems. The system&#8217;s already gone through provisional ATOs, and that&#8217;s where you essentially have the government review the security infrastructure around the software and how it&#8217;s tested and its deployment, to even something that sounds as simple as getting military IDs. But a lot of these terminals require all of these things to be able to then just deploy your software directly into that government network, to inherit the controls of that network, to inherit things like user rights and permissioning. And that&#8217;s critical for an application like ours &#8212; to know when someone puts their ID card into a network terminal, the system is gonna provide them only the data that they have access to see, and they&#8217;ll only be able to leverage it in a way that keeps that information secure. So we understand why the hoops are there, but yeah, for a lot of new entrants, it&#8217;s quite difficult to navigate.</p><p><strong>Maggie</strong> 22:46</p><p>Yeah. What&#8217;s remarkable to me &#8212; I saw genai.mil recently got stood up, but if you actually look at the models on the back end of something like that, I believe they&#8217;re models that are two or three years old. So the department is just now getting access to the ChatGPT that we all had access to three years ago. Which does bring me to another question, which is: how does something like Danti compare to a ChatGPT or Claude just straight out of the box? How much are they able to do versus what is the special sauce that you all are bringing to the table?</p><p><strong>Jesse</strong> 23:16</p><p>Yeah, it&#8217;s interesting, &#8216;cause when we deploy in different environments &#8212; we&#8217;re just deploying in a different environment now with the Army, where I think in that case it&#8217;s an OpenAI model, where in some other cases it&#8217;s a very different model. Our system is architected to be able to leverage the best as these models improve. They get better at information synthesis tasks, or they get better at whatever the task might be. We can leverage that model, but there&#8217;s a lot of parts of our system that don&#8217;t require LLMs at all. Some of it is graph technology, some of it is learning graphs that are really built on Danti&#8217;s own IP that can understand and learn this tradecraft. Whereas the models that are just so broad and trained on a very broad set of data &#8212; once you start to go into these physical-world environments that have much more nuanced and complex data sets, things like signals from satellites and organizations like a HawkEye 360 &#8212; this is complicated information that is super powerful. A lot of these models just have no prior training or understanding of how that data is used and how it&#8217;s used across a variety of different tasks. And so what Danti does is more of the orchestration &#8212; based on what the user&#8217;s trying to accomplish, understanding what the tradecraft and use is there, and knowing when the right steps to introduce a model are. The other thing is, there&#8217;s very little tolerance for hallucinations or incorrect information. And so we have to provide a lot of standardization in how results are presented back to users, and citations. And so you can only introduce some of those non-deterministic models at certain parts in those sequences, and knowing also when you can&#8217;t use those models is also very important. So we provide a lot of that, so that the end user shouldn&#8217;t have to care nor think about that. They can trust that when they go into a system like Danti, they&#8217;re asking their question and they&#8217;re getting a cited-back answer every time, consistently, knowing the provenance of all the data &#8212; data that is their government&#8217;s information living on their government server completely securely &#8212; and then just leveraging the AI to speed up certain portions of that task.</p><p><strong>Maggie</strong> 25:21</p><p>So Jesse, looking back at your career, you&#8217;ve worked at defense primes, you&#8217;ve worked at startups. From all this experience, what do you think startups are uniquely good at in the government space versus where do you think more traditional primes will still win? And maybe a secondary question: how do you think about opportunities for startups to partner with primes to accelerate the chance of bringing technology to the warfighter?</p><p><strong>Jesse</strong> 25:45</p><p>Yeah, I think that&#8217;s a really important question, myself being a Booz Allen alumni and seeing all the great work they do across so many different agencies and their ability to have that deep customer understanding. They&#8217;re involved in them and many others. You guys mentioned some of the deployment environments. They&#8217;re supporting a lot of the build-outs of those environments as close, trusted partners of those organizations. And for a startup like us to just walk into an intelligence agency and pretend to understand the complexities and nuances of their IT environment, their procurement environment, the user infrastructure, and the applications and workstations? These defense primes have already built it. They understand it. They understand where the issues are, and they can help accelerate companies, I think, much more quickly versus a company trying to come in by themselves and do everything new. I think there&#8217;s definitely some nuances in things like shipbuilding or autonomous aircraft or things like that, where you&#8217;re building a complete end-to-end system. But sure, they do have C2 environments and others that maybe some of the primes are engaged in. But from a software perspective, it&#8217;s really, I think, important to leverage a lot of partnerships with those prime contractors, again, because they so deeply understand the customer environment.</p><p><strong>Maggie</strong> 27:04</p><p>Yeah, absolutely. So you&#8217;ve been at this now three years. You&#8217;ve been working in the defense space longer than that. What advice do you have for startups embarking on a journey, the kind of journey that you&#8217;ve been on? Or what advice would you have for yourself if you could go back in time and talk to yourself three years ago?</p><p><strong>Jesse</strong> 27:21</p><p>Yeah. Don&#8217;t underestimate how long things may take. There&#8217;s a lot of buzzy news stories out there about companies getting massive contracts and going huge, and I would say that that is not the standard. And I would say, maybe look into how long ago those organizations actually started. And I think my advice to folks is, definitely over-index on the amount of experience you bring into the team early on. Don&#8217;t think that it&#8217;s just simple &#8212; like a commercial industry &#8212; to go and build something and disrupt everybody, and you&#8217;re gonna grow like a Snapchat would, but inside the government domain. It&#8217;s definitely a different animal. So heavily rely on a lot of experience as soon as you can get it. Relationships are critically important, so make sure that you over-index on those things as well. And just make sure that you plan for the right time horizon, because things are complicated. Things take time. There&#8217;s things outside of your customer&#8217;s control. It&#8217;s not like in the commercial market, where your customer can just like you and buy it. There&#8217;s so many other things behind the scenes that they cannot control, and you just have to be patient and understand that there&#8217;s just frustrating things that you&#8217;re gonna encounter that are well outside of you and your own customer&#8217;s control.</p><p><strong>Maggie</strong> 28:36</p><p>Great. Well, Jesse, with that, thank you so much for coming on the Mission Matters podcast, and we&#8217;re super excited to be investors in Danti.</p><p><strong>David</strong> 28:42</p><p>Yeah, thanks, Jesse.</p><p><strong>Jesse</strong> 28:43</p><p>Thanks for having me. It&#8217;s great to work with you guys.</p>]]></content:encoded></item><item><title><![CDATA[🎙️ Ep 29 - Ent: The AI Cybersecurity Arms Race – Defending at Machine Speed ]]></title><description><![CDATA[How cyber defenders can use AI to keep up with hackers]]></description><link>https://maggiegray.us/p/ep-29-ent-the-ai-cybersecurity-arms</link><guid isPermaLink="false">https://maggiegray.us/p/ep-29-ent-the-ai-cybersecurity-arms</guid><dc:creator><![CDATA[Maggie Gray]]></dc:creator><pubDate>Tue, 08 Sep 2026 17:38:28 GMT</pubDate><enclosure url="https://api.substack.com/feed/podcast/214765679/5b70bcd1e251a4d38edc555a7a794871.mp3" length="0" type="audio/mpeg"/><content:encoded><![CDATA[<p><span>AI lets hackers attack at machine speed. Human defenders cannot keep up. Luckily, the team at </span><strong><a href="https://www.linkedin.com/company/ent-security/"><span>Ent</span></a></strong><span> is building the future of AI-native cyber defense and prevention. <br><br>In the latest episode of the </span><strong><a href="https://www.linkedin.com/company/mission-matters-podcast/"><span>Mission Matters Podcast</span></a></strong><span>, </span><strong><a href="https://www.linkedin.com/in/akhil-iyer/"><span>Akhil Iyer</span></a></strong><span> and I sit down with Ent CEO </span><strong><a href="https://www.linkedin.com/in/eliasmanousos/"><span>Lou Manousos</span></a></strong><span> to discuss Ent and the future AI for cyber offense and defense. We discuss everything from:<br> &#128073; The recent </span><strong><a href="https://www.linkedin.com/company/openai/"><span>OpenAI</span></a></strong><span> attack on </span><strong><a href="https://www.linkedin.com/company/huggingface/"><span>Hugging Face</span></a></strong><span><br> &#128073; How AI agents deployed at the edge can prevent hackers from attacking in the first place<br> &#128073; Why defenders need access to locally deployed open source models to ensure they have control over their cyber defense in the face of rogue offensive agents<br> &#128073; Why the current security stack is insufficient in the world of AI<br> &#128073; And much more...<br><br>As always, please reach out if you or anyone you know is building at the intersection of technology and national security, or if you have any interest in joining the team at Ent. If you&#8217;re interested in working in the Shield Capital portfolio, please fill out this </span><a href="https://workindefensetech.netlify.app/"><span>form</span></a><span> to Work in Defense Tech.</span></p><p><span>You can listen to the podcast on </span><a href="https://open.spotify.com/episode/0RJxf8w3mye0mwHuLw7kzO?si=4U1_Uo-VTryoZnHqA2aU-g">Spotify</a><span>, </span><a href="https://www.youtube.com/watch?v=SZ-Hnar8Wg4">YouTube</a><span>, the Shield Capital </span><a href="https://shieldcap.com/episodes/ent-security">website</a><span>, or right here on Substack.</span></p><p class="button-wrapper" data-attrs="{&quot;url&quot;:&quot;https://maggiegray.us/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe now&quot;,&quot;action&quot;:null,&quot;class&quot;:null}" data-component-name="ButtonCreateButton"><a class="button primary" href="https://maggiegray.us/subscribe?"><span>Subscribe now</span></a></p><p><strong>Transcript</strong></p><p><strong>Maggie</strong> 01:12</p><p>Offensive cyber attacks are officially moving at machine speed. Just last month in July, OpenAI reported a cyber incident in which one of its AI agents broke out of its sandbox and hacked into Hugging Face in an attempt to obtain solutions to a test that OpenAI was running against the model. Notably, during this Hugging Face attack, the Hugging Face team reported that they actually couldn&#8217;t use closed source frontier AI models to help defend themselves against this attack because all of the frontier AI labs have put up guardrails on their models to prevent people from using the models for cybersecurity tasks. Now, of course, they&#8217;re trying to prevent offensive attacks like the attack Hugging Face themself was actually experiencing, but ultimately, these guardrails prevent any kind of defensive use of these models as well. The Hugging Face team ultimately ended up needing to use a Chinese open source model, specifically ZAI&#8217;s GLM 5.2 model, to defend themselves in this situation. How can companies defend themselves today against automated machine speed attacks in the age of AI? In this episode of the Mission Matters podcast, we sit down with Lou Manousos, the co-founder and CEO of Ent Security. Ent is building the future of what they call intent-aware cybersecurity, leveraging edge deployed AI agents to prevent cyber attacks in real time at the endpoint. This kind of technology is absolutely crucial for companies to have to defend themselves in this age of AI for offensive cyber. Ent is working to bring security tooling into the AI era. By deploying AI agents on the edge at the operating system layer, Ent can detect and prevent attacks as they happen at machine speed with full context of a user&#8217;s typical behavior on a system. Since it was founded in 2025, Ent has raised more than $100 million and started working with enterprises across financial services, defense, hospitality, and more. This conversation covers everything from the current state of AI for offensive and defensive cyber, what it takes to build AI agents for cybersecurity, the debate over closed versus open source models, what it takes to deploy AI agents at the edge, and what it takes to build a successful cybersecurity business. All right, Lou, thank you so much for joining us on the Mission Matters podcast. This has been one of the interviews I&#8217;ve been most excited to do back since Akhil and I started this podcast more than a year ago. There&#8217;s been a lot of hype and discussion publicly recently about the role that AI agents can play in both cyber defense and of course, offense. I mean, lots of discussion around Anthropic&#8217;s Fable models, OpenAI&#8217;s newest models, even some of these Chinese open source models about their ability to conduct offensive cyber. Akhil and I, and Lou, you yourself, have all sat through many, many pitches for all kinds of uses for AI and security, whether it&#8217;s automated pen testing, SOC management, incident response, threat intelligence analysis, and much more. But I wanna hear it from you, what do you see as the state of AI for cybersecurity today? What is actually real versus what is just hype around what AI agents can do in this space today?</p><p><strong>Lou</strong> 04:32</p><p>Look, I mean, it&#8217;s amazing. All offense will be AI entirely, I think by the end of this year. Mythos really gave us a window into that. So a lot of the hype really is people who worked with these models hands-on and have seen some of the capabilities. And so it&#8217;s pretty clear to me where this is heading. The models are really great at coding, they&#8217;re really great at technical tasks, and that&#8217;s what a lot of the security incidents are built around. So I think that Frontier AI labs, they&#8217;ve been talking a lot about this through this lens of safety, and I think they&#8217;re taking it seriously, but the cat&#8217;s kinda out of the bag, and that means those capabilities are gonna flow to open models, and attackers are gonna be able to increasingly use offensive AI. And what that means for security teams and the whole industry is it&#8217;s a speed question. So it all comes down to speed. If an offensive attack is operating at machine speed, people operate at human speed. We&#8217;re humans, we can only type so quickly, we can only move the mouse around so fast. So even if you have a defensive agent as a human operator, you may already be too late, even by the time you start to triage these incidents. And if you can&#8217;t understand the incident, really wrap your arms around what&#8217;s going on... I mean, frankly, if you look at some of these attacks, like 27 seconds, under a minute, that amount of time, just to reason in your own mind as a human, it&#8217;s unlikely. So to me, it&#8217;s pretty obvious that as offense is all AI, defense is gonna have to be mostly automated and able to execute in under a second and really prevent these attacks. So we&#8217;ve heard about all these different dramatic things that have happened recently, and whether it&#8217;s discovering vulnerabilities... I mean, you mentioned a bunch of them. Software inventory, hacking a system. These are all real risks that we&#8217;ve seen AI successfully pull off. So at this point, whether you&#8217;re a defender or somebody doing offense, you&#8217;re using AI at this point. It&#8217;s just a matter of how much the human is in the loop versus out of the loop. And I don&#8217;t think it&#8217;s about convincing anyone about the impact here. So that&#8217;s my view of it. It&#8217;s not hype, it&#8217;s happening. I think what&#8217;s maybe under-hyped is just how important it&#8217;s gonna be to stop thinking about response and focus more on prevention.</p><p><strong>Akhil</strong> 07:21</p><p>Hey, Lou, I love that framing of offense versus defense. Actually, Maggie, I think on our first podcast we were talking about, obviously, here at Shield Capital, we talk a lot about and discuss revolution, military affairs generally. What I find interesting about this conversation, whether it&#8217;s in the digital world or whether it&#8217;s drone, counter-drone, there&#8217;s always this balance of power and velocity when it relates to technology as applied to the offense versus the defense. Correct me if I&#8217;m wrong, Lou. What I&#8217;m hearing from you is that where we are with AI today, you are arguing that that naturally favors the offense right now. Is that a correct statement?</p><p><strong>Lou</strong> 07:58</p><p>Yeah. The investment certainly has gone into offense and, you know, even the first wave of companies in cybersecurity largely were around pen testing vulnerability. You know, that&#8217;s what the models were really good at, whether that&#8217;s in source code or in actually scanning live systems. And then the second wave went into understanding SOC operations, but that was really much more of a response function. So does it favor offense or defense? I think it&#8217;s really hard to build real-time defense and prevention. These agents are actually, while they&#8217;re faster than humans, they&#8217;re slower than a normal prevention system which operates in under a second. The agents do need to reason over larger quantities of data. And so I don&#8217;t think that the frontier labs are focused on that type of use case right now, and most security companies are just adopting what they can get from these frontier labs. I wouldn&#8217;t characterize it as the offenders have the advantage. They almost always have the advantage, right? Even before AI. It&#8217;s just much easier to find one hole in a system than it is to defend a system.</p><p><strong>Maggie</strong> 09:28</p><p>Now, Lou, one of the big debates that I know we&#8217;ve discussed and a lot of the industry is discussing right now is really around the models&#8217; capabilities for offense and defense, and really around the model providers putting in these guardrails to try and ensure that these models are being used in a safe way. But, of course, a lot of these guardrails maybe actually make it harder for defenders to use the model for defensive cyber operations. So I just wanted to get, what is your take on this debate around, to what extent the model providers should be building these safety guardrails in, especially in this world where we&#8217;re seeing this proliferation of open models that don&#8217;t necessarily have those same guardrails in place?</p><p><strong>Lou</strong> 10:14</p><p>Yeah, this is kinda how we kicked it off. I think some of the recent incidents, Hugging Face and others that have happened in the last couple weeks really underscore that when you give an agent an objective, it&#8217;s... You&#8217;re not telling it, like, &#8220;Go hack this system.&#8221; It&#8217;s trying to get to its objective, and you didn&#8217;t have to give it step-by-step instructions like, &#8220;Go do this.&#8221; And it finds a way to work around the controls that you put in place. As long as you&#8217;ve got the tokens, it&#8217;s just gonna keep going. And so as a defender, if you&#8217;re specifically asking the model to do things and you&#8217;re using a frontier lab or an API provider that&#8217;s blocking you, I mean, that&#8217;s very troubling. And you don&#8217;t have control over that. You don&#8217;t really know at what point you might be blocked. That might happen once it understands what you&#8217;re trying to do, that might happen later. So I think organizations, defenders have to have some ability to run local models and switch out their model provider. I mean, that really became painfully clear last week when several people blogged about how they were blocked while they were defending themselves, and that caused them to spin up local capabilities. Now, what&#8217;s interesting about that, and Hugging Face, I mean, they&#8217;re like the experts in running local models, so they were able to do it. But how many organizations really have the capability to deploy and run a local model in that way? Probably not many. So yeah, to me, it is the digital right to bear arms or the right to bear technology. As a defender, if you&#8217;ve been given a guardrail, it&#8217;s like fighting a fight with one hand tied behind your back. So I feel pretty strongly that, as a security expert, you need to have exact knowledge as to when you&#8217;re gonna be blocked and what the model&#8217;s gonna do, and frankly, what it&#8217;s not gonna do when you ask it to do that. I think that&#8217;s where it ultimately ends up is you&#8217;ll need to remove guardrails for defenders. There will need to be... At least the frontier labs are gonna be challenged by this. But it will drive the best security teams towards open-weight models and open local models. At least as a backup plan, you&#8217;ll need to have that capability. I don&#8217;t see a way around it.</p><p><strong>Maggie</strong> 12:59</p><p>Yeah, can you tell us more about what you think the proliferation of these open source and open-weight models will mean for both offensive and defensive cybersecurity?</p><p><strong>Lou</strong> 13:11</p><p>Well, it lowers the costs, whether it&#8217;s social engineering, deception, just basic types of phishing, credential theft, data leakage. I mean, really you go through all the bad things that can happen in a security program. The models are trained on all this amazing research that&#8217;s been published. I have background in threat intelligence, published thousands of articles over the years. All of that information is in the memory of the model, so they&#8217;re quite good at this. And that I think is... Yeah, I think that&#8217;s the basic problem that you&#8217;re facing as a defender is, like, you&#8217;ve just lowered the bar for offense. I do think... We saw this in the early days of web exploits where just average cyber criminals could go online and buy a web exploit. They didn&#8217;t have to know very much about exploiting a web browser. They just go buy this exploit, they run the exploit kit, and now they&#8217;re able to target, whether it&#8217;s a nation state threat actor or just your average cyber criminal. It just made it way harder as a defender when you could get your hands on these. I think we&#8217;re entering a new phase now where that&#8217;s gonna become the new normal, where fairly effective attacks will be in the hands of ordinary cyber criminals. So in a world where we know that that&#8217;s gonna happen, and we have the speed of the attack being driven by AI, you have to be able to prevent and actually go beyond just detection and response. And this is gonna require a shift in thinking on architecture and how we&#8217;ve architected these systems. They&#8217;re currently architected to deal with human-driven attacks, which are, again, relatively slow. Once I go back to the exploit kit example, once I had a foothold on your network, as an attacker, I&#8217;d go to this panel, be like, &#8220;Oh, great, I hacked Maggie&#8217;s computer.&#8221; And now I would start tasking and going to look for my objective. That&#8217;s very slow. That might take hours, at least many minutes. So if you had an EDR system in place, your threat hunters would see that activity, and then they&#8217;d be able to isolate that machine. When that occurs in like under a minute, by the time your security architecture alerts you and your team starts responding, the damage has been done, the data has already leaked. So the answer is to move back to something where as soon as you detect this behavior that is potentially malicious or suspicious, that machine must be isolated immediately. You have to intervene at the moment that you see this behavior. And that&#8217;s a change in terms of how we&#8217;ve been behaving as a security industry the last almost 15 years now.</p><p><strong>Maggie</strong> 16:29</p><p>Yeah. So maybe we&#8217;ve been hinting at it a little bit, but let&#8217;s move to discussing Ent itself. Can you tell us a little bit about what Ent is building and how it relates or compares to this old generation of security tools?</p><p><strong>Lou</strong> 16:45</p><p>So we&#8217;re building an intent-aware security platform, and it&#8217;s designed to secure both human and AI-driven work. Our goal is to move the industry back to prevention because it&#8217;s only with prevention that you can see productivity and secure it and really increase the adoption of this AI technology faster. So we deploy an intelligent agent directly on the endpoint, and we model what people are doing, what applications are doing, what the AI agents are doing, and how that accrues to the work that&#8217;s happening. And we understand that in context. And so by understanding what the intent is, what humans and AI agents are doing, we&#8217;re able to see if there&#8217;s any risk there, if it&#8217;s deviating, and then we can intervene before that becomes an incident. What makes the endpoint super interesting in this AI world is I believe that humans are always gonna be in control at some point. And so you have to think where&#8217;s the place where humans and machines are going to meet. That&#8217;s how I define an endpoint. That is the place where a human and an AI agent or some future AI comes together. Once you start using your endpoint, you&#8217;re moving around a lot. You move between browsers, chat, other business applications. These agents are working hand in hand with users at that endpoint layer. So we provide security for this modern workspace. Instead of looking at each application separately, we look at the entire endpoint, from the operating system up, and that&#8217;s why operating systems were built. They are supposed to provide a platform and common primitives like security. So that&#8217;s Ent in a nutshell.</p><p><strong>Akhil</strong> 18:54</p><p>No, Lou, that&#8217;s awesome, and exciting just how quickly too you have moved, and a lot of that obviously based upon your background experience and the team that you could bring together. Let me dig into a couple comments you made. The first is you talk about this shift back to prevention. So what has been missing, Lou, that you really felt like, &#8220;Hey, this is the one&#8221;? You&#8217;ve done many startups in the cyberspace. You decided to focus in this particular... Why this approach and why this vector?</p><p><strong>Lou</strong> 19:25</p><p>You know, again, on why is the endpoint so special, I was just thinking about all these risks that are now playing out. I mean, I thought we&#8217;d have a little bit more time, but they&#8217;re happening now. Where&#8217;s the right place to build security? You have the cloud. So definitely a lot of things happening there. You have the network layer, and you have the endpoint. Again, the endpoint is where humans and machines meet, and that is the logical place to put the security control. That&#8217;s where the information&#8217;s gonna leak back to the user. That&#8217;s where the user is actually prompting or tasking their agents. And so when I thought about... I looked across the market and say, who&#8217;s doing this, and who&#8217;s got the capabilities? There&#8217;s plenty of great security companies out there, but they&#8217;re challenged. The incumbents are challenged because their model is based on detection and response, and we moved away from prevention about 13 years ago when the EDR market took off. And it would require a complete reboot, reset as to how prevention is done, which really relies on detecting a threat, using threat intelligence to hunt and then sending that as rules back to endpoints. The latency there is just too long. So that&#8217;s why we stepped up here. It&#8217;s just a ground up first principles rewrite of prevention and security.</p><p><strong>Akhil</strong> 21:09</p><p>Yeah. Thanks, Lou. We&#8217;ve got some folks who listen to this podcast who are deep in cyber and know what EDR and SOC automation is, and then some that don&#8217;t, might be coming from different domains, but this certainly applies to them regardless of industry. Can you give an example, maybe a tangible one, of a threat that Ent agents have or were or will be able to detect and prevent?</p><p><strong>Lou</strong> 21:35</p><p>So one example might be, you have an employee who is working on sensitive data on their local machine, and you wanna move that data from one machine to the next. In this example, this is kind of an anonymized example. This organization uses WhatsApp to communicate with some of their customers. So WhatsApp is an approved application in this environment. The data that the employee is using is approved. What&#8217;s not approved is for the AI model built inside WhatsApp, which there&#8217;s Meta AI, should not have access to this specific data. They&#8217;re only supposed to use WhatsApp to communicate with customers. So what happened was this approved communications app all of a sudden now had proprietary data put into it, and that was kinda cut and paste from another application on the desktop. So unless you have local AI capabilities that are watching the sequence of events, like data is taken from a Word document and pasted into WhatsApp, but into this portion of WhatsApp that has Meta AI for summarization, you would not be able to detect a company policy violation and potential regulatory violation and exposure. So it&#8217;s only when you have the context of the work, the legitimate work that that person is doing and the knowledge of the data, and putting that whole picture together, which is very difficult to do when you don&#8217;t have AI running directly at the operating system, watching not just the web browser, but communication applications, productivity applications, and you can design an adaptive policy that protects that entire environment. So that&#8217;s just one example.</p><p><strong>Maggie</strong> 23:49</p><p>And so moving to a little bit of the discussion of the technology behind Ent, one of the things I found really interesting about it is that you guys did decide to deploy this on the edge, on the endpoint. Can you talk a little bit about what that decision gets you, and maybe also some of the challenges with deploying on the edge?</p><p><strong>Lou</strong> 24:07</p><p>Yeah. The edge gives you context of what the user is doing. I&#8217;ll go back a little bit to, like, intent aware. One of the inspirations for Ent was autonomous vehicles. Riding in an autonomous vehicle here in San Francisco, I was, like many people, amazed at how the car can adapt to the world around it. So they have a world model, and then the vehicle intervenes. If that worked like a security system, right, it would log accidents, and then some analyst would come in and then tell it not to do that again. That&#8217;s not how it works, right? It doesn&#8217;t log an accident. It just intervenes so that there isn&#8217;t an accident. And so when you&#8217;re kind of at that point, at the edge, you actually have the ability to intervene in sub-second time. So you have the context of the environment, you have speed, and you have total control. And so that, in the world of cybersecurity really only exists at the endpoint itself, at the edge. And that&#8217;s where all these applications interact. That&#8217;s where human work is handed from your mind and translated through the keyboard or through your voice. It could be different modalities, right? It will be at that point where we hand off control to AI agents. And so if you don&#8217;t have that context, if you&#8217;re not living at that point, if you&#8217;re living sort of in application logs, or through network events or through the logs at the cloud, you completely miss the intent of the operator and what they&#8217;re trying to do. And so that&#8217;s really was one of the key pieces. And the other is that when you run locally, you can run very quickly, so that removes this sort of roundtripping that happens where I have to log the event, send it to the server, the server processes the information, sends it back. When you have something that has to complete in less than a second, you&#8217;re gonna gate the user and intervene, you&#8217;re gonna lock process execution or something. Like it has to be quick, otherwise the machine will crash or the user will complain. So that&#8217;s a really critical second reason. And then the last one is we really believe in the data boundaries. We wanna have a decentralized system. There&#8217;s a lot of sensitive data that happens on the endpoint, and we wanna keep as much of that information there and allow customers and their organizations to decide what they collect, how they analyze that. So all these things now can happen within the memory and compute of a modern endpoint. So we&#8217;re designing Ent around this future where we have a lot more happening locally, and these handoffs between humans and AI are just increasingly sort of the norm. So we just thought that&#8217;s the logical place, is the endpoint.</p><p><strong>Akhil</strong> 27:37</p><p>Oh, that&#8217;s awesome, Lou. Hey, Lou, can I follow up on, as you decentralize and take action at the edge, there&#8217;s some trade-offs associated with potentially the decision-making or something broader. So two questions. One, as you look at proliferating at the edge, how do you find commonalities between different attacks if you&#8217;re trying to prevent and engage with those? And number two is, if you have to make some major refinement to how your agents respond or prevent at scale, how do you think about doing that? Where I&#8217;m going with this is, what is the trade-off between being able to prevent at the edge and being able to have a little bit of that centralized pivot or adjustment at scale?</p><p><strong>Lou</strong> 28:27</p><p>Look, there&#8217;s some trade-offs, but there&#8217;s also barriers. I think the first one is are we sort of ready to hand off control to some local, very fast, Ent-like agent that can prevent. I mean, that&#8217;s just a change in the way security systems work now. So that I think is the first one. The second part of it is, are end users themselves ready for this security system to intervene and potentially coach them away from risky behavior? &#8216;Cause if I can predict the next thing you&#8217;re gonna do will put your computer at risk, or you&#8217;re falling for some social engineering scam, or you&#8217;re gonna run a command that could compromise your machine... I can&#8217;t just block it. Again, going back to the examples we talked about earlier, if it&#8217;s an agent, it&#8217;ll just keep trying to go through the steps. And also, humans do the same thing, by the way. If they get blocked, they just keep trying to go around you. And so having a system in place that intervenes and can also convince the operator, like, the next thing you do is gonna be really bad, it&#8217;s a total change in the relationship that end users have with security systems. And then the third thing is local hardware and the speed of the models. And we&#8217;ve done a lot here to build our own models. We can use what customers have access to. A lot of this relies on the local compute, which is changing. It&#8217;s getting faster. We&#8217;re getting more capabilities at the edge. And that I think has been playing out. It&#8217;s driven by broader market forces than just cybersecurity. In terms of what are the trade-offs, there really are no trade-offs because you can still go grab threat intelligence. You can still share within your own company or within cohorts. Whether you&#8217;re in financial services or government, there&#8217;s no reason you cannot share the threat intelligence of the types of attacks that you&#8217;re seeing with your peers, what is now magnified by the fact that you have both local reasoning capability and global threat intelligence or market threat intelligence. So I think this is sort of the best of both worlds.</p><p><strong>Maggie</strong> 31:05</p><p>How do you think about combining both deterministic and non-deterministic models together in your platform?</p><p><strong>Lou</strong> 31:12</p><p>Yeah. Basically, to answer the question on deterministic and non-deterministic, security controls generally are deterministic. And for example, access control. I&#8217;m either granted access or denied access, very strict, constrained. But I think where it becomes difficult is where you have unconstrained language models. How do you use such a thing in security? So the way we do it is we combine three forms. We start with the deterministic controls, which provide clear policy, clear, predictable enforcement, and that&#8217;s usually regulatory driven. If these things happen, I must block it. And then we layer in behavioral. So what action is normal for this user or the types of users that work in the company like this user works with, their role, we try to derive the role, and the generative models and multimodal models can interpret what&#8217;s ambiguous in this context and map it to intents, and then those intents will help you really understand, again, what is normal for this user. So a policy might start with, again, a deterministic, like, all right, I&#8217;ve got clipboard activity, and inside the clipboard is sensitive data. That&#8217;s fairly easy to determine deterministically. But now the action, like what is the user doing with that data, is non-deterministic, and then the destination is deterministic. Like, oh, I&#8217;m pasting it into Meta AI, I&#8217;m pasting it into WhatsApp. That&#8217;s very easy to determine. So, and then finally, looking at the entire action, and understanding the boundary conditions of the policy and reasoning over it and reasoning over larger time periods, for that we use reasoning models. And so we combine all three approaches, again, under a second, and that&#8217;s a very powerful thing because now you get the compliance things you need, but you also get this flexibility to deal with benign false positives and try to capture more recall and make sure you can broaden the net for situations which you&#8217;re unsure if you can act deterministically.</p><p><strong>Maggie</strong> 34:01</p><p>And are these models that you all built yourself to be able to fit on an edge device, are these open source models that you&#8217;ve used or distilled?</p><p><strong>Lou</strong> 34:09</p><p>Yeah. We distilled and we started with things that we can get, and there are certain things that we could build from scratch that are really useful for data classification and are becoming easier to build on your own. But for the larger reasoning tasks, we&#8217;re taking off-the-shelf models, just quantizing and distilling those down. But it&#8217;s still very, very hard work and you have to have training data and other scenarios. And the way we do that is we do have a synthetic environment which allows us to take real world information that we&#8217;ve populated with these virtual workers, these virtual workers that represent what you commonly see in the enterprise, and they are repeating tasks, and they&#8217;re repeating adversarial tasks as well. And so we can take that data without using any customer-sensitive information to help train and fine-tune our models.</p><p><strong>Maggie</strong> 35:15</p><p>And are these reasoning models multimodal models? Do they have, like, vision capabilities to see the screen, or are they more relying on text data that&#8217;s coming in or current data?</p><p><strong>Lou</strong> 35:26</p><p>Yeah, the model itself combines being able to operate on the operating system telemetry, which is very technical telemetry. The application layer, user layer telemetry, which is more human content, mouse moves, copy and paste actions, the text that&#8217;s actually on the screen, and what&#8217;s in a document, and then the visual aspect of what&#8217;s on the screen, using vision capabilities when that&#8217;s appropriate. And then many customers, they wanna change the way this behaves for different reasons, so we also allow customers to turn off some of these capabilities or tune some of these capabilities. And then the thing that we always do is we use very lightweight embeddings models and specialized small language models, and yes, those also can optionally have these vision capabilities. So we&#8217;re pretty deliberate in this, and we attempt to stay model agnostic when a customer is saying, &#8220;No, I wanna use this particular frontier model.&#8221; We choose the best model depending on the customer constraints, and also the limitations of hardware and other things within that customer environment. So that&#8217;s what we&#8217;ve been doing. I don&#8217;t think I&#8217;ve talked to anybody who says that, &#8220;Hey, this isn&#8217;t a problem.&#8221; It&#8217;s just a matter of how they&#8217;re gonna tackle it.</p><p><strong>Maggie</strong> 37:01</p><p>Yeah, one question I have, and I ask this of a lot of companies that are building these AI solutions for mission-critical use cases. What have you done to build trust with customers to actually allow you to have these autonomous agents operating on these mission-critical systems?</p><p><strong>Lou</strong> 37:21</p><p>Well, I think, again, it goes back to the way you&#8217;ve architected the system. Have you built a product so that you as the author of that product cannot see the customer data, you can&#8217;t control the environment? Once you&#8217;ve deployed it, it is completely in the hands of your customer. So we&#8217;ve designed... And some of this goes back to my background. I&#8217;ve done a lot of work in governments and critical infrastructure, worked at some of the largest tech players in the industry. And in those environments, these are table stakes things. Like, sensitive data must stay in the customer&#8217;s data boundary. Then it&#8217;s all about when the product is running, like customers see what we would have detected and how the product would have responded before we actually turn on interventions or prevention capabilities. And that creates a real proof, like this is what this product will detect, this is how it will respond. And once that happens, then... You know, we had just a kind of a story. We had a customer who was worried about inside risk and they told us, like, Ent is the first product that made them feel like an expert on the first day, like, explained what was happening in their environment in terms that they understood as an inside risk expert. And it took all these technical signals and put them together in a narrative that made sense to them. So some of that trust comes from just building the product properly for not just security experts, but the business leaders and the end users. It should feel... The product should feel natural. That&#8217;s one of the amazing things about this gen AI movement, is we&#8217;re actually able to build products that speak in the language of real humans. And so it&#8217;s a magical moment in building things.</p><p><strong>Maggie</strong> 39:29</p><p>You mentioned that at some of your past companies, you&#8217;ve done work with the government, and in past roles you&#8217;ve had. Is that something that you all are focused on for Ent? Are there any defense or government customers that you&#8217;re working with?</p><p><strong>Lou</strong> 39:41</p><p>So Ent is an American company. We&#8217;re built and headquartered in the United States. That actually matters quite a bit in this AI race, and it matters to us. We&#8217;re here for our government customers, and we care about accountability, having a supply chain that you could verify, like, where we wrote the code and how it operates. I also think the legal jurisdiction matters. Alignment with national security really matters quite a bit. Government and defense customers, they face the same challenges that we&#8217;ve been talking about in this podcast, but the impact is just so much greater. Like, AI attacks just have much bigger consequence in those environments. And it&#8217;s not that they want local control, they absolutely require it. They have to have a very decentralized system. Obviously, it has to be sovereign. The provenance of the data, everything has to work within very strict environments.</p><p><strong>Maggie</strong> 40:52</p><p>You&#8217;ve been working on building AI agents for cybersecurity longer than probably almost anybody else on the planet. After your last company, RiskIQ, was acquired by Microsoft, you stayed on at Microsoft to lead their initial security co-pilot product development. I&#8217;m curious, where have you seen the tech change the most these last four years, and what have been the biggest surprises watching this tech evolve over the past few years?</p><p><strong>Lou</strong> 41:19</p><p>Yeah, I mean, it&#8217;s been... It&#8217;s wild, but it&#8217;s five years of thinking about gen AI and cybersecurity, which is an awfully long time. So during that, I think the biggest change is we were using AI to help security analysts and make their life better, and that was more around summarizing incidents, querying systems, like things that security experts do or threat analysts do, really important stuff. And we&#8217;ve seen the models evolve from being great at writing code to now these agentic flows, which are amazing. The multimodal stuff has come an awfully long way in the last year. And then finally, these small models and being able to distill and quantize and run them locally, which makes all of the local security possible. So the biggest surprise to us really has been how much you can do locally now. I mean, I wish that was possible five years ago. It just wasn&#8217;t. And so that&#8217;s what we&#8217;re really focused on, and that&#8217;s the biggest change, is the speed and just how much you can squeeze into a smaller compute memory footprint. I&#8217;ve seen the whole thing evolve, and it&#8217;s been one of the more rewarding parts of my career, to be able to work on this technology, which I think is a dream for so many who&#8217;ve been in cyber and been sci-fi fans and dreamed of seeing the robots. It&#8217;s finally happening, so fun time to be working.</p><p><strong>Maggie</strong> 43:15</p><p>Lou, I saw you made a post the other day that AI agents are going to kill the browser. Could you just talk a little bit more about what you mean by that?</p><p><strong>Lou</strong> 43:25</p><p>So when you think about the modern endpoint, there was this trend with SaaS that got everyone thinking that, like, the web browser, and maybe this was Google pushing this narrative, I&#8217;m not sure, that the web browser was the center of the universe. Like, everything was gonna happen in the web browser. And frankly, as somebody who built RiskIQ, I&#8217;d say a ton of what we did was web-related. It was all around websites. What&#8217;s just totally fascinating about AI is it&#8217;s broken this concept of the web browser being the center of the universe. Like, I do not immediately go to Google and type in a search query anymore or go try to find a web page for a company. I start with my AI tool that runs locally. I type my query into that system, and my objective, and I let it go do the thing that it does best, and it comes back with a good summary. And then from there, if I have to fetch the page, I go fetch it. But usually, the AI agent has done that for me. And I&#8217;m probably on the more bleeding edge, but more and more people I talk to, they&#8217;re like, &#8220;Yeah, that&#8217;s exactly what my day looks like.&#8221; A lot of the security that we&#8217;ve built the last 15, 20 years has been around this narrative of external threats coming through the web. And if that vector is shrinking, you look at where we spend money, we should be allocating money very differently than protecting a usage modality of web browsing that&#8217;s actually decreasing. It&#8217;s not that we&#8217;re not using HTTP. We are. It&#8217;s just that the agents are actually running it, which gives you... It really contains the blast radius within that application layer. So I have more desktop applications now than I&#8217;ve had in a long time. You mentioned earlier, everyone&#8217;s coding again. I&#8217;m coding again. I&#8217;m bringing down local packages. So my machine has a lot more going on than just a Chrome browser running on the desktop, and I think the future is gonna look a lot more like many applications and agents running locally, running in the cloud, all talking to each other. And so that just changes the gates that we traditionally protected. So yeah, thanks for that. Thanks for reading my post.</p><p><strong>Maggie</strong> 46:09</p><p>Of course.</p><p><strong>Akhil</strong> 46:10</p><p>Lou, I have so many follow-ups. Can I ask one on that? Okay. Then how do you decide what runs locally and what runs in the cloud?</p><p><strong>Lou</strong> 46:17</p><p>I don&#8217;t think you decide at all. I think the AI&#8217;s seemingly deciding, right? You describe to the AI what you want, and it goes ahead and writes code. It fires up a container, whether it&#8217;s inside WSL or Ubuntu containers. A lot of these local agents then run programs, compile programs, and run them locally. You could see a future where the user experience is then generated by that program. So instead of it being generated by the website in a DOM object that comes across the browser, the local AI agent is just gonna develop an application for you that&#8217;s purpose-built based on your intent, and that&#8217;s why that stack is going to increase at the edge, at the... or whatever the modern endpoint ends up looking like. So this is a reality. Anyone who&#8217;s been using some of the latest Anthropic or OpenAI local capabilities, you&#8217;re living in this future right now.</p><p><strong>Maggie</strong> 47:25</p><p>You know more about building security startups than almost anybody else. This is your fifth cybersecurity company, right?</p><p><strong>Lou</strong> 47:33</p><p>Yeah, that&#8217;s right.</p><p><strong>Maggie</strong> 47:34</p><p>What advice do you have for early-stage founders building technology for some of these critical industries?</p><p><strong>Lou</strong> 47:41</p><p>I mean, choose a problem where there&#8217;s a real cost to... where failure has a real cost. It&#8217;s a loss of something that you care about deeply, and I think that that creates passion and conviction for you and your co-founders and for your team. And then you gotta spend a lot of time with customers who respect that. And when you&#8217;re solving problems that have major impact, working hand in hand with customers is just very, very rewarding. And I think in terms of mission-driven customers and mission-critical industries, these types of customers are amazing &#8216;cause they know that... It&#8217;s really the passionately curious that can solve any problem with them. Yeah, so they make some of the best customers, and I would encourage founders who listen to the podcast, lean in on that. You probably have a lot more in common with your customer than you realize. And then the last thing for me is it&#8217;s always important to be hands-on with the technology. I mean, I&#8217;m an engineer. That&#8217;s my natural way of thinking, and I&#8217;ve seen these problems firsthand, and I&#8217;ve seen how customers have to deal with the problem, and I know how difficult it is to solve the problem, and that gets your brain thinking in the right way, how to understand the technology and build essentially a better mousetrap. So there&#8217;s really no excuse to not get hands-on with AI today. You can learn almost anything, and I would encourage everyone who&#8217;s thinking about starting a company, you wanna be, as a leader in that company, you have to really understand not only the problem that you&#8217;re solving, but really understand underneath the hood, how this thing works so you can...</p><p><strong>Maggie</strong> 49:46</p><p>You said you learned Rust for Ent.</p><p><strong>Lou</strong> 49:49</p><p>Yeah.</p><p><strong>Maggie</strong> 49:49</p><p>Is that right?</p><p><strong>Lou</strong> 49:50</p><p>Yeah, exactly. I actually never... I mean, in my programming career, I&#8217;d stopped programming when Rust took off, and then when I went back to work on Ent, Brandon and I were talking about what the right way to build this was. So I&#8217;m like, &#8220;All right, I&#8217;ll write a little Rust program.&#8221; It&#8217;s amazing what you can do with the help of AI or with our Clanker friends. And then the other thing I&#8217;d say is, don&#8217;t build a company around the models, like whatever the frontier labs have because these things are gonna change. So these models are gonna come and go, but durable value will come from the insight that you have working with your customers, the data you have access to, the evals that you&#8217;re building, the distribution that you&#8217;ve built, and the customer trust, which was a big theme in this talk here. And with those things, you build the right team that can execute and deliver consistently, and that&#8217;s kinda how you get to the promised land and build something super special. And then the top talent in the industry will be attracted to that. You&#8217;ll be able to hire the best, and turns out that those people also care deeply about the mission.</p><p><strong>Maggie</strong> 51:12</p><p>I know some people are worried that the frontier labs are going to eat all other software companies. Obviously you don&#8217;t believe that, otherwise you wouldn&#8217;t be here building Ent. But what&#8217;s your take on how the future of these models and these labs are going to play out?</p><p><strong>Lou</strong> 51:27</p><p>I think, if you look at Microsoft and what they did with cybersecurity, just as an example, they got very serious about security and have a great security business. Like, I would not, just speaking for myself in cybersecurity, I do think, will OpenAI have a security business? Probably. Anthropic already has a security product inside Claude. So obviously the frontier labs are looking for markets where they can apply their models, and they&#8217;re gonna have fantastic distribution. So there&#8217;s no question that that will continue to be the case. I feel like the harness and understanding these applications is equally important now, and we&#8217;re seeing that play out in other industries. So I would not fear as much the frontier labs. I would just focus on the customers and the use case, and I think you&#8217;ll build a great business.</p><p><strong>Akhil</strong> 52:40</p><p>That&#8217;s right. That&#8217;s right. Yeah. Was there anything... I mean, obviously you&#8217;ve seen where Microsoft has been going. You&#8217;ve got these big providers here that have been on the front. What to you is a sustaining advantage to some of these larger security providers? Like what&#8217;s one area that you&#8217;re like, &#8220;You know what? It makes sense that Microsoft or CrowdStrike or name your entity are doing relative to the types of things that Ent is doing&#8221;?</p><p><strong>Lou</strong> 53:11</p><p>I think there&#8217;s a major advantage that Microsoft has in their ecosystem of, with Windows and the O365 productivity suite and Azure. It&#8217;s just so much easier to adopt technology. They&#8217;ve made it extremely valuable. There&#8217;s so much value in those products. The cost, because they run Azure, there&#8217;s no way to beat the cost on storage and compute. When you&#8217;re a hyperscaler, that&#8217;s a tough thing to beat. So for us, we deploy our technology directly in the customer&#8217;s data boundary. If that data boundary is Azure, then great. We&#8217;ll deploy it inside Azure, and we&#8217;ll deploy it on the endpoint within Windows. I think it&#8217;s very difficult for anyone to go toe-to-toe and say, &#8220;I&#8217;m gonna beat Microsoft, Google, Amazon at the inference game.&#8221; I mean, that makes no sense at all. Or, &#8220;I&#8217;m gonna beat on storage.&#8221; Those are things that I think you let the hyperscalers take and you work with your customers, where you can add value. Generally, when I look at the security incumbents, the value that they have is they&#8217;ve been collecting all of this data on the security events that the customer&#8217;s been seeing. That data has value. It&#8217;s just at a different level in the stack. It&#8217;s describing device failures more than what&#8217;s happening where modern work is occurring. So modern work is occurring really in the application stack. I&#8217;m running these co-work models. ChatGPT has one, Anthropic has one, Microsoft has one, and a lot of the security risk is happening in that application layer, which the security incumbents traditionally have stayed away from. So modern work is all about moving up that stack. But that doesn&#8217;t mean that that traditional device-level malware and the network attacks, they&#8217;re still real too. So our view is we&#8217;re not gonna go back and compete with Microsoft Defender or with CrowdStrike as an antivirus or an EDR provider. Companies are relatively happy with what they get from those capabilities. It&#8217;s where they&#8217;re lacking visibility and prevention is one layer up that stack, and then unifying all of the other applications that sit on that stack. So it&#8217;s very much a complementary thing, and I think, time will tell, if that remains durable for those incumbents. It probably is gonna change too, but for the time being, we coexist with them, and I think it&#8217;s very much a better together story.</p><p><strong>Maggie</strong> 56:31</p><p>Great. Well, Lou, thank you so much for coming on the podcast and sharing all your insights.</p><p><strong>Lou</strong> 56:35</p><p>Thank you, guys.</p>]]></content:encoded></item><item><title><![CDATA[🎙️ Ep 28 - The Navy's Chief Talent Officer on Attracting Top Talent]]></title><description><![CDATA[How the Navy can best attract top tech talent]]></description><link>https://maggiegray.us/p/ep-28-the-navys-chief-talent-officer</link><guid isPermaLink="false">https://maggiegray.us/p/ep-28-the-navys-chief-talent-officer</guid><dc:creator><![CDATA[Maggie Gray]]></dc:creator><pubDate>Tue, 25 Aug 2026 19:19:28 GMT</pubDate><enclosure url="https://api.substack.com/feed/podcast/212747630/cbaa5b1e85ac19b581be959a0f0f582a.mp3" length="0" type="audio/mpeg"/><content:encoded><![CDATA[<p><span>Assistant Secretary of the Navy </span><strong><a href="https://www.linkedin.com/in/benjaminkohlmann/"><span>Benjamin Kohlmann</span></a></strong><span> has flown F-18s in combat, invested in startups, and run a hard-tech company. Now he's the </span><strong><a href="https://www.linkedin.com/company/us-navy/"><span>US Navy</span></a></strong><span>'s chief talent officer, responsible for a workforce of over a million people.</span><br><br><span>On the new </span><strong><a href="https://www.linkedin.com/company/mission-matters-podcast/"><span>Mission Matters Podcast</span></a></strong><span> episode, we discuss how the Navy recruits and retains talent for an era of software-enabled warfare, modernizing an industrial-age personnel system, bringing commercial expertise into uniform, fixing shipyard pay, and the demographic challenges ahead.</span></p><p><span>As always, please reach out if you or anyone you know is building at the intersection of technology and national security.</span></p><p><span>You can listen to the podcast on </span><a href="https://open.spotify.com/episode/20sYF3yROTLc0Po4TVQ44f?si=d92a4b7389034e9e">Spotify</a><span>, </span><a href="https://podcasts.apple.com/us/podcast/the-navys-chief-talent-officer-on-attracting-top-talent/id1807120572?i=1000785806997">Apple</a><span>, </span><a href="https://youtu.be/XxRi3U0xAvc?si=RZqB1AWm-Pg1RXAC"><span>YouTube</span></a><span>, the Shield Capital </span><a href="https://shieldcap.com/episodes/asn-kohlmann">website</a><span>, or right here on Substack.</span></p><p class="button-wrapper" data-attrs="{&quot;url&quot;:&quot;https://maggiegray.us/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe now&quot;,&quot;action&quot;:null,&quot;class&quot;:null}" data-component-name="ButtonCreateButton"><a class="button primary" href="https://maggiegray.us/subscribe?"><span>Subscribe now</span></a></p><p><strong><span>Transcript</span></strong></p><p><strong>Maggie</strong> 00:36</p><p>In this episode of the Mission Matters podcast, we sit down with Secretary Ben Kohlmann, the Assistant Secretary of the Navy for Manpower and Reserve Affairs. As ASN for M&amp;RA, he is responsible for the oversight of manpower and reserve component affairs of the Department of Navy, including the full spectrum of policy and programs for military, that is active duty, reserve, retired, their families, and the civilian workforce.</p><p><strong>David</strong> 01:04</p><p>Before his appointment, Secretary Kohlmann held a variety of roles both in and out of government. He served in the Navy for 20 years, where he was deployed into combat as an F-18 carrier pilot, flew as an instructor with the US Marine Corps, and worked in several tech-focused roles at the Office of Naval Research, Defense Innovation Unit, and Chief of Naval Operations Rapid Innovation Cell. In the private sector, Secretary Kohlmann worked as a consultant at McKinsey, as an investor and CEO at Cubic Capital, and as the CEO of New American Industrial Alliance.</p><p><strong>Maggie</strong> 01:37</p><p>In this conversation, we cover everything from how the Navy can recruit tech talent, how they can upskill their existing workforce to prepare for the future of software-enabled warfare, how the Navy is modernizing its manpower management systems, what the private sector and public sector can learn from each other, and much more. So Secretary Kohlmann, thank you so much for joining this podcast. We&#8217;re really excited to have you.</p><p><strong>Sec. Kohlmann</strong> 02:00</p><p>David and Maggie, honored to be here. Thank you for having me.</p><p><strong>Maggie</strong> 02:03</p><p>So let&#8217;s start with just a simple question. I think most of our listeners are probably not familiar with your role and organization. However, it&#8217;s clearly a critical role. Organizations are only as good as the people within them. So can you tell us a little bit about what your responsibilities are as the Assistant Secretary of the Navy for Manpower and Reserve Affairs?</p><p><strong>Sec. Kohlmann</strong> 02:23</p><p>Yeah, the government likes to put huge titles on what are... Have far shorter titles in the private sector. This is basically chief talent officer, Department of Navy. So a million personnel across our whole organization between active duty, reserve, military folks, and then all the civilian workforce, including the 200,000 civilians across the world, and a contractor workforce about 150,000. So everything from policy, promotions, retention, recruitment, all the things that go into fielding this workforce fall under my remit.</p><p><strong>David</strong> 02:54</p><p>That&#8217;s awesome. And, so Secretary Kohlmann, it&#8217;s great to have you on the podcast. We&#8217;ve known each other, gosh, for over a decade, I think, when I met you, through the Defense Entrepreneur Forum, on Stanford&#8217;s campus 2016, I think it might have been. I&#8217;m sure we&#8217;ll dive into some of the DEF stuff and everything that your career&#8217;s entailed. But, in preparation for this podcast, I was, reading your Senate confirmation hearing notes, and clearly you come from a long lineage of military pilots, and so to say that this job is core to your DNA I think would be a bit of an understatement. But now having been in the role for, gosh, seven-ish months, eight months, what are your top priorities, for the Navy as far as manpower and readiness?</p><p><strong>Sec. Kohlmann</strong> 03:45</p><p>Yeah, there are three things I&#8217;m focusing my time and attention on. The first is broad talent management and kind of updating our approaches for the 21st century. Military manpower and even the civilian manpower force that I&#8217;ve, have the honor of serving and leading has an industrial age approach. Single widget comes in on the entry. There&#8217;s career pipeline things that happen. For the most part, they&#8217;re interchangeable, then you retire on the back end We&#8217;re trying to change that into an into an information age approach, where an individual has unique skills and talents that they have inherent to who they are, the things they are gifted at, the things that they like to do. The organization has specific problems that they need solved. Figuring out ways to better match the specific skill sets with the problems the government has, and then providing promotion paths and options through that is somewhere where I&#8217;m trying to push the department. The second category really gets into really ensuring we have a strong foundation, and this gets into our civilian workforce. You know, when I was in the military, I didn&#8217;t realize we had, you know, 200-plus thousand civilians that were doing a lot of great work behind the scenes. How do we ensure that they have the right promotion pathways, the right recruitment opportunities, the right baseline of interesting things that we can leverage?And then more importantly is... Not more importantly, but equivalent to that, is the shipyard workforce. You know, shipbuilding has become, front of mind all the way from the president down to where we&#8217;re at right now. And to be honest, we&#8217;ve kind of hollowed it out over the past 20 or 30 years. And we&#8217;ve realized that the American shipbuilding industry and our maintenance approaches could use some improvement. And so we&#8217;re spending a lot of time trying to figure out, do we have the right incentives in place to recruit, retain, and then attract the next generation of shipyard workers, to do the maintenance activities that are in our four public shipyards right now. And then the last one is what I call white glove service for those who have served and those who serve. And this is about the day-to-day processes that folks might experience. So I&#8217;m also responsible for a number of boards that we have, the Board of Naval Corrections, being one of them. And if someone who is of, former service comes in and says, &#8220;Hey, there&#8217;s something wrong with my record. I wanna have that corrected,&#8221; they send a mail package into this mailbox, and it kind of gets in the system. And the system does its thing and might pop out six months later or three years later or some amount of time. We have all these processes in the department that if we can map and understand better, we can compress that time in order to deliver the outcomes that our service members both in uniform and out of uniform deserve. Those three areas are spending a lot of my time right now.</p><p><strong>Maggie</strong> 06:19</p><p>Yeah, so I&#8217;d love to pull a thread on that first one, on, you know, talent management and modernizing that process. Can you talk a little bit about, you know, what does this industrial age approach look like today, and what will it take? You know, what is your vision for bringing it into the 21st century?</p><p><strong>Sec. Kohlmann</strong> 06:35</p><p>Yeah, I mean, on the military side, there&#8217;s been what we call golden path career paths for a long time, especially in the officer community, where if you&#8217;re an aviator, surface warfare officer, a submarine officer, you kind of know what every step of the hierarchy is from the time you enter service to the time you retire, whether it&#8217;s at, you know, 10 years and you transition out, or 20 years, or 30 years. And There, there&#8217;s a lot of flexibility though that isn&#8217;t really built into the system. So my personal story, I chose to leave the military at about 12 years of active service to go get a graduate degree. At the time, graduate degrees were not really encouraged in the aviation community. And if I wanted to do it on the government&#8217;s dime, I&#8217;d basically be pushed off track and would go into a different category of officer. That didn&#8217;t necessarily seem right to me. On the civilian side, we kind of don&#8217;t really have any track whatsoever. There are some for highly technical areas, but most folks, you know, kind of feel their way around promotions and opportunities and people they know, as opposed to, you know, clearly defining what their outcome they wanna be and then knowing how to get there from step first to step last. And especially in the reserves as well, one of the things we&#8217;re seeing is there&#8217;s an immense amount of talent in the commercial sector that has a deep desire to serve their country How do we slot that in to the organization so that they can get recognized for kind of their skills on the outside, but also bring those skills directly into what&#8217;s happening in the military? This is what we&#8217;re doing with the Naval Innovation Unit and other organizations. But it comes down to that fact, you gotta find the right person in the right job to solve the right problem. And I think up until recently, we&#8217;ve had more of a, &#8220;Hey, anybody will do for this specific job. There&#8217;ll be a good enough outcome that happens,&#8221; as opposed to take, as opposed to taking advantage, like the asymptotic upside that comes when finding the perfect genius for the perfect thing to be solved. With kind of a full force data analytic view, we can start parsing through and finding more signal amidst the noise to really match the right people into those jobs that really will accelerate the outcomes that we have for the organization.</p><p><strong>Maggie</strong> 08:34</p><p>Yeah, I wanted to ask one question on something you brought up, which is this, you know, how do we get more people from the commercial sector into the Navy and into the armed forces more broadly? I mean, I know I have some friends who have looked into it. It&#8217;s a pretty long process to get in, and even once you&#8217;re there, you&#8217;re not guaranteed to necessarily get a role that is gonna fit your particular skill set. I know this is something you&#8217;ve had some initiatives around, like with the Navy Innovation Unit, so would love to hear a little bit more about how you&#8217;re thinking about getting people from the commercial sector into either the Reserves or other parts of the government.</p><p><strong>Sec. Kohlmann</strong> 09:09</p><p>Yeah, it&#8217;s challenging, but it&#8217;s, now&#8217;s the time to do it. So we&#8217;ll use the Naval Innovation Unit as a great example. So the Army actually led the way here about a year and a half ago now with what they&#8217;re calling Debt 201, which was taking senior executives from Silicon Valley and quickly getting them through a commissioning process, through an application, and then applying them directly against the problems the Army had. The Navy&#8217;s taken a little bit more expansive view with a larger footprint, but taking 10 folks from the outside, direct commission them in as 0-3s or 0-4s or 0-5s, so lieutenants, lieutenant commanders, or commanders, commensurate with the level of skill, and then putting them within the Rapid Capabilities Office, which is a group in our Research, Development, and Acquisition organization, and then using them combined with existing Naval Reservists that have, working in Silicon Valley but have risen through the ranks to kind of have that cultural, insight that they already have, then applying them against direct problems. Bit of an expedited pathway, kind of an experiment where it&#8217;s an application process. Hey, we have 10 slots available, got about 300 folks who have thrown their name in the hat right now. Have a filtering, select those 10 folks, and then very quickly commission them and put them through a five-week, what we call, ODS, so Officer Development School, that gets them up to speed on the militarization pipeline faster than you would normally. And what we&#8217;re trying to seek out is like, hey, the Navy knows that we have gaps in particular areas. How do we then, again, take the unique individual to solve that problem and slot them in more quickly? You know, there are a number of other areas the Navy has as well that are professional in nature. We already do this with doctors a lot. One of the biggest challenges and shortages that we have in the Navy is with high-skill surgeons and other skillsets that, you know, people on the outside are making a lot of money on. They don&#8217;t necessarily wanna deploy, but if they do, we can direct commission them, &#8216;cause really what we&#8217;re solving for is their specific skillset as opposed to their military rank equivalent of militarization. We have things as the Supply Corps or the JAG Corps or others that at the end of the day, you have to have some level of militarization, but if you have the right skillset and you&#8217;ve proven the outside, we should be able to bring you in at a relatively senior level to actually apply your insights to solve that problem for the military. So for me in the organization, NIU is a way to start that with the tech scene, but I can see that if it works, kind of expanding it to broader segments of the reserve population in particular, to have that kind of revolving door between the civilian and military sectors to get the best of both worlds.</p><p><strong>David</strong> 11:36</p><p>Yeah, it&#8217;s fascinating. And, you know, this translation between going from the commercial sector into the military apparatus and back and forth to try to take advantage of some of the cultural norms within the commercial innovation ecosystem, apply it to the national security use case. I think that&#8217;s something that, you know, we stumbled upon with Defense Innovation Unit so many years ago when we brought in these hi-highly qualified experts, essentially entrepreneurs, and, you know, put them on some of our most vexing problems across the department, and then just see the magic happen. And it&#8217;s really cool to see the Navy and the Army, and I&#8217;m hoping my, beloved Air Force at some point also adopts these types of innovative approaches as well. But maybe, you know, moving gears to your second pillar on the civilian workforce and incentives especially, you know, whether we&#8217;re talking about those in acquisition program offices, which is the world I came from. And so, yeah, upon commissioning and getting out to Peterson Air Force Base, you know, the military people were the minority, and the majority of people that you interacted with on a day-to-day basis were civil servants. And then you go out to the shipyards, and it&#8217;s even more dramatic, right? As far as seeing a uniformed, member versus a civilian corps. So how are you thinking about incentives and, you know, especially with a very robust private sector that you&#8217;re ultimately competing against and trying to take advantage of the reindustrialization excitement that&#8217;s happening, especially in the Navy around shipbuilding. You know, I&#8217;m curious how, you know, how you&#8217;re taking a very, like, strategic vision but then a tactical approach towards making it better, right? And it can always be better, but certainly, you know, we have a lot to work with here.</p><p><strong>Sec. Kohlmann</strong> 13:29</p><p>Yeah. I mean, incentives absolutely matter, and increasingly over time, the patriotism premium has gotten higher and higher for those who choose to serve their country and their government. I use the shipyard example in some of the things that we&#8217;ve tried to do recently to kind of bridge the gap. You know, up until a couple years ago, it was in some cases better for someone, say, in Pascagoula, Mississippi, to actually work at a Chipotle across the street than be in the shipyard because the wages they were paying just weren&#8217;t competitive with the market. And so, we had to figure out how to, how to incentivize them and make sure that they were getting paid what they were worth. So a number of things that we&#8217;ve done, include more pay-for-performance opportunities. We&#8217;re working with a number of organizations, both within the executive branch and legislative branch, to think about how do we restructure the pay scale, to reflect specific skill sets but also reward people for outstanding performance? What&#8217;s been interesting is many people heard about the Department of War awards that happened at the end of 2025, kind of, 15,000 or $25,000 bonuses that were given to a set number of folks, for high performance. And as I walked around to some of the shipyards getting some feedback on that experience from some of the frontline workers and even the supervisors, there was one supervisor in particular that said, &#8220;Hey, this has actually transformed our workforce.&#8221; In one instance, it was life-changing money for some of these shipyard workers, but it also was an opportunity for those that didn&#8217;t quite meet the bar to have hard conversations with their supervisors, asking, &#8220;Hey, why wasn&#8217;t I eligible for this?&#8221; Or, why did I just not meet the cut?&#8221; And a lot of the supervisors are gonna lay out expectations in a way that they hadn&#8217;t been able to do before, &#8216;cause now there was a motivation to get to that higher compensation level. And got a report a couple weeks ago from this individual, that I&#8217;d followed up with kind of earlier in the year, and he said, &#8220;Hey, output&#8217;s basically doubled on some of our core projects because people now realize there&#8217;s an opportunity for them to be rewarded for hard work.&#8221; Another example that we looked at is the way that the government does wage scales and GS employees, one&#8217;s kind of the touch labor, individual contributor, the other are supervisory roles in the GS scales, is there was a crossover point where if you had a... If you, if you were sufficiently advanced in your individual skill, like a welder, for instance, 10 or 15 years in, you kinda capped out on your pay, and you had to then jump over to the GS scale to be a supervisor to make more money. But not everyone&#8217;s built to be a supervisor or manager, and David, as you and I know from our work in Silicon Valley, sometimes the IC software engineer is making more than their manager &#8216;cause the value they&#8217;re providing to the force is that much higher. And so you look at some of the Korean shipyards and Japanese shipyards, one of the reasons they&#8217;re so good is they have this cadre of folks who have been there 20, 30, 40 years that are absolute exceptional people in their craft in one specific thing. How do we take that mindset and bring it to the government workforce as well? How do we create those master welders that they can stay on the front lines doing that job for decades and get rewarded for that without having to hop over to be a supervisor? So we&#8217;re exploring ways to kind of fix that gap And then on the, on the, on the civilian side, just writ large, I think we gotta we gotta be more intentional how we reward people. Right now, the government has a lot of authorities with, you know, what it can do for spot awards or special purpose awards, and being more intentional about being clear of, &#8220;Hey, if you do X, Y, and Z and excel at a great level, there will be a bigger award bonus pool.&#8221; We have authorities to do that right now, but it&#8217;s a matter of shifting it and then shaping our budget in such a way that we have the right amount of money given to the right people to drive that incentive loop moving forward. So a lot of it has to do with incentives within existing authorities, kind of restructuring the way that... Again, things were designed in the &#8216;50s and &#8216;60s for a reason, but, you know, 2026 is different than what it was 60, 70 years ago.</p><p><strong>Maggie</strong> 17:24</p><p>Yeah. It makes a lot of sense. You know, I wanna turn to a question. This podcast, we typically focus on our discussions around technology. I think we&#8217;re all tech nerds here. So I wanted to hear, how do you see the role of technology helping to support your priorities when it comes to managing talent in the Navy?</p><p><strong>Sec. Kohlmann</strong> 17:43</p><p>Yeah, I&#8217;m gonna go in a little bit different direction. We can circle back to that question as well. You know, I&#8217;m a, was a venture capitalist, ran a hard tech startup, flew F-18s, another value of technology. Technology&#8217;s a critical enabler, especially in warfare, and even our broader American economy. But at the end of the day, technology is always in service to humans, and technology does not actually work or accelerate unless it&#8217;s solving a human problem. And on the battlefield, it&#8217;s men and women who are on the front lines using technology who find the most creative uses in that crucible of combat, something I call weapon-warfare fit. If you have weapon-warfare fit, it means that there&#8217;s a system that&#8217;s actually doing something in service to fighting and winning that war. And the most tangible example recently is Ukraine. You know, it&#8217;s the tens or hundreds of thousands of folks on the front lines who are having, you know, their friends killed beside them with these unmanned systems. And on a daily and weekly cycle, they&#8217;re taking that technology and modifying it to sort to human ends, and that requires a very creative human to get that, to get that question right. So as I think about, like, talent development, it&#8217;s about how do you think about that technology-human fusion such that technology is built to solve those human problems, but at the same time, the human is in or on the loop to be able to utilize it in the best way possible and use creativity to kind of break the rules when needed because it&#8217;s a life or death situation. And so as we think about talent development in the, in the, in the Department of the Navy, on the military side, it&#8217;s about creating great leaders who can use technology to the best of their abilities. But on the civilian side, it&#8217;s about how do you find those exceptional people that then can be put in positions to drive change and opportunity? And I&#8217;ll end this, kind of this theme with a story. So we ran a data challenge back in the, in the spring, and we kinda gave open access to a much of our HR data. As long as you had clearance to view it, you were allowed to do it, and self-generated teams across the force. And we probably had 10 teams kind of develop themselves, and one of the, one of the winning teams, one of the top three teams, they were sharing their development story with me, and what was interesting is their senior leader actually didn&#8217;t want them to participate. They said, &#8220;This is taking away from your day job.&#8221; And for one of these individuals, their boss actually put more workload on them to prevent them from taking part. And yet this individual, with their team, still managed to do exceptional things and developed a solution that&#8217;s now very useful for us at the Department of the Navy. Like to me, it wasn&#8217;t the tool or technology that was the problem, it was the human systems that elevated the individual capability to a level that could take advantage of the technology that we had right now. So as I think about talent management in the department, it&#8217;s about how do we find those nodes of genius and make sure that they&#8217;re empowered to solve the problems they can and align with the, with the technology advancement we have that&#8217;s developing. So it&#8217;s gotta be a parallel process.</p><p><strong>David</strong> 20:31</p><p>Yeah, and what you talked about with that anecdote also highlights a lot about culture and, you know, no amount of tools can fix culture. Though, you know, I&#8217;ve been in the military now for a long time on the active duty and the reserve side, and Lord knows I&#8217;ve interacted with any number of HR admin tools I honestly feel as though it&#8217;s sort of a potpourri of at some point I get to the right conclusion of the task I&#8217;m trying to figure out, but it was never as obvious and intuitive as it should&#8217;ve been. And I feel as though part of the issue when it comes to the military, and you touched upon this a little bit with your people are thought of like fungible assets that are just interchangeable cogs of the, of the machine. And really, we should be treating individuals for the unique talent that they are so they can reach their highest potential. And I find that a lot of our HR and admin systems are trying to boil the ocean and treat everyone, regardless if you&#8217;re a fighter pilot or an acquisition officer or something in between the tip and the blunty part of the spear, one system to solve everything. And I&#8217;m curious if in part of this, you know, priorities of execution that you&#8217;re trying to maybe subjugate the career fields and find the right tools given, their culture, the lifestyle, whether or not they&#8217;re in an office or on a computer more often than not, or if they&#8217;re behind, you know, a joystick in a cockpit. Curious how you&#8217;re kind of thinking about that piece of the equation instead of one size fits all for the entire workforce.</p><p><strong>Sec. Kohlmann</strong> 22:12</p><p>Yeah, I mean, it&#8217;s truly a balance. I think one of the eye-opening experiences in this job is you kinda do have to look at the macro to some extent. You know, the three hundred and sixty thousand Navy active duty folks and another sixty thousand on the Reserve side. There is a degree in which People are a part of the whole, and so you wanna have the broad trends. Do we have enough, you know, department heads in the surface warfare community? Do we have enough commanding officers in the, in the submarine community? Those are somewhat interchangeable. And yet each submarine is gonna have a different setup of the commanding officer, the executive officer, the wardroom. If you inject a new person, that person has a personality, and that person has a unique skill set. What if you could have an algorithm that inherently knew, a, I&#8217;ll call it a digital twin or digital human, that, hey, Ben is an INTJ. He had, you know, one and a two on the working genius, and he was X, Y, or Z on another personality profile. And oh, by the way, he&#8217;s really good at kind of high-level strategy. He loves playing Axis and Allies and Risk, loves to read on the weekends. And then you have person X who&#8217;s very gregarious and outgoing, an X, Y, or Z thing. Well, how do Ben and person X interact? Well, you can imagine a world in which it&#8217;s not just about putting Ben in the same squadron because he&#8217;s a body, but, like, how does this, how does this interactive team work together, across the whole? If you can have the quantum of data of a digital human that has characteristics about their performance, about their skills and whatever, you can, you can do the macro-level aggregation. Hey, I know I&#8217;ve got 11,000 financial analysts in the Department of the Navy. I&#8217;ve got 8,000 contracting specialists. But you can also say, okay, when Ben goes to apply for this job or when Ben goes to in this squadron, here&#8217;s the characteristics of people around him, you know, based on trends or performance reasons. We realize there might be a mismatch in terms of how he fits in. Maybe he&#8217;s better suited over here. Or we know that he wants, his family is in Dallas, and he should be stationed in Dallas, and so our matching algorithm kind of highlights that in whatever capacity he thinks is important. I think there&#8217;s a world in which we get there, where we can take the macro and the micro and kind of find the right happy medium. And we&#8217;re starting to do this right now with detailing for the enlisted force, and this is to the deep credit of Admiral Hames and some of the folks down there, is there&#8217;s right now an algorithm that a bunch of sailors can, apply for basically, and it&#8217;ll send them, &#8220;Hey, these are the top 10 jobs we think that you&#8217;re eligible for based on what your career progression needs to be, what your skill sets are, what you care about from a, from a location standpoint.&#8221; You don&#8217;t have to take these 10, but it&#8217;s a great starting point to have that conversation with your detailer. What we found is even though that&#8217;s like a human on the loop with a computer doing the system, there&#8217;s, there&#8217;s a higher level of uptake rate and retention because the sailor now realizes there is some intentionality around their careers. They may not leave the service. We&#8217;re seeing anywhere from 30% to 40% of the people who would&#8217;ve left staying because of that more, that more high-touch detailing approach. So I think we&#8217;re seeing a convergence of technology and insights right now where in the medium term, maybe a year or two if we build it right, we could start having these nascent systems to kind of do this matching better to ensure people are in the right job.</p><p><strong>David</strong> 25:33</p><p>Yeah. And so it sounds like, you know, you are trying to incorporate AI and just a ton of big data into helping identify, you know, jobs and roles and opportunities for folks. I guess I&#8217;m curious, you know, where from a Navy standpoint are you guys taking inspiration, right? Obviously, the Navy it&#8217;s the best navy in the world, and I think probably potentially the largest. Not sure exactly what China&#8217;s numbers are relative to the US. But, you know, you&#8217;re not the only large corporation trying to figure out a diverse set of skillsets across a diverse set of locations to ultimately, you know, get mission readiness, mission effectiveness. And so where, you know, when you think about solving these problems, are you looking towards large private corporations, whether they be, you know, big energy, you know, from the state that you hail from, or other Fortune 10 type entities, or maybe the Air Force?</p><p><strong>Sec. Kohlmann</strong> 26:33</p><p>Yeah. I mean, to be honest, this is probably a gap in where we&#8217;ve spent our time to just know what&#8217;s happening in the outside world. You know, in my consulting days, I did a number of HR studies for large organizations, so taking some of the lessons learned there of how to look at the workforce, how to think about restructuring, how to do some of this data analytics. But I think there&#8217;s actually a big opportunity for us to improve, and I think there&#8217;s a, there&#8217;s a couple cultural things that, you know, we can, we can lean more heavily into The first is this belief like the government is different, and the military is different, and the broader skillsets that are over there don&#8217;t apply to us. I think one of the things I learned in consulting, having worked in the government, having worked in a bunch of industry is a lot of the problems are the same, and the insights are like 80 to 90% there. There&#8217;s the 10% that&#8217;s important, you gotta get it right, but the foundational of how to manage humans, how to think about structuring, they&#8217;re all similar. So we could reach in there and grab some more information. The other thing too is more cross-pollination, and we talked about this earlier in the conversation. More cross-pollination for business ideas coming into government to just, you know, raise the awareness. There is a different way to do things, and I think this is where the Department of War has been leading forward in the bond program especially, where they&#8217;ll bring in senior executives who are post-economic in many cases and just want to serve, and bring them in executive roles to kind of partner up with their equivalent to kind of Hey, this is what&#8217;s happening in the private sector. This is what we did at Energy Company X. This is what we did at Walmart or whatever, and help that, help that, help that kind of exchange of information flow. I can&#8217;t help but think there&#8217;s probably value in more secondments, you know, mid-grade GS&#8217;s goes over to work in industry for a couple years knowing they&#8217;re gonna come back to solve a problem, to kind of get that experience, the... I think there&#8217;s a, the, what is it? Secretary of Defense Technical Fellows or something like that goes to industry. That cross-pollination is critical. Not as good as we could be at it. I&#8217;ll also say one other thing. You know, the Chick-fil-A model of high customer experience I think is one I wanna see about integrating into our reserve centers. You know, who is the customer of a reserve center? It&#8217;s the reservist who&#8217;s coming in on the weekend, and right now the experiential level isn&#8217;t as high, which kind of drives misintegration. How do we get the lesson learned from high customer service organizations and apply them into high customer service facing military functions to drive that experience and also the outcomes better? So a lot of work we could do, but we&#8217;re thinking about it.</p><p><strong>Maggie</strong> 29:07</p><p>I recently read, an article with some pretty concerning statistics, or statistics I found concerning. It said, you know, fewer than 25% of Americans age 17 to 24 are eligible to serve in the military without a waiver. The number of 18-year-olds is actually projected to decline by 13% by 2041, and the propensity of Americans to serve in the first place has fallen from 16% in 2003 to 10% in 2022. However, I also saw the Navy is actually ahead of schedule on recruiting this year. So I just wanted to hear a little bit about how you all are thinking about recruiting and some of the challenges that the department as a whole is facing.</p><p><strong>Sec. Kohlmann</strong> 29:50</p><p>Yeah, it&#8217;s a paradox. I attribute it to probably three things. The Navy Marine Corps, you know, I have the honor of helping to oversee both. 2022, 2023 was a real nadir for us, and Navy Recruiting Command saw that deficit and started to apply kind of best practice from industry with Salesforce and others. And the current commander of Navy Recruiting Command, Jim Waters, he&#8217;s basically instituted a daily ops update that has incredible dashboards to highlight and pinpoint which specific recruiting stations are falling short on which specific line items they need, they need to fill for. And as a result, it&#8217;s driven attention to leadership level to areas of improvement. And it&#8217;s, you know, it&#8217;s an accountability measure, but it&#8217;s also like, &#8220;Hey, what&#8217;s going wrong here? How do we problem solve that?&#8221; So that deep dive execution and being relentless at the basics, I think, has gotten the Navy back on track On the Marine Corps, it just comes back to the core ethos they&#8217;ve always had, the few, the proud, the Marines. Like, that mindset continues to resonate, that are you good enough? Can you meet the standard? There&#8217;s a lot of young men and women who wanna try out for that, and they-- If I do that, if they achieve that, like, that&#8217;s something they can hold their head high about. And I think that has driven kind of a resurgence in recruiting, across both the Navy and Marine Corps right now. You know, looking to the future, the demographic cliff is real. You know, 2028, I think that&#8217;s when kind of the 17, 18-year-olds kind of fall off, given what happened in the early 2000-- or, you know, kind of post global financial crisis era. And I saw this when I was at the board of a university down in Texas. We were kind of looking at that number. It&#8217;s like, &#8220;Hey, how do we make this math work?&#8221; there will still be the cohort of 17 to 23-year-olds that will be a target market. But the question is, how do we think about then augmenting it from folks who are kind of in career one and a half or two? Maybe the more reserve option. You got five to 10 years in, how do you slot that experience in a different capacity? Who knows where AI takes us, but as those jobs become maybe less secure, there will always be a need to have people defend their country and make it high enough status and high enough paying that it&#8217;s a, it&#8217;s a, it&#8217;s an option for people to flow back in. Maybe there&#8217;s a world in which we have some sort of loan repayment program for 25 to 30-year-old folks who tried the private sector out, couldn&#8217;t quite get traction. It&#8217;s an incentive bonus to kind of get those folks back in the, in the realm. I don&#8217;t know. There&#8217;s a bunch of stuff that we&#8217;re thinking about to try to, try to accelerate. But I&#8217;ll also say, whenever the American public realizes there&#8217;s a need, and a legitimate one, they tend to, they tend to fill that gap. You know, we saw it in 9/11, we saw it, you know, kind of 2024, 2025. So I&#8217;m optimistic, but, like, w-we are watching it closely, and there are some changes that will have to be made down the line.</p><p><strong>David</strong> 32:31</p><p>Yeah. So, you know, you highlighted on the top of the funnel with the next generation of uniform wearers. I&#8217;m kinda curious on the other side, right? So you and I are kind of anomalies getting out at the 12, 13 year point, or at least separating. Normally, people would stay in for the full 20, right? The whole cliff vesting strategy that we were under. But about 10 years ago, they implemented the blended retirement system, which makes it a little less obvious to stay in from a financial reward standpoint as you become a, you know, mid-career officer. I&#8217;m curious if there&#8217;s anything you could speak to on whether or not recruitment at the later stages of officers to get to go for O-five and O-six, or whether or not there&#8217;s a bit of a fall off there too.</p><p><strong>Sec. Kohlmann</strong> 33:24</p><p>Yeah. Broadly speaking, we&#8217;re hitting our retention numbers, in many cases are exceeding them. But there are specific communities where we&#8217;re struggling. These are kind of the more high skill communities, cyber, aviation, submarines, places where there are really clear and tangible, financial benefits on the other side that even if you stayed at 20 to get your pension, you know, you&#8217;re missing out on millions of dollars potentially. I think the integration of the Blended Retirement System, if anything, forces us to be better to make sure that what do we have to do to keep these folks? And it&#8217;s not the same thing that took in the &#8216;90s or the 2000s or even the &#8216;80s, but, like, it forces the organization to shift their approach to try to retain these people with the salary caps that have been given to us by Congress and others. And I think we&#8217;re kind of going through those growing pains right now, especially with aviation. This is something near and dear to my heart One of the reasons I got into this, you know, 15 years ago was I saw the flight of fighter pilots from the Navy and wanted to figure out why, and it&#8217;s only snowballed from there. This is getting increased congressional attention, attention elsewhere in the Department of War. And it comes down to quality of service, what&#8217;s the experience they have, do they have other options? A lot of people are putting a lot more stake, especially men, into families, and so they&#8217;re not maybe taking the 8 to 10-year carrier pathway &#8216;cause they wanna spend time with their kids between 18 and 20 in a way that maybe they didn&#8217;t 20 to 30 years ago. So that&#8217;s having an increased effect on that as well. So what does that mean for what it means to be a fighter pilot in 2026 and beyond when you need that exceptional skill set? I think we&#8217;re wrestling through that question in particular. We have some things that we&#8217;re thinking about, but it&#8217;s becoming more and more apparent in that community. But writ large, we&#8217;re actually meeting a lot of our &#8216;04, &#8216;05, and &#8216;06 goals. It&#8217;s just those highly skilled roles where there&#8217;s a deep market, competition, that it&#8217;s becoming trickier to retain those folks.</p><p><strong>Maggie</strong> 35:19</p><p>You&#8217;ve now spent time in government, in the military, active duty, as an investor working with startups. Having seen all sides of this equation, what advice do you have for startups looking to work with the Navy and the U.S. Military as a whole?</p><p><strong>Sec. Kohlmann</strong> 35:36</p><p>First of all, find exceptional talent. I mean, I think at the end of the day, like, this job just reinforces something I learned being an investor, is that the best companies win &#8216;cause they have the best talent. They can solve the hardest problem. They can figure it out. And that talent in government comes down to understanding how the government buys things, how Congress works, who the true decision-makers are in the department, and what the non-intuitive problems are, you know, downstream of what happens. I&#8217;ll just give an example. You know, submarine supply base, not just about building the submarine itself. It&#8217;s about the tier two and tier three suppliers that have to supply the parts to both maintain the submarines and build them. Well, if we know that we&#8217;re gonna have an increase in the total number of submarines and, maintenance capability, we&#8217;re probably gonna have a submarine supply shortage. You&#8217;re seeing a couple startups that have kinda sneaked into that realm in a very impressive way and are filling that gap. So where do you see the puck going that is gonna be a funded source that is not yet filled yet? So thinking about it that way. There&#8217;s a little bit of luck. Two, three, four years ago, UASs weren&#8217;t... Well, I guess they&#8217;ve always been big. But there were some capabilities and systems that if you were ahead of the curve building then, are now emerging right now. Are you ready to jump on that, take advantage of it? But honestly, David&#8217;s probably the best expert here. He&#8217;s written the most on it. I know you have too, Maggie. You guys are, you guys are well-versed in this. But it comes down to finding the right people to find the other right people in the organization to then win those contracts and kinda find the scaling opportunities.</p><p><strong>David</strong> 37:12</p><p>Awesome. Well, thank you. And I guess, as we wrap up, we just have one special question that we did not prep you for, and we were wondering what kind of insight you can provide us about Top Gun 3 coming out, and will you be playing a starring role as a wingman to, Tom Cruise?</p><p><strong>Sec. Kohlmann</strong> 37:30</p><p>Well, I can&#8217;t say much, but there won&#8217;t be any people in it &#8216;cause it&#8217;s gonna be all unmanned, so.</p><p><strong>David</strong> 37:35</p><p>Will it, though? I mean, gosh, the magic of Top Gun: Maverick was, you know, going back to the third gen fighters, right? Or fourth gen fighters to take out whatever adversa- fictitional adversarial was.</p><p><strong>Sec. Kohlmann</strong> 37:48</p><p>No, that&#8217;s right. That&#8217;s right. Well, the sad part is when they come out with Top Gun 3, the old airplane will be the Super Hornet, which is what I flew, which makes me feel really old. So no, like I can&#8217;t wait for the third one to come out if they choose to do it. So I don&#8217;t know if you guys have any tipper, but that&#8217;d be a great one.</p><p><strong>David</strong> 38:01</p><p>Awesome. Well, Secretary Kohlmann, thank you so much for spending your time with us, and really look forward to all the great work that you&#8217;re doing to help increase readiness, get the talent pool ready to go, and make sure that we can deter our adversaries that, not today, not tomorrow. That&#8217;s right.</p><p><strong>Sec. Kohlmann</strong> 38:17</p><p>Thanks, David. Thanks, Maggie.</p>]]></content:encoded></item><item><title><![CDATA[🎙️ Ep 27 - Arena Physica: Building Electromagnetic Superintelligence]]></title><description><![CDATA[Electrical and RF engineering are becoming more and more important as more hardware becomes software-defined.]]></description><link>https://maggiegray.us/p/ep-27-arena-physica-building-electromagnetic</link><guid isPermaLink="false">https://maggiegray.us/p/ep-27-arena-physica-building-electromagnetic</guid><dc:creator><![CDATA[Maggie Gray]]></dc:creator><pubDate>Fri, 24 Jul 2026 19:57:35 GMT</pubDate><enclosure url="https://api.substack.com/feed/podcast/208378208/601ecf1346150e63282bb18c246d8353.mp3" length="0" type="audio/mpeg"/><content:encoded><![CDATA[<p><span>Electrical and RF engineering are becoming more and more important as more hardware becomes software-defined. However, the software tools for electromagnetic engineering have not kept up with the 21st century. In the newest episode of the </span><strong><a href="https://www.linkedin.com/company/mission-matters-podcast/"><span>Mission Matters Podcast</span></a></strong><span>, </span><strong><a href="https://www.linkedin.com/in/akhil-iyer/"><span>Akhil</span></a></strong><span> and I sit down with </span><strong><a href="https://www.linkedin.com/in/pratap-ranade-7272829/"><span>Pratap Ranade</span></a></strong><span>, the CEO and co-founder of </span><strong><a href="https://www.arenaphysica.com/"><span>Arena Physica</span></a></strong><span>, to discuss the future of these engineering tools. Arena Physica is building the future of &#8220;electromagnetic super intelligence,&#8221; developing an AI native platform for electrical and RF engineering. </span><br><br><span>We discuss:</span><br><span>&#9889;&#65039;Arena&#8217;s new foundation model for RF design</span><br><span>&#9889;&#65039;Combining deterministic and non-deterministic models to automate electrical engineering workflows</span><br><span>&#9889;&#65039;Pratap&#8217;s vision for the future of electromagnetic superintelligence </span><br><span>&#9889;&#65039;And much more&#8230;</span><br><br><span>As always, please reach out if you or anyone you know is interested in working with Arena Physica or building at the intersection of technology and national security.</span></p><p><span>You can listen to the podcast on </span><a href="https://open.spotify.com/episode/4lEjcslG9vfoXBW3grsWkW?si=155c129b73734101">Spotify</a><span>, </span><a href="https://podcasts.apple.com/us/podcast/arena-physica-building-electromagnetic-superintelligence/id1807120572?i=1000777909924">Apple</a><span>, </span><a href="https://youtu.be/AMd1OEDaqjA"><span>YouTube</span></a><span>, the Shield Capital </span><a href="https://shieldcap.com/episodes/arena-physica">website</a><span>, or right here on Substack.</span></p><p class="button-wrapper" data-attrs="{&quot;url&quot;:&quot;https://maggiegray.us/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe now&quot;,&quot;action&quot;:null,&quot;class&quot;:null}" data-component-name="ButtonCreateButton"><a class="button primary" href="https://maggiegray.us/subscribe?"><span>Subscribe now</span></a></p><p><strong>Transcript</strong></p><p><strong>Maggie</strong> 00:18</p><p>In this episode of the Mission Matters podcast, we sit down with Pratap Ranade, the CEO of Arena Physica.</p><p><strong>Akhil</strong> 00:43</p><p>Really excited for this conversation. Pratap&#8217;s building something truly revolutionary. Arena Physica is really focused on the future of what he will describe as electromagnetic super intelligence. What exactly is that? It&#8217;s developing an AI-native platform for electrical and RF engineering, and it&#8217;s applicable across domains. It&#8217;s an agentic platform, Atlas, that pairs non-deterministic AI agents with deterministic hardware, physics, and simulation models to autonomously debug, verify, test, and optimize electrical designs. And as part of Atlas, Arena has also developed the first foundation models for radio frequency, or RF design.</p><p><strong>Maggie</strong> 01:23</p><p>As more and more hardware systems become software-defined, which is a term we&#8217;ve talked about on many past episodes, electromagnetic engineering will be more important than ever. However, the tools available to electrical engineers remain slow and fragmented, largely relying on computational physics simulations that can really take hours to run. Many of these tools really don&#8217;t talk to each other. The data remains siloed and fragmented in all kinds of different tools, really slowing down some of the most crucial engineering that we&#8217;re doing today.</p><p><strong>Akhil</strong> 01:54</p><p>And what&#8217;s really exciting as Maggie and I and the Shield Capital team look at technologies that truly do serve the national security market as well as a host of others throughout commerce and industry writ large. That&#8217;s customers like Amkor, semiconductor customers like AMD, healthcare customers like Bausch + Lomb across the gamut. And, last time I think, Pratap, when I came to the office, I mean, you&#8217;ve been at this since 2019, raised more than 60 million, but most importantly have an incredible 80-person team all in-person in Manhattan working collectively on both the future of hardware and how it integrates with AI agents, and evolving and developing faster. So excited for this discussion.</p><p><strong>Pratap</strong> 02:35</p><p>Great. Guys, it&#8217;s great to be here. Thank you for having me.</p><p><strong>Maggie</strong> 02:38</p><p>So, Pratap, I wanna start with just a basic question. What exactly does it mean to you to be building the future of electromagnetic super intelligence? And maybe part of that, can you tell us a little bit about what Arena is building today?</p><p><strong>Pratap</strong> 02:51</p><p>Yeah, for sure. Like, let me answer your first question, electromagnetic super intelligence first. So the thesis very simply is, you know, there is, I would say, consensus view that language models equal intelligence. So ultimately make a language model very big, and it will kind of reason about everything. We actually think language is not the only primitive of intelligence, and we&#8217;re seeing, you know, this fringe belief getting a little bit more popularity under the moniker of world models, right? So an animal doesn&#8217;t learn to move by reading books about it, right? Like movement is probably another primitive in and of itself. You know, protein structure may actually also be one, and we&#8217;re seeing some really great work out of DeepMind on this. Our belief is, for physics, the fundamental primitive is fields. And, you know, Isaac Newton did not come up with calculus, because it was fun. He came up with it because language was a very poor description of what&#8217;s happening with physics. And so if you think about electromagnetism, of the four fundamental forces of physics, which is the strong force and the weak force, which are nuclear forces, gravity and electromagnetism &#8212; electromagnetism is the one that humans have industrialized the most. We use it to make, you know, our entire semiconductor revolution. Think about radars, photonics, it&#8217;s all powered by that. One of the core beliefs we have is if you were to build a very large model trained on electromagnetic fields. So imagine your training tokens aren&#8217;t words, but they&#8217;re EM fields. You would be able to understand how particular materials and geometries, create certain electromagnetic behavior. And this is basically what&#8217;s used when people are designing, phased array systems for satellite communication, for radar, for high-speed chip-to-chip communication, and interconnects. And even as you move into light and photonics. You asked about software-defined hardware. We&#8217;ll talk more about that, I&#8217;m sure. But you think about a lot of these companies, like our customer set, including companies like Anduril and AMD, Akhil, like you mentioned, they&#8217;re fusing the benefits of advanced electrical design, mechanical, and software all together under one h- one roof to create remarkable new machines, right? And so here you have problems that part of them can be solved with LLM-based agents, part of them require physics models. And so our Atlas product is an agentic product allowing advanced hardware engineering across those three disciplines when they&#8217;re enmeshed together. And actually Heaviside, our EM foundation model, becomes available through Atlas.</p><p><strong>Maggie</strong> 05:21</p><p>So maybe just to level set for people who aren&#8217;t as familiar with the world of electrical and RF engineering, you know, what is the current state of design tools for these kinds of engineers? And then maybe just contrast that with your Atlas platform.</p><p><strong>Pratap</strong> 05:34</p><p>Yeah, for sure. So the current state of design tools is highly fragmented and old, right? So if we look at it, you have... Let&#8217;s say you&#8217;re building a new, autonomous aircraft, right? You are designing electrical circuit, you&#8217;re designing the logic of it, then the physical layout. You&#8217;re putting that in time, in a housing, like probably a metal box of some sort that has to go through, withstand G-forces, go through various, you know, temperature regimes, probably like do some degree of insulation to sort of EW. And then you&#8217;re running specific software on it, probably low-level software, on the flight computer. You&#8217;re not writing, you know, you&#8217;re not writing like a Python app, right? And so all those three interact. If I change how the software behaves, I might heat up my, you know, I&#8217;m gonna generate more heat, right? I&#8217;m gonna generate different behavior. I&#8217;m gonna change how much current is even going into a servo. So these three disciplines, interact very deeply, right? And you can imagine, you know, someone once mentioned to me, the problems always emerge at the seams between teams. And so the problem here is you have a mechanical, engineering group, an EE group, and a software group. Now, software, they&#8217;re running on GitHub, which is owned by Microsoft. Mechanical might be running on NX by Siemens, or SolidWorks by Dassault, and then electrical might be running on Altium, which is owned by Renesas or, a Cadence or Synopsys product. So you have three different, very large incumbent tool chains that you can imagine aren&#8217;t the most sophisticated and don&#8217;t play nice with each other. And then oftentimes, you actually have siloed organizations as a consequence. These guys, you know, they&#8217;re not having lunch together, even if they&#8217;re in the same office, right? And so, but yet we need all these three disciplines to come together for, like, that first autonomous flight to go successfully. And so structurally, we think there&#8217;s actually a problem with the fragmentation and the age of those tool chains. Plus, you know, the organizational mirroring of that, which is three siloed orgs. If the future is more companies doing software-defined hardware, more and more vertical integration, moving really fast, we need a way for this to look much more integrated, much more seamless, sort of like the way software engineering is done.</p><p><strong>Akhil</strong> 07:48</p><p>Pratap, I love the seams between teams connotation. It brings up so many things, and I think maybe highlights we&#8217;ve been hearing a lot about this, you know, software-defined hardware, or in the national security domain, right, the software-defined warfare. But that inherently involves both technically and operationally combining those two seams together. What does software-defined actually mean to you? We&#8217;ve had this conversation on a couple podcasts, and I think it&#8217;s an amorphous term, right? There&#8217;s a technical aspect to it. There&#8217;s clearly, you know, a cultural, a team aspect to it as well. But how do you see the software-defined future and really the role of electronics in the work that you&#8217;re doing evolving? And where do you want it to be? If you can paint a vision or day in the life of someone working at that seam, what does it look like right now, and what should it look like?</p><p><strong>Pratap</strong> 08:37</p><p>Yeah. It&#8217;s a great question. So I think software-defined is this broad term that has come to mean in many things, but it&#8217;s definitely like it&#8217;s a powerful trend. A simple example is a Tesla with an over-the-air software update. You&#8217;ve got the same hardware, new software update lands, it&#8217;s suddenly capable of more. And I think this is a beautiful idea because you can take advantage of the sort of, you know, rapid ways in which we can evolve and adapt software to give your hardware new capabilities. And so this theme, I think we started to see with software-defined radios, but just continues to be sort of the dominant theme. I think one thing that&#8217;s not talked about often is, you know, we can draw up this image in our heads of, great, I&#8217;ve got hardware, now I&#8217;m just gonna put some software on top and software eats the world. I think the reality is it&#8217;s like you&#8217;ve got your brain, you&#8217;ve got your body. There&#8217;s actually a very complicated nervous system and spinal cord and a bunch of stuff that is really important to get these things to work together really well. And I think this is where we&#8217;re seeing a lot of the fracturing, both on the tool chain side and the sort of, you know, employee side. Now let&#8217;s say in a simple example, I&#8217;m an individual engineer with all of these skills and I&#8217;m working on my own project. I&#8217;m taking files out of one system, I&#8217;m putting them in another system. You know, my code, and even if I&#8217;m using my coding agent, is unaware of the hardware environment it&#8217;s going into. My electrical software is unaware of the mechanical. We&#8217;ve literally seen cases where you&#8217;ve made a board, an electrical flight computer board. It&#8217;s great. It&#8217;s designed to spec perfect, turns out beautifully. You&#8217;ve-- your mechanical guys have done your mechanical housing, also designed to spec really great. You literally have a case where then the copper on the board touches the metal from the mechanical, they&#8217;re both in tolerance, and you short the board. And this is not a-- this is not rocket science. This is very knowable, but again, it&#8217;s a function of those sort of, separation of teams and separation of tool chains. You know, in software, we have, this idea of like, you know, continuous integration, you know, like CI/CD. You&#8217;re shipping your code, tests are autonomously running, it&#8217;s getting merged in, and of course, this is taken to the next level with agents. Why can&#8217;t you have something like that on the hardware side, right? Why can&#8217;t you have sort of like, &#8220;Hey, I&#8217;ve updated my firmware,&#8221; automatic compatibility checking with everything else? &#8220;Oh, I&#8217;ve updated my board design,&#8221; why can&#8217;t it check for coherence across the mechanical things? I think these are things that hold our engineers back, and I think what&#8217;s super exciting to be doing this at this moment in time is, you know, for the first time, it feels like you have-- these companies have an imperative to move fast and ship new hardware. This hasn&#8217;t always been the case in the last several decades in hardware. But with companies like Anduril, leading the charge on the aerospace and defense side. Also, companies like AMD, putting the most advanced AI inference chips in the world now out there and building data centers, at like breakneck speed. There&#8217;s this massive race which is creating extraordinary demands on engineering teams that are already pushing the limits of collaboration, but now they&#8217;re going an order of magnitude faster. They&#8217;re already building frontier hardware. You know, the only solution here is AI and automation. This is not one of those things where we&#8217;re coming in to take a job. This is one of those things where literally our customers are like, &#8220;There is no way this roadmap gets done without AI as part of it.&#8221; And I think that&#8217;s what&#8217;s-- it&#8217;s creating a very natural place to plug in. And personally, as a big science fiction fan, you know, we want a future with like sentient factories, growing machines and stuff. How are we gonna get to that world? We want space elevators. I think this is one of those key unlocks. I think if we&#8217;re successful, we get to see that science fiction future come centuries sooner.</p><p><strong>Akhil</strong> 12:11</p><p>Yeah, absolutely, Pratap. In the last 10, 15 years, most people didn&#8217;t go become double Es. They became CS majors. And so you&#8217;re not taking jobs because actually we just don&#8217;t have enough of folks at that layer to go support that.</p><p><strong>Pratap</strong> 12:24</p><p>No, exactly. Everyone went into software engineering. We lost a lot of hardware talent.</p><p><strong>Maggie</strong> 12:29</p><p>Yeah, so Pratap, I wanted to, you know, switch gears a little bit here and dig into a couple of just technical questions on how exactly you&#8217;re able to make a system that&#8217;s capable of doing some of the work of electrical engineers. And one of the things I find really interesting about your platform is that it&#8217;s not like today you just have AI models that are magically able to do everything. You know, if you actually look back at the history of a lot of these electrical engineering tools, you know, there&#8217;s some very sophisticated tools that have had decades and decades and decades of engineering put into them to make these simulations work really well, you know, whether that&#8217;s Ansys, Altium, Cadence, Keysight, et cetera. So I&#8217;m curious to hear, could you talk a little bit about how you combine these non-deterministic foundation models alongside these deterministic simulation and solver tools in order to 10X the performance of both of them?</p><p><strong>Pratap</strong> 13:26</p><p>The way we think about it is, so if you think about the sort of life cycle of engineering, right? You have-- You could think about it as kind of a grid, right? Where the rows are, you&#8217;ve got electrical, you&#8217;ve got mechanical, and you&#8217;ve got software, and they&#8217;re all interacting as you sort of co-evolve through this sort of evolution of developing a new software-defined hardware product. So you&#8217;d start with design, right? And then you would do some degree potentially of simulation. Oftentimes it&#8217;s quick calculation, not quite simulation in the design verification, because obviously it&#8217;s fastest to iterate on the design. The minute you start making it, you start incurring this longer cycle time &#8216;cause you have to make the first version physically. So you get that back and you enter like what people would call engineering validation testing or design validation testing. You have the first prototypes. You know something&#8217;s wrong, you wanna iterate it and tune it. Then you get to, okay, I&#8217;ve got like a production instance, my testing is good, and then you move into kind of mass production and operations. So if we think about this as our life cycle, what we believe is the current system of tooling, right, EDA tools, simulation tools, you mentioned Keysight and test equipment. These are amazing companies that have built very deep, sophisticated solutions that are trusted by pretty demanding engineers for a reason, right? Our view is not that we&#8217;re gonna roll in and, like, do an agentic EDA platform. I think that&#8217;s a... You know, maybe one day one will kind of exist and replace it. But I think the idea is you as an engineer are often, like, flipping. You&#8217;re moving across those stages, and as you move across stages, if you&#8217;re a small company, you may be doing all of it. If you&#8217;re a larger company, that&#8217;s usually a different team. And again, in our grid, you&#8217;re either going up and down, like talking to mechanical, talking to software, or you&#8217;re moving left to right as you go from design to validation to test, you know, into production. And here, like the simple case is you&#8217;re alt tabbing, switching between tools, trying to give them context, right? And so how can we take the power of all these tools? You know, there was a statistic I read, I think recently, I think it was a couple weeks ago now, agentic traffic on the internet has now surpassed human traffic, right? So we&#8217;re seeing like the advent of agents. So now if I&#8217;m an engineer and I&#8217;m going to invoke my agents, how do I get an agent to effectively help me across this thing? The idea is not like I don&#8217;t need to replace my EDA software, but I want my agent to be able to do work in my EDA software. I want that agent to be aware of what the mechanical implications are. And I think here is where your question is very, like, particularly becomes like very pointed, because you do want this flexible reasoning capability of an agent. You do wanna be able to ask it a question. You don&#8217;t wanna have to spell everything out. You wanna be like, &#8220;Hey, can you check if this is gonna work well under the conditions that you know I&#8217;m going to operate in?&#8221; It can inherit like, you know, the ConOp and requirements and specs. So it&#8217;s like, oh, I know you&#8217;re operating under these G-forces, these temperature gradients, this sort of electromagnetic environment. So, you know, it can fill in the blanks, and this is where you need to be very precise. And so the first piece Atlas has is a meta graph which spans those three layers and is deterministic in nature. So it enables graph traversal, hierarchical graph traversal, so you know what nodes this is connected to. Like I mentioned the automotive example, it&#8217;s literally tracing the wire paths and saying, &#8220;This is the most likely place where you&#8217;re probably seeing a short.&#8221; So you really want that to be just, you know, a deterministic picture of the world, right? The second place is then sometimes you need to say, &#8220;Okay, what is-- what am I seeing and how does it match with expectation?&#8221; And those expectations are still determined by physics, right? And so this is where, you know, in the current case, you would agentically invoke a physics simulation. And now I think anyone who&#8217;s used physics simulators, unlike Apple products that are really built to make it easy for use, because you have a very sophisticated user group, these products are terrible to use. They&#8217;re slow, they&#8217;re ugly, they&#8217;re... I mean, it&#8217;s not a fun experience, right? And so how do you actually execute that simulation workload or that physics workload correctly? So these are the two places where if we get this right, you can pair the flexibility of the language model with deterministic lookups on the graph, and then deterministic invocation of the physics simulator. And then if we play this movie forward and we say, okay, agents are gonna continue to get better and this is gonna get easier. You solve the efficiency problems. This is when we start hitting the hard physics wall, and then the next inevitable solution has to be a change in how we do physics simulation or train AI models for physics. And this is where we strongly believe LLMs are not the answer here.</p><p><strong>Maggie</strong> 18:02</p><p>Yeah. So can you talk a little bit more about what it means to build a foundation model for RF? I think most people when they hear foundation model, they think of a language model, you know, maybe a coding model, maybe they can understand like an image generation model. You know, we&#8217;ve all played around with ChatGPT and Gemini and others to generate images. But what does that mean to build this for RF or electrical engineering? Like, what is the data that you&#8217;re training this on? Are you starting from scratch? Are you building on a base model?</p><p><strong>Pratap</strong> 18:30</p><p>Yeah. So in order to answer your question well, I might take a one-minute detour and talk about language models, right? So before language models, we had a whole field of natural language processing and where we&#8217;re really solving these sort of use case-specific problems. We were using different types of models to group words together and, you know, kind of like dismantle sentence structures and create n-grams and really like think about that kind of problem set. What we found with language models was an architecture with the transformer that let us scale it up very easily and, an attention mechanism that let us fetch all of the right context around a particular word to understand what it means. And I think as someone said, like, the meaning of a word is entirely determined by the words around it, right? And so effectively, your cross-attention mechanism is scanning every other word, associating that and saying, &#8220;Okay, great. If I can understand the full context around this word, I can predict the next word.&#8221; So what&#8217;s interesting is that that problem setup is very general, right? That would apply to any word, any language, like, and as we&#8217;ve seen even in things that we don&#8217;t traditionally think of as languages, but are languages like coding. And so as you scaled it up, you know, OpenAI in January 2020 published this seminal paper on scaling laws, also followed by a DeepMind paper on the Chinchilla scaling laws, and that was a profound moment, right? It was the first time in machine learning history where a model got better, as the model got bigger, not just as a function of data. So, as you scale compute, model size, and data size, you&#8217;re getting more capability. As we pushed those parameters to very large values, we saw this emergent behavior where you could do more general learning, generalize across languages, generalize across tasks, right? So that&#8217;s the current state. Now, if we think about electromagnetism, and you mentioned RF, is like actually determined by how Maxwell&#8217;s equations kind of determine how like, you know, any current that basically creates an electric field &#8212; electric field creates current creates electric field. But you have an electric field that&#8217;s changing, that induces a magnetic field. And, you know, electric, changing electric and magnetic fields are also like literally fully describe light, which is a photon. If you actually have a model that&#8217;s going to learn and generalize, it will learn the behavior of electromagnetic fields as a function of the geometry and the material that&#8217;s an input. So the premise is if we can build a large model trained on EM fields, you learn that relationship. So just like you&#8217;ve seen with language models, you&#8217;d be able to basically just say, &#8220;Hey, give me a seven gigahertz band pass filter,&#8221; and it gives you back. And so what we achieved in March, end of March this year, was what we consider the GPT-1 milestone for electromagnetism. Fully autonomous design for 2.5D RF structures. So an RF structure being like some combination of a metal wire and an insulator, a few layers of it, and then they&#8217;re connected together with these little vias that connect the different layers, and the structure should, you know, behave in a certain way. And I think what was super interesting is, one is it was done autonomously. You-- There&#8217;s actually a public preview. You could play with it online. You could type it in, and it will generate you a design. But two is we saw some very strange designs coming out of this, and there was a few that looked more like QR codes than something a human would draw. Now, these are not superhuman designs. Those designs did not have a capability that human designs couldn&#8217;t do, but it&#8217;s super interesting. At this current scale, GPT-1 scale of the model, you&#8217;re seeing weird designs that we wouldn&#8217;t have come up with that work automatically. If we scale this up, our bet is the best answers live in those weird designs that we couldn&#8217;t even think of. And, you know, GPT-3 version of an EM foundation model is probably a breakthrough EM capability that, like, just hasn&#8217;t been done by people today. And like, you know, We got a copy of the book about Lockheed Martin Skunk Works, for everyone on the team because I think that&#8217;s probably the first example of people wielding EM in an original way and actually creating stealth as a national security advantage. So, you know, you think about where that goes, I think there&#8217;s a lot of, like, technology that we could build that we can&#8217;t really do today that this would basically unlock.</p><p><strong>Maggie</strong> 22:44</p><p>So I guess one question that always comes to mind for me when I hear about these sorts of specialized foundation models is just where do you even get the training data to build something like this? Like, where do you get the EM fields that allow you to build these kinds of models at scale?</p><p><strong>Pratap</strong> 23:02</p><p>There is no EM training data publicly available. We looked really hard. On the one hand, that makes it difficult for us, but on the other hand, that&#8217;s why, one of the reasons why it&#8217;s very valuable. Anyone who would need to do this would have to create their own data. And so there&#8217;s a few ways in which we build this. We think about it as a layer cake. So the first layer is you create a lot of expert-guided templates. And so the reason here is there&#8217;s 10 to the several hundreds in the power of possible EM designs. So if you just go and explore the space and simulate it, most of the space is garbage and not interesting, so let&#8217;s not waste our time. How do we get the interesting parts of the space? You know, in human language, we were training off of something someone wrote on Reddit or something someone wrote on GitHub, so it was automatically meaningful. We were training on the meaningful set. So here we&#8217;ve hired a few of the world&#8217;s leading RF experts, and they&#8217;re actually creating seed designs. These seed designs then we scale up parametrically, similarly to how video games procedurally generate forests and trees with varieties based on like one initial template. So that creates like a big part of the initial layer of the cake. Then around that, we insert random deviation and noise because we wanna get some of the interesting stuff. So you start exploring the entire wider universe, rate limited by spend and compute, but like starting with the interesting regions and distorting from there. So that&#8217;s all part of the simulation stack. We use a mix of different open simulators to do this. I think one of the great insights from the language models is all of your data doesn&#8217;t need to be great data. Like a lot of bad data is still useful to learn language. So then we take the very top candidate designs, we fabricate them, and then we measure them in our lab. And so that&#8217;s the smallest amount of data, but that is the highest quality data. And again, if we look back to language models as an analogy, you know, that last layer for alignment for the ChatGPT model was, I believe it was only a few hundred thousand data points, but it was very high quality data points. So the view is that&#8217;s sort of the layer cake, that we&#8217;re building for training the model.</p><p><strong>Akhil</strong> 25:06</p><p>Thanks, Pratap. Maybe switching gears again, you&#8217;ve got a range of folks that are using and pretty rapidly, right? You&#8217;ve got a lot of inbounds that have just come in being like, &#8220;Oh, this is a huge bottleneck. Let me go try and run with it,&#8221; and then seeing some amazing expansion based upon some initial pilots. Any immediate lessons on, you know, one of the first pilot that comes to mind and just how quickly it scaled? What&#8217;s kind of interesting about the initial use case that came about? And then, is that generalizable across some of these which seem kind of niche, right? Like going from Anduril to Bausch and Lomb on initial surface don&#8217;t seem that near to each other, but at the end of the day, we&#8217;re making an embedded system and a set of systems and devices to go do a variety of things.</p><p><strong>Pratap</strong> 25:53</p><p>Yeah. So even though the industries are different, you know, those are a few of the public customers we could talk about this more in each of these industries. But even though the industries are different, it-- they&#8217;re-- what they share in common is they&#8217;re all building software-defined hardware at the frontier of their field in a hurry, right? And so this is kind of, you know, you have, all of them have this property of a mechanical, a software, and electrical team coming together to create something brand new. And I think where we&#8217;re focused today is really people on that frontier because they&#8217;re the ones who are really pushing the limits. So, you know, AMD with their next generation chips, Anduril obviously with next generation hardware, you know, BNL actually innovating a lot of like, surgical hardware as well, like actually on the med device side. So you look at the-- those-- the functionally, the problems actually look very similar, and the teams actually are structured in similar ways with similar tool chains. Obviously some of the details are different. The degree of electromagnetics in each one is different, but you actually have this sort of like common set. I think the pattern that we&#8217;ve seen from pilot to rollout, that&#8217;s very exciting to me, is- We&#8217;re either getting pulled in where there&#8217;s, of course, a pilot would usually begin where there&#8217;s the most acute pain. So either you have acute pain, which is you&#8217;re trying to get a brand new product out the door, you&#8217;re having challenges in design validation or in testing, or you have like, let&#8217;s say, a production product and you have like a troubleshooting or operational like repair problem. These are often two acute places where we will get drawn in. What I&#8217;m super proud of is every time, once we&#8217;re through the pilot and it&#8217;s deployed and people understand and see what Atlas can do, it gets pulled upstream. So if we started on the right side, which is like test and production, it&#8217;s continuously getting pulled into R&amp;D, which is the next question is, &#8220;Oh, wow, it helped me...&#8221; Like, we have had multiple cases where the time to root cause a failure has dropped from six hours to about 20 minutes. And that&#8217;s pretty profound change, but it&#8217;s able to pinpoint the problem, and not just that, but because of the meta graph, link it back to the specific design area of interest. And so what we&#8217;ve seen now is those companies now injecting Atlas into the design review process so that you basically have, oh, great, I want to connect those two. So not just gonna help the technician in the field root cause, it can actually help my next version of the product get better. And so we&#8217;ve seen this in automotive, we&#8217;ve seen this in aerospace and defense, we&#8217;ve seen this in semiconductors, and we, you know, we&#8217;ve also seen the other version of it, like expanding right, which is starting in test and design and saying, &#8220;Oh, wow, can I now give this expert capability to a field technician?&#8221; And that will often, from the design team is like, context switching is expensive. I don&#8217;t wanna take a designer off of their next project to go field an L1 or an L2 support request, but could I give kind of Geek Squad in a box to an operator in the field, right? And so you&#8217;re seeing this sort of intelligence getting initially deployed in one place, and then sort of radiating out. And I think this is actually one of the organizational benefits is you have, you know, there has been this quest for shared learning and all of the data going into one place, for a long time, right? Ever since like the big data days, and obviously, you know, given, my experience at Palantir, you know, that&#8217;s a core kind of, value prop of Palantir, for example. But I think what you see very often is people are busy. You can interpret that as people are lazy, but they&#8217;re busy. I may have all the data there. Am I really going to go and spend my evening now going and like searching through it to see if there&#8217;s a way I can make my design better? Probably not. I probably have better things to do. And so what&#8217;s different now is we&#8217;ve changed what used to be like a pull into a push. The AI is doing that for you, and it&#8217;s injecting in your natural course of work, &#8220;Hey, Akhil, this next design, by the way, this part of the battery management system has had challenges in the past. You might wanna consider this additional piece of pre-charge circuitry.&#8221; Right? And that&#8217;s just being pushed to you in your natural flow before you were gonna go to design review. That&#8217;s where you want it, right? And so that&#8217;s actually what we&#8217;re seeing is like this, the organization now as an organism starts to learn and have memory in this way that&#8217;s totally new.</p><p><strong>Akhil</strong> 30:05</p><p>Makes sense. And, Meg and I can definitely share some stories on battery management. Definitely a hot topic these days. Can you, Pratap, share an example? You know, have us come into a sales pitch or customer call or an on-site visit where you had just that one person in the room that was totally not with the program, that was just like, &#8220;This will never work. I can&#8217;t trust this.&#8221; What was that conversation like? How did you build trust with someone like that?</p><p><strong>Pratap</strong> 30:35</p><p>Yeah, happens all the time. And I think especially with our target set, you can imagine these engineers are remarkably good at their job, and they got there by being right, right? These-- They&#8217;re not software engineers. Software engineers, we&#8217;re wrong all the time. Oh, ship something, it breaks. Move fast, it breaks. You can&#8217;t move fast and break stuff if you&#8217;re building a plane, right? Like, you don&#8217;t do that. It is a very, very different culture, very different mindset with a very good reason. And especially like we mentioned the customer, we&#8217;re lucky enough that, and, you know, by good fortune and also by deliberate choice, we&#8217;re working with customers that are at the cutting edge. These are very, very good engineers. So skepticism is high. Barrier of entry is very high, right? And so what we found &#8212; I&#8217;ll give you one example &#8212; is we came in with a very hard problem around, like, a new type of chip. And, you know, we&#8217;d scoped it down to, &#8220;Let&#8217;s help you test this chip faster. Let&#8217;s help you, like, do the testing faster.&#8221; And, you know, we had, like, a larger set of things we wanted to do, and we narrowed it down to one where there was one engineer who was, let&#8217;s say, slightly more open-minded than the rest to, like, give something a shot. And the skepticism was very deep, and it was very grounded in the principle that I&#8217;m an engineer, this is how I think, this is how I reason. This is not a probabilistic game. There&#8217;s no way some AI model is gonna come in and do that. Like, it was like... And in fact, they&#8217;ve all then used ChatGPT and Claude at this point and been like, &#8220;I can&#8217;t trust it,&#8221; right? So you have this immediate out-of-the-gate trust problem. And in this environment, it started with basically just creating usefulness, just creating utility, which is saving a ton of time around their core problem. So not yet touching the core that we wanted to go after of that intelligence, but all the little stuff around it, making it easier, like, oh, kick off your testing job, execute your testing job, parse your data. Like, make it all really easy to use. And one of the principles has been show me your work. So Atlas evidences everything it&#8217;s doing. It annotates exactly the calculation it used, where it got the value from, so it&#8217;s auditable. So Atlas is like, it&#8217;s like a good student showing you its work. It&#8217;s one of the features that our engineer users love. They literally call it show me your work, and so that&#8217;s been powerful. And then it&#8217;s just been a lot of, like, good old startup, like, grit and grind and being in it with our customers, which is something we learned from Palantir, which is, you know, you&#8217;re not going to be trusted with the customer&#8217;s biggest problem overnight. No matter how great your innovation is, they&#8217;re not gonna give access right away. Like, we&#8217;ve been working with these customers now for several years in many cases. And over time, you know, we&#8217;ve been with them sort of through thick and thin, and we find that&#8217;s earning access to the problem. And for us, that&#8217;s earning more degrees of freedom for the agent. So in the semiconductor example of it was probably maybe, like, nine months in, 10 months in, they give us a call. They said, &#8220;Hey, can you help us boost performance of the chip?&#8221; But like it&#8217;s basically a natural consequence once you&#8217;re done with testing and you&#8217;re getting the results and it&#8217;s working, how do you get it to sort of hill climb in performance? And they&#8217;re like, &#8220;We know you didn&#8217;t exactly build it for that, but could we, like, could we do it?&#8221; And we said, &#8220;Look, we didn&#8217;t build it for that, but do you have some sort of verification environment the agent can access?&#8221; And they actually had a device farm of chips, new ones that had come back that were set up on boards, and, it was a performance optimization game, performance per watt being a big unit. And we said, &#8220;Look, give us the weekend. Give us access. Let Atlas run.&#8221; It took about a year of trust-building to even be in the place where they would ask us, and they would give Atlas that secure access. And then Atlas just went to town. And that&#8217;s when seeing is believing, and like it set a new performance frontier, superior to what was possible by people alone. And that triggered a really interesting sort of watershed moment where, you know, eyes were opened in terms of, oh, wow, this is the new way to kind of do performance optimization. So I would say it&#8217;s very like starts humble, we&#8217;re in it with our customers for a long time, building in a transparent way with show me your work, and then ultimately, there are these moments where they&#8217;re like, &#8220;Hey, can you try?&#8221; And then we&#8217;re having these moments of surprise, and then actually our greatest skeptics have become our biggest champions.</p><p><strong>Maggie</strong> 34:49</p><p>So Pratap, I&#8217;m curious, do you guys ever use your own product internally for any projects?</p><p><strong>Pratap</strong> 34:56</p><p>Yeah. You know, we use it for a number of things. I think one recent one has been we&#8217;ve been tearing down some DJI drones and actually basically using sort of a little bit of a reverse engineering approach to build that meta graph that I was telling you that Atlas uses. And then in our lab, hooking the components up and characterizing them by connecting them to our test equipment like oscilloscopes and spectrum analyzers and even like, you know, in the thermal chamber, seeing how they perform under different temperatures. And actually it&#8217;s been really interesting just looking at, you know, the entire BOM of components and how they&#8217;re connected, how they&#8217;re organized, and just seeing how, like even if you take DJI as an example, how as their drones have evolved, how the architecture, has shifted towards more vertical integration, where they&#8217;ve vertically integrated, where they&#8217;ve collapsed different electrical packages onto a single piece of silicon, and where they have, either chosen not to or struggled to insource. So yeah, it&#8217;s been a really fun project we&#8217;ve been working on, using Atlas internally.</p><p><strong>Maggie</strong> 36:04</p><p>Anything particularly surprising or interesting from those teardowns that you can share right now?</p><p><strong>Pratap</strong> 36:08</p><p>Sure. I mean, I think, you know, if you compare a version from about 2019 to like kind of like 2023, 2024, you know, the, you know, top five or six components make up the bulk of the cost. A good old Pareto principle turns out to be true. They were largely non-Chinese components, Western, many Western components actually in 2019, and now it&#8217;s predominantly Chinese. The second thing is a lot of the independent components have moved onto their own proprietary silicon. There&#8217;s definitely a weight saving, so we know at least that&#8217;s like definitely driving a performance gain, potentially cost as well. It&#8217;s definitely more secure as well. The one piece which hasn&#8217;t moved, which is almost surprising &#8216;cause it&#8217;s in the top five, is the GNSS receivers. So, you know, something interesting for us to keep digging into there.</p><p><strong>Maggie</strong> 36:59</p><p>Pratap, I wanna move to talk just a little bit more about your vision for the company and for this technology. On your website, you say the vision is to ultimately become the world&#8217;s first AI electromagnetics laboratory. Can you tell us more about what that means to you?</p><p><strong>Pratap</strong> 37:15</p><p>Yeah. So, you know, I started out my journey as a physicist. I was at Stanford, and then I went on to do my PhD at Columbia, and yeah, I was deeply interested in just like science, like how does physics work? It&#8217;s actually quantum electromagnetism, so like weirdly a full circle moment for me. But I always felt like I had to make this choice. I could pursue science, right? Or I could go to industry. And, you know, definitely my advisor was very unhappy when I left the academy, right? But if we look at what&#8217;s happening today with AI broadly, a lot of the barriers to building software are going away. It&#8217;s easier than it&#8217;s ever been. A lot of that work is going away. And there&#8217;s definitely one, like, negative side that people are looking at, which is, &#8220;Oh, where are all the jobs?&#8221; But there&#8217;s a positive side, which is we can up the ambition of what we&#8217;re able to build with the same team at the same price point in the same unit time. And I think what&#8217;s happening &#8212; and what we want to usher in &#8212; is almost a new variant of what was once something like Bell Labs, right? Which is, I think you can pull the physics much closer to the engineering. That chasm between science and application can close. And so I believe that there&#8217;s a future where if you are pushing at the frontier of applied physics, with advanced models and applied physics, and you&#8217;re in a connected loop that&#8217;s very close with customers working at the bleeding edge, which is why we&#8217;ve been very deliberate at picking customers working on frontier technology, you can create a new type of science and industrial collaboration. Like if I look at my critique of academia is it&#8217;s slow. It, you know, there&#8217;s no real motivation. It&#8217;s not necessarily targeted at like the most important problems. And my critique of industry is we chase the low-hanging fruit, and we don&#8217;t go for like the ambitious, hard stuff. Like, I think there&#8217;s a new company, and I think the time is finally right to emerge, where you could actually be pushing increasingly into sort of breakthrough science with commercial application and create an engine where like if, you know-- I wanted to create a place I would like to work. Coming out of my physics program, I wanted to work with smart people in a high-intensity environment where I was shipping things that had impact that I could be proud of, with real people who are benefiting from that impact, you know, connected to the real world. But I wanted to do something that was fundamentally rooted in science. And I think my hope is those don&#8217;t need to be binary choices anymore. And Arena Physica is a place where with Heaviside pushing the frontier and Atlas as the delivery vehicle today, you actually have the beginnings of a loop that will start with like electromagnetic super intelligence. But inevitably, as we climb, that will have to become a more multi-physics capability. And so that&#8217;s a roadmap. If we can create something that&#8217;s a new kind of Bell Labs, I would be, you know, just super happy.</p><p><strong>Maggie</strong> 40:10</p><p>Yeah, I think that&#8217;s an amazing vision. And, you know, also came out of Stanford, had a lot of friends working in the engineering and physics space, and it seems like their only options were either to go get a PhD, go work at like a super slow, big legacy, you know, defense prime or company, or go work at a software startup and kinda give up on the world of hard science if they wanted to move fast and, you know, really make a big impact on the world. So it&#8217;s great to see that maybe there will soon be another option for all of those people. What&#8217;s been the biggest challenge building Arena Physica over the past seven years?</p><p><strong>Pratap</strong> 40:44</p><p>Yeah... I think, well, part of it is seven years &#8212; You know, we started in kind of a field applying machine learning, when the challenge was getting people to care and pay attention to what was an esoteric, you know, nerdy field. And then we flipped into the opposite problem, which is everything is AI, what&#8217;s different, right? And so I think the beauty is we&#8217;ve sort of stayed the course. It&#8217;s funny, which is, we actually executed a large pivot of the company where we focused entirely on hardware engineering, whereas in the original days we were more broad across industries. That was a tough moment. Like, you know, just to be clear, we purposely deleted a double-digit million revenue stream that we&#8217;d worked tirelessly to build. And you can imagine those phone calls, and we&#8217;re doing that off of conviction in something that was barely a six-figure revenue stream, right? Like, because we believed in the meaning of what that small six figures represented and the capability set it represented of what we could do in hardware. And, you know, it goes back to the origin &#8212; when we first founded the company, that was always the end state on the website. And we&#8217;d said, &#8220;Hey, we were gonna start with like accessible commercial problems to prove economic viability and then literally work with companies building robots and in space.&#8221; And so we&#8217;ve exhibited the plan, although the way there was different. I would say that was probably one of the singular hardest moments of the company, which was it was, you know, it&#8217;s rare where you have to make such a clear bet based on conviction. And, you know, something that, like, one of my friends had taught me that stuck with me is he&#8217;s like, &#8220;The only decisions that matter are the decisions that have a cost.&#8221; And in this case, we had to make a very specific, pointed decision with a very clear cost on the one side and an unclear outcome on the other side, right? And, yeah, that was hard. I would say we definitely were kind of-- We just silently built for like a while after that. Like, you&#8217;re not in a loop getting feedback. It&#8217;s just you&#8217;re just betting on the dream with a few people, betting on that dream and building that dream. And, yeah, that was probably, if I were to think about it, probably the single hardest moment. But actually now looking back, you know, probably the moment I&#8217;m most proud of.</p><p><strong>Akhil</strong> 43:10</p><p>Your gut told you a pain point that customers really need across a variety of industries, ones that really matter right now, whether that&#8217;s in aerospace or defense, or even for just improving our daily lives and society&#8217;s lives, by first advancing, you know, how we think about embedded systems and doing it in a way that is fundamentally better. So thanks so much for taking time, Pratap. Any last shared wisdom for folks listening in that might be thinking about working on a technology set or just a problem that really matters?</p><p><strong>Pratap</strong> 43:44</p><p>No. I would say if you&#8217;re interested in our mission, definitely come join us. We&#8217;re hiring actively. But yeah, I would say now is the time to just really be ambitious. I think I&#8217;m excited for more folks who wanna push the boundaries. I think foundation models are gonna continue to get better. More foundation models are gonna start to exist, like ours for physics. There&#8217;s so much more we can build and, you know, it&#8217;s actually necessary. We need gainful employment for humanity. We think there&#8217;s plenty to do, but that&#8217;s gonna come down to entrepreneurs, going and building stupidly ambitious things, and we could probably just up that level a few degrees. So yeah, you know, let&#8217;s do it. Let&#8217;s build it.</p><p><strong>Akhil</strong> 44:23</p><p>Thanks, Pratap.</p><p><strong>Maggie</strong> 44:24</p><p>Thank you so much.</p><p><strong>Pratap</strong> 44:25</p><p>Thanks, guys. Appreciate being here.</p>]]></content:encoded></item><item><title><![CDATA[🎙️ Ep 25 - UFORCE: Ukraine's First Defense Tech Unicorn]]></title><description><![CDATA[The Magura family of USVs, built by UFORCE, sank 14 Russian warships.]]></description><link>https://maggiegray.us/p/ep-25-uforce-the-ukrainian-startup</link><guid isPermaLink="false">https://maggiegray.us/p/ep-25-uforce-the-ukrainian-startup</guid><dc:creator><![CDATA[Maggie Gray]]></dc:creator><pubDate>Mon, 22 Jun 2026 19:54:49 GMT</pubDate><enclosure url="https://api.substack.com/feed/podcast/203144594/cd0a52b364da37439711c35409d0f7f7.mp3" length="0" type="audio/mpeg"/><content:encoded><![CDATA[<p>The Magura family of USVs, built by UFORCE, sank 14 Russian warships. UFORCE aerial systems have flown over 220,000 combat missions and downed two Su-30 fighter jets &#8212; all in under three years of operation. </p><p><br><span>In the latest </span><strong><a href="https://www.linkedin.com/company/mission-matters-podcast/"><span>Mission Matters Podcast</span></a></strong><span> episode, </span><strong><a href="https://www.linkedin.com/in/david-rothzeid-7a116961/"><span>David Rothzeid</span></a></strong><span> and I sat down with </span><strong><a href="https://www.linkedin.com/in/olegrogynskyy/"><span>Oleg Rogynskyy</span></a></strong><span>, CEO of UFORCE, Ukraine's first defense tech unicorn, to talk about what it takes to build systems that actually work when lives are on the line.</span><br><br><span>A few things that stuck with us:</span><br><span>&#8226; A PACOM general told Oleg: "If you can't fix it with a coconut on an island, I don't want it." Most Western defense tech can't pass that test.</span><br><span>&#8226; UFORCE has flown more combat missions than all Western defense tech companies combined, and is expanding to NATO allies and the US market now.</span><br><span>&#8226; Ukraine's acquisition model is outcomes-based in real time. Units rate their weapons like Amazon reviews, updated from missions flown that morning.</span><br><span>&#8226; The lessons from the Black Sea are directly applicable to the Strait of Hormuz, the Baltic, and the Indo-Pacific. </span><br><br><span>As always, please let us know what you think. And please reach out if you or anyone you know is building at the intersection of technology and national security. &#127482;&#127480;</span></p><p><span>You can listen to the podcast on </span><a href="https://open.spotify.com/show/3uHmLy98VzGssrJ4xWI2nT">Spotify</a><span>, </span><a href="https://podcasts.apple.com/us/podcast/uforce-the-ukrainian-startup-sinking-russian-warships/id1807120572?i=1000773443619">Apple</a><span>, </span><a href="https://youtu.be/S0opg4-ilY8">YouTube</a><span>, the Shield Capital </span><a href="https://shieldcap.com/episodes/uforce">website</a><span>, or right here on Substack.</span></p><p class="button-wrapper" data-attrs="{&quot;url&quot;:&quot;https://maggiegray.us/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe now&quot;,&quot;action&quot;:null,&quot;class&quot;:null}" data-component-name="ButtonCreateButton"><a class="button primary" href="https://maggiegray.us/subscribe?"><span>Subscribe now</span></a></p><p><strong>Transcript</strong></p><p><strong>Maggie</strong> 01:18</p><p>In this episode of the Mission Matters podcast, we&#8217;re joined by Oleg Rogynskyy, the CEO of UFORCE, Ukraine&#8217;s first defense tech unicorn.</p><p><strong>David</strong> 01:21</p><p>UFORCE builds some of the most consequential battle-tested autonomous systems in the Russia-Ukraine war. Its platforms have executed tens of thousands, nay, hundreds of thousands of real missions in highly contested environments, informing not just autonomy software, but manufacturing, supply chains, deployment, and sustainment at scale.</p><p><strong>Maggie</strong> 01:44</p><p>Perhaps most notably, UFORCE builds the Magura Unmanned Surface Vessel, or USV, the first ever naval drone to sink an enemy warship in combat, destroying eight Russian warships in the Black Sea in its first year of operation and causing hundreds of millions or even billions of dollars of damage to other ships. UFORCE also develops several other defense systems, including the Nemesis Unmanned Aerial Vehicle, UAV, Liut Unmanned Ground Vehicle, UGV, and a command control software platform.</p><p><strong>David</strong> 02:14</p><p>In addition to its Ukrainian customers, UFORCE is expanding to NATO allies and the United States, where it will bring its combat-proven systems to an industrial base in dire need. In this conversation, we dive into what it takes to build defense technology that actually works on a real-world battlefield, the lessons the US, the Middle East, and the rest of Europe should take from Ukraine, what it takes to scale this technology beyond Ukraine and more. And with that, Oleg, thank you so much for joining us. I guess first things first, like how are Ukrainian forces using UFORCE systems today, and where are they creating the biggest operational advantage?</p><p><strong>Oleg</strong> 02:53</p><p>David, thank you for having me here, Maggie. So to your question, we have a number of platforms, and they&#8217;re all used in different ways in Ukraine. We&#8217;re most known for the Magura USV, and in the beginning when there were still, Russian naval assets in the Black Sea in the open, Magura was used in a number of operations, both as, one-way attack strike platform to strike those ships, but also as a short-range air defense platform to defend the swarms of Maguras from incoming aircraft, incoming drones, et cetera. Magura was also used to find subs, to find sea mines, to deliver UAVs to the enemy shore against the hard targets in fully denied environments, and so on and so on. So that&#8217;s just one chapter. The second product we have is Nemesis, which is the workhorse of Ukrainian mid strike capabilities. So every night there is thousands of these drones flying to deliver tens of thousands of payloads, to the distances of 20 to 50 kilometers, return back, reload, and go back out again. All of that driven by software that kind of works like DoorDash, where launch teams just go from spot to spot to spot and relaunch, reload, change the battery of the drones. We also have the ground vehicle, called Liut, that, allows Ukrainian forces to, do first ever, trench assaults without any humans on the line. These are fully remotely controlled UGVs, that have AI capabilities in them, have turrets with guns that both shoot down incoming FPVs as well as help, complete unmanned trench assaults, kind of smoking out enemy soldiers out of the trenches. There&#8217;s a mo- a lot more I can tell you, but that&#8217;s, those are the three main CONOPs we are running.</p><p><strong>Maggie</strong> 04:52</p><p>Oleg, what are the actual combat effects that UFORCE has had in Ukraine to date?</p><p><strong>Oleg</strong> 04:59</p><p>Great question. So, on the maritime front, we have affected latest count, I believe 19 Russian warships, out of which 14 are verified sunk. And then in terms of aircraft, because as you remember, we do, USV, unmanned surface vessel-based short-range air defense and counter-UAS. We&#8217;re the first company ever to take down fighter jets. We got two Su-30s, as well as we have two confirmed and a number of unconfirmed, as in we didn&#8217;t film them, helicopter kills, over the Black Sea, and that&#8217;s the maritime side. The land side, we have flown over 220,000 missions within all versions of Nemesis drones, and that has allowed us to destroy, over 10,000 Russian vehicles And I mean, the body count is really high, as you can imagine. And then, we&#8217;re talking over 2,000 armor, we&#8217;re talking number of logistics trucks, very large number of logistics trucks. But more importantly, we have been the artillery hunter for the Ukrainian side. So we mow down that thing all day long, every day, all night long, every, all the time. And then we had the technology that got close to 100% of the kills for the North Korean, howitzers that they gave to Russians. So that&#8217;s one of the claims to fame.</p><p><strong>Maggie</strong> 06:32</p><p>You know, I think Oleg, I think UFORCE is probably the first company that we have invested in at Shield that had actually been used on the battlefield before we made the investment. What&#8217;s it been like building and operating a defense company in Ukraine during wartime, and how has that environment shaped the culture and urgency of the business?</p><p><strong>Oleg</strong> 06:53</p><p>So that&#8217;s really interesting because I&#8217;m not a founder. I joined as a CEO, two and a half years into the company when the company was already north of $100 million in revenue, and the difference was stark. In Ukraine, everything is real time. You just go and do it right now. You don&#8217;t wait. Obviously, there&#8217;s downsides in terms of longer term planning, longer term system thinking, et cetera, but at the same time, the sense of urgency, the sense of why it is right now and why it is extremely important is nothing like I&#8217;ve seen before. The systems, the communication patterns, everything else in the company is organized around that real-time communication. And that&#8217;s different. Now, if you layer on what I&#8217;m trying to do, layer on knowledge management systems onto real-time communication, some really good things are happening.</p><p><strong>Maggie</strong> 07:46</p><p>Can you tell us a bit about the origin story of the company and how you came to lead it?</p><p><strong>Oleg</strong> 07:50</p><p>Yeah, absolutely. So the company came together through a merger of initially two companies. One was making Nemesis drone, another one was making a Magura C Drone. And then as those two came together, then became clear that, they were sharing a C2 system by a third company that got brought in. And then turns out there were other companies like a UGV company running on the same C2. So the interesting part is there was a whole cluster of companies and teams that were operating together even pre-merger that kind of were acting as one team, and it was just a very obvious move to bring those together using Western capital and, identify synergies, create scalability across them, start normalizing the tech stack, code base, training, ConOps, TTPs, business development, and so on and so on. So in the end, we now have, I think the latest count was nine companies that have come together, but they all have been operating as one for a while.</p><p><strong>David</strong> 08:56</p><p>Well, like it&#8217;s so interesting, and it feels like very organic and like Silicon Valley-esque, right? That everyone&#8217;s doing their thing. They&#8217;ve got these core competencies. You find these opportunities to sort of collaborate, and then lo and behold, the whole is greater than the sum of its parts, so you start to incorporate raising money, and obviously now headquartered in London and trying to proliferate the combat-proven technology across multiple domains, multiple geographies. And I guess the basis of my question is like how replicable is this, you know, across the Ukraine, entrepreneurial, you know, which has really shown itself, in a pretty inspiring way. But, you know, is UFORCE going to be a one of one, or is this a model that we&#8217;ll see happening over and over again?</p><p><strong>Oleg</strong> 09:47</p><p>So I think there is two answers to that one. From one side, it&#8217;s replicable. It has to be replicated because the consolidation to achieve scale, especially as the war in Ukraine ebbs and flows, will need to happen. Like at our size and scale, we can, not only continue leading in Ukraine but also start expanding to other markets. On the other hand, the bottleneck is actually in the leadership talent And there&#8217;s only so many, leaders out there who have done, and it&#8217;s not just me, it&#8217;s my whole leadership team, who have done work with Ukraine before, but have also seen Western large scale companies that allows them to not figure out things on the spot, but also bring in Western governance, scalability, finance, and other capabilities to the bear, to combine it with the product market fit that was achieved by the Ukrainian, ingenuity, iteration, and exposure to a real war.</p><p><strong>Maggie</strong> 10:51</p><p>Yeah, Oleg, I think that&#8217;s an interesting point that you make. I know that your experience previous to this was as a CEO of a software company in Silicon Valley. Can you talk a little bit about how you bring some of the principles from running a business like that, which as far as I know, had no connection to defense into this new market area?</p><p><strong>Oleg</strong> 11:11</p><p>Yeah. Running a software in AI company in Silicon Valley taught me a lot. I mean, what&#8217;s happening in defense right now is that there is a massive amount of growth opportunities happening all the time, and that means you gotta be hiring fast, but with really, consistent quality. You have to be working with capital markets. You have to be thinking about, capacity models, both on the manufacturing but also on the sales side, on customer support, success, et cetera side. And SaaS and AI were the places where those skills had to be developed at significant, scale because of the templatization of, SaaS industry that happened in between 2010 and 2020 or so. So having learned those pathways, having learned those patterns, has been extremely helpful in order to scale up this business very quickly. I mean, we went from over, from about 800 people to 13, 1400 people in less than Nine months, 10 months, something like that. So the growth is staggering. The bookings growth, I don&#8217;t wanna talk about it, but it&#8217;s also staggering. And all of that is only happening if you&#8217;re able to hire people at consistent, significant scale and consistent quality. And then one more thing to actually to bring to that is we learn how to run efficient companies in Silicon Valley between 2020 and 2024, kind of through the downturn, through COVID, et cetera. And so scaling up a business like UFORCE is very hard on its own, but scaling it up efficiently without lighting massive piles of money on fire on stupid things is a lot harder. And then doing that while introducing AI capabilities in every part of the business, both in terms of personnel efficiency, documentation, engineering, sales, everywhere, is also a challenge of its own, especially in high OpSec environment where every minute Russians are trying to get you, and not just Russians. So it&#8217;s been probably the most challenging and the most exciting thing I&#8217;ve ever done, but man, it&#8217;s a lot of work</p><p><strong>Maggie</strong> 13:33</p><p>Yeah, I mean, speaking of some of those OPSEC challenges and, you know, just actually what it takes to build for real combat conditions, can you tell us about some of the biggest technical and operational challenges that you&#8217;ve had to work through in order to actually harden these systems for real-world battlefield deployments?</p><p><strong>Oleg</strong> 13:51</p><p>Yeah. I mean, first of all, in Ukraine, everything is kind of move fast and break things because Ukraine knows, Ukrainian soldiers know that whatever is the weapons are today, it&#8217;s not gonna be the same tomorrow. So nobody&#8217;s focusing on building that highly certified, highly perfect, highly integrated set of systems, just the rate of change is so fast. And so, on one hand, that leads to, really fast iteration. On the other hand, it leads to kind of more dynamic environment that what Western militaries are used to. And then from OPSEC perspective, you have to approach it very differently. If everything&#8217;s changing all the time, you cannot defend your perimeter as well, &#8216;cause you cannot think through every little bit of operational security. And so what you gotta focus on is a lot more prevention of the lateral movements. You assume they&#8217;re in, you gotta stop them from moving to other places. Very different, approach in the West, where you have to really focus on your perimeter security, you have to really focus your interoperability to your NATO certification, other certifications, and other integrations and slow things that you can afford when you&#8217;re not at war. So completely two different cultures, and you have to be very conscious about what&#8217;s relevant from wartime to peacetime and the other way.</p><p><strong>Maggie</strong> 15:12</p><p>Kind of following up on some of the technical deployments here, you know, something I found interesting when you read about what&#8217;s happening in Ukraine, in the news and elsewhere, there&#8217;s a lot of discussion of autonomy, you know, completely human out-of-the-loop action. But if you actually look at a lot of the technology being used today, most of it is still mostly remotely operated, you know, maybe there&#8217;s some small pieces of autonomy in terminal guidance or elsewhere. What will it take to move towards greater autonomy, and how do you see this future of software-defined warfare and UFORCE role in that?</p><p><strong>Oleg</strong> 15:46</p><p>Yeah. So there is an interesting stat for why autonomy is not picking up in Ukraine, and it&#8217;s actually harder for it to pick up elsewhere. There&#8217;s not enough targets, and so it would be akin to over-engineering if people went for full autonomy right away. There is pockets of it developing really rapidly, such as terminal guidance in denied, in fully denied environments, autonomous resupply using aerial ground and sea drones, Swarm intelligence, but in a very basic way. Like, how do you queue up multiple drones in case one drone gets distracted to another target, opportunistic target? How do you make sure the others are following and both missions get completed? So kind of mission queuing, et cetera. But nobody in Ukraine is thinking about, &#8220;Well, I&#8217;m gonna send in drones over there and have them figure it out.&#8221; The kill boxes are too undefined, the terrain is too complex, the assets are too sparse, the battery ranges are too low. And so from that perspective, it basically would be an overkill. Now, when you look at Indo-Pacific, for example, where distances are massive, you know roughly you expect better ISR, but then at the same time you expect denial and kind of peer-to-peer, fight, autonomy would play a much bigger role there. And so you have to modulate what&#8217;s relevant and where. In fact, that leads to the base mantra that UFORCE carries with it everywhere, which is we start with the customer. I call us, we are the first bottoms-up adoption defense tech company. Other defense techs go and go straight to the ivory tower and push the top down. Okay, capture the Congress, shove down $20 billion of contracts down your throat, and then see what COCOMs do. We try to do the opposite, and Ukraine taught us that. We got the users who love the product and ask for more, and then Ukrainian government has enabled commanders of individual units to have a say in what weapons they get to fight the war, specifically of the type that they are facing. And so that&#8217;s the approach we&#8217;re taking elsewhere. We have combatant commanders of different theaters in the US being very excited about what we do before the Pentagon figures out. We have individual war fighters of war-fighting leaders kind of ask for our hardware because it works, because it&#8217;s battle proven before we show up to the procurement teams. And that has been very different Of an approach, and it&#8217;s a much more wartime approach. But unfortunately, the world is becoming less stable than more, so that approach is gonna be taking more and more space.</p><p><strong>David</strong> 18:47</p><p>Yeah. Oleg, I definitely wanna jump into it, and I know you brought up a little bit about the Indo-Pacific Theater and INDOPACOM. And then, you know, saying a little bit of heresy there, that centralized control and decision-making at the world&#8217;s largest bureaucracy, the Pentagon, maybe isn&#8217;t the best path to creating innovation and combat-proven technology. But before we jump into that, maybe just like one quick anecdote for our listeners about how the Ukrainian acquisition system and its fixation on outcomes-based, capability, development and funding versus this requirements-based that we sort of have here in the US, where you have to think about what it is you want to build, then you go and build it, then you test and you iterate, and then at some point it reaches the operational environment. But in Ukraine, it&#8217;s obviously been different &#8216;cause you don&#8217;t have the luxury of test and evaluation. It&#8217;s just outcomes-based. So can you maybe just highlight a little bit of that?</p><p><strong>Oleg</strong> 19:53</p><p>Yeah, absolutely. So in Ukraine, you don&#8217;t have the time. You don&#8217;t have the time to develop a thing and then spend couple years certifying it and getting it, and then perfecting it, et cetera. Everything gets to the front line in Ukraine in days, weeks. It gets iterated within hours, gets upgraded. If you don&#8217;t ship code same day as you got the mission data, you&#8217;re out. And so that&#8217;s the speed at which Ukraine operates nonstop, and that&#8217;s the only way to play. And so that speed is actually enabled by a number of inventions that only Ukraine so far has. Now, some of them are only possible because Ukraine is in an active fight, and we... at the same time, we&#8217;ve seen lack of those innovations, slow things down in the Gulf, for example And what I mean by that is, so in Ukraine, both vendors and units get points for kill videos that they get submitted. So basically, you fly a mission, you got a kill, you submit the video to a government website. There is like a government Amazon for weapons. And the AI verifies that this video is unique and not AI generated. And then, you basically get points, and you can use those points to buy weapons that you want for your next mission. They even have Amazon Prime for that. You can spend more points to get it by tomorrow. And so that is very interesting because it pushes down the decision-making to a unit commander level, and at the same time, it gives the government perfect data of what works. Because if it doesn&#8217;t work, people won&#8217;t order it again. There is literally reviews you can go and read on every drone and from missions that were flown this morning. I&#8217;m not even talking about, like, last year on a slick sheet. And then from there, the government is now starting to layer on more and more data, like how many missions did this system actually fly? How many kills did they have? How many... What kind of units are using it? What kind of operators are more successful with them? So they are now collecting the ecosystem metadata and segmenting the procurement data about what can be bought with factual battlefield data to an insane extent. And then on the other side of this invention, they have created very tight partnerships between the tech partners like us and the units themselves. And so for example, we are closely paired up with Unit 412 Nemesis, which started as a battalion, and then it became a regiment, and now it&#8217;s a brigade. And rumors are, unconfirmed rumors, that it&#8217;s gonna become a corps at some point And what it means is we started with 100 operators, which became 1,000, which then became 5,000 operators, who could become 25,000 operators that are sitting and whose job is not just to fly missions, but to deliver feedback to us. And our job is to iterate on that feedback in real time with them. There is tens of thousands of code commits and design changes that happen all the time based on that real-time feedback. So now that you know there are units that can access the data and influence procurement in real time through the government system, and all this kit is being co-developed with people that are trusted in real time, things are changing very quickly and improving all the time.</p><p><strong>David</strong> 23:17</p><p>Yeah. That&#8217;s fascinating. I mean, it&#8217;s a real markets-based approach to capability development and acquisition procurement, and definitely some lessons that could be learned over here in the United States military. Maybe from, like, the operational standpoint, right? Like, the last couple months, the US has been embroiled in a number of different conflicts. You know, there was Venezuela, which went fairly quickly, and now nobody talks about that. And of course, you know, the situation with Iran, Given where our capability deployments have been, and there was a great chart within the first couple weeks of the Iranian conflict that kind of highlighted that there were very few capabilities developed in the last 10 years that were actually operationally being used, in Iran. And I&#8217;m wondering, you know, at some point, did the Pentagon come calling or people in Central Command or European command about, &#8220;Hey, how can we get some of this stuff over there?&#8221; And then, you know, could Ukrainian combat-developed technology be useful to helping the situation with the Strait of Hormuz?</p><p><strong>Oleg</strong> 24:30</p><p>I can&#8217;t really comment on specific engagements, but as I mentioned in one of the interviews, the phone had been ringing and has been ringing off the hook, with interest because when you are dealing with the challenges that we saw in Iran, the lessons from Ukraine are directly transportable. These are the same Shahed drones flying. The tactics and concepts of operations that Iranians are using against Dubai and Qatar is no different than what they&#8217;re doing against Odesa in Ukraine. Russians are doing it against Odesa in Ukraine. The mining, demining in Hormuz is no different than when Russians tried to mine the grain routes to bring Ukrainian grain out of Ukraine. So the analogy is all there. Maybe the temperatures are slightly different, but the sea is also similar. Black Sea and, the Gulf both go maximum sea state three, and so on and so on. So lots of lessons to be learned from there. Ukrainian experience is extremely, effective there. As you know, there was a delegation from Ukraine helping take down a number of Shahed drones in Middle East. That has been extremely successful, and lots of lessons learned from there, including in design of interceptor drones. Ukraine was able to change how interceptor drones are designed in less than two weeks to match the Middle Eastern requirements, which was very interesting. So yeah. I think, also there is a very effective knowledge transfer that happened from those examples of how Ukraine fights to people on the ground in Bahrain and other parts of US military installations in Middle East right now. People are learning. We saw the Lucas program. There is many other programs where Ukrainian experience is being implemented right away. Now, when is it gonna arrive to Pentagon? Great question. Hopefully soon.</p><p><strong>David</strong> 26:30</p><p>Yeah. And hopefully, your investor at Shield Capital is helping, you know, accelerate that whole process, which I know can feel a bit mind-numbing. Now maybe just real quick, speaking of engaging with the Pentagon, you just hired your US-based CEO, Sean Planke. Maybe talk a little bit about how you met Sean and what you were looking for in somebody to help sort of, push out the US, UFORCE, exposure.</p><p><strong>Oleg</strong> 27:01</p><p>Yeah. So, we got our introduction to Sean through our investors. And then what&#8217;s interesting is at least three of our investors triangulated the same person to us around the same time, which was, a great way to know that we&#8217;re talking to someone who is for real, where, all of the US really plugged in defense investors we have on the cap table at once said, &#8220;That&#8217;s the guy.&#8221; And then at the same time, just the level of expertise that we saw, the level of ability to navigate, Washington DC, which is not easy to navigate. But also the knowledge of having served, the knowledge of having met a number of people in a number of missions and just being super mission-aligned is something that really caught our eye. Level of energy is more than mine, which is really hard to imagine. But guess what? We were just in a, literally in a bunker with a number of commanders a couple days ago. It was day eight on the job, and I was sitting in the back of the room. I&#8217;m like, &#8220;Huh, I&#8217;m not really needed here anymore. That&#8217;s amazing.&#8221;</p><p><strong>Maggie</strong> 28:14</p><p>What have been some of the biggest challenges, you know, or unexpected surprises in scaling UFORCE beyond Ukraine to international markets?</p><p><strong>Oleg</strong> 28:24</p><p>That&#8217;s a really good question. So early on, about a year and a half ago, it was financing, not private capital financing, but like walking up to a bank and saying, &#8220;Yeah, we want some working capital to make some weapons,&#8221; was a difficult thing. In the UK, even opening a bank account was a very difficult thing. We had to go through a chairman of a banking group to get someone to open a bank account for us there. Not an issue anymore. Scaling, talent has been an issue because especially in Europe, where there is much less density of venture scale outcomes and so there&#8217;s very few, much fewer people who have seen unicorn growth, 10Xing year over year, et cetera. And so, finding those people was hard. And it&#8217;s like I&#8217;m juxtaposing them with people who come from defense world, which actually historically has been barely growing has been difficult. How do you get hypergrowth people who know defense? In the US, there is a bit more of that because you have hardware companies that have scaled, they have seen hypergrowth that are not technically defense. But, in Europe it&#8217;s very much harder. And even the US defense stuff, like we are talking to number of folks we&#8217;re trying to recruit from the larger defense tech companies in the US, and all of them are like, &#8220;Yeah, we&#8217;ve built shit. Nobody has used it, so we don&#8217;t really know if we built the right thing. So we know how to build stuff, we don&#8217;t know if anybody&#8217;s gonna use that stuff.&#8221; And how do you hire that? And they&#8217;re like, &#8220;And how about hypergrowth? Well, we know how to hypergrow a company on investment capital, but it&#8217;s not really revenue-driven hypergrowth.&#8221;</p><p><strong>Maggie</strong> 30:20</p><p>Yeah, I think it&#8217;s an interesting point that you&#8217;re making that a lot of these, you know, international companies have not actually deployed technology yet on the battlefield. And I&#8217;m curious, what do you think are some of the things that maybe Western, international defense tech companies misunderstand about what it takes to actually deploy on the battlefield? And what will it take for them to get over that hurdle?</p><p><strong>Oleg</strong> 30:46</p><p>Well, like, everything. There&#8217;s only two Western companies that I can think of that have real battlefield effects in Ukraine. It&#8217;s Quantum Systems and it&#8217;s Tekever, and Destinus. Everybody else, I&#8217;m sorry, there&#8217;s two wars going on right now, and this is, like, my favorite question for investors to ask other defense tech companies. Ask them how many daily active users they have. Like, there is two active wars right now, and you don&#8217;t have daily active users, like people logging in and using your stuff daily? What are you doing? And so to that point, the challenges to deploy are, first of all, just even getting your stuff to the frontline is a whole thing of its own. Like, I was just talking to someone who is like, &#8220;Yeah, the, this defense tech company showed up and said, &#8216;Hey, here is our product. Use it.&#8217; Like, great, I wanna modify something. &#8216;Oh, you can&#8217;t do that. Our agreements and everything doesn&#8217;t allow. If you wanna pay us more, we can send in our four deployed techs, and they&#8217;re gonna try to do something here.&#8217; Most likely they&#8217;re gonna have to ship it back.&#8221; That was a real discussion with the top three largest defense tech company in the US. And I&#8217;m not even talking Prime, I&#8217;m talking, like, hard defense startup company. So that doesn&#8217;t work in Ukraine. A general in the PACOM during one of the exercises told me something. He&#8217;s like, &#8220;Hey, when I&#8217;m on an island and you can&#8217;t fix your thing with a coconut, I don&#8217;t want it.&#8221; And so that&#8217;s the stuff that Ukraine has figured out, that everything is simple, modular, deployable, doesn&#8217;t need experienced MIT PhD field technicians, doesn&#8217;t need to be shipped back to the HQ for a software upgrade, or whatnot, and it just works. And unfortunately, defense tech outside of Ukraine is not getting that.</p><p><strong>Maggie</strong> 32:44</p><p>How do you actually scale a manufacturing process or manufacturing facility in the middle of an active war when you yourself as a weapons manufacturer may actually be a target for the enemy?</p><p><strong>Oleg</strong> 32:58</p><p>Well, you approach building manufacturing facilities very differently. Like, nobody in Ukraine builds large, beautiful, brand-new facilities with a big company logo on the roof and kind of people wearing white suits, white space suits or whatever it is, inside, and you can hear a pin drop. Like, in Ukraine, if you do that, you&#8217;re gonna get a ballistic missile in 40 seconds, and we&#8217;ve, uh... Even without doing that, we&#8217;ve lost a number of facilities over the years because you become the prime target. If your kit works, Russia is gonna use their 40 million dollar ballistic missiles to take out the manufacturing facility for your kit. And trust me, every one of the Western factories for weapons is already mapped out by China. It&#8217;s already mapped out by whoever needs to map them out, and those things will be gone in the first 30 seconds of a hot exchange. Now, what we do in Ukraine is we use, secondhand or underground facilities for pretty much every critical element so that we can withstand missile strikes. There is a lot of operational security protocols on how to stay under the radar, how to not endanger your people, how to know how to behave when an airstrike is imminent, and how to not use your, not lose your expensive equipment, or don&#8217;t use the expensive equipment. So the way we operate our manufacturing processes is it, the factory needs to be built from a local Home Depot using components from a local Best Buy, because you will not have the time to wait for nine months for the machine to arrive, and you&#8217;re not gonna have, continuous power, you&#8217;re not gonna have continuous supply chain technicians to come fix the machine, et cetera. So it has to be something simple, it has to be something scalable, easy to repair, field deployable, and fast.</p><p><strong>Maggie</strong> 34:58</p><p>How did you all think about designing your systems to be able to be manufactured at scale during this kind of environment?</p><p><strong>Oleg</strong> 35:06</p><p>Well, you take the tools you have, and you build what you can with them, and then when they ask for more, you figure out how to do more of it, and you keep on iterating until you get to large scale. Again, Ukraine doesn&#8217;t allow you to build for scale right away has to be... Manufacturing is as much of an iterative process as design and as fielding in Ukraine. You cannot plan for it. Spreadsheets don&#8217;t work. You, and the way Ukrainian government is purchasing, it&#8217;s all supply-constrained right now. So they walk up to you and they say, &#8220;Hey, look, how many can you make? We&#8217;re gonna give you margin on top, and we&#8217;re gonna buy everything you can make,&#8221; versus kinda shelfware and stuff like that.</p><p><strong>Maggie</strong> 35:49</p><p>How have you all thought about managing your supply chain during this conflict? I know today a lot of the systems that Ukraine fields do still come from China or have a lot of componentry coming from China. So how have you thought about that, you know, right now, and then where do you see that going in the medium to long term?</p><p><strong>Oleg</strong> 36:05</p><p>Well, if your stuff really works, your supply chain is gonna be targeted. So we had our supply chain targeted multiple times, and because of that, as a company, we made a decision to insource most of our supply chain. So we make our own drone motors, we make our own cameras, gimbals, battery packs, frames obviously, hulls, you name it. And so, we had to grow up to be fully NDAA compliant and not depend on Chinese and other non-fully aligned national, sources. And so PCBs, circuit boards, all that stuff has to be made in-house. Now, costs are different, but over time you can drive it down, and at our scale, it&#8217;s not impossible to execute.</p><p><strong>Maggie</strong> 36:52</p><p>So how are you seeing international demand for battle-tested systems like UFORCE? I guess, you know, geographically, where are you seeing the most demand, and what kinds of products are people most eager to purchase? I mean, it sounds like you have a pretty unique offering on the market as being one of the only scaled or scaling combat-tested defense tech startups.</p><p><strong>Oleg</strong> 37:15</p><p>Yeah. We think about the world in terms of four theaters that are active right now. You have Indo-Pacific, you have CENTCOM, you have EUCOM, and Ukraine, kind of overall. And from that perspective, the, each of these theaters has different problem sets. And so what we are doing, we are figuring out what are the problem sets we can actually solve with the same platform capabilities across the board. It turns out Magura is relevant in all four theaters. In Ukraine, it&#8217;s done its job mostly. But in the Baltic and in the Gulf and in the Pacific, Magura can do different things for each one of them. In the Gulf, it&#8217;s demining and counter-UAS against Shaheeds. In the Pacific, it&#8217;s all kinds of things, from one-way attack to ISR to demining to sub-hunting to C-UAS, you name it. Same in the Baltic. And so, demand is skyrocketing everywhere. There&#8217;s a lot more water outside of Ukraine than in Ukraine. At the same time, the distances are much larger, and we are very good at long distances, high endurance, loitering, delivering payloads, working as a truck to get things over there where nothing else can get through. And then the other part is we&#8217;re starting to see more and more demand for our Nemesis bomber drones. You know what&#8217;s interesting? I don&#8217;t think US understands bomber drones. Two days ago, for the first time, I was meeting with a very senior general in the US Army, and he basically for the first time brought up their interest in droppers and how they&#8217;re thinking about it. In Ukraine, droppers are Probably more cost-effective than FPVs in some way. And the battlefield damage for droppers is on par with FPVs, it&#8217;s just at the longer standoff distance. And so we&#8217;re seeing more and more adoption for the dropper technology in Europe. A major European country right now is deploying, is basically upgrading one of their light armor brigades to full CONOPS and TTPs and software and hardware and doctrine we developed for 412 Nemesis, and then rolled out across 40 brigades in Ukraine. And the moment that started happening, other countries with light, started thinking about what is gonna change about what needs to change about their light armored brigades in order to increase their survivability and effectiveness. Because in the world of FPVs, light armored brigades don&#8217;t have a future. And so we are seeing a whole queue right now of light armor brigades, which is leading to a whole NATO FLE, the field lethality experiment, which is kind of like a, when NATO as a whole decides, &#8220;Hey, we need to change something as a NATO, recommendation across all forces at once.&#8221; And so to summarize, demand for Magura where there is more water, outside of Ukraine, and then demand for Nemesis, where they expect a lot of land fighting and a lot of, kind of 20 to 50 kilometer, effects needed.</p><p><strong>David</strong> 40:29</p><p>Well, yeah, I think, what the picture you paint is both terrifying but also in certain respects, like reassuring that opportunity for the US to modernize its capability, its kit, is very much available and very proven. And so maybe just, you know, Oleg, as we kinda come to the end of this, interview, you know, what is the future of UFORCE? We&#8217;ve seen some pretty lofty valuations for a couple of these other defense tech companies that have gotten started in the last 10 years, three years in some cases, right? Anduril just raised that, I think 61 billion, and, Saronic raised, I think just sub of 10 billion. Where do you see UFORCE fitting into this picture, across this emerging defense tech landscape?</p><p><strong>Oleg</strong> 41:19</p><p>Well, at some point, customer is gonna ask, &#8220;Does this really work?&#8221; And that&#8217;s kind of where we come in. We&#8217;re seeing more and more war fighters and commanders really focus on being combat proven for their kit. And so in terms of valuations cannot comment on it as you can imagine, but, we&#8217;re already a unicorn. At some point we&#8217;ll be a decacorn, as they say. But the valuation is not the point. What the point is that battle proven kit is how you save war-fighters&#8217; lives and help them achieve their mission. And, the amount of experience we bring to the table is absolutely unparalleled. I think UFORCE has flown together like an order of magnitude more missions than all of the Western defense techs combined and I haven&#8217;t done the numbers, but just eyeballing it looks significantly larger. We&#8217;ve flown 220,000 combat missions so far. That&#8217;s more than all of US forces have flown in, over Iran, for example. Way more. I think it&#8217;s, like, 10 times more. And so the future of this is we&#8217;re just gonna keep on scaling. We are building stuff that works. It&#8217;s not gonna be the most expensive stuff, it&#8217;s not gonna be the most exquisite, but you can always rely on it to do the right thing.</p><p><strong>Maggie</strong> 42:44</p><p>Oleg, if you were the American Secretary of War for a day, what changes would you make to the department, the way it buys and what it buys, to ensure that the United States is ready for this next generation of warfare?</p><p><strong>Oleg</strong> 42:58</p><p>That&#8217;s a great question. I actually think there are some really good positive dynamics happening at the DOW. The whole team that came in from private equity background is moving fast, and it&#8217;s very encouraging. But, what&#8217;s less encouraging is just the complexity of procurement with, COCOMs, combatant commanders, basically being in full dependency of Pentagon, where the actual war fighting leaders don&#8217;t decide what they need for their region. They can submit a vote, but they don&#8217;t really guarantee you get that, is something that needs to change, it needs to change ASAP. Like, Admiral Paparo knows better than anyone else on the planet how to fight the war in the Pacific, and so he should be getting what he wants and needs. Same with the leader of CENTCOM, same with other leaders. And that&#8217;s something that I think, only US has for its size. Like, when we work with European countries, the linkage between the combatant commander and the procurement office is extremely tight.</p><p><strong>Maggie</strong> 44:07</p><p>Great. Well, Oleg, thank you so much for coming on the show. We really appreciate it, and we&#8217;re super proud to be investors in your business.</p><p><strong>Oleg</strong> 44:15: Thank you, Maggie. Thank you, David. Appreciate being here. Thank you, Oleg.</p>]]></content:encoded></item><item><title><![CDATA[🎙️ Ep 24 - Code Metal: Rewriting the Code Behind National Security]]></title><description><![CDATA[Modernizing and optimizing the code behind US national security]]></description><link>https://maggiegray.us/p/ep-24-code-metal-rewriting-the-code</link><guid isPermaLink="false">https://maggiegray.us/p/ep-24-code-metal-rewriting-the-code</guid><dc:creator><![CDATA[Maggie Gray]]></dc:creator><pubDate>Mon, 01 Jun 2026 16:01:19 GMT</pubDate><enclosure url="https://api.substack.com/feed/podcast/200077006/24d9a6cadfcd9b742677aa18a73880e2.mp3" length="0" type="audio/mpeg"/><content:encoded><![CDATA[<p>Each year, enterprises and government agencies spend billions of dollars re-writing code bases for modernization, edge optimization, and security. However, today, tools like <strong><a href="https://www.linkedin.com/company/code-metal/">Code Metal</a></strong> verifiably automate this code translation tasks that are crucial for national security. <br><br>In the latest <strong><a href="https://www.linkedin.com/company/mission-matters-podcast/">Mission Matters Podcast</a></strong> episode, <strong><a href="https://www.linkedin.com/in/pat-o-reilly-815770178/">Pat</a></strong> and I sat down with <strong><a href="https://www.linkedin.com/in/io-peter-morales/">Peter Morales</a></strong> to discuss the role code translation and verification plays in national security. Code Metal is trusted by mission critical organizations like <strong><a href="https://www.linkedin.com/company/united-states-air-force/">United States Air Force</a></strong>, <strong><a href="https://www.linkedin.com/company/l3harris-technologies/">L3Harris Technologies</a></strong>, <strong><a href="https://www.linkedin.com/company/toshiba-americas/">Toshiba</a></strong>, and more to modernize and optimize their mission critical code bases. Check out the full conversation to learn more.</p><p>A few things that stood out:</p><ul><li><p>The legacy code problem is bigger than people realize. US weapons systems still run on COBOL, Fortran, and Ada. These are decades-old languages maintained by a shrinking pool of specialists. Modernizing a single codebase has historically taken teams of engineers months.</p></li><li><p>LLMs alone aren't enough for safety-critical code. Code Metal pairs AI code generation with formal verification.</p></li><li><p>The shift Peter is betting on: Code generation is becoming a commodity. Verification is where the value is moving. Whichever foundation model wins, mission-critical industries will pay for the layer that proves the output is correct.</p></li></ul><p>As always, please let us know what you think. And please reach out if you or anyone you know is building at the intersection of technology and national security.</p><p>You can listen to the podcast on <a href="https://open.spotify.com/episode/08l5WSsDZCrEmRu1T4q6Dq?si=1tQTaL8ZTg-sRy5-k3orLA&amp;nd=1&amp;dlsi=f898f06b58374003">Spotify</a>, <a href="https://podcasts.apple.com/us/podcast/code-metal-rewriting-the-code-behind-national-security/id1807120572?i=1000770209326">Apple</a>, <a href="https://www.youtube.com/watch?v=V_k8ogUYqJk">YouTube</a>, the Shield Capital <a href="https://shieldcap.com/episodes/code-metal">website</a>, or right here on Substack.</p><p class="button-wrapper" data-attrs="{&quot;url&quot;:&quot;https://maggiegray.us/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe now&quot;,&quot;action&quot;:null,&quot;class&quot;:null}" data-component-name="ButtonCreateButton"><a class="button primary" href="https://maggiegray.us/subscribe?"><span>Subscribe now</span></a></p><p><strong>Transcript</strong></p><p><strong>Maggie  </strong>00:36</p><p>In this episode of the Mission Matters podcast, we sit down with Peter Morales, the CEO and co-founder of Code Metal AI. Code Metal is building the future of code translation. That is taking code written in one coding language and translating it into a different coding language, and then verifying the accuracy of that translation.</p><p><strong>Pat </strong>00:57</p><p>Code Metal is focused on building code translation and verification tools for several major use cases, including code-based modernization, edge hardware deployment optimization, and code portability. Code translation projects that previously took teams of engineers months of work can now be completed in just minutes with Code Metal. Code Metal&#8217;s capabilities are a crucial part of the future of efficiently developing software-defined commercial products and has many military applications, helping engineers build software-defined hardware products and bringing modern software capabilities to the US government and other mission-critical customers</p><p><strong>Maggie  </strong>01:41</p><p>Since it was founded in 2023, Code Metal has raised close to $200 million and signed contracts with groups across national security and commercial sectors, including L3Harris, RTX, Toshiba, and the US Air Force. The founding team has deep experience in building AI tools for defense, hailing from MIT Lincoln Labs, BAE Systems, Microsoft, IBM, Data Miner, and more. Peter, thank you so much for joining us.</p><p><strong>Peter </strong>02:08</p><p>Yeah, thanks so much for having me, guys.</p><p><strong>Maggie </strong>02:10</p><p>So I wanna start with just a softball question. Can you tell us, why would somebody actually want to translate code in the first place?</p><p><strong>Peter </strong>02:18</p><p>Yeah. Um, that&#8217;s a great question, and I think, um, you know, we&#8217;ve gotten that even, even some of the folks that have been here a long time have gotten that question that worked on some languages themselves, so the authors. Uh, you know, language is essentially really how you talk to the hardware and command what it does, and sometimes you wanna move really fast, and you wanna speak really abstractly, and that&#8217;s what we call, like, high-level languages. They&#8217;re great for prototyping. They&#8217;re great for maybe writing some different algorithms you wanna try. But then sometimes you wanna run really exquisitely fast on hardware. You want it to be really efficient, and that means having a lot of say in how you control things. If you think of C++, that&#8217;s a language where you actually get to decide what you do with the memory, where a lot of other languages maybe don&#8217;t worry about memory. Um, that level of control gives you optimization, gives you speed, and so being able to translate code into more optimal code, uh, is, you know, one of the hard use cases of what we do.</p><p><strong>Maggie</strong> 03:15</p><p>And I should think of this of, like, if I&#8217;m trying to put a computer vision algorithm on a drone or on a satellite or something like that where I may not have access to a whole lot of compute capabilities, that&#8217;s where I really care about this kind of optimized code. Is that the right way to think about it?</p><p><strong>Peter </strong>03:28</p><p>Yeah, yeah. I mean, it doesn&#8217;t have to be a drone, right? You want battery life on your phone. You might want battery life on your laptop. But yeah, being able to be efficient is a real reason for translating code. And then on top of that, you might even have different hardware providers, so maybe you&#8217;re efficient on NVIDIA, but you wanna be efficient on Qualcomm. Um, having to rewrite your code that, you know, uses their proprietary libraries is a big pain in the butt, but something that I think AI is letting us automate now.</p><p><strong>Maggie </strong>03:57</p><p>So what does it look like today sans Code Metal? If I am an engineer at a car company or a laptop company or a chip company and I need to build software for these hardware products, or if I&#8217;m working in some of these legacy code bases, what does it take to deploy code to these systems, and how can Code Metal fit into accelerating these processes?</p><p><strong>Peter </strong>04:19</p><p>Well, I, I think there&#8217;s a really interesting spectrum here. There&#8217;s sort of, you know, I&#8217;m building a product and I need to pick and, and really get locked into hardware. So one of the early use cases that came up was folks were asking not necessarily what hardware c- we could get to, but what&#8217;s the minimum amount of hardware to make their product as cheap as possible that they needed to run certain code. Um, so, you know, traditionally, that would be maybe you over-spec a bit. You spend a lot of time writing it and hoping it all fits on there, and that means hiring a whole team to do that. Or on the other end of the extreme, we&#8217;ve, uh, we&#8217;ve talked to companies that actually outsource all of their development. They write specs, and they hire contracting houses that are really specialist in the hardware that they&#8217;ve chosen. So maybe they&#8217;re gonna write FPGA code on a Xilinx FPGA. They&#8217;ve got a favorite shop, and they basically write instructions, wait months for that code to come back, and then have to spend time integrating it back into their product. So it&#8217;s a wide gamut, but a really, really slow loop that essentially, you know, our mission is to make that instant.</p><p><strong>Maggie </strong>05:21</p><p>So I know another major use case you all have hit on is the code-based modernization use case. Could you talk a little bit about some of the customer interest there?</p><p><strong>Peter </strong>05:30</p><p>Yeah. Where, where we&#8217;ve seen a lot of growth, uh, recently is in the Air Force and, you know, DOD writ large or DOW. Uh, you can think of they&#8217;ve invested a lot, right? They pay a lot for software. Um, there&#8217;s a lot of latent potential in all the different software they&#8217;ve spent But these are old code bases. Sometimes they&#8217;re reusing systems from the &#8216;80s, &#8216;90s, even older. Getting those into something that can be cloud distributed across the entire DOW, uh, is something that I feel like is a consistent use case, where they wish they had access to XYZ tool, um, but right now it takes a specialist with hardware that&#8217;s a pain in the butt to get access to, um, and software, and they need to, you know, basically wait months to get answers back. So we&#8217;ve been taking a lot of code bases in these sort of older formats, or at least more expert-driven formats, and getting them ready to deploy, uh, you know, sometimes in an easy language like Python.</p><p><strong>Maggie </strong>06:22</p><p>Pat, I know you&#8217;ve talked about how a number of our key weapons systems are written in old programming languages like Ada, which is a programming language from the 1980s. I don&#8217;t know how many Ada engineers there still are out there today, but it seems like if we wanna have any chance of modernizing these systems or even just maintaining them, these kinds of capabilities that Code Metal is developing are really going to be crucial.</p><p><strong>Pat </strong>06:44</p><p>Yeah. Actually, it&#8217;s, it&#8217;s a mixture of codes. It&#8217;s even, it&#8217;s not just one old code. It&#8217;s COBOL, uh, Fortran, Ada, you name it, uh, uh, develop- large projects the government and industry has developed over many decades is, uh, this in- in- inconsistent, uh, set of, uh, codes that makes it highly inefficient maintaining compilers that are, you know, been out of production for decades, all of that across the board. So that&#8217;s, that&#8217;s a real world application of this.</p><p><strong>Peter </strong>07:16</p><p>Yeah, and I, I think you mentioned the mixture of languages, and it&#8217;s, that&#8217;s, that&#8217;s so true &#8216;cause it&#8217;s like they&#8217;re... DOW will buy capabilities, and they&#8217;re not gonna tell you how to do it. They&#8217;re gonna tell you, &#8220;Meet these requirements.&#8221; Um, and so, you know, some of these systems we&#8217;ve built that are mixtures of different code bases, it&#8217;s the contractor&#8217;s favorite language, and it&#8217;s, like, something random like a data science language like R, uh, that they were doing. Uh, uh, I think one of my favorite examples ever is we found a, a, a web app. So it had a Leaflet front end and all these sort of features, but it was an R code base, which is, uh, I guess for all the coding nerds out there, just a very crazy choice that when I tell people, they&#8217;re like, &#8220;How did that happen?&#8221; And it was really &#8216;cause it was the contractor&#8217;s favorite language. That&#8217;s what they knew. And they, like, just kinda squeezed the use case into the code base and the, the software tools they knew. So not necessarily always the best choices even to start with. I&#8217;ve heard people basically looking to start retraining engineers in Ada &#8216;cause exactly that. It&#8217;s memory safe. They can&#8217;t hire enough Rust engineers. There&#8217;s enough legacy Ada code that They&#8217;re just kind of biting the bullet and, um, for anybody not familiar with Ada, it&#8217;s really cool formal methods and, um, sort of security built in, but very old language that never got the momentum of Rust, so not a lot of public support out there for libraries. So really these enclaves of hidden code bases that you kind of have to be an expert in to use.</p><p><strong>Maggie </strong>08:38</p><p>Yeah. So I want to turn to a couple questions about the technical details of the product you&#8217;re building, something that&#8217;s really interesting. So unlike a lot of the, the hype out there today, which is, you know, LLMs, AI is everything, you all use a mix of both, you know, LLMs, artificial intelligence, as well as more traditional formal methods and formal verification. So can you talk more about how you architect your system using all these different kinds of technologies to really ensure, uh, trust and verifiability of the code that you&#8217;re translating?</p><p><strong>Peter </strong>09:11</p><p>Yeah, I, I think if you step back and it&#8217;s, it&#8217;s, it&#8217;s really, again, a spectrum of, of validation and verification tools. On, on the high end, you have formally verified. That&#8217;s essentially saying, &#8220;I&#8217;ve proven mathematically these things are equivalent.&#8221; And you can&#8217;t always do that, but for some use cases, you have to in order to have that confidence. Um, and then on the other spectrum of that, you&#8217;ve at least built up enough evidence that you&#8217;re giving the customer, you know, sufficient trust that the AI did the right work. And if you think about where we are today in AI, like code almost costs nothing if you&#8217;re a company that can use some of these copilots. Where you are spending a lot of time is actually validating now this mountain of code. And so the task has moved to human verification and va- validation of, you know, what the code has written or that the AI has written. And so what we&#8217;ve done is we&#8217;ve essentially started pairing together, um, these sort of little powerful code generation tools with a suite of test harnesses. That&#8217;s where a lot of our IP lives, actually, like validating that these tasks that we think can be fully verified, um, actually are by creating this evidence. This essentially third-party, you know, auditor that isn&#8217;t AI-driven that&#8217;s able to check the AI in a way that&#8217;s automated and lets the teams move really, really fast.</p><p><strong>Maggie </strong>10:24</p><p>Many of the coding li- languages that you all are working with, and whether it&#8217;s Rust or Ada or, um, VHDL or others, these are not super common open source programming languages like a Python or React or something along those lines. How well do these AI models work with the languages out of the box, and how much customization is required to actually get these systems working with these more esoteric languages?</p><p><strong>Peter </strong>10:50</p><p>Yeah, I think that&#8217;s, that&#8217;s something that it&#8217;s been encouraging to see how much better the language models are getting out of the box with just some form of explanation of the languages. Um, but yeah, there is a huge gap between what it&#8217;s used to working with and sort of these more esoteric... I think VHDL is a great example of a, a language that&#8217;s more of a hardware spec masquerading as a language, um, that the language models just have trouble grokking because it&#8217;s so different than, um, the, the normal languages that they&#8217;re used to working with. So What we do is we actually decompose these really difficult tasks using sort of static analysis techniques into really bite-sized, manageable, provable steps. Um, and again, that sort of pulls in the, uh, the non-AI component of the, the product that we&#8217;re building. So I think we, we-- You know, our hope is actually that the tools get good enough, the AI tools that is, where we&#8217;re not doing as much customization as we are at, &#8216;cause there&#8217;s still the need for validation, verification, all the things that we&#8217;ve invested effort in. Um, it&#8217;ll just converge a lot faster. So right now, uh, on some of these trickier languages, we do a lot of fine-tuning of models. We do a lot of breaking down the problem into bite-sized steps. We do a lot of, uh, other sort of tricky in-house secrets on getting these things to converge. Um, but you know, we view us to be in synergy with like basically the growth and the capabilities of these models.</p><p><strong>Maggie </strong>12:14</p><p>And then how do you think about what models to use on the back end? And, you know, maybe carrying a little bit to some of the customers that you work with, a lot of them, you know, are working in air-gapped environments, maybe even classified environments. How do you think about, um, the models that you use that you&#8217;re able to actually deploy on those systems, and what are some of the, the trade-offs of deploying in some of those high sensitivity systems?</p><p><strong>Peter</strong> 12:36</p><p>Yeah, and I, and I don&#8217;t want to undersell the commercial space either. If you talk to a Japanese automotive company on their treasured code base, like they won&#8217;t even tell you what they&#8217;re doing. So it feels like you&#8217;re, you know-</p><p><strong>Maggie</strong> 12:46</p><p>They&#8217;re, they&#8217;re not all deployed in the cloud</p><p><strong>Peter</strong> 12:48</p><p>Yeah. It feels like a TSSCI SAP program when like you&#8217;re not even allowed to know what they want to do with your, your product. So, um, def-definitely I think writ large our customers want to have a lot of control of where their data&#8217;s going, and that means deploying on-prem. I think they&#8217;re all looking towards deploying in cloud in some way, and some of the business side has deployed some of those tools. But in terms of like, I&#8217;ll call it their treasured code base, like, you know, AMD isn&#8217;t putting the IP cores for their, you know, GPUs necessarily in a cloud, um, or at least anything that isn&#8217;t locally controlled. So I, I think the way we&#8217;ve looked at it is we want to be open to plug and play with any model. Um, you know, from our training stacks to our deployment stacks, we try and support everything. I mean, I think the kind of crowd that we have that work here is The second a model drops, everybody&#8217;s excited to immediately plug it into our pipeline and see what the baseline sort of results are. So I think there&#8217;s a fun sort of nerdy culture here in terms of like some new diffusion models are dropping, and immediately the team&#8217;s figuring out how to get it plugged in and running, uh, benchmarks. But, uh, it, it&#8217;s keep up with things. Um, you know, defense definitely wants to run US models, which is getting tougher. Uh, China&#8217;s definitely run quite ahead in terms of performance there, so there&#8217;s a little bit of a handicap working in that space. But, uh, on-prem and whatever&#8217;s the latest is the, you know, the way we&#8217;ve taken, uh, our product.</p><p><strong>Pat </strong>14:11</p><p>Uh, you had mentioned, uh, you are working, uh, in Japan. Uh, what are your thoughts on, uh, navigating international markets that you&#8217;ve...lessons learned?</p><p><strong>Peter</strong> 14:22</p><p>Yeah. Yeah. I think for us, that market is one that, you know, we got excited because there is a real hunger for US technology and moving fast, and there&#8217;s a lot of socioeconomic reasons where they are looking to adopt AI and looking to adopt new technology. So it&#8217;s been a country ready and excited for the types of things we&#8217;re working on. All that being said, time zones are hard. Field deployed engineering is hard. Um, you know, and for us that, you know, less than three years old now, um, it, it&#8217;s something that I definitely think you wanna go there with a, a, a really sort of locked down playbook. And I think it&#8217;s something where, um, we had to kind of slow down the, uh, demand that we had because we wanted to make sure the people that we are working with there, uh, we&#8217;re nailing it for them. So we almost, you know, we had to treat Japan a bit like a wait list situation where we&#8217;ve got our key sort of tent pole customers, um, that we&#8217;re partnering with now. But I think next year we&#8217;re gonna be focused on growing that area quite a bit more.</p><p><strong>Pat </strong>15:19</p><p>Well, speaking about growth, you&#8217;re pursuing a, uh, dual use strategy with commercial and, uh, government, uh, customers. Uh, what is the difference you see, and what is your advice on how to manage the, those differences?</p><p><strong>Peter </strong>15:36</p><p>Yeah, it&#8217;s really interesting, and I think it comes into how you talk about what you&#8217;re doing. Uh, when I&#8217;m talking to commercial space, it really is how are you gonna use Code Metal and sort of fitting to their use case and really focusing in on what our product does. Um, because we&#8217;re sort of in the productivity tool suite, a lot of the times when we work with DoD, what makes the things we do possible is our technology, but we&#8217;re talking about the capability it enables for them. And so it&#8217;s, it&#8217;s, I guess it&#8217;s a higher level up, um, in terms of when we&#8217;re selling DoW versus when we&#8217;re selling, um, you know, let&#8217;s say Bosch or something. Talking to each client, you know, I have to tell DoW the ultimate use case, the benefit to the warfighter, and it&#8217;s just a little bit, you know, higher level in terms of the impact. And with that comes into the way we execute, the way we prepare material, more on site, more sort of, you know, um, longer sort of contract cycles. But all of those things I think, you know, help us because one thing I do think DoW is great for is essentially on those early bets that we&#8217;re taking at Code Metal, we&#8217;re looking for DoD to sort of springboard and de-risk and build a technology base that then we take to commercial space.</p><p><strong>Pat </strong>16:47</p><p>And what are the unique challenges you&#8217;ve found that, uh, founders should prepare for if they&#8217;re gonna work with national security?</p><p><strong>Peter </strong>16:54</p><p>Uh, well, contracting is something I didn&#8217;t realize how little I understood. Um, I think, you know, it was interesting in that like luckily because I have a background in defense, uh, you know, I used to work at BAE Systems, uh, worked at MIT Lincoln Laboratory. Um, but I didn&#8217;t-- I wasn&#8217;t necessarily on the contracting side. I was in like the make the customer excited by the things we were doing side. And, um, it was interesting when we had customers who wanted to buy and it, it-- When they don&#8217;t understand how to buy, and you have to actually go help them navigate, like, their own organization, it becomes really, really interesting. And some of the successful, I think, you know, uh, I&#8217;m not sure if neo-primes is the right word, but some of the, the newer defense companies, uh, where I&#8217;ve sort of discussed with them and we&#8217;ve talked about what&#8217;s worked, it&#8217;s really being able to help them with that contracting side, helping them with that, like even up to the legislative lobbying side so that they can get what they want. But it&#8217;s a really weird situation versus commercial, where you have somebody, like, dying for the thing that you&#8217;re doing, and you have to go help them walk all these steps in order to actually pay you for it. So-</p><p><strong>Pat </strong>18:03</p><p>Yeah. Besides contracting, another area that&#8217;s unique to the government that, uh, startups have to str-struggle with is the, uh, working with classified information and the authority to operate. Uh, what was your journey like getting approval for authority to operate on your, for your classified customers?</p><p><strong>Peter </strong>18:24</p><p>Yeah. I, a lot of this, again, is gonna be driven, and I hate to keep hitting the contract, it&#8217;s like we had to do so much work in order to even get the permission to submit for ATOs, um, or submit for classifications, and it was all waiting for essentially the contract to say the words that, like, &#8220;You shall need this.&#8221; And then that kinda got everything running, which is its own headache, and it, it&#8217;s a lot of work, and there&#8217;s a lot of great companies, uh, spinning up, I think, to help startups with these problems. But at the core, you need somebody to buy in that, &#8220;Hey, Code Metal needs a top secret clearance, and Code Metal, uh, you know, needs to submit it to this, let&#8217;s say, cloud provider,&#8221; and to really kick off all those processes. And so it was pretty much a crawl in terms of getting these things done, and the second we had the contract in place, uh, I think it was like three months later, we had an FCL, um-</p><p><strong>Pat </strong>19:18</p><p>Which is a facility clearance.</p><p><strong>Peter </strong>19:21</p><p>Yeah. And, and I had gone from, you know, basically an inactive TS clearance to now I have my TSSCI. So it was a really fast process once this painful contracting piece had been done in place. And, and friends of mine and, you know, other founders I&#8217;ve talked to, similar sorts of journeys in terms of like either getting a prime, maybe they&#8217;re subcontracting to you to help them with that, uh, or, you know, their own direct contract.</p><p><strong>Maggie </strong>19:46</p><p>Yeah. I wanna know, I think you guys have really had a lot of success here just because the customers did get so excited about your product and were ready to go run through walls to help you get the ATO and the FCL. Maybe can you tell us about a moment when you showed the product to a customer and you felt like they really got it, and, you know, what was that experience like and what were they experiencing?</p><p><strong>Peter </strong>20:08</p><p>Yeah. I think, look, uh, I think as, as venture capital companies in dual use, we have this advantage that we can sort of build ahead of what our customers want and show them and not tell them. And I think a lot of the traditional industry out there is sort of selling through slides, selling through SBIRs. Um, I think you have the advantage of like, you have a customer who has needs, uh, and I don&#8217;t see enough founders actually think in the dual use space talking to the customer first. And so we-- I&#8217;ll give you an example of, of what really kicked this off We were working a, a project that was more of a, a favor due to expertise of the company to a friend. Um, but the, the customer that they had essentially wanted to come and visit Code Metal. And so as part of that, uh, I briefed them on sort of code translation and what we do before I got into, like, the detail thing we were helping them with. Uh, and sorry to be a little vague. But we, uh, we, we briefed them on the core capability, and the customer asked, like: &#8220;Oh, you know, we have this modernization thing. We&#8217;re getting bids for about a year to actually take our code base and update it to new. Uh, would you guys be able to do that with your tool?&#8221; And I said, &#8220;Yeah, sure. Can I get access to it?&#8221; And they&#8217;re like: &#8220;Yeah, it&#8217;s Git owned. We&#8217;ll send it to you.&#8221; Um, and I was... Originally, I was asking for more of, like, a, &#8220;Can I, like, see it to scope out the work?&#8221; And we just went ahead and did it and sent them back the code. And there was this, like, &#8220;Holy shit.&#8221; It was that, like, uh, they went from thinking, &#8220;We&#8217;re gonna take a year to, to modernize this one module,&#8221; to like, &#8220;Hey, we&#8217;ve got about 19 that we wanna do, and, like, we were dreaming about connecting these things and building this bigger platform.&#8221; And we were like: &#8220;That&#8217;s great.&#8221; And we, instead of just, like, waiting and trying to do this other end, and, and look, this might not work for everybody, but this is the way we did it. Uh, we just got to work, and we&#8217;re like: &#8220;We&#8217;ll figure out how you guys pay us. We&#8217;re just gonna do good work and focus on, on, on starting to build this system.&#8221; And, and it&#8217;s paid back in spades. So we, you know, I, I can say fast-forwarding to where we are today, um, you know, they&#8217;ve done a great job in terms of, like, coming back to us and, and paying for the work and then also expanding the opportunity. And they see it, and the sort of reputation, it&#8217;s a small industry, starts rippling around. You know, we were at an event just now supporting and deploying, and folks were coming by from the other services saying: &#8220;Hey, you need to come out to visit me. I see the way you guys are here day and night, day and night. Um, I see what you&#8217;ve done with them, and, like, this is six months from, like, when we talked to you to IOC that we&#8217;re now running. That&#8217;s initial operating capability, uh, your platform.&#8221; So I think- What I can say is we have an asymmetric advantage in that we&#8217;re trying to build, uh, you know, companies that, that scale and, and sort of play this long game. And you have these customers who have needs, so talk to them. Um, don&#8217;t try and just invent a thing and then, like, sell it to DOW. Like, there&#8217;s amazing problems that they have that, like, I don&#8217;t see people tackling. So I guess that&#8217;s my advice on selling to them and some of those things.</p><p><strong>Maggie </strong>23:06</p><p>How have you thought about building trust with some of these mission-critical customers? I mean, I know there&#8217;s a lot of distrust out there about AI broadly, so how have you approached that?</p><p><strong>Peter </strong>23:18</p><p>I think what we get a little bit of inherent in what we do is kind of like a practical thing we&#8217;re solving. So we&#8217;re not trying to boil the ocean, uh, or, you know, we, we kind of have to limit a bit sort of even the pipelines we do. Like, the North Star is any language to any language. Right now, we have very practical Python to C++, C++ to Rust sort of targets that we&#8217;re working. And so I think just hear-them hearing the proof points and sort of all the non-AI bits, um, like sometimes I actually get reminded like, &#8220;Oh, you can at least also mention that we&#8217;re using AI,&#8221; is sort of what we&#8217;re selling them. Um, and, and we&#8217;ve had pitches and they&#8217;ve seen the product where they&#8217;ve gone like, &#8220;Oh, you&#8217;re using LLM, I didn&#8217;t know that.&#8221; Um, and yeah, I, I think that&#8217;s, that&#8217;s been some of that trust building, that we&#8217;re just really trying to hear what their problem is and focus in on, &#8220;Here&#8217;s what we do, here&#8217;s how we do it, here&#8217;s the evidence we show you.&#8221; Um, and, and that&#8217;s been, you know, a huge part of it.</p><p><strong>Pat </strong>24:11</p><p>You have a broad experience with, uh, not only national labs but, uh, federally funded research development companies and, uh, academia and industry. Uh, what made you decide to start your own company?</p><p><strong>Peter </strong>24:25</p><p>Uh, that&#8217;s a great question. So I was, uh, I was at Microsoft during COVID working on the HoloLens, very, very frustrated in leadership, working very, very hard, um, to, to essentially solve a lot of problems that CodeML solves today. But, um, uh, 100% transparency, Code Metal wasn&#8217;t the first company that I started. I started another one after that, and I was very naive at that point. I was an engineer first, didn&#8217;t know anything about startups. I, uh, m-met a fellow who, you know, great sort of partner in business, but maybe not what a VC company would be looking for, and, um, ended up starting a company that, like, got into Techstars accelerator and did these things. And really, I just assumed a startup was like, &#8220;Oh, I&#8217;m in a job I want and make money.&#8221; That was, like, the extent of my business knowledge. Um, I remember being in, like, the Techstars whatever, uh, like, cohort, and they asked me, like, &#8220;How&#8217;d you get in?&#8221; I was like, &#8220;Oh, I didn&#8217;t know what this was,&#8221; but they were talking about stuff I was doing. So, uh, it was, it was a, a big learning curve, and I learned a lot about what a startup was. But the thing I pulled out of that, that, that got me excited was this idea of like, oh, the problems have to be big enough and the founder has to really fit the market to actually, you know, be reasonable as a venture-backed company. And so even though we had a great, you know, I consider it great success that we sold the company that, that I&#8217;d started, like, I really got a sense of what is, like, a true venture-backed, venture-scale company look like from that first kinda you know, I&#8217;ll call it pseudo failure. Um, and, and, you know, that&#8217;s-- a lot of those lessons went into Code Metal. So part of it was the autonomy of tackling the problems I wanted to tackle. Um, that&#8217;s a big part of it, like, uh, rather than sort of selling the company to do the things I wanted to do. Uh, and then really understanding that actually that&#8217;s a great fit for a venture-backed company. When you have the background, you have a problem that&#8217;s big enough to be r- you know, sort of worth venture backing. Um, you know, it seemed like a great fit and all the things I like to do and the ways I like to work.</p><p><strong>Pat </strong>26:22</p><p>And you mentioned the, uh, challenges of people working in, in venture companies and, uh, uh, venture-backed companies and, uh, uh, dealing with work-life balance comes up a lot, uh, when you&#8217;re retaining and growing and motivating, uh, teams. Uh, what have you found is, uh, successful, or how do you approach recruitment, uh, so that folks know, realize, uh, that working in a startup has a huge benefit, but at the same time, it, it&#8217;s not a normal nine-to-five, uh, five-day-a-week job?</p><p><strong>Peter </strong>26:56</p><p>There is a great description of people that fit, um, Valve, which is a video game company that I&#8217;ve stolen in, in everywhere I&#8217;ve tried to hire, and it was they look for T-shaped people. These are people with, like, a deep expertise through, like, um, you know, one core topic, but, like, broad exposure to a lot of things, willingness to be flexible. And I think, uh, the reason we look for that sort of T-shaped person is we, we look for people that, like, the thing that they like to do is almost their, like, life mission. Like, one of our pillars is passion. And the reason being is, like, I want these people rambling about formal methods or rambling about optimizing some, you know, embedded CPU core and, like, looking for signal on things where they&#8217;re doing this in their free time or that they&#8217;re, like, taking the extra mile on their own to do it. Because then my job is to give a really good North Star that we can all rally around so that, like, on their off days... I&#8217;ll give you an example. We spent a grueling, like, uh, deployment where it was, like, eleven PM, you know, we were wrapping up, and we were back in there at six AM for about two weeks solid and on the weekend. And, you know, coming at the end of that, I told the team, like, &#8220;Get out of here. I don&#8217;t want to see you for a few weeks. So, like, don&#8217;t wait to die. Go, go take a break.&#8221; They&#8217;re like pushing me things that they like, they still wanted to like fix the problem or, or still work on it. And so I&#8217;m getting like architecture ideas or improvement ideas like as they&#8217;re going away on vacation. Um, so it&#8217;s, it, it&#8217;s tough. Like it&#8217;s a competitive market. Like you need to have people motivated to put those hours and do that work. Um, I don&#8217;t think you can pretend that like you don&#8217;t have to put it, but it has to be good work. It has to be thoughtful work. It&#8217;s not just work for work&#8217;s sake. If you get your work done and you are, you know, you can leave the office, leave the office. Like we take sort of just get your job done attitude to how we do things. So, and a lot of that just comes from passionate people with broad exposure to things.</p><p><strong>Maggie </strong>28:47</p><p>You&#8217;ve worked in the defense space for more than a decade at national labs, at defense primes, elsewhere. What have been some of the biggest changes you&#8217;ve seen in the industry over your career, and what are you most looking forward to for the next five to 10 years or most excited about?</p><p><strong>Peter </strong>29:01</p><p>Maybe this one isn&#8217;t as like novel, but it&#8217;s still one I think about a lot. Um, it&#8217;s been a lot cooler to do defense stuff. And so, um, uh, you know, that, that sort of has its ups and downs. But I remember being, you know, Project Maven kicking off while I was at MIT Lincoln Laboratory and the Google employees sort of walking out, and now you have something similar now with, uh, sort of Claude and what happened, but I think it&#8217;s a little bit different. Um, but yeah, I, I think just the fact that people see the sort of value in, you know, doing this work, uh, has been something exciting to me. It&#8217;s easy to recruit. It&#8217;s, uh, a lot easier to walk on a Stanford campus and, you know, find kids that are excited by the stuff that you&#8217;re doing. Um, I think that was one change that I still sort of really appreciate. Uh, the other is I think more recent in this idea of like trying to figure out new ways to actually fix these issues in acquisitions and, and contracting and, um, I&#8217;m, I&#8217;m actually super excited by it. I think it&#8217;s one of the things we are getting right, at least trying things. Um, and so yeah, I&#8217;m looking forward to seeing the next two, three years where that goes.</p><p><strong>Pat </strong>30:11</p><p>Today, you&#8217;re having a board of directors meeting. Uh, what are your thoughts about,  the benefits or how best to leverage a board for founders and investors that are, um, listening to this podcast?</p><p><strong>Peter </strong>30:27</p><p>Yeah, I, I think it&#8217;s really hard when you&#8217;re a founder and you&#8217;re waking up every day and thinking, &#8220;What&#8217;s the most important thing I need to do?&#8221; And at some point you&#8217;re gonna need to raise funds and build your board. And it&#8217;s like, it feels like a luxury when you get told like, &#8220;Hey, pick board members you like. Pick-- Work with people that you wanna work with.&#8221; Um, I, right now I do, which is what I feel very like lucky that we get to do that. But, um, in terms of like horror stories I hear from other founders and, and things that like basically they blame the company going wrong on, it, it&#8217;s a non-insignificant percentage where it&#8217;s like board dynamics. So I think it&#8217;s, it&#8217;s really important to actually like when it feels desperate and you&#8217;re like, &#8220;Oh man, I really should take this check.&#8221; And like I, I get it, as like a founder you might, you know, wanna take money for a certain reason from a certain fund. If there isn&#8217;t that fit with like, &#8220;Hey, I can work with this person,&#8221; um, it, it&#8217;s really stupid sort of repetitive advice that every founder gets, but like I&#8217;m just stressing it as like, yes, like listen to that. Figure out how to like extend your runway a bit or whatever it takes to like take the right capital in because you are tethered to these people. Um, and at least the way I&#8217;ve looked at it is at different stages of the company, we&#8217;ve needed different sort of help, and we&#8217;ve looked for people that, one, fit the, you know, had the background to provide that type of help, whether it be like technical product guidance or it be, um, you know, sort of moving to commercial is, is another example. Um, you know, giving us connections and top cover as we do defense work. All of those things were the criteria in how we targeted who we targeted, but first and foremost was, hey, I gotta work with this person forever maybe. You know, I have to pick people that I wanna work with.</p><p><strong>Maggie</strong> 32:15</p><p>What lessons, if any, have you taken or has Code Metal taken from overseas conflicts in Ukraine and the Middle East? Or has it changed your approach to the ecosystem and your product?</p><p><strong>Peter </strong>32:27</p><p>Yeah, I think in, at least in Ukraine, there&#8217;s this notion of like, hey, the acquisitions process does not work for a war that&#8217;s adapting, you know, every week, every, you know, month. How do we actually start building, uh, ways of acquiring and reacting to, um, immediate sort of situations? So without getting into too much detail, obviously a company that&#8217;s like built around like immediately deploying hardware, the latest idea, you know, benefits from, from that sort of change in thinking. So it, it&#8217;s one of the things I think DoD still hasn&#8217;t quite figured out how to acquire and pay for that consistent adaptivity. Um, but it&#8217;s something that&#8217;s an open question and, and obviously first and foremost important.</p><p><strong>Maggie</strong> 33:10</p><p>As I say, you guys have done some work as a, a subcontractor to larger primes. Is that right?</p><p><strong>Peter</strong> 33:15</p><p>Yeah, absolutely.</p><p><strong>Maggie</strong> <strong>33:16</strong></p><p>I&#8217;m curious how you think about those kinds of arrangements as a way to get access to some of these government customers that might be difficult to access otherwise. Could you talk a little bit about your experience with subcontracting?</p><p><strong>Peter </strong>33:29</p><p>Yes. There, I mean, there are calls for proposals, customers that you won&#8217;t get to see as a startup. Like, they won&#8217;t exist to you, they won&#8217;t be in the market to you, but maybe you actually solve exactly what they do. Uh, thinking about that early when you&#8217;re partnering with the primes, like wanting to be in the room when things get presented, wanting to get that connection is something that maybe when you&#8217;re trying to close a deal doesn&#8217;t feel like a order one priority, but it kind of is if you&#8217;re trying to build a long-term company. So I can say from experience, um, that was one of the things that we pushed back on wanting with some of the agreements that we had. Like, &#8220;Hey, we&#8217;ll work together on this, but we wanna be in the room for certain aspects of this.&#8221; And again, to get exposure to the company or the, the customer who doesn&#8217;t have the luxury of... You know, I think there&#8217;s a lot of saltiness in the DLE space about like, oh, they&#8217;re giving it to the same people or whatever, but they need stability. They need like repeatability. Like they can&#8217;t just be trying everything in a lot of these critical industries. So, you know, there&#8217;s some empathy to the customer in terms of like going with the same solutions over and over again. And the primes are a great way to actually start bootstrapping that exposure and, and relationship.</p><p><strong>Pat </strong>34:39</p><p>And what&#8217;s your vision for how you see your company growing and the product, the use and adaption, uh, adopting, um, the products that you&#8217;ve developed?</p><p><strong>Peter </strong>34:50</p><p>Yeah. I view we&#8217;re starting with a, I think, a really strong baseline in our defense clients, and it&#8217;s, it&#8217;s just industries that we know it&#8217;s a great place for developing, uh, deep tech technology. Uh, but it is a general use technology. Like it doesn&#8217;t just impact, uh, DOW. And so you do this first tranche about growth and, and defense of our, you know, sort of core positioning and the things that we wanna care about. Uh, and then, you know, we&#8217;ve been growing now out into more sort of initial landing and exploratory work in the industries like automotive, like semiconductor, uh, that skew more pure commercial. So I think that&#8217;ll be our phase two. And you know, personally, one of the mantras I&#8217;ve said to the team is we don&#8217;t wanna be a series Z company. Like we wanna get to, you know, reasonable, predictable revenue and IPO in, you know, three to four years.</p><p><strong>Maggie</strong> 35:38</p><p>What have been some of the biggest surprises building Code Metal?</p><p><strong>Peter </strong>35:42</p><p>The AI market was moving Fast, but, like I said, the last six months to me have been, like, absolutely insane. So I think, um, I&#8217;ve liked it &#8216;cause we&#8217;ve had a clear focus on who our customer is and who our market is, so we&#8217;ve gotten to, like, kinda avoid the noise. But man, does it sound crazy out there. So, uh, that&#8217;s been, um-- It&#8217;s been interesting watching, to tie back to us, like, how smart our customer has gotten in a very quick amount of time. So I can think about two years ago what it was like to talk to them about AI code generation to today, and it&#8217;s interesting, like, seeing their evolution across these sort of legacy industries.</p><p><strong>Maggie</strong> 37:44</p><p>Great. Well, Peter, thank you so much for the time, and thanks so much for coming on the podcast.</p><p><strong>Peter</strong> 37:48</p><p>Yeah, thanks. It was great to talk to you guys.</p>]]></content:encoded></item><item><title><![CDATA[🎙️ Ep 22 - Armada: Building American Edge AI Dominance]]></title><description><![CDATA[In the latest episode of the Mission Matters Podcast, Akhil and I sat down with Dan Wright and Pradeep Nair, co-founders of Armada, which is building distributed AI infrastructure for the world&#8217;s most demanding environments.]]></description><link>https://maggiegray.us/p/ep-22-armada-building-american-edge</link><guid isPermaLink="false">https://maggiegray.us/p/ep-22-armada-building-american-edge</guid><dc:creator><![CDATA[Maggie Gray]]></dc:creator><pubDate>Mon, 20 Apr 2026 17:50:38 GMT</pubDate><enclosure url="https://api.substack.com/feed/podcast/194817029/fb328cb473c0b590775258068db2e2b6.mp3" length="0" type="audio/mpeg"/><content:encoded><![CDATA[<p>In the latest episode of the Mission Matters Podcast, Akhil and I sat down with <a href="https://www.linkedin.com/preload/?_bprMode=vanilla#">Dan Wright</a> and <a href="https://www.linkedin.com/preload/?_bprMode=vanilla#">Pradeep Nair</a>, co-founders of <a href="https://www.linkedin.com/preload/?_bprMode=vanilla#">Armada</a>, which is building distributed AI infrastructure for the world&#8217;s most demanding environments.</p><p class="button-wrapper" data-attrs="{&quot;url&quot;:&quot;https://maggiegray.us/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe now&quot;,&quot;action&quot;:null,&quot;class&quot;:null}" data-component-name="ButtonCreateButton"><a class="button primary" href="https://maggiegray.us/subscribe?"><span>Subscribe now</span></a></p><p>Dan has a phrase that stuck with us: &#8220;AI drags infrastructure.&#8221; Everyone sees the value of AI. The hard part is deploying it where it&#8217;s actually needed, like oil rigs, mine sites, aircraft carriers, and national labs. These are places where the cloud simply can&#8217;t reach, and that&#8217;s where Armada comes in.</p><p>In this episode, we cover:</p><p>&#8226; Why the cloud breaks at the edge (latency, sovereignty, and cost)</p><p>&#8226; How Armada is enabling real-time AI in fully disconnected environments</p><p>&#8226; Armada&#8217;s role in the DOE&#8217;s Genesis Mission, the most ambitious AI project in U.S. history</p><p>&#8226; Why winning the AI race is just as much about infrastructure as it is models</p><p>&#8226; What it takes to build mission-critical technology for mission-critical customers</p><p>As always, please let us know what you think. And please reach out if you or anyone you know is building at the intersection of technology and national security.</p><p>You can listen to the podcast on <a href="https://open.spotify.com/episode/42ujRgVy6hkVedE1vPvZrf?si=btWTdwpDTq-vSPowHLIVlQ">Spotify</a>, <a href="https://podcasts.apple.com/us/podcast/armada-building-american-edge-ai-dominance/id1807120572?i=1000762419857">Apple</a>, <a href="https://youtu.be/vhdlEEARI5g">YouTube</a>, the Shield Capital <a href="https://shieldcap.com/episodes/armada">website</a>, or right here on Substack.</p><p>One more quick reminder that <strong>registration is now open</strong> for the <strong>third annual National Security Hackathon</strong>, taking place <strong>May 1-3 in San Francisco</strong>!  We are partnering with the U.S. Army to award $50,000+ in cash prizes to hackers building solutions to crucial U.S. military problem sets. <strong>&#127482;&#127480; Register now <a href="https://cerebralvalley.ai/e/3rd-annual-natsec-hackathon">here</a>.</strong></p><p class="button-wrapper" data-attrs="{&quot;url&quot;:&quot;https://maggiegray.us/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe now&quot;,&quot;action&quot;:null,&quot;class&quot;:null}" data-component-name="ButtonCreateButton"><a class="button primary" href="https://maggiegray.us/subscribe?"><span>Subscribe now</span></a></p><div><hr></div><p><strong>Transcript</strong></p><p><strong>Maggie  </strong>00:36</p><p>In this episode of the Mission Matters podcast, were joined by Dan Wright and Pradeep Nair the founding CEO and CTO of Armada AI. Armada is building the future of distributed AI at the edge.</p><p><strong>Akhil  00:50</strong></p><p>Armada is a quintessential company addressing both a commercial and national security pain point, and that is how to get connected compute to the edge, to these potentially remote or disconnected environments for mission critical applications. That&#8217;s whether it&#8217;s an oil rig, a mining site, or even the US military and its allies. You can think of Armada as orchestrating both the compute via its containerized mobile data centers, as well as the connectivity associated with connecting those together to enable and accelerate AI applications, data analysis, where it is needed and in the timelines in which it&#8217;s needed.</p><p><strong>Maggie  01:31</strong></p><p>I mean, essentially you can think of Armada&#8217;s Galleon product as a bunch of CPUs and GPUs in a hardened Conex box with Starlink connectivity and all of the software infrastructure that you need to actually put AI applications on that edge. Armada&#8217;s technology is particularly useful in situations where you cannot assume reliable connectivity back to the cloud. Today, if you look at LLMs ChatGPT, the vast majority of these applications rely on having unbroken access to large cloud data centers to do all of the processing that you need to use those AI models. However, you know, you can imagine if you&#8217;re deployed out on an aircraft carrier in the middle of the Pacific during a conflict or on an oil rig, or even at a mine site or an oil and gas site, you might not have access to those cloud compute capabilities, but you still want to be able to use these powerful AI models to make your tasks your life easier.</p><p><strong>Akhil  </strong>02:27</p><p>Yeah, Maggie. I think a lot of us here at Shield Capital, whether we served in the military or have been deep in the space, recognize that. A lot of these environments, you just can&#8217;t connect back to the cloud and you have to be able to analyze, assess, and compute near the point of friction or the point of influence, so where it needs to be done. Even if you have that connectivity back to the cloud, it&#8217;s critical that analysis, that timeliness associated is done nearest to those who are actioning.</p><p><strong>Maggie </strong>02:57</p><p>Yeah, it&#8217;s also valuable having this edge compute capability as it allows you to process the data potentially where it&#8217;s actually collected, and it allows you to have those data centers right near your energy sources. Dan and Pradeep have both had long careers as AI and data infrastructure, technology company executives. Dan served on the executive team at AppDynamics and DataRobot while Pradeep was a vice president at Microsoft Azure for 10 years, and a VP of engineering at VMware. Now onto the conversation. Dan and Pradeep, thank you both so much for coming on the Mission Matters podcast. I wanna start out with a question, Dan, where is the Department of War today in terms of AI adoption and infrastructure build out, you know, what&#8217;s actually being used? There&#8217;s lots of buzzwords, lots in the news right now about how the DOW is actually using ai, but what are you seeing are some of the specific. Use cases that you&#8217;re excited about that are driving real value for the war fighter?</p><p><strong>Dan </strong>04:01</p><p>Yeah, I mean, we have a saying at Armada, which is that AI drags infrastructure and what is meant by that is that typically how things work, not just with the DOW, but with any customer that we work with, is first they see the value of the ai and then they&#8217;re like, oh, how do I enable this everywhere? And so that&#8217;s kind of the stage we&#8217;re at now, where now the DOW has obviously understood the value of drones. I mean, I think everything that&#8217;s happened in Ukraine and other conflicts has really highlighted the necessity of not just drones, but drones at massive scale, you know, drone swarms. And then the obvious question becomes how do we process all of that data? Locally, including in these more remote areas. And then on top of that, you see a lot of the foundation model companies now working with the DOW in a very close way that wasn&#8217;t happening in the past. And those capabilities too, it becomes, okay, well how do we actually deploy this? So then you heard Secretary Hegseth recently at Star Base talking about, you know, deploying these types of technologies at the edge. So the Edge is now really a focus, but that infrastructure rollout is happening as we speak right now.</p><p><strong>Maggie  </strong>05:25</p><p>Yeah, Pradeep, we&#8217;re starting to see some of these use cases expand drones, others, what are some of the existing technical challenges that still exist for actually adopting AI in these mission critical organizations?</p><p><strong>Pradeep  </strong>05:39</p><p>I think a couple of things it&#8217;s what we are seeing with a lot of our customers, we are actually deploying into countries or places where there&#8217;s an existing cloud region, right? So that, that&#8217;s something interesting to notice like most of our deployments are starting to happen and hey, there&#8217;s a, you know, one of the existing hyperscaler cloud region, but they want an edge deployment and that&#8217;s driven by. Primarily three things. One latency. They want to have you know, the compute close to where the data is generated. The second portion is sovereignty, right? That&#8217;s where the AI stuff is very important because if you see what&#8217;s happening as Dan was mentioning, a lot of large language models being, you know. But many of the enterprise customers or even government customers want to take it, you know, fine tune it on their you know, confidential or sensitive data and then push it to the in front for the edge, right? So that&#8217;s what we are enabling. One of the struggle has been, Hey, I have all these models, but I want to have the compute on the edge. Now how do I bring all this together? Which is one of the pain points we are solving is, Hey, okay, you can have all these AI models, you know, generated in the cloud, but how do you put to action on the edge that requests like, you know, distributed compute, a single amazing customer experience that allows customers to focus, to switch between cloud and edge. So that&#8217;s one of the things. And the last one we see is cost as well. Like in terms of the problem we are solving overall. Hey. Yes, I have the models in the cloud. I don&#8217;t want to keep pushing all the data to the cloud if I want to like, you know, run inference and get output out the edge and then push the post-process data to the cloud. That&#8217;ll save obviously you know, significant on my, cost as well, because you know, people are spending lots still on ai, cost, all the training, et cetera. Now how do we start, you know, optimizing it so that you don&#8217;t keep spending just on the large models or the large data and push all of that to the cloud.</p><p><strong>Akhil  </strong>07:43</p><p>Pradeep, you&#8217;ve experienced this built on the cloud side and now the Edge side. And Dan, you mentioned I love that sort of statement, AI applications are dragging the infrastructure. I think something we&#8217;ve observed, and this is not just in the national security spaces, when that does happen, I mean it takes a hot minute for the, in infrastructure to get developed, in fact, much longer than it does necessarily to take an AI application, right? And to build the potential use cases. And so Pradeep kind of curious on, as we think about the challenges, not just in the application development, but you know, as we think about that dragging infrastructure. What are the challenges of actually building and adopting that scaled infrastructure in a distributed manner for some of these mission critical organizations? And that&#8217;s not just national security, that&#8217;s oil and gas. These organizations that that, that have similar mandates when it comes to the deployability and challenges associated there.</p><p><strong>Pradeep  </strong>08:36</p><p>Yeah so interesting. I think as a, as you said, I was you know, fortunate to be part of the, you know, building the cloud journey for over a decade. What I significantly saw was what Cloud enabled was, hey, you can think about developers around the world could actually focus on the application and start deploying anywhere in the world, right? They don&#8217;t really care where the infrastructure is sitting. It&#8217;s just a dropdown for them in the broader experience. And I just go focus on my application deploying that. That is a similar thing we are doing here. Hey, you can think about distributed edge compute sitting across everywhere around the world. You focus on the application now what challenges we see? It&#8217;s literally if your application is modernized running on Kubernetes, like you&#8217;re able to do that. Then, you know, moving to the edges relatively straightforward. Where we see challenges, if it&#8217;s set of legacy applications that have been done that has very legacy dependencies, then you actually have to go through sort of a transformation or the second thing we have seen is. If you are actually too much tied to one of the cloud provider, right? You have so much dependency on some of the cloud services or specific cloud services coming from a cloud provider, then you have challenges transforming. But what we are also seeing a lot of the like, and if you think about you know, journey of multi-cloud like enterprise customers are deploying on multiple clouds, which means that. The app developers are like transforming the application to say that, oh, I should be able to run my applications on an Azure or A GCP or on Oracle, et cetera, right? That&#8217;s how they are thinking. Which makes our job easier because, hey, if you have you know, transform your application or you built your application from the scratch, that it can run on primarily any infrastructure, any cloud provider, then running it on engine infrastructure becomes relatively very easy. For example, we are at, we are one of the applications we actually, they were running on Azure. We were able to actually, you know, you know, enable them to run on the edge within less than 24 hours, right? Because it&#8217;s all you know, native Kubernetes stuff. So it is very easy for us to, you know, migrate them over.</p><p><strong>Akhil </strong>10:51</p><p>Thanks for that, that&#8217;s great. And I wanna pull on something you mentioned with a lot of these legacy industries. You know, legacy is not necessarily the right word, but with a lot of industries, like in national security. Basic dev tools, infrastructural tool just don&#8217;t exist in those environments. And what we&#8217;ve been finding, Maggie and I, with our portfolio companies here at Shield Capital that are on the AI application side is they&#8217;re allocating 20, 30% of their critical engineering talent. Not to the application, but to the deployability infrastructure and how it relates to the edge. And so I&#8217;m curious a little bit about how do you think about working with startups in these. Really advanced AI application companies, figuring out what that edge deployability looks like and maybe taking the burden off of them so that they can focus on, I think as I&#8217;ve heard before, focused on just making really good beer or making that really good application.</p><p><strong>Pradeep  </strong>11:43</p><p>Yeah. So super interesting. You know, we, you know, we spend a lot of time between, you know, Nvidia of the world and then, you know, and the cloud providers like Microsoft. If you think about the stack, what we are seeing is there&#8217;s obviously the infrastructure layer which is you know, hardware and all of those things. Then you have the past layer with Kubernetes. Then you have a lot of ML ops platforms, and then you have the AI applications, right? That&#8217;s. The stack is starting to work, and this is where some of the customers struggle because if they have to do it all by themselves, they have to go all you know, together by themselves. And then there are startups, to your point, is working on couple of these portions and oh, they have a really good ML off platform, or they are, you know, developing really apps. So what we have been is like we think about partnership very key. Like how do we make the experience simpler and easier for our customers? Is the partnership with these, you know, ML ops and AI apps. And we work with the, for example, have a specific team what we call as the marketplace team. What they are actually, their full-time focus is to like, you know, work with partners, onboard them onto our platform, make their deployment very easy. They don&#8217;t have to worry about Hey, what infrastructure, et cetera. Very similar as I explained in the cloud. So they can actually scale faster, right? And what that gives us the abilities, Hey, we deploy the infrastructure. The number of ML ops platform integration or the number of AI apps we support goes really well. So that&#8217;s and my team is. Deep infrastructure specialists and you bring in the application teams from the, you know, the startups or the app companies is what we are focused on. So that&#8217;s really what we are focused on and how we do through is partnership. We see that struggle like very much. They e even for example, even if I&#8217;m an app developer company and I can deploy it in cloud, then I don&#8217;t know how to move to edge, right? So we actually take care of that easily for them. So that&#8217;s really a problem. And through partnership is what we are solving. That</p><p><strong>Dan </strong>13:49</p><p>Just to piggyback on that, I mean, we say pretty, but I like to say our value prop is the three S&#8217;s. Speed, scale, and sovereignty. And the speed part is really important for the end customers that we&#8217;re serving, where it&#8217;s all about. Hey, I&#8217;ve got, you know, mission critical problems in these edge locations. I need them solved yesterday. And you know, for example, with the Navy, and this is public, we did a UNITAS exercise where we were able to rapidly deploy one of our Galleons on a ship. And we were able to show, Hey, you can take these really powerful models and for the first time, it&#8217;s never been done before. Run them at scale, you know, totally disconnected from the public cloud in these very remote locations. The speed piece of that is really important. And then once you do that, you create a ton of value, both for the end customer and then these model companies, which also look at us as a fast way to get deployed in these sites. And then you start to scale. And then the sovereignty piece is really important. I mean, I think what we&#8217;re seeing is that you need to take a broader lens when it comes to national security. And we work not just with defense, but we work in, you know, energy. Also thinking about like other critical infrastructure, like airports, right? All of it is really national security where you need to be able to do 24 7 monitoring of these sites, secure them, and then run all of these really powerful AI models securely locally at the edge.</p><p><strong>Akhil  </strong>15:20</p><p>That&#8217;s awesome. Thanks Dan. And yeah, I think very much aligns with how we think we, I mean, it&#8217;s mission critical, right? It&#8217;s about how do we. Safeguard and enable the varied use of AI applications with the right associated security measures if and when uncertainties happen. And that could be just a commercial cloud outage, which happens more frequently than we care to admit, or something more nefarious that affects not just the national security domain but our businesses and commercial enterprises. Dan, can you gimme another example? Maybe not from the military. Going to Pip&#8217;s comment about how you think about partnering with the best in breed of AI applications.</p><p><strong>Dan  </strong>15:58</p><p>Yeah. One example I really love &#8216;cause of the impact that it has is the example with Alaska Department of Transportation. And this started with us managing all of the connectivity as well as other connected assets for the state, like drones. They use Skydio drones, which are really great for emergency response, specifically using it for things like avalanches and floods. And obviously Alaska&#8217;s a huge, very remote state, and so a lot of times when these natural disaster strike people are affected, stranded in very remote locations and you can&#8217;t wait. For intelligence to respond, you need that in split seconds, just like you do in a defense scenario. And so what we did is for the first time, we deployed one of our Galleons, these modular data centers in Alaska, and we were able to cut their latency from over a day to near real time to respond to these things using all the data from the drones. Right, and that&#8217;s using AI models that are very, people are very, you know, familiar with. But the difference between deploying those at the edge locally versus deploying those in the cloud is literally, you know, life and death. You know, 2020 over 24 hours. I mean, people cannot wait in that scenario. You have to have the intelligence in the moment for it to be useful if you don&#8217;t, responding the moment the data&#8217;s almost like useless. And so that is our focus. And I like that example because I think that is something that is true everywhere in the world. And you&#8217;d be surprised how many different locations have this same problem around the world. I&#8217;ll just give you another example. I&#8217;m about to fly out to Australia. We&#8217;re making a big announcement with a customer in Australia and. I was talking to one of the former Prime Minister there yesterday in preparation for that trip, and they said, Hey, we have that exact same problem, you know, very remote part of the world. There are no large data centers outside of, you know, maybe Sydney and Melbourne. And you know, when fires break out or you know, even just to provide the opportunity to you know, educate the population, provide infrastructure for education, obviously huge area for mining and oil and gas as well. So going back to energy, your stuff is mission critical and we don&#8217;t have anything like it. So we just see a huge amount of opportunity with those types of high impact use cases in these more remote locations that have been underserved. From infrastructure historically.</p><p><strong>Maggie  </strong>18:50</p><p>Yeah. Dan, an another pretty interesting use case. I saw you all announced it was late last year. You announced that Armada is going to be an official collaborator on the Department of Energy&#8217;s new Genesis mission. So I wanted to see if you could talk a little bit about what that mission is and the role that Armada will play.</p><p><strong>Dan </strong>19:07</p><p>We are really excited about Genesis mission. I&#8217;ve really advocated for a project like this for my whole career, so I&#8217;m just. Pumped that we&#8217;re doing this as a country. The things that we&#8217;re doing there are twofold. So one is we&#8217;ve been working with secretary Wright and Dario Gill and the whole team Anthony Pugliese over there. And they&#8217;ve been great about just connecting us to all of the 17 national labs so that we can go there. We can meet with them and we can understand what are the gaps in infrastructure across the labs. Because again, AI drags infrastructure. Genesis&#8217;s mission is the most ambitious AI project in the history of the country. We&#8217;re talking about doubling productivity when it comes to you know. Science and engineering within a decade. That&#8217;s the goal. So if you&#8217;re going to do that, you&#8217;re going to need to deploy AI at a scale that has never been done before. But you can&#8217;t do that unless you have the right infrastructure to enable it. So that&#8217;s the first thing we&#8217;re doing, is we have gone to all of the national labs and we found out. Where are those gaps in infrastructure? And again, our value prop is speed, scale, and sovereignty. We can fill those gaps in infrastructure right away to enable us to. Accomplish the objectives of Genesis mission, which include getting, you know, big wins this year, right? We can&#8217;t wait, you know, years for traditional brick and mortar data centers to be built. So that&#8217;s number one. The second thing is there is a goal to create a common AI platform across all of the national labs. They don&#8217;t wanna operate in a siloed fashion where each Napa National Lab is doing its own thing, right? The power of Genesis mission is taking all of the data from all of the national labs and bringing it all together and having them work in unison. And so what&#8217;s really unique about our platform is the full stack nature of it. The fact that not only can we deploy. These Galleons you know, faster, more flexibly where you can scale up versus overbuilding and do it totally sovereign and disconnected from the public cloud in a way that nobody else can. But the full stack piece of it where each one of these things acts like a node to a distributed private infrastructure that can be leveraged locally, but then also. Coordinated across sites. And a very tangible example, getting into the weeds of this a little bit is take you know, take one of these model companies, right? If you look at who are the collaborators, we&#8217;re one of them for Genesis Mission, but also all of the Frontier model companies are part of it, all of the major ones anyway, you&#8217;ve got pretty much all of the GPU. Know, companies participating in it as well, but then the question becomes, okay, if I deploy those models on one of my sites for cybersecurity and other reasons, I&#8217;m gonna wanna use that locally. It also helps with cost, which is a big issue. Running the models is much more cost effective at the edge versus running it in the cloud. And we can get into that. But then I want to take. All of the improvements that I get, fine tuning the models on all of that data, and there&#8217;s a huge amount of data at each one of these labs, and I wanna leverage that across all of my different sites. And so what you can do is you can take one of those models, whether it&#8217;s from OpenAI or Xai, or you name it, you can run it on that data locally. You can fine tune it to the data, and then you don&#8217;t have to ship all the data back to leverage that across. All of the other labs, you just ship the fine tuned model back and then you leverage that across all of the other labs.</p><p><strong>Akhil  </strong>22:57</p><p>Hey Dan, you hit on something that I think some folks first learning about Armada may not entirely know or have a perception around. It&#8217;s not just about the data center in a box, right? Armada is not, Hey, I&#8217;ve got this galleon and I&#8217;m just gonna plop it somewhere and it&#8217;s gonna have some compute, some GP, you know, a couple of server racks. And have some power. The whole thesis is how do you interconnect those in a way that allows for this nearly hybrid compute environment, depending on the type of application and depending on whether you&#8217;re optimizing for cost or resiliency.</p><p><strong>Dan  </strong>23:32</p><p>Yeah, exactly. And I&#8217;ll let pretty comment on this &#8216;cause he, he saw this firsthand at Microsoft where, what, like when PIP and I were first talking at the beginning of Armada, the opportunity was. Oh, wow. There&#8217;s 30% of the world that has these big hyperscale data centers. But what about the other 70%? There&#8217;s all these gaps globally in infrastructure, and that&#8217;s why we call ourselves the hyperscaler for the edge. And you know, the Galleons are super cool and they&#8217;re very impressive, which in some ways is a big advantage for us. But in some ways, you know, we try to really make it clear it&#8217;s not just about one galleon. It&#8217;s about. The full stack nature of it in the fact that each one of them is a node to a distributed system that can plug all of these gaps in infrastructure globally, and then allow you to leverage your intelligent across all of your different sites.</p><p><strong>Pradeep  </strong>24:27</p><p>So I think Al interestingly, we talk about the world as, I mean, hey, there is you know, cloud for training. And then there is like what we see the world evolving to fine tuning and inference, right? That&#8217;s really it where we are with this thing. So what Armada is really playing a key role as being the platform for fine tuning and inference right now. All the edge boxes we are talking about is mostly for inference deployment. So that&#8217;s where we, basically, what we do is. We give the platform, but we also put the entire full stack solution with hardware and with the modeler data center. That&#8217;s what we&#8217;re doing. And there are cases in fine tuning, we are actually partnering with, you know, data center providers or colo providers where hey, they will actually bring in the hardware and it sits in a colo. And we give the platform, right? So what we are focused on is that customer wants a single platform for both fine tuning and inference, and then I bring down the models from the cloud then fine tune it like on my sensitive data. And then I click a button and I push it to inference for the edge. So that&#8217;s really like what. What Dan is talking about, that&#8217;s where an edge is actually evolving with that per premises. An edge can be like a small, you know, box sitting in a, you know, department of transportation vehicle, a police car. Then we are thinking about an edge box sitting at the bottom of a cell tower. And then you are starting to expand into a co, right? So that&#8217;s really like what we are looking at as, hey. That can be small to you know, a colo. Definitely not a cloud, but how do we have a single platform that spans across multiple? And where we are doing the hardware are both those like ruggedized boxes where we also have partnered with, you know, some of the folks on smaller boxes because they are already deploying those things. Then we want to run our software stack on top of it. So that&#8217;s how we are you know, helping customers.</p><p><strong>Akhil  </strong>26:27</p><p>Thanks, Pradeep. I wanna nerd out for a second here on fine tuning and inference, if that&#8217;s all right. I think we have a group, and I&#8217;m doing this because I think our listeners tend to be somewhat technical, but also a lot of functional experts, right? That recognize that the current models and what the applications look like cannot get to the level of fidelity for their specific use case and deal with the tail of outcomes without some of that. Inference or fine tuning towards the edge, but then comes in all the factors, cost, resiliency, et cetera. So maybe my first question here, Pradeep, is what is wrong with the current state of infrastructure to be able to support this fine tuning and inference and five years from now? What do you want that to look like with, as you said, Dan, with Armada as the edge hyperscaler?</p><p><strong>Pradeep  </strong>27:13</p><p>Pradeep: Yeah so I&#8217;ll give you a real example. We work with one of the you know, logistics customer. They had some physical security challenges. They had some like specific worker safety rules. And they had like literally somebody sitting in front of a camera or like a monitor looking to see if they were detecting some sort of violations, right? And they were like, you know, looking at maybe trying to look at their own models, et cetera. And their long-term plan was, Hey, it&#8217;s not just developing the models. They have you know, hundreds of sites and all of these models needs to run on those edge sites, right? So this is where hey, they tried a bunch of models. They said, Hey, there&#8217;s a bunch of consulting companies who came in, but everybody tries to solve the R piece. They&#8217;re like, oh, I will create the models for you, right? And then like then the next thing they have to deal with this. What&#8217;s the accuracy of the model, right? How do you keep you know, retraining the models or fine tune the models and then are you going to enable me to deliver it end to end, right? Many companies says, oh no, I don&#8217;t do this. You ought to go talk to somebody else and then it&#8217;s your job, right? So this is a case where you know, our AI team came in, we, you know, sat with the customer, they gave us like two weeks of data. Like we had we had our base model developed on the cloud. We, you know, we fine tune it or it drained the model on that. We actually pushed it onto the edge and then you won&#8217;t believe, like the first week we were able to detect seven out of 10 scenarios. Like before it was like a one or a one out of 10 or maximum two, because when the person looks away from the screen, they don&#8217;t see it. And from there we went to seven out of 10. But what the customer loved it and said, Hey, it&#8217;s not this one time. I wanna make sure that because new scenarios will pop up. How do you do that continuous training and then make sure that hey you can push it to the edge because we know what is the capacity available on the like edge. So it is not going to be hundreds of GPUs. So that is something which we are seeing, like where people are. Like in some ways when people are developing models, they assume that there&#8217;s infinite amount of capacity, right? And now how do you take that and run at hundreds of sites with a finite capacity is like the transition and that&#8217;s where. You know, we are helping customers or even partners are starting to look at saying that, yes. Okay, if I say I have got 4G Ps on the site, right? If I take like a small suitcase a deployment, you are barely one GPU, right? How can you like run the same models you know, what you need to optimize is what we are looking at.</p><p><strong>Maggie  </strong>29:48</p><p> Dan. I&#8217;m curious, turning back to, you know, what it&#8217;s like actually engaging with some of these customers. You know, when I think of oil and gas, national security, energy, I don&#8217;t think of the most tech forward-leaning customers. So I&#8217;m curious, you know, how much customer education have you all had to do with these customers? How forward-leaning have you found them to be and how do you get them to trust you to actually help them deploy, you know, really valuable, meaningful technology.</p><p><strong>Dan  </strong>30:17</p><p>Yeah. The good thing is when we first start talking to customers in general, they already have a clear set of goals at the edge, and they already have a backlog of use cases that are low hanging fruit. Once we deploy the infrastructure, there is an initial bridge that you have to cross, which is you have to demonstrate the value of each one of those use cases at these sites. And then they also almost every single one of them has a very stringent cybersecurity review that you have to get across. But then once you do that, and once you deploy at one site, going from one to many is much, much easier. And the reason is there is a huge amount of value that directly ties to their objectives. And if you look at what is a common pattern to go to, back to Pip&#8217;s point on pattern each one of these. Customers, whether you&#8217;re talking about defense or you&#8217;re talking about you know, oil and gas, mining, any one of them, they have a common set of things that are happening. So one is they have very distributed remote sites where they have a lot of data being generated and they understand that the value of that data is dependent upon it being used on the site. For primarily latency reasons, but also a lot of these are critical national infrastructure. And for that and cybersecurity reasons, you actually can&#8217;t take the data off the site. So you have to do all the data processing locally. And then once you deploy, there&#8217;s a huge amount of value to be generated. And I gave the, you know, the defense example and I gave the, you know, emergency response example with Alaska. But if you think about. An industrial example, like a remote oil rig or mine refinery manufacturing facility. I could go on. Each one of those things has a lot of value to be delivered in. Number one, not sending all of the data to the cloud because one, you&#8217;re reducing risk and secondly, you&#8217;re typically, if you&#8217;re, especially if you&#8217;re running AI on that data, saving a significant amount in terms of cost. But number two. Just making sure that those sites work 24 7 as they&#8217;re intended, has a huge amount of value. Every single one of them, whether you&#8217;re talking about an oil rig or a mine, or a refinery or a factory, they have the concept of unplanned downtime and unplanned downtime costs a lot of money. Then at the same time, each one of them is moving towards automation. And so you can help them on that journey as well. And just to give you a sense, like a large energy company, we work with some of the largest in the world. They&#8217;re all moving towards fully autonomous operations over the next three years. And so immediately by deploying this, we&#8217;re able to avoid unplanned downtime. And a lot of them have. Days or weeks of unplanned downtime every year, which can cost hundreds of millions of dollars or billions of dollars at scale. So that&#8217;s an easy business case right there. And then there&#8217;s a bunch of other use cases. But then the second thing is all of them are planning to go towards full autonomy at these sites, or nearly full autonomy. Maybe there&#8217;ll be one person on these sites. Within the next few years between now and 2028. And the only way to do that is to have local compute. So we have this same pattern across all these different areas. And Akhil, to go back to your point on inference, if you take a step back, that&#8217;s why you&#8217;re seeing this super cycle shift from just the training of the models now to the fine tuning and the inference of models is that everybody sees that they have now reached A level where if you do that fine tuning on all of that data at the edge. Then you can actually move towards autonomy and the use cases there are through the roof and the values through the roof when you do that.</p><p><strong>Akhil </strong>34:18</p><p>Super helpful. Dan, lemme just recap for the audience here. What I&#8217;m hearing, I think coming into some of these discussions, I think a lot of folks might see this as, hey, this is, you&#8217;re really paying for resiliency. You&#8217;re paying for whatever it is. What you&#8217;re saying is it&#8217;s not resiliency, it&#8217;s efficacy. There&#8217;s a matrix associated with, some people do want that resiliency, right? In a disaggregated, disconnected environment. Others are actually like, wait a second, this is the most effective way to do fine tuning and inference. And to be able to get that last, you know, not to use a football analogy, the last, you know, third and five, the last five yards to the application efficacy. The only way to do that with all the data sovereignty, all of the. Local nuances is to do it at that edge, and you need to be able to do it in a way that is connected across multiple nodes.</p><p><strong>Dan  </strong>35:05</p><p>Yeah, I would almost say it&#8217;s first about enabling all of these models, enabling local data processing at the edge in the way that was never possible before, which creates a huge amount of value. And then the resiliency is like a nice bonus. It&#8217;s oh, and by the way, these are a part of a really resilient. Distributed infrastructure that if something ever happens with your cloud or something ever happens, even with one of the nodes, you have really resiliency between nodes. But that&#8217;s like a bonus. The thing that gets people to say, Hey, I&#8217;m all in, is number one, there&#8217;s like a huge amount of immediate value to be generated. And then secondly, it aligns with these you know, multi-year initiatives to move towards autonomy in each one of these edge locations.</p><p><strong>Pradeep  </strong>35:56</p><p>Yeah, and I, just to add to what Dan said, we have a mining customer, like they have around 30 mining sites, a large mining customer. They are going through this whole process right now. They have all of these IOT assets sitting in. They all push that to a cloud. It goes to some central region. They were like, Hey. This is not the way I want to do modern edge or modern, like a distributed architecture. So they&#8217;re like working with us to re architect the whole thing from a distributed you know, architecture where hey, you want all of these it devices to actually send, you know, data to be processed in the gall. And then post-process data that pushes to the cloud for, you know, you know, for their compliance reasons, backup, et cetera. And that would also be used for larger training as well, right? You get you know, you know, the what the events which are really useful rather than pushing everything to go sit in some storage account and keep paying for the storage, right? So that&#8217;s why say, hey, it helps me in also that when you do this. At the edge, you can actually take actions because you&#8217;re immediately processed within seconds. You have the output so the people on site can take action. At the same time like I&#8217;m not trying to pay, I also, in many of these cases, egress cost is high as well, right? If you think about the network, if you&#8217;re pushing all of this data, raw data, it is you know, somewhere you&#8217;re paying the network bill too, right? So that&#8217;s, those are the way they are reaping at the architecture from a distributed computer is what they&#8217;re looking at.</p><p><strong>Dan  </strong>37:28</p><p>Yeah, this was actually a big eye-opener for us and our co-founder John, when we started Armada. You go actually talk to these mining companies just to use that example, and they have what&#8217;s called a hard segregation of it and ot it from operations. And you might ask what, why does that matter? What is the practical implication of that? Well, in mining, like in most businesses, especially industrials, time is money, right? And we work with a lot of the largest mining companies in the world. They&#8217;re constantly doing exploration for new projects, right? And a lot of times those things can take years. Well, why do they take years? They&#8217;re almost all in very remote locations. Then because of this hard segregation between IT and ot, they have to do the exploration work at the site. And then they ship this stuff in batch, like the same way they did decades ago to, you know, hq. And they analyze it and then they send it back. And we talk to a lot of companies where we ask, how long does that take you? Well, every time they do that, it takes them a month or maybe more. And so by actually bringing. Something like a galleon to the edge and deploying it behind the firewall on the site. You go from more than a month to real time, right? Which speeds up these projects, which creates a ton of value and also allows them to out-compete the competition. And so it&#8217;s really eye-opening where a lot of people just assume Hey, everybody&#8217;s doing things. You know, the kind of real time way now. Not with a lot of these types of businesses because of this hard segregation between IT and ot, and the only way to actually enable real time is to deploy behind the firewall on the site.</p><p><strong>Akhil  </strong>39:18</p><p>Very helpful. And Dan, as you were saying, that can&#8217;t help but think about the national security parallels of, you know, your analogy between the IT and OT world, right? We&#8217;re listening and observing what has happened over the past couple weeks in the Middle East. We&#8217;re recognizing that the ability to quickly sense what is in the environment and make use of it before it gets into the large IT systems or in the process of is absolutely just as critical. And a lot of those systems too are far. I&#8217;m reminded by some of the stories Raj here at Shield Capital shared about coming back from, you know, a, a fight or flight, a fighter pilot flight, and you know, manually downloading the sensor data. Just think about the latency associated with that. If you could do that in a way that that did not require that for the immediate analysis that needed to be done.</p><p><strong>Dan  </strong>40:12</p><p>Yeah. And Shield&#8217;s, obviously, one of our founding investors, you guys co-led our seed rounds, so thanks for all your support over the years. But I remember talking to RA about that when we started the company. Literally, it&#8217;s and that is happening globally. You cannot have a situation where you have. Very important data just sitting there and you have, you know, days or weeks or months of latency to try to do anything useful with it. You have to be able to use it in real time at the edge. And that&#8217;s the common thing we see playing out across all of these different areas, whether you&#8217;re talking about, you know, defense or you&#8217;re talking about energy, or you&#8217;re talking about you know, any other area.</p><p><strong>Maggie  </strong>40:53</p><p>Dan, I know that you all recently released a white paper on what it&#8217;s gonna take to build US AI dominance, and we know that a lot of our, you know, potentially adversary nations like China are investing very heavily across the stack in talent, in compute, build outs, in mining, in energy. What is it gonna take for the United States to maintain our AI dominance? What are some of the sectors that we&#8217;re going to need to invest in over the next five, 10 years?</p><p><strong>Dan  </strong>41:24</p><p>Yeah. It was funny how that played out. We didn&#8217;t plan it this way, but when we released that white paper, I was in Washington DC with some of our team and we were at the. Winning the AI race summit that the president spoke at last July, and that was the same day that the White House released its AI action plan. And we had been talking to them a lot and so I don&#8217;t think it&#8217;s coincidence, but they were very closely aligned our white paper to that. And the idea is number one, one of the biggest blockers to AI is energy, right? And if you look at how that is playing out globally, China has made very fast progress there. And that is a national security risk, right? We have to solve the energy problem. How do you do that? Number one, you use all of the energy that is available to you and I mean all of it. And one of the things that we highlighted is that in the US there&#8217;s about six gigawatts of stranded energy. And it&#8217;s not being used for ai. Why is it not being used? Well, it&#8217;s because we&#8217;ve been requiring that energy to somehow travel to these far away data centers, and that is very difficult to do. And so what we are instead saying is, let&#8217;s flip the script a little bit and let&#8217;s actually bring the data centers to the energy and enable that energy to be used right there. And a nice thing is that&#8217;s also where a lot of the data lives. And so that&#8217;s kind of our philosophy with Armada. The data centers are an enabler and they should go to where the energy and the data lives, rather than this dynamic where you&#8217;re having to have the energy and the data sail to some far away data center. That&#8217;s one of the reasons why we call the company Armada, is like each one of these things is a ship sailing to the data. And that&#8217;s why we call the data centers galleons. And then the other thing that we need to do is we need to use all different types of energy. And that includes, you know, stranded natural gas that includes things like some of these, you know, micro nuclear reactors. We think that you gotta invest in nuclear, you gotta invest in solar. You gotta, you know, be willing to look at things like data centers in space because the sun is like the ultimate source of energy. We need to use all of these different. Energy sources and then have the data centers go to those energy sources and enable ai. And we need to do it really fast &#8216;cause China&#8217;s moving fast. And so that&#8217;s what we&#8217;re focused on. The other thing, and this is the third pillar of the AI action plan and also in our white paper is you need to work with allies. The allies also have huge amounts of energy that is available for ai, and we can utilize that. And that also has other good impacts, like making sure that we don&#8217;t end up in a 5G situation like we did, you know, with China last time, where you&#8217;ve got other nations adopting that technology. We need to make sure that the world does run on the US AI stack, and so you kill two birds with one stone. When you work with allies, you are able to utilize all of that energy. Constantly improve these models, improve the entire stack, and then, you know, five years from now, instead of running on Chinese infrastructure, the world be running on the US AI stack.</p><p><strong>Akhil  </strong>44:46</p><p>Yeah. And the AI race, as we think about in this geopolitical competition, is not just about the large language models, right? It is also about the infrastructure and the deployability across the globe. And I mean, this is what you&#8217;re seeing, right? Pradeep, both your prior experiences and what you&#8217;re seeing as you deploy Armada, not just. The United States, but across the globe.</p><p><strong>Pradeep  </strong>45:08Yeah. I think, actually great question. I&#8217;ll tell you an example. In 2006 I was working on some of the telecom infrastructure stuff in Africa. What, interestingly I saw was like, you know, Huawei and some of the Chinese providers were actually setting up almost giving away free infrastructure. So they would set up all the telco infrastructure. You know, I didn&#8217;t realize that point of time, but they were actually taking sort of the backbone of the country, right? When you have all the infrastructure in your control, you have you know, the data and everything flowing through under sort of your control. I&#8217;m actually seeing similar thing. If you look at you know, the minerals industry, the mining, et cetera be like in a, if you have to build a lot of infrastructure to run AI models, you need all the, like silicons you for the silicons, you need all the minerals, right? So it&#8217;s a super interesting thing while I look at it as a LLM race, I also think about it&#8217;s a, you know, a race. For grabbing control of all the minerals and the mining sites and the oil and gas, right? So it&#8217;s very interesting to see that&#8217;s what I&#8217;m seeing. Hey you want those minerals in hand to produce more compute infrastructure to run better models, but, and also you want those to be deployed. So who has controlled all of this becomes super critical. And that&#8217;s where we have been talking about, hey, having a full American AI stack is super important from that perspective.</p><p><strong>Akhil  </strong>46:39</p><p>Yeah, interesting. Pradeep, if you actually tie that line together, you can start with AI dominance and the geopolitical aspect there. Then you go to the infrastructure dominance and then you tie to the use cases. I mean critical minerals, right? I mean we&#8217;re talking about that right now. We&#8217;ve been talking about it. Your experiences from 2008 honestly predates some of the news around Huawei. And we&#8217;re only just now seeing or have for the past couple years the. The real challenges and limitations and the desire to have a critical mineral access point, and all of that is predicated upon knowing where they are and being faster about acquiring those resources.</p><p><strong>Pradeep  </strong>47:18</p><p>Yeah. And I think that&#8217;s what to like really underline Dan point. It&#8217;s not just about within America, it&#8217;s about the allies too, right? You have to help and be partnering there to win the stack. Not because there are a lot of natural resources outside of us two, so we gotta be helping the allies to that.</p><p><strong>Maggie  </strong>47:39</p><p>Last question to wrap up, what advice do you have for founders looking to build mission critical technologies for mission critical customers?</p><p><strong>Dan </strong>47:49</p><p>I&#8217;ll start and then Pradeep you chime in my first piece of advice is very simple. Be clear on what your mission is and write it down before you ever hire anybody. Like the first thing that Pretty, and John and I did when we started our motto before we hired a single employee was we sat in a room at Founders Fund and we said, okay, let&#8217;s write down our mission, our reason for existence. Let&#8217;s write down our vision and let&#8217;s write down our values and let&#8217;s make sure that every single thing we do from this moment forward aligns to that. And let&#8217;s make sure that everybody who joins our company understands what we&#8217;re about. And it&#8217;s a simple thing to say, but 99% of companies do not do that. So if you do that, you will stand out and you&#8217;ll get the best talent in the world because people want to work for companies that have missions. They wanna work for, especially the best people they wanna work for companies that are solving the biggest, hardest, most complex problems. And so we did that. We, we had our manifesto that we published, you know, while we were still in stealth, people were like, who&#8217;s this company? But apparently they stand for something. And then we even did a founder&#8217;s film and we did a launch film when we launched outta Stealth. And it was all about our mission. And it&#8217;s funny how. You know, those things are now a few years old, but you go back and look at &#8216;em. It&#8217;s all the things that we&#8217;re doing now. It&#8217;s all the things that we&#8217;re talking about in this interview. It&#8217;s just real. But being very clear about what you&#8217;re gonna do, what you stand for, and then, you know, walking the walk is really critical.</p><p><strong>Pradeep  </strong>49:27</p><p>Yeah. Just to add, actually, as, when we were writing that thing, I remember in in one of our investors office, that time we didn&#8217;t even have an office. It&#8217;s funny that we actually took some of the hardest industries to go after, right? Because we believed that was the right focus area. And in some of the, you know, some of those industries are very hard to move because as earlier mentioned, they are legacy. So you&#8217;ve gotta believe in it and then you gotta be at it every day. So don&#8217;t do it if you&#8217;re not passionate about it. Because solving the hardest problem, you have to have the belief, passion, and you have to grind through it in many ways.</p><p><strong>Maggie  </strong>50:07</p><p>Great. Well, Dan Pradeep, thank you both so much for your time and for coming on the podcast. We&#8217;re super excited to be investors and can&#8217;t wait to see what you all do next.</p><p><strong>Dan  </strong>50:17</p><p>All right, thanks a lot. Great talking to y&#8217;all. See good. Thanks. Bye.</p><p class="button-wrapper" data-attrs="{&quot;url&quot;:&quot;https://maggiegray.us/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe now&quot;,&quot;action&quot;:null,&quot;class&quot;:null}" data-component-name="ButtonCreateButton"><a class="button primary" href="https://maggiegray.us/subscribe?"><span>Subscribe now</span></a></p><p class="button-wrapper" data-attrs="{&quot;url&quot;:&quot;https://maggiegray.us/p/ep-22-armada-building-american-edge?utm_source=substack&utm_medium=email&utm_content=share&action=share&quot;,&quot;text&quot;:&quot;Share&quot;,&quot;action&quot;:null,&quot;class&quot;:null}" data-component-name="ButtonCreateButton"><a class="button primary" href="https://maggiegray.us/p/ep-22-armada-building-american-edge?utm_source=substack&utm_medium=email&utm_content=share&action=share"><span>Share</span></a></p><p class="button-wrapper" data-attrs="{&quot;url&quot;:&quot;https://maggiegray.us/p/ep-22-armada-building-american-edge/comments&quot;,&quot;text&quot;:&quot;Leave a comment&quot;,&quot;action&quot;:null,&quot;class&quot;:null}" data-component-name="ButtonCreateButton"><a class="button primary" href="https://maggiegray.us/p/ep-22-armada-building-american-edge/comments"><span>Leave a comment</span></a></p><p></p>]]></content:encoded></item><item><title><![CDATA[🎙️ Ep 19 - Vector Defense: Building American Drone Dominance]]></title><description><![CDATA[Drones are re-defining modern warfare &#8211; and the U.S.]]></description><link>https://maggiegray.us/p/ep-19-vector-defense-building-american</link><guid isPermaLink="false">https://maggiegray.us/p/ep-19-vector-defense-building-american</guid><dc:creator><![CDATA[Maggie Gray]]></dc:creator><pubDate>Wed, 18 Feb 2026 15:52:26 GMT</pubDate><enclosure url="https://api.substack.com/feed/podcast/188328317/85a264a5645e2bff412c97c72bdb1490.mp3" length="0" type="audio/mpeg"/><content:encoded><![CDATA[<p>Drones are re-defining modern warfare &#8211; and the U.S. is behind. On the latest Mission Matters episode, we sat down with Andy Yakulis, CEO &amp; Co-Founder of Vector Defense, to discuss what it will actually take to achieve American Drone Dominance.</p><p>Vector isn&#8217;t just building drones. They describe their business model as <strong>&#8220;Modern Warfare as a Service.&#8221;</strong> Instead of waiting years to push hardware through traditional procurement pathways, they deliver integrated capability &#8212; technology, tactics, training, and battlefield feedback loops &#8212; under service contracts that tap into O&amp;M funding.</p><p>We discuss:</p><ul><li><p>Why the Pentagon&#8217;s $1B Drone Dominance initiative is the clearest USG demand signal for attritable systems yet </p></li><li><p>How &#8220;Drone as a Service&#8221; business model unlocks O&amp;M funding (the largest color of money) </p></li><li><p>Lessons from Ukraine &amp; Israel (and why it&#8217;s not copy-paste for the U.S.) </p></li><li><p>Building a China-free supply chain and re-industrializing American drone manufacturing</p></li></ul><p>As always, please let us know what you think. And please reach out if you or anyone you know is building at the intersection of technology and national security.</p><p>You can listen to the podcast on <a href="https://open.spotify.com/episode/2HIR2R0HLfrWhpMQE1OVYP?si=2HQmK4v0TAmQANY-xeRq7g">Spotify</a>, <a href="https://podcasts.apple.com/us/podcast/vector-defense-building-american-drone-dominance/id1807120572?i=1000750236016">Apple</a>, <a href="https://youtu.be/0G8EqTptiyo">YouTube</a>, the Shield Capital <a href="https://shieldcap.com/episodes/vector">website</a>, or right here on Substack.</p><p class="button-wrapper" data-attrs="{&quot;url&quot;:&quot;https://maggiegray.us/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe now&quot;,&quot;action&quot;:null,&quot;class&quot;:null}" data-component-name="ButtonCreateButton"><a class="button primary" href="https://maggiegray.us/subscribe?"><span>Subscribe now</span></a></p><div><hr></div><p><strong>Transcript</strong></p><p><strong>Maggie  </strong>00:38</p><p>In this episode of the Mission Matters podcast, we sit down with Andy Yakulis, the CEO and co founder of Vector Defense, a startup building the future of American Drone Dominance.</p><p><strong>David  </strong>01:22</p><p>For an acquisition nerd like me, I get super excited when I get to analyze and dig into a business like Vector. Vector has a pretty unusual business model compared to other startups we&#8217;ve had on the podcast. And describes Vector as delivering Modern Warfare as a service, providing war fighters with a full package of modern technology, Battlefield insights, tactics, techniques and procedure development, tactical integrated services and training, rather than solely tapping into research development, training and evaluation or RDT&amp;E funding and procurement dollars, like most companies, Vector also receives operations and maintenance, otherwise known as O&amp;M funding, for their products.</p><p><strong>Maggie  </strong>02:09</p><p>Vector&#8217;s first product is Hammer, a long range FPV, that is first person view, drone capable of deep sensing and deep strike. As I&#8217;m sure many of our listeners are already aware FPV drones and other attritable software defined systems have proven to be an integral part of modern conflict. FPV drones now cause an estimated 60 to 80% of casualties on the battlefield in Ukraine. However, the US is woefully behind in FPV manufacturing and procurement as China dominates the FPV drone market.</p><p><strong>David  </strong>02:41</p><p>However, late last year, Secretary of War, Pete Hegseth, announced the $1 billion Drone Dominance initiative for the Pentagon to procure hundreds of 1000s of these FPV drones over the next two years. This signals a clear turning point in the Department of War demand signal for FPV drones.</p><p><strong>Maggie  </strong>03:03</p><p>Since it was founded, Vector has raised more than $60 million, and they have an incredible founding team to execute on this vision. Andy, the CEO, spent 18 years as an Army officer, specifically as a helicopter pilot, with time spent at Special Operations Command, Army futures command and the Office of Strategic capital. His co founder, George Matus, began developing novel drone technologies all the way back in high school, and founded Teal Drones, a company he scaled into one of America&#8217;s leading drone manufacturers, winning the US Army&#8217;s Short Range Reconnaissance program of record, which is one of the first major US military programs related to small drones. Additionally, the founding team includes Matt Long and Larson Jensen, who also spent time in the Special Operations community as Navy SEALs.</p><p><strong>David  </strong>03:51</p><p>This conversation covers everything from the current state of U.S. attritable drone capabilities to the challenges surrounding drone manufacturing and supply chains and how the lessons learned in Ukraine translate to the United States forces.</p><p><strong>Maggie  </strong>04:06</p><p>All right. Well. Andy, thank you so much for joining us today on the Mission Matters podcast. I know one of the big reasons that we decided to do this podcast really trying to spread the word about one of the administration&#8217;s new initiatives, which is Drone Dominance, great name. So could you just tell us a little bit about Drone Dominance and the significance of this initiative?</p><p><strong>Andy  </strong>04:30</p><p>Well, Maggie, David, great to be doing this with you. We&#8217;re really excited to to go after the Drone Dominance program, or what we call a DDP, the Drone Dominance program is exciting for a variety of different reasons. One, it&#8217;s this major demand signal that we&#8217;ve been waiting for for many years from the Department of War. You know, I think the relationship with me and David goes back many years. We used to always lament about how we had these unclear demand signals. From the Department. This is the first time where we have a multi year program, multi-year funding, and large budget dollars of congressionally appropriated dollars. And so obviously there&#8217;s a lot of risk still in the market, but the Drone Dominance program has taken away a lot of that uncertainty that we usually see in defense.</p><p><strong>David  </strong>05:18</p><p>Yeah, and Andy. I mean, definitely thinking a lot about drones demand signal. What do you think it is like this time and moment today that is allowing the department to announce something like Drone Dominance? And then maybe, where do you think it goes from there?</p><p><strong>Andy  </strong>05:39</p><p>Yeah, it&#8217;s a great question. You can&#8217;t talk about drones without talking about Ukraine. Obviously, Russia invading Ukraine in February of 2022 set off this revolution in military affairs, where we see drones or unmanned systems used in ways we&#8217;ve never seen before, where you can take a drone that used to be used for racing, strap a bomb to it and have this outsized, asymmetric impact on the battlefield. And we as a nation, we as a company, both have been paying very close attention to how unmanned systems, or drones, are used on the battlefield in Ukraine and Israel and all over the world, and the Drone Dominance program is a clear indicator that the Department of War has also been paying attention, and it is now time for America to show its dominance in all areas of technology. For this program, in the drone industry and as the dominant superpower in the world, we need to also have a very resilient supply chain, a very resilient, powerful, competitive drone industrial base, and that&#8217;s what this program is incentivizing, is more competition, so more vendors like Vector are competing on that battlefield to build the very best system for our warriors.</p><p><strong>Maggie  </strong>06:58</p><p>I mean, there&#8217;s no doubt in my mind, right, the FPV drones have been just a tremendously powerful force in Ukraine. But I know a lot of critics point out the US military and our threat landscape is very different from the Ukrainian military. We have significantly more resources. So how do you see these systems translating to be powerful for US forces in conjunction with our other exquisite systems.</p><p><strong>Andy  </strong>07:25</p><p>Well, there&#8217;s a lot to be learned from the war in Ukraine. Maggie, there is a lot to be learned for how the Israelis use unmanned systems on the northern border against Hezbollah and then throughout Gaza and more like an urban setting. What I always tell folks is, there&#8217;s not a copy-paste from Ukraine or Israel to the United States military. The United States military has a very specific doctrine, and they are going to use unmanned systems in the way that makes the most sense for them. That doesn&#8217;t mean that because the Ukrainians or the Russians use drones in a certain way that there&#8217;s not lessons to be learned from them. I think that&#8217;s where the innovation of our company and other companies like Vector comes to play is how do we take those lessons learned from the overlap of tactics with technology and apply that to the American military? A lot of what Vector does is not just the production and the manufacturing of an unmanned system, but how that unmanned system is tactically employed. And I think having both sides of the company come together, you know, I think a lot of that is coming ahead in this Drone Dominance program, and having both sides of our company come together is a defining characteristic of this company, but it&#8217;s also a defining characteristic of where we see the drone ecosystem going in the United States, where the United States military is playing a little bit of catch-up right now, to be honest, that&#8217;s what this program is designed to do, is to rally the drone industrial base. But also, the drone is sort of worthless if we don&#8217;t know how to tactically employ it, and so we need to do a lot more work. We, as a military and as an industry, need to make sure that we are leveling up our game on how to tactically employ unmanned systems.</p><p><strong>David  </strong>09:05</p><p>So Andy, I definitely want to build on that. One of the things that you talked about early on with the company, and that really just couldn&#8217;t take my mind off of, is the approach you&#8217;re taking to the military, right? I think you call it drone as a service, or modern warfare as a service, getting in with the tactics, techniques and procedures, with the special operators and and the standing army as well. What has like tell the audience a little bit about your approach, because I think it is relatively unique to most venture backed startups engaging with the national security system.</p><p><strong>Andy  </strong>09:47</p><p>Yeah, absolutely. David, so when we first met, I was still in the Army. I was at Army Futures Command. You were, and still are, a venture capitalist, but we were always trying to work on this concept of how do we streamline technology through the acquisition system faster? How do we make transitions easier? How do we make sure that we are this dominant technological superpower with our defense technology? And I&#8217;ve been working on this problem set for five, six years of how do you push technology through the procurement system faster, so it&#8217;s still relevant when soldiers get their hands on it. You know, when I was in the Army, we used to have this saying that we&#8217;d get a laugh at conferences. I just don&#8217;t think it&#8217;s funny anymore, where we give our soldiers yesterday&#8217;s technology tomorrow. And that comment has actually turned into a national strategic vulnerability. The technology exists &#8212; this is not a technology problem. We&#8217;ve got great, innovative companies and amazing entrepreneurs and engineers that can produce great technology. What I kept looking at was, well, this is a contracting problem. This is a procurement problem at times. This is an administrative bureaucracy problem. And I think when you&#8217;re fighting sort of a long, sort of bureaucratic process, when you&#8217;re fighting the status quo, sometimes it&#8217;s a good thing to take a step back and like, why even try to go this way? Is there another way to attack this problem? And that&#8217;s when the idea of Vector was sort of born, which is like: what if we didn&#8217;t try to sell a drone through the procurement system that could take five, seven, or ten years. What if we attack this problem totally different, and flip the whole concept on its head? And what if we sell a service? What if we sell integration and training? What if we sell the innovation ecosystem that we were developing with those that we are working with? And then, what if we could sell unmanned systems underneath a service contract. And the more that we studied the problem, the more that we studied the Federal Acquisition Regulation, the more we realized this was actually a pretty innovative go to market to achieve a couple of things at once. And if you think about the concept of attritable systems, an attritable system is a consumable piece of technology. When you consume that technology, you have this opportunity to update what was just consumed with a better product. And that sort of fits in this sort of approach of, well, if you&#8217;re on subscription contract, or if you&#8217;re providing drones as a service, as the drone attrits, why not provide a new, innovative drone than the one that you sold before? And so that&#8217;s been our approach ever since we started the company, over 18 months ago, which was actually to attack this as a service contractor, still building products, still selling products, but all underneath service contracts. And I&#8217;m proud to say, every drone, every component, every kit that we&#8217;ve sold to date has been underneath the service contract.</p><p><strong>David  </strong>12:38</p><p>So you must have just a giant other direct cost contract line item, CLIN, within that contract, is that correct?</p><p><strong>Andy  </strong>12:46</p><p>That&#8217;s correct. Yes, that&#8217;s That&#8217;s correct.</p><p><strong>David  </strong>12:51</p><p>Awesome, because I think I mean, for a venture backed company, you do still have to be mindful of margins. And if you&#8217;re doing services, I presume, some somewhat of a time and material type contract, you&#8217;re not going to get the types of margins that you&#8217;re looking for, but I guess that&#8217;s where then the quantity of the types of systems that you&#8217;re looking to sell, the constant refresh rate. You could look at your TTP development as a bit of a moat over time.</p><p><strong>Andy  </strong>13:22</p><p>That&#8217;s absolutely true, and you&#8217;re right on the margins with service contracts. But again, there&#8217;s no limit to the amount of systems you can sell underneath a service contract, and so you can sell large quantities of system as long as they&#8217;re below a certain price point. This doesn&#8217;t work for a tank or a jet fighter, but for attritable systems, the strategy makes a lot of sense, moreover, and I think this is what gets a lot of folks excited about the the business strategy here is, if you get into the different appropriations for what we call different colors of money, you have operations and management dollars, and that&#8217;s what we&#8217;re talking about right now, service contracts, leverage the O&amp;M budget, which just happens to be bigger than the procurement budget and the R&amp;D budget. But because we&#8217;re still building systems, there&#8217;s nothing that says I can&#8217;t go after procurement contracts as well. There&#8217;s nothing that says I can&#8217;t go after R&amp;D contracts as well. And most defense technology startups are just in those latter two bins and leave the O&amp;M budget completely alone, but that&#8217;s a huge untapped market that most companies aren&#8217;t going after, and there&#8217;s competition there that for us to go after. But Vector is attacking those three main buckets, those three main colors of money all at the same time, and a lot of times the work that we do on the service side can benefit the work we&#8217;re doing, going after different procurement contracts.</p><p><strong>Maggie  </strong>14:46</p><p>Something else that I think makes a lot of sense with this as a service model. You know, when I think about SaaS software as a service, you know, the whole point behind that is that software is constantly changing, so you don&#8217;t actually want to buy one static piece of software and then use it forever. You want to pay kind of a recurring fee that allows you to always have the newest, latest, best technology. And I see that applying really well to the drone space. And I think we see on the battlefield in Ukraine, in Israel, people say these drones are changing basically every day. You might actually have to throw out all of your drones every three months, the DOTMLPF is changing all the time, and I&#8217;ll just define that for listeners. That&#8217;s doctrine, organization, training, materiel, leadership, education, personnel, facilities, and policy. So how are you all keeping up with what is actually happening on the battlefield in the technology space, and how do you bring that back into the tech that you&#8217;re building today, into the TTPs and DOTMLPF that you&#8217;re discussing with your customers?</p><p><strong>Andy  </strong>15:51</p><p>Yeah, well, let me say first, Maggie, it&#8217;s very hard. I mean, it&#8217;s very hard to keep up with how fast the Ukrainians are moving, the Israelis are moving. So necessity being the mother of invention, the Ukrainians have gotten so good out of innovating because their survival depends on it. They are constantly trying to find a new way to incorporate advanced technology and the unmanned systems they&#8217;re using to keep the Russians at bay, and they&#8217;ve done a fantastic job. And the fact that the lines have barely moved over the last four years is is evidence of that. And so we have gone to where the Ukrainians are. We have a team in Ukraine, we have a team in Israel, and we maintain a very consistent leader presence back to those two locations, you know, not to do anything operational, obviously, but to study the tactics, techniques, and procedures, to study the cross section of technology and the tactical implementation of that technology used on the battlefield, we now do a monthly report, which we call the Vector report, which is our learnings from the modern battlefield over that last month, of how unmanned systems or other modern warfare technology was used on the battlefield in different parts of the world, and so it&#8217;s been very, very challenging to incorporate all those lessons, to put that into a training course, or put that into the next generation of product development. We use training courses with the United States military to mimic that innovation cycle. And like I was saying before, it&#8217;s not a copy paste of what the Ukrainians are doing and what the Israelis are doing with unmanned systems, because the American way of war is different. But we take a lot of inspiration from those battlefields, applying it to your point, David and Maggie, to the DOTMLPF, and the cross section of how the American military will leverage unmanned systems from their doctrine all the way down to the facilities and the policy.</p><p><strong>Maggie  </strong>17:49</p><p>What have been some of the biggest technical challenges that you all have had to work through as you&#8217;re trying to build these systems to operate on a realistic battlefield?</p><p><strong>Andy  </strong>17:59</p><p>Yeah, it&#8217;s a great question. Maggie, unfortunately now, and I say unfortunately because we need to do better as an industry, but unfortunately now we&#8217;re still very much in a one-to-one, one pilot operator to one drone. The next phase of warfare, the next phase of the technological development for unmanned systems, needs to go from one to many. And so it&#8217;s kind of interesting, if you if you think back to the global war on terror, where we had multiple individuals piloting, operating, launching drones, predators, reapers and things like that. We are very much in a many to one. Now, for the most part, we&#8217;re in a one to one, one operator to one drone. We need to go to the one-to-many concept, and this is a technological challenge to be able to put enough processing power, enough autonomy on a drone, which can be done but a low enough price point. So the unit economics makes sense to realize this vision of what we call a triple mass, again, &#8220;triple&#8221; being the idea of consumable or throwaway technology, mass being we want to have large quantities of unmanned systems. The economics only work out if you can have just enough autonomy at the right price point on a low-cost system, so you can produce in mass, and the United States military can buy in mass, leveraging the right amount of autonomy and finding that balance, to not put too much R and D into a drone, but still have enough automation and keep the unit economics low enough so the Department of War can buy not tens of thousands, but hundreds of thousands or millions of drones. That&#8217;s really the technological challenge, right there.</p><p><strong>Maggie  </strong>19:35</p><p>As we think about this constantly changing technology, as autonomy technology is getting better, electronic warfare, resilient communications is constantly changing and improving. How do you think about the government&#8217;s plan to stockpile hundreds of 1000s of these drones? How do we keep them updated and make sure that you know when the war fighter needs these systems, they have the most cutting edge version of them.</p><p><strong>Andy  </strong>20:01</p><p>Yeah, so I think there&#8217;s actually two questions in that. One: how do we keep the stockpile current? How do we even have a stockpile? And then, how do we keep it current? To the first part of your question: we learned this lesson the hard way during covid, that our supply chain was not as resilient as we thought, and that&#8217;s everything from medicines to toilet paper, to the components that go into drones. And what we have done at Vector, you know, really, over the last 18 months, is to shore up our supply chain, to make sure every component is decoupled from China and, where we can, to lean on the domestic, the US supply chain, which is very, very hard to do when we, as an industry, are trying to create this decoupled, China-free drone supply chain almost overnight. That&#8217;s what the Drone Dominance program actually requires, and is designed to do, is to stimulate and energize the drone industrial base, making sure it&#8217;s clear and decoupled from China. You know, a lot of money needs to be poured into this ecosystem to make sure the price points can come down so we can realize this concept of economies of scale. Because China is just this manufacturing powerhouse, and they&#8217;ve got incredibly cheap labor over there, which is basically very, very challenging to compete on price. And so, you know, I applaud the Department of War for launching the Drone Dominance program, because this program is doing a fantastic job to energize the drone industrial base, to make sure we have the components decoupled from China at a low enough price point so that we can produce drones at scale. So I think that is happening. We need to see even more come from the Department of War and other agencies. But we&#8217;re really excited about where this is going on how to keep things current and up to date. I think this goes into our strategy, which is to have a very much more open architecture, a much more modular design. That goes into everything from how we design the drone, how we engineer the drone, how we manufacture the drone &#8212; all in a very open-architecture way. We like to say at times, we&#8217;re like the Android of drones, where a lot of other companies, for better or worse, are more like the iPhone of drones, very close, very proprietary. Our philosophy is, in order to capitalize on these constant innovations, just as you said, Maggie &#8212; the constant evolutions from one piece of software or hardware to the next. The only way to do that is to have a very open, modular architecture, and that&#8217;s how we design from the start.</p><p><strong>David  </strong>22:32</p><p>Andy, I think that was really great. I would love to maybe dig in a little bit more on the supply chain and manufacturing and how you all think about that buy versus build conundrum that I think a lot of hardware companies go through right SpaceX, famously completely vertically integrated, and then others, you know, there is a robust supply chain, and you&#8217;re picking out different partners for the drone industry specifically, given that a lot of components come from China, I think some of the main ones include the motors and the batteries, and there being kind of a lack of an industry base for those types of sub components, I guess. How do you differentiate your product if you were to go to the same suppliers, that&#8217;s, you know, fairly in its infancy. But then too, like, you know, how do you make that decision about this is the thing we&#8217;re going to do in house, and this is the thing that we&#8217;re going to outsource to a domestic partner.</p><p><strong>Andy  </strong>23:39</p><p>Yeah, another great question, and I think this actually takes us back to, like the evolution of Vector. When we first started Vector, we wanted to be a systems integrator, a tactical systems integrator of unmanned systems. We did not want to build anything, and we started working with a variety of partners and incorporating integrating their drones into different DOTMLPF, going through the DOTMLPF, incorporated them into different war fighting exercises for our customers, we would do mods, we would repackage into different strike kits. But our customers kept asking us to build very bespoke drones for them. They wanted different features that just didn&#8217;t exist on the market, so we started manufacturing our own drones in low quantities in probably the middle of 2025 but as we looked into the supply chain to your question, David, we realized that the components that were going into the drones either weren&#8217;t getting us the results we needed when we were buying off the shelf, or they weren&#8217;t meeting the compliance requirements for the Department of War, especially as they have refined the interpretation of the National Defense Authorization Act, the NDAA compliance scrutiny has definitely grown over the last 18 months, and to that end, we have gotten much more vertically integrated over the last six months, out of necessity, because we had to, because. We could not leave any room for error on compliance. And you know, going back to last year, we thought we understood what was required for NDA compliance, and it wasn&#8217;t really until the last six months where we really, really dug in, where we hired some really, really top talent on supply chain. We really did a forensic analysis of our tier two, three and four suppliers, and made sure we understood, we understood exactly down to the resistor, transistor level, where everything was coming from. And so I kind of tell that arc of Vector of getting more and more vertically integrated to say, you know, there&#8217;s, there&#8217;s certain parts of the drone that we build ourselves, there&#8217;s certain parts of the drone that we just have great partners, and we&#8217;re really excited to actually announce two of our major partners. Both are domestic suppliers. One is a company, a battery company, actually, that was making batteries for a different purpose, and we brought them into the drone industry. We have actually done this with a variety of our different vendors, where we found vendors that were in adjacent industries, and we brought them into the drone industry, one, because they were decoupled from China, but two, to give us an advantage on supply chain, knowing that there wasn&#8217;t a lot of competition for that specific vendor. So we spent a lot of time analyzing the supply chain, a lot of time working with vendors, and a lot of time investing in there. And I think to more directly answer your question, David, is those items that require an increase, increase capital investment, ie, spinning motors that would take a little bit of a capital investment, a lot of time to stand that up. That&#8217;s a great that&#8217;s a great thing to buy and then assembly into your drone. A lot of the things we do on PCBAs. You know, we&#8217;re not printing our own boards here at Vector, but we do a lot of work to design our own boards as well, and that&#8217;s also a great thing to contract manufacture out. And so looking at especially the stage we&#8217;re at which we&#8217;re a post series A company, what makes sense from a capital investment side, what makes sense from an IP side. That&#8217;s really how we make our decisions thus far. But we also are taking a hard look at where do we need to have the most control over the components, either for the capability, for the consistency, for the quality and or for the compliance. That&#8217;s really what, what drives a lot of our decision making,</p><p><strong>David  </strong>27:19</p><p>And I would imagine also like, what allows you to then scale?</p><p><strong>Andy  </strong>27:25</p><p>Yeah, absolutely. And that&#8217;s also a strategic decision based off where the company is, either from a capital raising perspective or a revenue perspective. You know, you can do a lot when you&#8217;re on a large contract to further scale. And again, this is what the Drone Dominance program is doing for the industry. It is giving companies like Vector and some of our suppliers a chance to scale, because now they can see the demand coming, really, for the first time in a very long time. So again, we applaud the Defense Department or the Department of War for clearly showing that demand signal.</p><p><strong>David  </strong>28:02</p><p>When you know, talking about this compliance stuff, I think something we hear a lot of from startups, or at least the idea of is who I&#8217;ll partner with a defense prime, right? People that have been here done that before you know, if there&#8217;s one thing that they&#8217;re good at, it is checking all of the boxes around compliance for working with the department. Can the same, is the same true for this particular program, or is there a little bit of a everyone&#8217;s at the same starting point, and it&#8217;s all about how you execute. So I guess short of the long on this question is, is is Vector partnering with any defense primes, and is that a part of your overall partnership roadmap?</p><p><strong>Andy  </strong>28:46</p><p>It absolutely is. I don&#8217;t think you can be in the defense space and not look to the primes for partnership opportunities. And there&#8217;s a lot of folks out there that will throw shade on the primes. I&#8217;m not one of them. I think the primes are fantastic. They&#8217;ve done so much for this nation, and they&#8217;ve done so much for a lot of you know, innovative startups like Vector, as they become much more accepting of partnering with companies like like like Vector, because we provide a lot of value to them as well, a lot of the innovation and speed side. So yes, we have partnered with a number of primes. The primes are fantastic for a lot of the compliance, helping us navigate the regulatory environment for, you know, contracting pathways, and so we use them for things like that. And so an invaluable resource. And if there&#8217;s any startups out there, or budding entrepreneurs, I would always encourage them to reach out to the primes sometimes that&#8217;s a that&#8217;s the best way to get started is to is to be a sub for a number of years before you&#8217;re even a prime yourself.</p><p><strong>Maggie  </strong>29:51</p><p>Andy, one question that I have is surrounding testing. One of the things that I&#8217;ve heard from a couple. Companies building in the national security hardware space is that it can be really hard to actually get access to test ranges where you can realistically test your systems the way that they need to be tested to be resilient in a place like Ukraine, a lot of times, electronic warfare in particular can be difficult to test because of the way that FCC and FAA regulate airspace and regulate the spectrum space. So could you talk a little bit about how you all have approached actually testing your systems to ensure that they&#8217;ll be resilient on the modern battlefield?</p><p><strong>Andy  </strong>30:34</p><p>Yeah, it&#8217;s a great question. Maggie, I think we&#8217;ve been very fortunate in the testing domain. Early in Vector&#8217;s history, we jumped into testing as a service of electronic warfare as a service where we had access to very unique ranges here in the United States that did have their FAA and FCC certifications. And so we were able to kind of jumpstart a lot of testing there. One of the things I always asked when I was in the government to companies like a Vector, was, Are your products in Ukraine? Have you tested in Ukraine? And I feel like that&#8217;s almost table stakes at this point. Now, here in 2026 where, if you were going to approach the Department of War with a product they&#8217;re going to want to know, did you test this in some way in the Ukrainian ecosystem, there&#8217;s a lot of great Ukrainian test ranges off the front lines, and they&#8217;ve done a fantastic job of setting those up and providing pathways to being able to test your systems there in some very, very realistic scenarios. And so we&#8217;ve gone down that path. We&#8217;ve used a lot of domestic test ranges, and then, of course, we run a lot of simulation as well. I think the best way to test though, is with your end user. And this is where Vectors business model really comes into play, where a lot of times we get paid to test our products on a service contract with our end user. And that&#8217;s sort of part of the contract, and that&#8217;s part of what our end users expect is, is they want us to bring them the latest and greatest piece of technology that we think may, you know, give them some sort of exponential value, and they understand that it&#8217;s being done in a test environment, and they love that, they love being introduced to something new. And, you know, I think being very honest, and having that relationship with your end user, telling them, like, Hey, this is a prototype. This isn&#8217;t ready, but we really want your feedback. Tell us what you think, see if you can break it, see if it flies in this environment. Please give us that feedback. And so we do a lot of that as well.</p><p><strong>Maggie  </strong>32:38</p><p>Something that I think is interesting about Vector. You guys are based in Utah rather than some of the other big defense startup hubs like LA or Seattle or Austin or even San Francisco. Can you just tell us about your decision to build the company there?</p><p><strong>Andy  </strong>32:53</p><p>Yeah, sure. We actually started in North Austin. We still have a satellite facility in North Austin. We probably always will, for a variety of reasons, but we made the decision to move to Utah for a variety of reasons. Nothing against El Segundo or the Bay Area. I actually had a previous startup in the health tech space based out of Silicon Valley. Great experience, but there is this very different startup culture in the bay area or El Segundo than there is here in Utah. In Utah, it&#8217;s very collaborative, it&#8217;s very founder friendly. The Economics of running the business in Utah is very, very different than in California, and it&#8217;s much easier. The taxes are way better. What you pay employees in Utah is very, very different than in El Segundo. You know, it&#8217;s hard to make the unit economics work on the drone, on the labor, on the rent and all that overhead that goes into your facility if you&#8217;re in California, especially if you&#8217;re building attritable systems. And knowing that Vector would probably build hardware at some point, we wanted to be outside of California, just to make the financial aspect that much more scalable for us. The state Government has just been fantastic to us. They&#8217;ve been very welcoming Utah for testing. Back to your testing question, Maggie, is pretty fantastic. There&#8217;s a lot of BLM land here that we use for long range testing, and there&#8217;s a variety of different military bases here that we use as well, where we partner with the military to do a lot of live kinetic testing on our drones as well. And just having easy access to all those ranges has just made this a world class place to build and to test. You know, the summers get to sometimes 105 110 degrees, and the winters get to below zero. So we get to do a lot of environmental testing, high altitude testing around here as well to ensure that the products were put into the to the hands of the war fighter, have been tested in a variety of different conditions, so all of that kind of put together just just made a lot of sense for us, and we&#8217;re happy to call Utah Home, and it&#8217;s just been fantastic for the team.</p><p><strong>David  </strong>34:55</p><p>Utah is a great place. Do you enjoy skiing there? I&#8217;m excited for the innovation. An ecosystem that&#8217;s burgeoning. I won&#8217;t tell the El Segundo people, you know, how you feel about them when I&#8217;m visiting out there later this week, but maybe moving to the international side. You know, you talked about Ukraine, sort of receiving a lot of lessons learned there and doing some testing as well. How do you think about the rest of the international landscape? Right? America still has very strong like foreign military sales, a strong technology culture selling, whether that&#8217;s to the Asian Pacific market, out to the Middle East, to other European partners, is it still too early, and right now, we&#8217;re just focused on getting this right here at home in the United States, or is Vector also thinking about international expansion.</p><p><strong>Andy  </strong>35:49</p><p>We&#8217;re very much focused on the international market as well. Again, we&#8217;re excited for some interesting announcements we&#8217;ll make here in probably the next 60 to 90 days of some international markets that were opening up for the Vector team. What has been very interesting with the international market, though, that really closely ties into this administration is previously there would be a lot of U.S. aid to our partners and allies. And what this administration has done is sort of flip that script, incentivizing our partners and allies to do more direct contracts with innovative companies like Vector. The other thing that has been an interesting change in the international market is a lot of our foreign partners don&#8217;t want to buy all-up systems. They want to do in-country manufacturing, they have seen the same vulnerabilities to supply chain that we learned during covid. And what they&#8217;re more interested in is not an all-up system that Vector may build, but more so the components, the raw components, that Vector is designing, and then helping them stand up a world-class unmanned systems factory and drone Center of Excellence. And so everything from support in standing up in-country manufacturing, to teaching and training, their own version of DOTMLPF, their own version of tactics, techniques, and procedures for their military, that is what&#8217;s most interesting to our international partners, and that&#8217;s how we sort of attack the international market &#8212; focusing on those countries that are ready to move dollars toward those types of programs.</p><p><strong>Maggie  </strong>37:27</p><p>Andy, you&#8217;ve had a long career, both in the military and national security space and now in the founder startup space. What advice do you have for founders who may not have your years of experience as they&#8217;re looking to build startups to support national security customers.</p><p><strong>Andy  </strong>37:46</p><p>That&#8217;s a great question. Maggie, so I spent 18 years in the Army. The last five or six years were focused on this market &#8212; focused on how you build for defense &#8212; not knowing I was going to become an entrepreneur in the space, but I was just fascinated by the defense acquisition process, and so I thought I had a good handle on how to go to market. It&#8217;s way more challenging than I ever thought. You know, I look at all the advice I gave entrepreneurs when I was in the military, and I sort of shake my head at myself, because I really had no clue on how hard it really was for the entrepreneur. And so I say that to say, don&#8217;t start a company, period. Don&#8217;t start a company in the defense space unless you absolutely can&#8217;t not do it. And I use the double negative on purpose, like you have to lie awake in bed every night thinking about your idea, thinking about your startup, thinking about the market, thinking about how you want to do all of this, and if you can&#8217;t sleep because you&#8217;re so captivated by diving in and joining this coalition of entrepreneurs that are trying to build it for defense, then great. But if you have doubts, then it probably isn&#8217;t for you, because it&#8217;s hard. It&#8217;s a slog. Every day I relish in it. I enjoy it very much. I don&#8217;t think there&#8217;s anything else really worth doing, at least in my professional career, than building for defense. But you have to be ready for the challenge. You have to be ready for the highs and lows. And if you are, then it&#8217;s a very, very rewarding sort of industry to be in, but it&#8217;s not for the faint of heart.</p><p><strong>David  </strong>39:19</p><p>Yeah, I think that&#8217;s well said, it&#8217;s definitely a labor of love, not so different than serving in certain ways, right? It&#8217;s a grind, and you&#8217;ve got to love it for all the right reasons. Beyond the things you&#8217;re listening to and reading about in the defense tech space, give the listeners a bold prediction, you know, an Andy special, if you will, on something you see playing out in the next year or five years, but obviously the more relevant to today, even better.</p><p><strong>Andy  </strong>39:58</p><p>Yeah, so, um. I&#8217;m not an everyday reader, but I think a book that has changed my perspective and has influenced me a lot is<em> Freedom&#8217;s Forge</em>. And I think Freedom&#8217;s Forge 2.0 is coming. I think the involvement of the United States government, for better or worse, is going to change the defense ecosystem, especially in the unmanned space, in a way that we could never imagine. I&#8217;m seeing a lot of very interesting things come from the United States government, from direct investments into companies, MP Materials, Intel, L3, and a couple others. I think that&#8217;s a big signal of how involved the Defense Department wants to be to ensure that we have a Freedom&#8217;s Forge 2.0 to ensure that this re-industrialization actually happens, to ensure that we do have the industrial base, to ensure we&#8217;re ready for hopefully the next fight that never happens, to ensure that we&#8217;re ready for it. So I think what we have seen come out of this administration and the Department of Defense, or the Department of War, is just a signal of much more to come. And I think Freedom&#8217;s Forge 2.0 is coming in a big way, and we&#8217;re really excited to be a part of it.</p><p><strong>David  </strong>41:15</p><p>Well, that&#8217;s awesome. Andy, I&#8217;m sure, and I hope that they write a chapter about Vector in Freedom&#8217;s Forge 2.0 but just for our listeners out there, that same author, Arthur Herman, he&#8217;s coming out with a new book called<em> Founder&#8217;s Fire: From 1776 to the Age of Trump</em>, set to release on the 21st of April this year. So I don&#8217;t think they&#8217;ll write about Vector in that one, but I&#8217;m sure, you know, Arthur will be looking you up pretty soon. So with that, Andy, thank you so much for taking the time to come on to Mission Matters. It&#8217;s awesome to hear about your story, to see veterans like yourself getting out there, you know, putting their time, their sweat, their energy, right, all their lessons learned, into building a company of consequence. We wish you the best of luck. I can&#8217;t wait to hear about how well you do in the Drone Dominance program, right, and that maybe in the very near future, airmen, soldiers, Marines, and sailors, etc, will all be flying your drone. So just awesome. Thank you so much.</p>]]></content:encoded></item><item><title><![CDATA[🎙️ Ep 18 - Starfish Space: Building Autonomous Satellite Servicing in a Contested Space Domain]]></title><description><![CDATA[Space is a contested domain.]]></description><link>https://maggiegray.us/p/ep-18-starfish-space-building-autonomous</link><guid isPermaLink="false">https://maggiegray.us/p/ep-18-starfish-space-building-autonomous</guid><dc:creator><![CDATA[Maggie Gray]]></dc:creator><pubDate>Wed, 11 Feb 2026 18:31:29 GMT</pubDate><enclosure url="https://api.substack.com/feed/podcast/187601748/90bdd8a4b48918241652c910200d495a.mp3" length="0" type="audio/mpeg"/><content:encoded><![CDATA[<p><strong>Space is a contested domain. </strong>Russian and Chinese satellites are conducting proximity operations near American satellites. Critical U.S. and allied infrastructure depends on space-based assets that can be inspected, approached &#8212; or interfered with. On the latest <em>Mission Matters</em> episode, we sat down with Austin Link, CEO of Starfish Space, to discuss why rendezvous &amp; proximity operations (RPO) are becoming mission-critical.</p><p>Starfish is building &#8220;space tugs&#8221; that can dock with and move other satellites &#8212; extending mission life, disposing of debris, and enabling other national security use cases. Their recent Remora mission autonomously maneuvered one satellite within 1,250 meters of another, validating a core thesis: <strong>software can radically lower the cost of operating in orbit.</strong></p><p>We discuss:</p><ul><li><p>Why affordability and scale matter as much as exquisite capability in a contested domain</p></li><li><p>The role RPO plays in U.S. military operations</p></li><li><p>The current state of our adversaries&#8217; orbital warfare capabilities</p></li><li><p>How SBIR &#8594; STRATFI can be a springboard to building a scalable business</p></li><li><p>Navigating classified work without slowing commercial velocity</p></li><li><p>Where LEO, GEO, and cislunar actually fit in over the next five years</p></li><li><p>The power of software to conduct complex RPO missions with relatively cheap, simple hardware</p></li></ul><p>As always, please let us know what you think. And please reach out if you or anyone you know is building at the intersection of technology and national security.</p><p>You can listen to the podcast on <a href="https://open.spotify.com/episode/1ReoOpME4kPfDU14hvvkiW?si=QDsVNdmVQMmoOeiTv0Zw2g">Spotify</a>, <a href="https://youtu.be/WTpkW50AjQk">YouTube</a>, <a href="https://podcasts.apple.com/us/podcast/starfish-space-building-autonomous-satellite-servicing/id1807120572?i=1000749199706">Apple</a>, the Shield Capital <a href="https://shieldcap.com/episodes/starfish">website</a>, or right here on Substack.<br></p><p class="button-wrapper" data-attrs="{&quot;url&quot;:&quot;https://maggiegray.us/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe now&quot;,&quot;action&quot;:null,&quot;class&quot;:null}" data-component-name="ButtonCreateButton"><a class="button primary" href="https://maggiegray.us/subscribe?"><span>Subscribe now</span></a></p><div><hr></div><p><strong>Transcript</strong></p><p>Maggie  00:39<br>In this episode of the Mission Matters podcast, we sit down with Austin Link, the CEO and co-founder of Starfish Space. Starfish is building the future of rendezvous proximity operations, or RPO for short, for satellite servicing, beginning with space tugs for satellite life extension missions. Essentially, Starfish satellites are able to attach to other satellites and pull them into a higher orbit in order to extend their lifetime in space. RPO are the maneuvers and technologies that enable one spacecraft to safely approach, navigate around, inspect, dock with, or service another object in space while maintaining precise control and collision avoidance. I know Austin often describes this as two bullets coming together to very lightly kiss without actually touching each other. The same technology for life extension can also be used to clean up orbital debris, otherwise known as space junk, to ensure crowded orbits can be free of clutter from other satellite operators, as well as a whole host of maintenance and US government mission sets.</p><p>David  02:03<br>Historically, RPO missions, like life extension missions, have been prohibitively expensive for most use cases. Of course, before Starfish, the RPO missions would require large, expensive spacecraft outfitted with several complex sensors to conduct the operations. With Starfish, they&#8217;re revolutionizing the industry with their Software Defined Platform, which can conduct RPO missions with just one or two sensors and cameras at a tenth or even a hundredth of the price of your traditional RPO satellites.</p><p>Maggie  02:34<br>Since they were founded in 2019, Starfish has launched two technology demonstrator satellites, the Otter Pup One and Otter Pup Two, successfully deployed their software on an Impulse Space satellite, raised more than $50 million, and closed contracts with government organizations like NASA and Space Force, as well as with commercial companies including SES. The founders, Austin Link and Trevor Bennett, are both aerospace engineers who met while working together at Blue Origin.</p><p>David  03:03<br>In this conversation with Austin, we&#8217;ll cover everything from the role RPO plays in US military operations, the current state of our adversaries&#8217; orbital warfare capabilities, and, of course, how to navigate the United States government contracting process as a space hardware startup. Okay, Austin, it&#8217;s great to have you with us. Thanks so much for joining us on the Mission Matters podcast.</p><p>Austin  03:27<br>Good to be here. Thank you guys for bringing me on.</p><p>David  03:31<br>Yeah, I&#8217;m sure you&#8217;re a first-time, long-time with this podcast medium, but Maggie and I are just super excited to have you here, so we want to jump into it. In December, you know, as a little pre-Christmas gift&#8212;I don&#8217;t know, maybe to your investors, maybe to the space economy&#8212;you and Impulse came out with a pretty large announcement about your mission, Remora. Can you tell us a little bit about it? I mean, how did it come together, the partnership with Impulse Space? It&#8217;s really cool. And then what are the implications for Starfish as a company? And then, I don&#8217;t know, maybe wax poetically about the broader space economy.</p><p>Austin  04:11<br>So we did&#8212;we announced in December our Remora mission. And on our Remora mission, at Starfish, we put a camera and some software on an Impulse Space satellite, and they allowed us to take control of their satellite and fly it towards another Impulse satellite. And we&#8217;re not just flying it from the ground&#8212;we flew it autonomously onboard and used our cameras to take pictures of the other satellite. And we got&#8212;we got 1,250 meters away, which is close proximity operations when you&#8217;re in space. We got some awesome pictures of them, and we got a chance to validate a bunch of our technology and gather a bunch of data to anchor simulations going forward. And this was a big mission for us for a few reasons. Number one, this mission touches on the core thesis of our company, which is we can use software to make it easier to do rendezvous and proximity operations among satellites. And making it easier to do rendezvous and proximity operations is what ultimately allows us to build our Otter satellite that does the life extension and satellite disposal at a price point that commercially works. And it&#8217;s what allows us to show up to Impulse Space less than a year before we&#8217;re going to launch and drop some software on them, and drop a little bit of hardware from TRL 9 on them, and get to space and have it work and do a proximity operations mission. And so, A, it&#8217;s just awesome to announce doing anything in space. That&#8217;s always super fun. B, it really validated a couple of our core theses on, &#8220;Hey look, we can do proximity operations easier than it&#8217;s ever been done in the past.&#8221; And then the last thing I would say&#8212;it was an awesome chance for our team to showcase their capabilities, and for the Impulse team to showcase their capabilities. They were really a pleasure to work with, and they&#8217;re a super impressive team.</p><p>Maggie  06:30<br>Yeah, so it sounds like with this mission, you guys have really demonstrated that you actually can, you know, get two satellites relatively close to each other and take a look at each other, you know, maybe do some servicing. I want to turn to what this demonstrated technology can actually be used for. And maybe the first topic on that is the US government use case. You know, I think previously, it was relatively taboo for the US government to talk much about their space operations. However, I know that&#8217;s changed in the past two years, where concepts like orbital warfare, Golden Dome, space control are now actually being discussed publicly by top military leadership. So how does a capability like what you demonstrated with this most recent mission relate to some of these military mission sets?</p><p>Austin  07:22<br>Yeah, sometimes, in trying to describe our company, I say we build satellites that grab and move other satellites. And that always raises the question, &#8220;Who the heck wants that? What&#8217;s that useful for?&#8221; Sure, it&#8217;s cool, but how, as a business, do you provide value and through that get money so that you can continue to exist as a business? And for us, with our Otter, there&#8217;s really two core commercial missions that we focus on. One of those is the life extension of geostationary satellites. You run out of propellant, we can grab on, hold the satellite in that slot still. And the other one is satellite disposal in constellation. So this satellite has died, it&#8217;s occupying a slot, it&#8217;s threatening other assets&#8212;just get it out of there so that a replacement can be put in and you can continue to operate your critical space infrastructure. Both of those apply to the government the same way that they apply to commercial satellite operators. There are many organizations inside the US and allied governments that operate satellites, and in many ways, they look just like our commercial customers do too. There is also, as you touched on, a variety of mission sets for the US government that are not ones that folks are as interested in commercially, although sometimes they are interested in them commercially. They range from protecting satellites on orbit from&#8212;really, usually Russian or Chinese satellites that are nearby. They range from potentially interfering with an enemy asset that is doing services for bad things. They can range to a little bit more complex servicing missions on orbit. So the US government is sometimes a little at the forefront of refueling, sometimes a little at the forefront of on-orbit repairs or assembly or upgrades in a way that commercial companies don&#8217;t necessarily have the risk appetite to go bite off at first pass. All of those are areas that the US government expresses interest to us as we develop rendezvous, proximity operations, and docking technologies&#8212;we can operate satellites close up to and touch other satellites. I think there&#8217;s two challenges for us as a business as we grow into those opportunities. And one of those is to figure out what is going to be fundamentally useful over the long term, because we&#8217;re not building a business to go try to grab whatever the shiny contract at the moment is. We&#8217;re trying to build a business that fundamentally provides real value to our customers, and that&#8217;s true for the government in the same way it is for the commercial side. And then the other factor that we have to decide as we bite off new opportunities is we have an efficient team, and we need to focus on the things that are going to give us the most bang for our buck right now. And so that means that the Otter is always our core focus at the moment, as we build Otters, as we fly Otters, as we grow that line of business. And the next wave of opportunities to take advantage of our technology, we have to tackle bit by bit as they come, as the right ones come for Starfish, and as we can jump and provide a lot of value to our customers for relatively little effort on our side.</p><p>Maggie  10:53<br>Yes, you mentioned some of our adversaries&#8217; actions in space right now&#8212;China, Russia. So I wanted to ask, what is the current state of our adversaries&#8217; capabilities as it relates to RPO, orbital warfare? You know, I know there was just an announcement late last year about China demonstrating an on-orbit refueling mission. So how are you seeing our adversaries&#8217; capabilities, and what role does Starfish and other startups play in maintaining US dominance in the space domain?</p><p>Austin  11:25<br>Yeah, so I think there&#8217;s not a lot of broad awareness about what goes on with rendezvous, proximity operations, and docking in space, and what can make space a contested domain. And I understand why there&#8217;s not always that awareness, because, on the other hand, there&#8217;s a lot of incredible things that happen in space. And not to say that some of what&#8217;s going on isn&#8217;t incredible, but there&#8217;s a lot of excitement, and there&#8217;s a unique kind of positivity and optimism that often comes with space missions. And sometimes you don&#8217;t want to think about, &#8220;Oh, this could be a contested domain of warfare also.&#8221; But we go talk with government customers and actually commercial customers also, and they&#8217;ll talk about, &#8220;Yeah, there is 10 to 20 kilometers away from us some Russian satellite or some Chinese satellite, and it has no reason to be there except to be poking around at us and trying to figure out and potentially interfere with what we&#8217;re doing.&#8221; And these satellites from both commercial and government folks are providing valuable services, and if they went out at the wrong time, that would be a really critical challenge for humans here on Earth. And so they ask us things like, &#8220;Hey, could you guys use your proximity operations to help protect our satellite on orbit?&#8221; And, you know, that&#8217;s something that our technology can lead to, and it&#8217;s a real thing that you have to think about, because Russia and China both have proximity operations capabilities, and they have both demonstrated them on orbit. There are multiple Chinese satellites that have docked in geostationary orbit, and there&#8217;s some speculation that there is refueling being done as part of it. There are Russian assets that have docked and have gotten close to US assets, and I believe even fired little projectiles at US assets. And those capabilities mean that if you have a US satellite that is relaying communications back and forth to Taiwan at a critical moment, and somebody&#8217;s threatening to disable that, that has a huge impact on the safety and well-being of people here on Earth. And that&#8217;s something that our technology can help and support. And it&#8217;s not that we are the only ones who are capable of doing proximity operations and docking for the US. The US has those capabilities too, but the US has them in a way that&#8217;s really expensive. And if&#8212;I think we see this in a variety of frontiers of conflict right now&#8212;if the US is bringing really expensive capabilities to the theater and adversaries are bringing really affordable capabilities, then over time, the US is losing the economic battle that comes with conflict. And so I think that is where Starfish Space can make a positive impact, the same way that we can make a positive impact on our purely commercial missions by providing more value from the services that we provide than what it takes for us to provide those services.</p><p>David  14:43<br>Well, I gotta say, this whole conversation has made me exceptionally nervous, because it wasn&#8217;t that long ago that what we&#8217;re talking about is just totally not taboo&#8212;Maggie, like verboten, go to jail, like talking about these elements of orbital warfare. So I&#8217;m stretching out some of the highest clearances I ever enjoyed in the Department. But it&#8217;s good. I mean, we&#8217;re seeing this push for these exquisite missions that don&#8217;t need to also cost an arm and a leg, right? And I think taking a different, a fresh approach, maybe some might say a first principles approach to doing these various missions is like, right in the wheelhouse. So, I mean, Austin, maybe just talk a little bit to us about the construct of Starfish, right, how your RPO technology serves a lot of different mission applications. And then more so, how do you articulate that to the variety of stakeholders? Because it&#8217;s different organizations in the military and the intelligence community who would be interested in life extension versus those that are in orbital debris. But for you as a company building Otter, it&#8217;s like, it&#8217;s just Otter, like, you know, you don&#8217;t need a special widget, you just use it for different purposes. Yeah.</p><p>Austin  16:08<br>I mean, it&#8217;s funny. That&#8217;s always a tricky challenge, especially for technical founders, but I think for everybody in pitching everything that they work on, you get so involved in the details that you need to do to make it work that that&#8217;s what you end up talking about. And in reality, when we&#8217;re out there and we&#8217;re selling to customers&#8212;and for people&#8217;s reference, we have Otters that we&#8217;ve announced, that we&#8217;ve sold their services to the US Space Force, to NASA, to SES commercial company. We&#8217;re building all of those now. They&#8217;re all getting set to launch over the next year here. And when you go out to sell the services of an Otter, a lot of times, the people that you&#8217;re selling to are a bunch of aerospace engineering nerds like yourself. So they&#8217;re excited to go and talk about proximity operations, because they think it&#8217;s fun, but they&#8217;re also good at their jobs, and so they&#8217;re ultimately going to make the decision based off of, do they get value out of signing a contract for our services? And on the commercial side, that actually often turns out to be a really straightforward thing to go and talk to people about, especially if they&#8217;re a public company. Then the knowledge is kind of out there, and you can go and say, &#8220;Hey, you&#8217;ve got this satellite or this constellation, you make X amount of money per month on that satellite. We can add five years to that satellite. We&#8217;ll charge you Y amount of money per month. X is bigger than Y, and so it is valuable for you to use our services.&#8221; And on a commercial side, that&#8217;s a pretty straightforward thing. When you&#8217;re talking to a commercial company, and then you go and talk to the US Space Force, and we can say, &#8220;Hey, you can extend the life of this satellite. We&#8217;ll charge you Y money. We&#8217;re curious how much money is it worth to you a month to have this satellite?&#8221; And people will look at you like, &#8220;What the heck are you talking about? Why do you talk about this in terms of dollars?&#8221; And so it can be a little bit of a trickier proposition to understand the language of the US Space Force there, and what is the value that they see from life extension. But we try to talk about it in the same way. We try to talk about, you know, the satellite is gathering critical data. The satellite is a key piece of resolving emergencies. And sometimes you can talk about dollars, where you can say, &#8220;Hey, if you were to procure a new satellite for these services, it&#8217;s going to be like a $2 billion satellite, so you might as well get five more years for a whole lot less money than that.&#8221; NASA may be the trickiest of the entities that we&#8217;ve needed to talk to, because the ultimate value that the US Space Force wants to provide is pretty clear, even if it isn&#8217;t dollars. Ultimately, they want to protect the US as a nation and our allies and our interests. With NASA, there&#8217;s some folks there that are going, &#8220;We want to explore the edges of outer space.&#8221; There&#8217;s some folks that are saying, &#8220;We want to do as much science as possible.&#8221; There are some folks who are saying, &#8220;We want to build a technical base.&#8221; There are some folks who are saying, &#8220;We just want to create American jobs.&#8221; All of those are good and valid end goals, but to navigate your way through NASA, you kind of have to understand each group and what their particular interests are going to be. That&#8217;s an experience that you can navigate and you can learn, but you also have to be repeating it throughout. Like, &#8220;Hey, this is what we all agreed that our goals were going to be at the beginning, and those are the goals that we&#8217;re going to pursue.&#8221;</p><p>Maggie  19:43<br>So Austin, it sounds like you guys are working with a swath of customers across, you know, military agencies, civilian agencies, as well as completely commercial non-government agencies. I know a lot of the terrestrial tech companies we talk with discuss, you know, some of the specific standards and compliance certifications that they need to get through to work with US government customers, to work on classified mission sets. So I wanted to see if you could talk through, you know, what were maybe some of the bigger surprises or challenges or differences that you&#8217;ve had to work through in order to work with some of these government customers on classified mission sets.</p><p>Austin  20:26<br>Yeah, there are, both for classified reasons and unclassified reasons, a variety of licenses or approvals or certificates that you need to get to work with the US government in different stages. Starfish Space does have a facility clearance that we got recently, and it does allow us to work on classified missions or work with classified data. That does unlock a variety of additional mission sets and a variety of additional customer organizations for us. It&#8217;s kind of funny to all go through as an organization and have to figure out how to get that. On the back end, I&#8217;ve had clearances in previous lives, both at Blue Origin and Lockheed Martin. Both places, I kind of had no idea how it came together that the company could work with me to get those. You&#8217;re just sitting there. Then somebody said, &#8220;Hey, you should get a clearance.&#8221; You go, &#8220;Okay, sounds good. I&#8217;ll fill out the paperwork.&#8221; It is tricky to get a facility clearance, and you have to work with folks. I think that the US government is putting a lot of effort into figuring out how to work with companies like ours. I think they see the value that companies like Starfish Space or Impulse Space or Varda or K2 Space, or a lot of other great space startups that are out there can provide. I think the trick is actually not just getting the FCL, not just getting the clearances for the individuals, but also being careful about how and when you take on classified work. There is a lot of overhead to doing work in a classified manner. And there will be a lot of folks that are tempted to just say, &#8220;Hey, everything&#8217;s classified. Let&#8217;s just be careful and safe here and make sure that everything&#8217;s classified.&#8221; And you want to be careful, and you really want to protect the sensitive information that allows our nation to defend itself. But you also have to be careful about how much work you&#8217;re trying to do in a classified lab, because if you develop some awesome piece of your GNC algorithms that&#8217;s really going to make your satellites do proximity operations a lot better, and you develop it in a classified lab to get all of the code and the simulation results and everything back into the unclassified world and apply it to other missions, it&#8217;s a whole lot more complicated than it otherwise would be if you&#8217;d started off in the unclassified world. And so there&#8217;s both the you have to get the paperwork and the approvals, and there&#8217;s also the you have to figure out how to operate with it in a way that is efficient for your business and allows your business to continue to do the things that you want to do. Because at the end of the day, I don&#8217;t think classified world, I don&#8217;t think working with the government world is really that fundamentally different from any sort of business. You&#8217;re out there to try to provide value to your customers. You have to build a product that you can actually build, and then it has to deliver that product, or the services of the product, to your customers in a way that is worthwhile for them. And as painful as it can sometimes be to work with the government, oftentimes, when we&#8217;re talking about, at least for us, the kinds of sizes of the contracts that we&#8217;re working on, the pain of working with the government is a relatively small pain in comparison to the total effort that it takes us to fulfill the mission. Otherwise, probably the biggest challenge is not figuring out how to do it or not doing the paperwork. I think the biggest challenge is that it&#8217;s just going to take a really long time, because the government isn&#8217;t used to operating at the speed of startups. They&#8217;re trying, man, they&#8217;re working harder, they&#8217;re getting better at it. But there&#8217;s still sometimes where you&#8217;re like, &#8220;Really, that took us six months to pull that off.&#8221; There&#8217;s a whole lot that can happen in six months at a startup.</p><p>David  24:17<br>Yeah, so, I mean, from a timing and startups and trying to keep the pace of change, you know, ultimately you need to generate revenue, and it seems like a lot of the revenue programs for the military, at least for an early-stage startup, is around some of these non-dilutive R&amp;D type opportunities. So talking about SBIR and STRATFI, can you maybe just like, walk us through a little bit like that approach that you took? How did you find the right stakeholders, and how did you turn that SBIR into a STRATFI?</p><p>Austin  24:56<br>Yeah, SBIR is Small Business Innovative Research contracts are, I think, a really neat thing that the US government does. And a variety of agencies do this&#8212;the Department of War, NASA, Department of Energy, the National Science Foundation, they all give out Small Business Innovative Research contracts, although all in a little bit different ways. And these contracts are often broken up into a Phase One and a Phase Two. And a Phase One is on the order of about $100,000, and a Phase Two is on the order of about a million dollars. And when you are two people working from a public library, the idea of getting $100,000 to work on your ideas is like an incredible and overwhelming amount of money. And so that was from the very earliest stages for Trevor and I&#8212;one of the early things we looked at was Small Business Innovative Research contracts. And as we were looking into it, we learned there&#8217;s kind of a couple of philosophies on how you can use these contracts. You can use these contracts to try to make money and sustain your business. And you can build a company where you&#8217;re winning several SBIRs a year, and you have a dozen folks working on these SBIRs, and you can operate for several years like that. Or you can really try to use SBIRs as a springboard, and you can try to use these as a way to become the business that ultimately you&#8217;re trying to achieve. And that is actually what the US government tends to want. That&#8217;s what the Air Force or the Space Force wants. That&#8217;s what NASA wants. They want to use these innovative research contracts to develop technology and teams and business relationships that eventually allows these companies to go fulfill needs for the US government and for the commercial world at a large scale. And so we went into these SBIRs going, &#8220;Okay, let&#8217;s go into Phase One, let&#8217;s go turn it into a Phase Two, and let&#8217;s ultimately use that as a way to sell our Otter satellites.&#8221; And that played out almost to a T in multiple avenues for us. So our very first SBIR was a $50,000 contract to study some of our proximity operations. Then we turned that, through Space Force Pitch Day, into a, I think it&#8217;s like a one and a half million dollar contract at the time. That was real and substantial money for us. And we turned that eventually into a TACFI, a Tactical Financing contract, which is a couple million dollars. And through another set of SBIRs, eventually won a STRATFI, which in our case is $37.5 million coming from the US government to do an Otter mission for the Space Force. And now we aren&#8217;t bidding on SBIRs for the Otter or for our key technologies. That&#8217;s not what our business is about now, but it really was the springboard to the future. And then it turned out people were really excited that we were trying to use SBIRs in that format. You would go and talk to whoever in the government you thought might buy proximity operations technology or might buy Otters. And they would say, &#8220;You know, this is pretty interesting. I&#8217;m not going to go give you a $40 million contract off the bat here, but I&#8217;d like to work with you a little bit and see what you&#8217;re capable of.&#8221; And you go, &#8220;Okay, well, you know, that&#8217;s awesome. We actually know about this SBIR framework where we could go do a Phase One, or we could go do a Phase Two, if you just write us, you know, a letter of support, and we&#8217;ll go through the proposal application process.&#8221; And it doesn&#8217;t always work. These are competitive proposals, but we kind of lead by talking to the customers, and you take it back, and the SBIR process is just a vehicle that allows you to start working with them more closely.</p><p>David  29:07<br>That&#8217;s great. And I think, yes, you are using the SBIR program the best way possible. And I wish other companies took that approach and lead, but we don&#8217;t need to get into that topic here, but maybe we can just drill in a little bit more. Did you feel like you were educating the customer about what you could do with the Otter and starting to unlock RPO, or did they already have some sort of a knowledge base around it, and they were like, &#8220;Oh my God, thank you. I found you. Like, let&#8217;s go.&#8221; Like, which way was it? Was it a push or a pull?</p><p>Austin  29:48<br>I actually think it was a little bit more us educating, and maybe and definitely not us educating the Space Force on what they would get value from. They&#8217;re the ones that can say, &#8220;Oh yeah, life extension would be valuable,&#8221; or &#8220;Oh yeah, proximity operations to do this mission would be valuable for us.&#8221; But what we could educate on was what was possible and what was possible in different ways. We&#8217;re not the first ones to go to the US Space Force and say, &#8220;Hey, how about we do a little bit of life extension?&#8221; Many folks have gone and done that before us, but we were the first ones to show up and say, &#8220;You know, we could do life extension for this price point.&#8221; And the first time we said that to a general, we got some funny looks like, &#8220;What are you talking about? That&#8217;s totally out of family with all the price points I&#8217;ve been told in the past.&#8221;</p><p>David  30:41<br>And so they call you a heretic at all? You know, do they say, &#8220;I don&#8217;t&#8212;&#8221; Voodoo. Maggie called&#8212;</p><p>Austin  30:47<br>Called a heretic, fortunately. But I think that people probably appropriately look at ambitious technology startups and go, &#8220;You guys are crazy, like you&#8217;re just out here saying stuff. You&#8217;re not going to be able to pull that off.&#8221; And so you have to fight your way through what is, I think, an appropriate level of skepticism. And to some degree, you can go do that and present to them like, &#8220;No, here&#8217;s the breakdown. Here&#8217;s why we as a business would actually like make money by providing the services to you at the price point we talked about.&#8221;</p><p>David  31:20<br>Last question on, like, sort of this general topic. I mean, I&#8217;d love to hear, like, how many conversations did it require from you and your team, and probably a very small team, in those early days, to get that Phase One into a Phase Two, that Phase Two, or series of Phase Twos, into a TACFI, and then eventually a STRATFI? And then did you arm yourself with like other third-party consultants, whether they be supporting you through proposal development or lobbying, even?</p><p>Austin  31:53<br>The one that is maybe the easiest to track is going from the Phase One to the Phase Two. In early stages, we had very clear and dedicated pipelines, because that was before we really knew many folks in the US government. Sometimes now we can short-circuit the process a little bit for something like that. We can go, &#8220;All right, here&#8217;s the three folks that we know that are most likely to support it. Let&#8217;s just go and talk right to them.&#8221; But when we&#8217;re trying to take our first Phase One to a Phase Two, I think we had 30 to 40 dedicated conversations with different folks that we thought might potentially be able to support the Phase Two in the US government. And we had those conversations through all sorts of forums. It would be in person at conferences. It would be through warm connections over Zoom calls. It would be through accelerator or startup mixers. It would be sometimes people that just randomly showed up to one of our SBIR deliverables that we were putting together because they&#8217;d heard about us. But I think it was ultimately like 30 to 40 conversations. And then, if you take a look at like, &#8220;Well, hey, what does it take to get from the very earliest stages to a STRATFI?&#8221; It&#8217;s hundreds and hundreds of conversations between Starfish Space and folks in the US Space Force. You want to be careful. You want to be efficient with those conversations. You&#8217;re not just talking with the same person over and over 100 times. Like they have things to do too, but you want to cast a wide net and that allows you to eventually find, like, &#8220;Here&#8217;s the people that are&#8212;they&#8217;re most interested and can most benefit from what we&#8217;re building.&#8221; We did and have and continue to, in various ways, work with some third-party organizations along the way. In the very earliest stages, we had no idea how SBIRs worked. I think we lost our first 11 SBIR proposals, and so we started working with some consultants who were really knowledgeable about the SBIR process, and they show up, and there&#8217;s some things that they tell you from day one that are like, &#8220;Oh, you&#8217;re not actually trying to put the most advanced technology descriptions in there, because it&#8217;s not scientists that are reviewing the SBIRs. You need to talk about how your business is viable and how what you&#8217;re doing would be useful, and that&#8217;s what the Air Force likes to go and evaluate SBIRs on.&#8221; And so we got some of the tips. We figured it out. We started learning how to win SBIRs. And eventually you get to a point as a business where you go, &#8220;Great. We figured it out, and we don&#8217;t even need SBIRs as much anymore.&#8221; And so these folks that did a great job for us in a certain stage, that particular skill set isn&#8217;t as useful for the next stage. So we go, &#8220;Thanks for all your help. We&#8217;re going to refer other companies to you, and you know, we&#8217;re going to move on to the next stage of our development as a company.&#8221; And so that&#8217;s all sort of what drives us to go, &#8220;Hey, we don&#8217;t hire and bring some SBIR expert in-house. We hire and bring in really, really capable people who are great problem solvers, generally, in-house, and we&#8217;ll bring in a little bit of third-party support along the way.&#8221; And we did that in the SBIR stage, and we did that in the STRATFI stage, and we do that now with some of the government affairs or some of the policy work that we&#8217;re doing. All of those are supplemental. At the end of the day, only you and your team can tell the story the way that you and your team can. So you still have to get in there and get your hands dirty. You don&#8217;t just hand it off, but as advisors, the third parties, I think, can be useful services at times. David, Maggie, what do you guys see other companies do? What do you recommend when you&#8217;re talking to some super early founder that is just getting going and saying, &#8220;I think I might want some of these?&#8221;</p><p>David  35:49<br>I mean, I think what we&#8217;ve seen be successful is the founders, especially in those early days, need to be at the vanguard of those conversations and finding their champion. And what I see from the military folks is they really do like talking to founders, right? The people that are going to like build the thing that&#8217;s actually kind of novel to them. But as far as, you know, you talked about, &#8220;I don&#8217;t understand all the elements of an SBIR&#8221;&#8212;to me, I would advise the startup founder not to go figure it out for themselves. Like that is a lot of effort, and likely wasted effort, and you can pay for those types of services. The key is, can you find a good, trusted source to help you? And that&#8217;s where leaning on your investors, who are deeply experienced in this domain, becomes quite clear. And why, you know, as a startup, wanting to engage in the defense ecosystem, you should, you know, pick your investors and your advisors wisely. So, I mean, the way you guys went about it, I think was absolutely perfect, and I think the rewards speak for themselves.</p><p>Maggie  37:01<br>I mean, Austin, another question I had&#8212;unlike a lot of the companies that raise venture money, where they&#8217;re able to build an MVP in a month, or maybe even a hackathon over a weekend, you guys are building a really complex piece of technology that has taken years to build and prototype and launch and test. So I&#8217;m curious, you know, how do you build a go-to-market sales engine while you are still proving out a piece of technology?</p><p>Austin  37:34<br>I think probably fundamentally, the biggest challenge for our business is that we have ambitious goals, and it&#8217;s really challenging to build a bunch of satellites that extend and protect and upgrade and improve infrastructure in space. We can&#8217;t just go out and be like, &#8220;Look at our revenue. It&#8217;s going up 30% month over month, and we sell, you know, $10 at a time subscriptions, and it&#8217;s a nice hockey stick graph.&#8221; You have to get folks of all sorts to buy in on the risk along the way. And that&#8217;s customers need to buy in and take some of the risk with you. It&#8217;s investors need to buy in and take some of that risk. It&#8217;s employees, it&#8217;s suppliers. Everybody that you work with is betting on you a little bit in one way or another. And one of the things that you have to do is construct your development plan as a business in a way that allows people to see the risk reducing, allows people to see progress all along the way, and that allows everybody else to buy in a little bit more. And so you might sit there at the beginning and say, &#8220;Okay, this is going to cost us $100 million to design and get to flying the first satellite.&#8221; But you can&#8217;t go out and just get $100 million from your customers, from your investors, when you&#8217;re two guys that are sitting in a library. And even if you did, you&#8217;re not going to know what are the right things for you to do. You can&#8217;t just be like, &#8220;Well, I mean, I got $100 million and turn it into a satellite.&#8221; You always have to have the steps and the milestones along the way. And some of that is your key technology development, and some of that is pieces of your system architecture, and some of that is demonstration missions. And those are all on the technology side. And some of those are early contracts and conversations with customers. Phase One SBIRs can fit the bill. Letters of interest, or we did something that we call development partnerships with commercial customers. Those can really fit the bill. Early rounds of investment, pre-seed rounds, seed rounds, Series A rounds, those all help do the risk reduction. Hiring great early employees. Sometimes in the proposal process, you go, like, &#8220;Okay, well, we just have to make these, we have to send these couple of people&#8217;s resumes in, because that&#8217;s going to be a key part of why people want to work with us, as they go, &#8216;Oh, look at this awesome team that you&#8217;re building.&#8217;&#8221; You have to have the little milestones, and you have to buy, get people to buy in on a little bit of risk, and that&#8217;s true in basically everything that we do. And so go-to-market is a part of that. The customers that we work with today are generally customers that we&#8217;ve been on the journey with for years at this point, and they were the first ones on the commercial side to sign LOIs for us. They were first ones to just pick up the phone when we said, &#8220;Hey, we&#8217;re a couple of crazy folks in the library, and we just want to pick your brain and see if this would be valuable at all.&#8221; And then they were the first ones to dive in on the development partnerships and the first ones to sign up on contracts. And the same way on the government side, you start off with, like, &#8220;Who&#8217;s willing to talk with you when you&#8217;re going through the Hyperspace Challenge accelerator?&#8221; And then who&#8217;s maybe willing to sign a letter, and who do you talk with on your very first Phase One SBIRs? And there&#8217;s a lot of people that start working with you there. And if you buy the risk off along the way, they&#8217;re the ones that eventually&#8212;maybe they aren&#8217;t signing the big contract or the big contracts, but they&#8217;re in the meeting in the hallways with those people saying, &#8220;You know, you should really take a look at this company. They&#8217;ve been doing impressive work.&#8221;</p><p>Maggie  41:27<br>Yeah, Austin, since you guys started the company in 2019, you now have launched what, two satellites. You just completed this Remora mission successfully. Can you tell us about some of the lessons learned from each of those experiments testing your technology actually in space?</p><p>Austin  41:46<br>It&#8217;s funny, you set out to test the key pieces of your technology, and you do learn things about the key pieces of your technology. You go do some&#8212;you go fly some missions. You&#8217;re like, &#8220;You know what? We actually have some star tracker outages every once in a while, and so we have to update our filters so they&#8217;re not expecting measurements on a regular basis. And this is what our GPS error profile actually looks like, and this is the number of dead pixels we&#8217;re seeing, or the spurious bright flashes that we see in the background that we need to filter out in our images.&#8221; And so there are some technical things that you really learn about your key technology, but there are a lot of other things that you learn about along the way too. You learn about how to operate a satellite, how to get the data down in ways that people can look at it, how to send your commands up in ways that are efficient, and you can move through your testing operations quickly. You learn how to manage a satellite program, even when you&#8217;re working with vendors. And we work heavily with vendors to build the components. Just getting the vendors to deliver on time and to talk to each other in a way that everything interfaces correctly, turns out to be a huge amount of effort, and something that we have to pay a ton of attention to as we build the Otters. You learn a little bit about your team and what it takes to be ready for the moments of stress and challenge you have to resolve and what it takes to be ready to do that awesome.</p><p>David  43:17<br>Well, Austin, you&#8217;ve been, I don&#8217;t know, super generous with your time, and I know you&#8217;d probably rather be in the lab building or closing customers, but before we let you go, I think we just kind of love to hear a little bit of you and how you think about the future of space in the next, I don&#8217;t know, five to 10 years. Maybe 10 years is too far along, if we really think about what&#8217;s happened in the preceding 10 years, but over the next five years. And I know you&#8217;re a visionary, you wouldn&#8217;t have, like, come up with the name, you know, Starfish in the first place, and all the fun names that you have for all of the componentry, but maybe one area that I would be really curious on your take within this five-year journey is how the various orbits play into each other.</p><p>Austin  44:04<br>It&#8217;s easy in the space industry to dream really big and then to not fulfill and follow through on it. And more often than not, when you ask, &#8220;What does the space industry look like in five years?&#8221; it kind of looks a lot like today. And so I think the areas where it&#8217;s changing are the ones that are most interesting to call out. And areas where it&#8217;s changing is not necessarily announcements of, &#8220;Oh man, we&#8217;re going to land humans on the moon in four years.&#8221; We announced the same thing, what, six years ago, and didn&#8217;t really make that much progress along. And I don&#8217;t think we&#8217;re gonna have a bunch of people wandering around on the moon in four years, but the areas where you can already start to see the change&#8212;the increasingly rapid launch and the landing of rockets, and obviously SpaceX is absolutely at the forefront there. But Blue Origin also recently landed a rocket that took things to orbit, and Stoke Space is working hard on it, and Rocket Lab is working hard on it, and Starship with SpaceX is working on it. And you can already see that progress happening. I think that as more folks enter the launch market, that&#8217;s just better and better for people that want to send things into space and get value out of it. You saw a trend for a long time of satellites getting smaller, and now you see a trend of satellites getting bigger again, because people go, &#8220;Oh crap, I want to get a bunch of capability into the satellite. I want to have all the data throughput. I want to have the exquisite camera capabilities or compute capabilities.&#8221; And all your satellites went down to 3U CubeSats, and now they&#8217;re all going back to 1,000-kilogram satellites, and then perhaps even bigger. Some folks are really on the leading edge of that, taking advantage of it. I think K2 Space is an awesome example. And you can see other folks like us, Astroscale is a great company that are going, &#8220;Hey, it&#8217;s not just a world of CubeSats and really low Earth orbit. There&#8217;s a lot of opportunities in geostationary orbit in particular.&#8221; And so maybe to touch on your particular question, David, I feel like there are four real orbits that people talk about, at least from a commercial perspective, as potentially having value. There&#8217;s low Earth orbit. There is MEO, mid-Earth orbit. There is GEO, geostationary Earth orbit. And then there&#8217;s cislunar orbit, which is around the moon basically. And in low Earth orbit, I mean, the biggest thing that&#8217;s going on in the space industry right now is Starlink and internet service providers from low-Earth orbit satellite constellations. And Starlink is absolutely very much at the forefront. And what they&#8217;re doing is really incredible. And then you see folks like OneWeb and Amazon Kuiper that are following along. There is just tremendous and huge growth going on in LEO, and that&#8217;s going to accelerate, accelerate, accelerate. In mid-Earth orbit, the biggest thing going on there is the GPS constellation, and GPS is really critical for what people do in a variety of different ways. From a commercial side, being in mid-Earth orbit, frankly, comes with a lot of radiation challenges that sometimes force you into traditional production lines in the aerospace industry that are long and expensive and very difficult to work with. And so I don&#8217;t know that MEO is going to be a very popular place for folks doing new things. Maybe there&#8217;ll be some use cases, but boy, the radiation of Van Allen belts can kind of make it difficult. Then you have geostationary orbit, and as you&#8217;re building big, exquisite assets that cost millions or billions of dollars, sometimes putting them in a place where they&#8217;re over the same spot on Earth and you can trust for them to be there the entire time, turns out to be really valuable. And that was really valuable 50, 60 years ago when people first started launching GEO satellites. And I think it&#8217;s still going to continue to be really valuable going forward. And so there&#8217;s a lot of folks that are looking at geostationary orbit with a lot of interest, and it&#8217;s a key part of what I think we&#8217;re building our business around. And then there&#8217;s cislunar orbit, and people like to talk about cislunar orbit, but I don&#8217;t think we&#8217;re going to see a lot of exciting activity in cislunar orbit over the next five years. I really hope that we do someday, because, oh my gosh, how cool to see people on the moon or operating around the moon. I think that, you know, beyond Earth&#8217;s realm of orbit, let&#8217;s send things to Mars. Let&#8217;s send things to Venus. Let&#8217;s send things to the moon, to Saturn and Jupiter. That&#8217;s so cool. And that&#8217;s ultimately some of the absolute most interesting things going on in the space industry. Maybe unfortunately, if you&#8217;re trying to build a business around it, you have to take it with a little dose of realism over the five-year time horizon too. And you got to say, &#8220;All right, well, we&#8217;re not building our business to focus on servicing cislunar satellites right now. Let&#8217;s see some satellites there first.&#8221;</p><p>Maggie  48:59<br>Great. Well, Austin, thank you so much for taking the time and for coming on the Mission Matters podcast. We&#8217;re super excited to be investors in your business and excited to see where you all take it from here.</p><p>Austin  49:12<br>Hey, thank you guys always for having me. Always good to chat with you, and I&#8217;m sure I&#8217;ll see you somewhere soon.</p><p>David  49:18<br>Have a good one. Thanks, Austin.</p>]]></content:encoded></item><item><title><![CDATA[🎙️ Ep 15 - Geopolitical Briefing: Venezuela with LTG H.R. McMaster (ret.)]]></title><description><![CDATA[Listen now | This episode of the Mission Matters podcast features a conversation between Shield Capital Managing Partner Philip Bilden and Lt.]]></description><link>https://maggiegray.us/p/ep-15-geopolitical-briefing-venezuela</link><guid isPermaLink="false">https://maggiegray.us/p/ep-15-geopolitical-briefing-venezuela</guid><dc:creator><![CDATA[Maggie Gray]]></dc:creator><pubDate>Tue, 13 Jan 2026 16:45:34 GMT</pubDate><enclosure url="https://api.substack.com/feed/podcast/184405473/083721778608202d60efc82765a86646.mp3" length="0" type="audio/mpeg"/><content:encoded><![CDATA[<p>This episode of the Mission Matters podcast features a conversation between Shield Capital Managing Partner Philip Bilden and Lt. Gen. H.R. McMaster (ret.) on the recent U.S. operation in Venezuela. This episode covers everything from:</p><ul><li><p>The operational complexity of modern joint warfare and the role of commercial technology</p></li><li><p>Why Venezuela has become a key piece of U.S strategy in the Western Hemisphere</p></li><li><p>What the operation signals to China, Russia, and other adversaries about U.S. resolve and deterrence.</p></li><li><p>And more</p></li></ul><p>You can listen to the podcast on <a href="https://open.spotify.com/episode/5X1mFvwkYNtCs5fv8Dwyu2?si=pR_b9d1ASDy-lMCYLI-f6Q">Spotify</a>, <a href="https://podcasts.apple.com/us/podcast/geopolitical-briefing-venezuela-with-ltg-h-r-mcmaster-ret/id1807120572?i=1000744946210">Apple</a>, <a href="https://youtu.be/ZbY5_1Aw5bs">YouTube</a>, <a href="https://shieldcap.com/episodes/venezuela">the Shield Capital website</a>, or right here on Substack.</p><p>As always, please let us know your thoughts, and please let us know if you or anyone you know is building at the intersection of national security and commercial technology. Tune in next month for our next episode!</p><p class="button-wrapper" data-attrs="{&quot;url&quot;:&quot;https://maggiegray.us/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe now&quot;,&quot;action&quot;:null,&quot;class&quot;:null}" data-component-name="ButtonCreateButton"><a class="button primary" href="https://maggiegray.us/subscribe?"><span>Subscribe now</span></a></p><p><strong>Lisa 00:36</strong><br>Thank you for making the time to join this timely discussion of the recent U.S. military action in Venezuela. We&#8217;re honored to have with us today SHIELD&#8217;s senior advisor and the former National Security Advisor to the President of the United States, U.S. Army General H.R. McMaster. General McMaster has a distinguished four-decade career as a U.S. Army officer, national security expert, and presidential advisor. He served as the 25th U.S. National Security Advisor from 2017 to 2018, where he led the National Security Council and advised President Trump on U.S. national security strategy. During his 34-year Army career, following his commissioning from West Point, he held multiple senior command and leadership roles. General McMaster commanded combat operations, including Combined Joint Interagency Task Force operations in Afghanistan, the Third Armored Cavalry Regiment in Iraq, and the Second Armored Cavalry Regiment during Operation Desert Storm. He is the recipient of numerous service awards. I could go on and on, but they do include the Silver Star, two Bronze Stars, and a Purple Heart. Those are stories that we will get out of him at the next limited partner annual meeting. He holds a PhD in military history from the University of North Carolina at Chapel Hill and a Bachelor of Science from West Point. General McMaster is a prolific author and historian and currently a senior fellow at the Hoover Institution at Stanford. We&#8217;re grateful to have his esteemed counsel and support at SHIELD, where the mission matters. And now it&#8217;s my pleasure to introduce to you Phillip Bilden, SHIELD founder and managing partner, who will help moderate the discussion today.</p><p><strong>Philip 02:14</strong><br>Thank you very much, Lisa. I also echo your thanks to the SHIELD investors and friends of the firm, our advisors and partners who have helped us build the firm that we have, and certainly our esteemed senior advisor and friend, General H.R. McMaster. H.R., very good to see you. I know that you&#8217;re on the Pacific Coast and had to wake up early today. You&#8217;ve been very busy since this news broke on Saturday. Amidst your other duties, thank you so much for being here for the SHIELD webinar.</p><p><strong>LTG McMaster 02:43</strong><br>Hey, Phillip and Lisa, what a privilege it is to be part of the SHIELD team and to be with you today as well. It&#8217;s a fantastic firm with a mission that I&#8217;m so excited about, and the vision you all had years ago to put this together. I think it&#8217;s already having a huge impact on our national security. Any time for you guys.</p><p><strong>Philip 03:01</strong><br>Thank you. And you have been there from the very inception of the firm as one of our advisors, helping us think through issues like we are dealing with today, which we are going to be discussing: the relevance of the technologies that SHIELD has been supporting and the companies that bring these capabilities to the warfighters, to our intelligence community, etc. Maybe that is where we should start. H.R., I am actually two miles north of Mar-a-Lago, where a lot of this activity took place over the weekend. You are no stranger to Mar-a-Lago in your duties with the President when you started out in 2017 as his National Security Advisor. But operationally, what was executed in the zero-dark hours Saturday morning? How would you assess this, just on a simple scale, one to ten, in terms of the complexity and ultimately the execution, all the planning that went into that in terms of its operational performance? How would you assess that?</p><p><strong>LTG. McMaster 04:07</strong><br>Hey, Philip, I will tell you, this is a ten in terms of degree of difficulty, if we are going to liken it to Olympic diving or something. And it was a ten score, I think, from all the judges. I mean, you have to look at the broad scale of preparation and then implementation and execution on the objective, on the X, and then the exfiltration. It was done so well, so professionally, and in a very difficult environment. It is Venezuela, which is the beneficiary, the recipient, of all kinds of assistance from the Cuban military and Cuba, Cuban secret police essentially, and intelligence. Russia and China have tried to help them perfect their technologically enabled surveillance and police state, and then you also have Iran active there. So getting into that denied environment, collecting the intelligence necessary to drive the planning, and then conducting that planning with so many different agencies and the joint force, this makes me think of the history of other interventions in the hemisphere, going back to Grenada, which was a successful operation but one that revealed a lot of disjointedness in our joint operations. We are so many orders of magnitude better now than we were then.</p><p>Then you look at the professionalism of the forces, from the suppression of enemy air defenses to the cyber activities and electromagnetic activities to blind the enemy as you get into the objective area. Just the number of aircraft conducting these electronic warfare missions and the suppression of air defense assets, and then responding immediately to any enemy fire and immediately suppressing that fire, is extraordinary. To have just one aircraft hit and that aircraft still be able to continue the mission is unbelievable. Just deconflicting the airspace was probably pretty amazing. And then the 1/60th coming in, you know their motto, the Special Operations Aviation Regiment, time on target plus or minus 30 seconds. Well, they did that. The timing was impeccable.</p><p>I think what you are seeing also, Phil, from the perspective of SHIELD and SHIELD investors, is that we are going to find out more and more that this operation was enabled by a combination of very highly classified government capabilities and a whole range of newly available commercial capabilities, from satellite imagery to RF collection. I am thinking of Hawkeye 360, for example, and then the big data analytical capabilities, the ability to fuse multiple sources of intelligence, and the cyber tools that allowed us to shut down cameras and shut down communications. So a fantastic operation. Degree of difficulty, ten, and I think the score is a ten.</p><p><strong>Philip 07:16</strong><br>Absolutely. Thank you for that. So this was a multi-jurisdictional, multi-agency combined effort that required an enormous amount of integration. Can you walk us through a little bit of the operational phases? The President did not just wake up after two years and decide that he was going after Maduro. This was in the works for several months. There were CIA human assets on the ground, monitoring through traditional espionage, augmented with technical means, drones, ISR capabilities, in order to get to the point where the President could give the order, which I think was before Christmas, that gave an operational window to our friend General Dan &#8220;Razin&#8221; Caine to pull the trigger and say, this is the go time. Can you walk us through that sequence a bit, H.R., and maybe focus on some of the elements of these technologies and capabilities that are so important to our emerging national security that we are supporting, how they played into the intelligence collection and then ultimately the extraction?</p><p><strong>LTG. McMaster 08:26</strong><br>Well, I think what you saw our intelligence community and the military give the President were multiple options. Of course, President Trump knew Venezuela was a problem in 2017. He actually said at the time that we were developing military options for Venezuela, when we really were not doing that, but he said it, I think, to try to coerce Maduro during that period. Maduro has become more and more of a threat since then, and I can imagine conversations that occurred very early in the Trump administration, especially with Secretary Rubio coming in, who has tracked hemispheric issues in such detail with his Senate staff. He is the most knowledgeable person on activities and the security and economic situation in the hemisphere. I relied heavily on his staff, actually we did. And Trump won for the Venezuela policy we put into place in 2017, as well as the 180-degree shift in Cuba policy away from the Obama administration and back toward maximum pressure on the Cuban army. So very early in the Trump administration, I am sure the order went out, &#8220;Hey, give the President options.&#8221; You have to put an infrastructure in place to do that. As you mentioned, you have to get intelligence collection capabilities, human intelligence capabilities, and Title 50 intelligence agency operational capabilities in place. I am sure a lot of that was going on that we will probably never hear about, activities aimed at setting conditions for the raid to extricate Maduro, his wife, and others. Then a range of military capabilities were put together. They did not just come together; they had to organize and put a task force together. I think they probably built a mock-up of the palace somewhere and rehearsed this multiple times across operational distances. That preparation phase probably began soon after President Trump&#8217;s inauguration. Then you had the organization and rehearsal phase when Maduro was intransigent. There were some initial efforts, and this is a pattern with President Trump. He wants a deal, he always wants a deal, so he tries the deal first, and when he gets stiff-armed, he considers other options. The rehearsals and organization, I think, began around November and December. These great servicemen and women involved probably did not really have a Christmas. You saw the staging that was happening, some of it in Florida, some in Puerto Rico, and other places. The maritime task force played such an important role in this operation. The preparation phase went through December, and then you are teeing up the option for the President. &#8220;Mr. President, here is what we have planned.&#8221; President Trump likes to get into the details. Just like he will walk around a construction site for one of his hotels, he wants to talk to people with different perspectives and learn more about it. One thing about President Trump is that he is willing to take a risky decision. I cannot share details, but there were multiple times I brought him an operation involving saving U.S. citizens from a dangerous situation. I would lay out the risks, the potential for failure, and the costs associated with that, and he would ask, &#8220;Is it the right thing to do?&#8221; I would say yes, and he would say, &#8220;Okay, do it, General, do it.&#8221; Oftentimes I would call back to the agency and say the President approved it, and they would respond, &#8220;Really? That can&#8217;t be true. Nobody makes a decision that fast.&#8221; I think he probably made this decision based on the advice he was getting, including from his principal military advisor, Dan Caine, a former SHIELD guy for a brief period of time and an amazing officer. Then you had the execution, and now we are in the aftermath.</p><p><strong>Philip 12:38</strong><br>Yeah, absolutely. How did this extraordinary military operation maintain operational security, or OpSec? I mean, you&#8217;ve got a flotilla of maritime assets, the Gerald Ford, the Iwo Jima, several DDGs, and other support vessels. It was no surprise that there was a buildup. And then, of course, there was the campaign against the drug boats that have been taken out by aerial means and with kinetic force. So maintaining that operational surprise element is very, very challenging, particularly when you have numerous interagency participants. It&#8217;s extraordinary. There&#8217;s no leak, no nothing. And as we know, the extraction took place in the wee hours on a Saturday, right after the New Year&#8217;s holidays, with Delta Force entering and breaching a highly secure Venezuelan military base where Maduro and his wife happened to be at that time. How do you do that? And across&#8212;</p><p><strong>LTG. McMaster 13:39</strong><br>&#8212;considerable distances, where I&#8217;m sure there was significant aerial refueling going on. Aerial refueling of rotor-wing aircraft, which is not an easy task, and operating off the Iwo Jima, which is the amphib that was committed. I think, Phil, this is a really important question because of the ubiquity of surveillance capabilities, low Earth orbit capabilities, RF collection capabilities. Really, it&#8217;s almost as if everything you do is visible everywhere. So what you have to do very early in an operation is desensitize your adversary. Sadly, this would be concerning for us. This is what China is doing right now around Taiwan. How will you know when it&#8217;s a real Taiwan invasion, or is it just another one of these live-fire exercises?</p><p>So having the maritime task force and the aerial activity that we had in the Caribbean prior, that was part of the desensitization. Then deception plays a big role. Deception can be public statements that you make that might indicate that you&#8217;re not really looking at this, that you&#8217;re looking at other potential options, and so forth. And you remember the President actually announced the clandestine strike on a port facility before that. But all this, I think, was actually beneficial because it indicated that our approach to what we were going to do militarily was pretty narrowly circumscribed and would really only be in the coastal area or involving these narcotics trafficking boats.</p><p>So noise was high, deception, and then you have to go into the blind phase. This is where, I think, we have to really think in terms of future war. We have to be able to blind and deceive our enemies. The reason why the situation in Ukraine is so stagnant is because, with the capabilities that both sides have there, you can&#8217;t conduct a sustained offensive operation due to the transparency of the battlefield combined with what each side has in terms of long-range precision strike capabilities, FPV drones, and so forth.</p><p>Then you&#8217;re into the blind phase, and this is something we&#8217;ll probably learn about maybe 30 or 40 years from now in terms of exactly what happened. But I think the implication is that we have pretty considerable offensive cyber capabilities, similar to those that the IDF displayed in the attack against Iran, and we probably assisted with that as well. So the importance of warfare across all domains, the space assets, the electromagnetic assets, the aerospace, the maritime, and of course all the set conditions for what happened on land during that successful raid.</p><p><strong>Philip 16:35</strong><br>Thank you. We&#8217;ve talked a lot about unmanned systems and drones. We&#8217;ve seen this on display in Europe with Russia and Ukraine and these first-person viewing capabilities, which are pretty extraordinary. It&#8217;s like playing a video game, but the consequences are unfortunately very deadly. There was a fair bit of aerial surveillance with drones before the operation and after the operation. But interestingly, what had the impact was 150 fixed-wing and rotary-wing assets, some of which were from our service, the Army, that were in the fight. But they were assisted by the anti-aircraft assets that were supplied, I believe, by the Russians and the Chinese. Those were blinded and those were taken out. How do you think they did that? Because that was similar to what happened in Iran with Operation Midnight Hammer just months ago.</p><p><strong>LTG. McMaster 17:38</strong><br>We had command of the airspace. Yeah, absolutely. There were a range of capabilities that were employed. A lot has been mentioned about electromagnetic effects, and I am sure cyber was employed there as well against UAS capabilities. By the way, it is worth mentioning that there is an Iranian Shahed drone factory in Venezuela. That is part of the problem. Part of the problem with Venezuela that brought us there was how Venezuela had become a platform for our adversaries in the region. Also, with the advanced radar capabilities that we have on our manned aircraft, everything from Army Apache Longbows to F-35s and F-16s, oftentimes it is manned aircraft that are the best counter to these unmanned systems. Your ability to command and control with our aerial command and control platforms, based on the common visibility or picture of the airspace, is critical. I do not think really anybody else can do that but us right now, Philip, in terms of the visibility and the ability to bring multiple platforms to bear. The other time you saw this from a defensive perspective was in the highly successful defense of Israel against the massive ballistic missile and drone assault that Iran launched. It was almost completely defeated. That was tiered and layered air defense, involving, as you are mentioning, manned and unmanned systems, aerial and ground systems. I think that is the answer in the future. In warfare, there is always a countermeasure. So what you need is a range of capabilities. You can play the game of rock paper scissors, but you have to have all three to be able to seize and retain the initiative and to create conditions, like we created across multiple domains, to affect a highly complicated raid like that or any other military operation.</p><p><strong>Philip 19:38</strong><br>Well, this is exactly why SHIELD exists, to stay ahead of those technologies that our adversaries are able to develop on their own, reverse engineer, or steal through cyber means, through espionage, or what have you. This rock paper scissors dynamic, staying ahead of adversary capabilities, really drives so much of what we do from a mission standpoint, quite apart from the fact that it is also going to be a very important economic activity. This is where the future is going. Thank you for that operational breakdown. That is extremely helpful for setting the table for some of the geopolitical issues which you have spent most of your career working on, in and out of uniform, in the Oval Office advising the president, thinking about and trying to create a more stable environment for the United States, trying to avoid unnecessary escalation where that is prudent and feasible, but also creating strategic deterrence. That means trying to get the Chinese, the Russians, the Iranians, and the North Koreans not to do things that we do not want them to do. Let us start in the region, and maybe even go back to when you were national security advisor. What has really changed in Venezuela specifically, and then more broadly in Latin America, from 2017 and 2018 at the beginning of the first Trump administration to now? Where did it get to the point where the president felt compelled to actually go do an extraction of a sitting, if not illegitimate, head of state.</p><p><strong>LTG. McMaster 21:16</strong><br>Well, there&#8217;s a lot of continuity. I remember a conversation with President Trump, with a number of other people in the Oval Office, and he said, &#8220;General, General, why don&#8217;t we just bomb them?&#8221; And I was like, &#8220;Well, who do you have in mind?&#8221; He said, &#8220;The labs. The labs in Mexico.&#8221; People were shocked. I was with the President multiple times a day, every day, so this is the way he thinks. He thinks out loud, and he&#8217;s contrarian and disruptive. That can all be positive at times, but people were kind of freaked out about that. So I huddled with them outside the Oval Office and said, &#8220;Hey, you know what he&#8217;s saying? What he&#8217;s saying is that 100,000 Americans are dying of fentanyl poisoning every year, and what we&#8217;re doing now isn&#8217;t working. He wants options. He wants options.&#8221; The narcotics part of this was always on his mind. What has happened is that with the Cartel de la Solace, Venezuela has gotten deeply involved with the Mexican cartels and deeply involved with the Colombian cartels. He&#8217;s a source of strength and support for them in a couple of ways. First of all, it&#8217;s good to have a nation-state on your side because you can issue false documents, you can do all sorts of things to provide them with cover, and you can provide your aircraft for them, for example. In Colombia&#8217;s case, you can provide the trafficking route to evade our interdiction. He was doing all this, and guess what, he was getting a huge cut for it. That helped him because now he had more cash flow. That circumvents our sanctions and allows him to sustain the criminalized patronage network that keeps him in power, this organized crime network. The other thing that&#8217;s changed since 2017 is that he&#8217;s provided more and more support for what I would call far-left progressive dictatorships in the region, as well as far-left political parties, with his money. I don&#8217;t have the data for this, but I hear this from people in the region. I believe it was a huge source of funding for Petro, for de Silva in Brazil, and for AMLO, and for the far-left party in Mexico as well. He was a big part of this pink wave that also affected Peru and Chile, and it was anti-American. He was providing money to build an anti-American coalition such that the balance of power in the hemisphere had shifted dramatically against us since 2017, 2018, and 2020, because the Biden administration, I mean some of them were actually kind of sympathetic to these guys. I&#8217;m not a partisan person, but if you think about the shift in policy between the Obama administration and the Trump administration, President Biden went back to the Obama administration approach. Remember President Obama did the wave with Raul Castro at a baseball game. There was this idea that opening up to them and being more tolerant would work, when in fact these regimes remained very hostile to the United States and were providing platforms for China, Russia, and Iran. There&#8217;s also an economic dimension to this. Remember the announcement of the Peruvian port and mineral development, for example, and the deepening ties in Argentina. That could shift back now, because if you&#8217;re a country in the Western Hemisphere and you&#8217;re thinking, &#8220;Oh yeah, I&#8217;ll take that Chinese money, I&#8217;ll take that Chinese infrastructure,&#8221; you might be aware they&#8217;re going to use it for coercive purposes and trap you in debt, but now you also have to ask whether you&#8217;re going to lose all those investments when the U.S. decides enough is enough. I think the dynamic has shifted favorably in that regard. But to answer your question, there have been big increases in the Cartel de la Solace and their connections to other cartels, the use of Venezuela as a platform for Iran, China, and Russia in the region, and the degree to which Maduro took upstream support from China, Russia, and Iran and distributed downstream support to keep the Cuban army in power in Cuba and to get Daniel Ortega back into power in Nicaragua. Nobody knows this better than Rubio, and I think he saw Venezuela as the linchpin for anti-American influence and activities in the hemisphere. He&#8217;s right about that.</p><p><strong>Philip 25:58</strong><br>And he is dual hatted. He had your former hat, or he has your former hat, as NSA advisor, but also Secretary of State, and I think a few other titles have been thrown at him, because he is going to be running Venezuela soon as well. So you have answered a very important question. Why Venezuela? Why Maduro now, as opposed to, say, going after cartels in Mexico, closer to our border, if eliminating narco-terrorism and transnational cartels was the key objective? So let&#8217;s talk a little bit about what the key objectives were, and then what the strategic impact is going to be, both in the region but also in Asia and back in Europe.</p><p>So the original justification, and this is only a few days old, was that the elimination effort is a judicial effort for an indicted felon under U.S. law to be repatriated to the United States forcibly to face U.S. justice for criminal activity involving transportation and all types of things that narco-terrorists do. Then, as we go into the news cycle of the week, we start hearing the President mention the oil factor and the implications of that. There have been references to the Cuban security presence. There have been references to terrorist ties to Hezbollah. There have been references to the Iranians having activities. There are Russian advisors currently in Venezuela. So there are numerous points that really do not have a direct link to the narco-judicial effort, but certainly are within U.S. strategic interest. You would not want this festering in your hemisphere, on your back door. So can you help us really understand what those objectives were?</p><p><strong>LTG. McMaster 27:59</strong><br>Yeah, well, you know, this is where I think the administration gets, it gets like a grade of improve. How about communicating clearly what the objective is? And I think really what it is, based on all these statements, is kind of all of the above. I would put it under the heading of ensuring that Venezuela is no longer a host or a threat to the United States and our security interests in the hemisphere. That is the overall objective. There are certain components to that, and this is where now you have heard the administration talking about the behavior of the regime. We do not really care what regime is in power, as long as the behavior changes. And the behavior you hear about is everything you already mentioned, which is narcotics trafficking, being a platform for enemies and adversaries in the hemisphere, and the grievance associated with the seizure of infrastructure that was built with U.S. investment and denying profits to U.S. oil companies and so forth. And, of course, the subsidization of other hostile regimes with oil money and the cash flow from oil and narcotics. So those are all sub-objectives.</p><p>But I think the fundamentally flawed assumption that President Trump might be operating on is that he can get those outcomes without a change in the regime, and he is not going to get it. The reason is that there are limits to what you can achieve with coercive diplomacy. This is where President Trump has this dissonance between peace through strength, which you just saw with this operation, and an impulse toward retrenchment and really not getting involved in long-term efforts abroad, even in the near abroad here in the hemisphere. He tends to view these options through the lens of the searing experience of the Iraq War. In this way, he has inclinations that are quite similar to those of the Obama-Biden administrations.</p><p>The flaw in that thinking is that it is not Iraq. I think there is a misdiagnosis of the complications, the cost, and the length of the wars in Iraq and Afghanistan in terms of what caused them. I think what caused them, in large measure, was our short-term approach to long-term problems. There was a Vietnam-style wrong lesson of saying we just do not want to do that, just get the hell out. What we did not focus on was how to consolidate military gains and get to a sustainable political outcome consistent with what brought us to those wars to begin with.</p><p>I think what we are seeing in Venezuela may be a replication, actually on a larger scale, because Venezuela is a much larger country in terms of population, of the Obama mistake in Libya. What the Obama administration did in Libya, in its effort to avoid what it perceived as the mistakes of the George W. Bush administration in Iraq, actually exceeded those mistakes by affecting a change in the regime and then doing nothing to consolidate those gains into a sustainable political outcome. What did you have? You had a continued war in Libya. You had a continued threat of jihadist terrorism. You had a huge migration crisis that funneled through Libya into Europe.</p><p>So I think what we are going to see here is a failure of coercive diplomacy, and the President will face a difficult choice of what more do you do. If you look at the leaders in Venezuela and what they are doing right now, they are using essentially brown shirts, I think they are called the colectivos, these brigades of thugs, to go after anybody who might be sympathetic to getting Maduro the hell out of there. They are going through people&#8217;s phones. They are increasing the number of political prisoners. They have about 900 political prisoners in Venezuela now.</p><p>So we have to be clear about what we are demanding. We have to be clear about how we are creating a sense of urgency among officials in this government, many of whom I know are criminals, indicted criminals. We also have to be clear about what kind of punishment we are willing to mete out to achieve our objectives. For these inducements to work, you have to convince the leadership in Venezuela that you are more committed to that change in behavior than they are to continuing it. They have profited a hell of a lot from it, and Venezuelans are not going to be kind to them if they leave their positions, because they have victimized them. Since Chavez took over in 1999, Venezuelans have been living this hell. Since around 2006, the economy has contracted by about 80 percent. They have driven eight million Venezuelans out of the country, about one-third of the population.</p><p>So I think there is overconfidence in the ability to affect meaningful change in the nature of the government and its behavior through just coercive means, or what we might call forceful persuasion.</p><p><strong>Philip 33:29</strong><br>So thank you for that, and for our listeners, I should point out that, H.R., you&#8217;re an esteemed historian. While in the Army, you wrote a seminal book on the lessons of Vietnam, which wasn&#8217;t career enhancing for a while until it became so. You really do have a wonderful historical perspective. And if it&#8217;s not regime change that we&#8217;re after, that the President is after, and instead it&#8217;s trying to get to better outcomes with the existing political leadership and the existing military leadership, what tools are in the toolbox to do that? I presume economics, oil, political isolation, cutting off ties to some of the adversaries that we want booted out of the region, out of Venezuela.</p><p><strong>LTG. McMaster 34:19</strong><br>Yeah, absolutely. So my colleague, Stephen Coughlin, who&#8217;s a hoot, talks like Joe Pesci. I said Joe like he has, he&#8217;s from the Bronx. But he says, hey, authoritarian regimes really need five things to stay in power. The first thing you need is cash flow. So what you see is the administration going after that, right, from the narcotics cash flow and the oil cash flow. The second thing you need is security forces. I think this is what our agents on the ground are working on overtime to try to splinter those security forces and to get enough of them, who maybe don&#8217;t have the most blood on their hands and aren&#8217;t the most corrupt, to break away and then to be part of creating the security space you need for a political transition. Because really, these regimes don&#8217;t have to be that strong, they just have to be stronger than any organized opposition. The third thing you need is stories to tell your people. Hey, it&#8217;s the Yankees, it&#8217;s the gringos, they&#8217;re creating all these problems. It&#8217;s not us. You need me. You need us to save you, the Chavistas to save you. So you&#8217;ve got to counter that. This is where I think we should be a lot more active, in the informational domain and in the battleground of perception. The fourth thing you need is control over life choices. That&#8217;s what they&#8217;ve done with these criminalized patronage networks. If you have a job in Venezuela, it&#8217;s because the state kind of controls it. The cash is flowing down through these pyramid-type structures, and your livelihood is at risk. So you&#8217;re incentivized to stick with the regime, because that&#8217;s all you really know, even though you&#8217;re impoverished. And then the final thing is you need an international system that will sustain that authoritarian regime to some extent. As you alluded to, Philip, that&#8217;s exactly what they&#8217;re working on from the outside in, isolating Maduro from external sources of strength and support. So how will this play out? We don&#8217;t know, but I think it&#8217;s going to take a long time. We&#8217;re not going to see a quick change here. Sadly, the opposition is fragmented. I wish the President had not made the comment about Mar&#237;a Corina Machado, like, hey, she&#8217;s not that popular. What we should be doing is helping to bring that opposition together and say, hey, play together like they did in the last election. They did that extremely well. What happened is the opposition got 70 to 80 percent of the vote, and they were able to expose that. So I think what&#8217;s missing, and this is why Marco Rubio, I mean, he can&#8217;t do everything. You need a National Security Council staff process to coordinate and integrate across the departments and agencies and develop a more coherent strategy and policy at this point. That&#8217;s really what&#8217;s needed. You see elements of it, everything I&#8217;m talking about is out there, but what I don&#8217;t see is how these are integrated and how they&#8217;ll be evaluated based on measures of effectiveness that would then alert you, hey, maybe this isn&#8217;t working, we have to bring other options to the President. I think that lack of clarity is hurting us at this moment.</p><p><strong>Philip 37:36</strong><br>So it sounds like a bleeding-out strategy. It sounds like you&#8217;re not anticipating a sustained military operation, the proverbial boots on the ground, or a buildup that&#8217;s going to make it very clear that the United States is coming with all of its military might, not just for a decapitation of a leader, but, you know, taking out.</p><p><strong>LTG. McMaster 37:56</strong><br>Expecting the change like in Grenada, you know, where we had about 10,000 troops in Grenada but were going against, you know, 1,500 Cubans. You had, in a very small country, Panama. Panama is a country about one-tenth the size of Venezuela in population, and it&#8217;s about one-twelfth the size of Venezuela in landmass, and that was an operation of 30,000 troops to displace Noriega. But importantly, those troops gave you the ability to conduct all those activities necessary to consolidate those gains, right, to reform the police forces, to create a new police force under new leadership, which, by the way, was attacked by the old Noriega crew and had to fight them off at the main police station, with one of my friends, Colonel Jim Steele, in there issuing weapons from the arms room and fighting them off, because he was advising the new police force. We had to revise the judiciary there with them, help them revise it themselves, put an election process in place. There was an election about a year later in Panama.</p><p>So what does that political path look like? What does that security path of transition look like? There&#8217;s a lot of talk about the economic path to transition, bringing oil companies in, but it all has to come together, because without the security reform, without the political change, you&#8217;re not going to get the right conditions for revitalization of the economy, and the oil economy in particular. Going back even further, the Dominican Republic, 1965, Operation Power Pack, another very effective intervention, partnering with significant Dominican forces on the ground. How many troops did we put into the Dominican Republic? Forty-two thousand, you know, in &#8217;65.</p><p>So I think the President might choke on the price of that, in terms of a massive U.S. intervention that&#8217;s sufficient not only to depose the Maduro regime, but then to begin to set security conditions for security sector reform efforts and getting a path toward reform of the judiciary and reform of the political process, to really restore sovereignty to the Venezuelan people. Now the good news is Venezuela has a tradition of constitutional democracy, so really you&#8217;re just restoring the old constitution, but it would take a significant effort to do it. And I think they&#8217;ve got to tee up this option for the President, because I think he&#8217;s going to try everything short of that before he considers that more direct option.</p><p><strong>Philip 40:35</strong><br>So we just this morning woke up to the news that an oil tanker off the northern coast of the UK, between the UK and Iceland, was seized and taken control of by the United States military. That&#8217;s just one of the elements. We&#8217;re going to chase down their cash flow. You mentioned the cash flow. So speaking from a business perspective, I can&#8217;t imagine too many oil executives, with the possible exception of Chevron, who are still there and operating, wanting to take a 30-year view on the multibillion-dollar investment required to bring that oil infrastructure capability back up so that sometime 10 years from now you&#8217;re generating reliable profits and have a stable operating political environment to do that. So that&#8217;s going to be one very interesting element.</p><p>But now let&#8217;s move to China and Russia in particular. The Chinese have had oil-for-cash agreements with the Venezuelans. They had a delegation two days before the operation. Some of them were here in Mar-a-Lago right after, because of sensitivities around that. So what is going to be the calculus for senior leadership of the People&#8217;s Republic of China, Xi Jinping specifically, with this action that shows U.S. resolve, U.S. technical ability, and U.S. massive capabilities to execute on a very specific military operation, particularly on the heels of what we just saw with Midnight Hammer in Iran?</p><p><strong>LTG. McMaster 42:24</strong><br>I think what you&#8217;re going to see is China, Russia, and Cuba, as the local support there, working together to ensure that the U.S. fails in Venezuela and is unable to get a government in place that is friendly to the United States and welcoming to the vast Venezuelan diaspora to return and rebuild the country. So I think what you&#8217;re going to see is a sustained Russian effort to foil U.S. efforts in Venezuela, because this is tied to their broader competition with us. I wouldn&#8217;t be over the top on this, but Russia and China are at war with us now already. They really are at war with us right now, and they&#8217;re acting against us with hostile intent and trying to get away with as much as they can below the threshold that might elicit a concerted response from us. There&#8217;s a reason why the largest Russian embassy in the world is in Mexico City. It&#8217;s there because Russia wants to turn Mexico against us and use Mexico as a platform to subvert the United States. The reason China is trying to gain control of critical infrastructure and indebt countries in Latin America is really twofold. One is to displace U.S. influence not only in the Indo-Pacific but globally by creating new spheres of influence internationally. The other is to strengthen its exclusive grip on critical supply chains that it can use for coercive purposes, especially involving minerals, and also to address its major vulnerability from an energy perspective. This is a major geostrategic competition that&#8217;s playing out. The worst-case scenario is something we have to be concerned about, which is fragmentation in Venezuela and a sustained civil war in which the Russians, the Chinese, and the Cubans do everything they can to ensure that the U.S. fails to get a change in behavior, as we&#8217;re framing it now, meaning a change in the nature of the Venezuelan government such that it ceases its hostility to the United States and nations friendly to us in the hemisphere.</p><p><strong>Philip 44:40</strong><br>We&#8217;re going to open up the Q&amp;A to our investors and friends who are participating, and H.R., I&#8217;ll share some of those questions with you, but let me get one rolling here. We&#8217;ve talked a little bit about Russia. We have an active war and conflict in Ukraine. Vladimir Putin is someone you spent a lot of time thinking about and trying to understand, what drives his motivations, and the advice you were able to give to the president kept the United States out of having to adjudicate a territorial invasion that ultimately happened later under a different administration and after the withdrawal from Afghanistan. So the same question I asked regarding Xi Jinping, how is Vladimir Putin viewing this now?</p><p><strong>LTG. McMaster 45:37</strong><br>You know, I think, I hope it&#8217;s given him pause. But really, what has emboldened Russia, I think, with the massive reinvasion of Ukraine in 2022, as you already alluded to, was the perception of weakness associated with the disastrous, what I would describe as a self-defeating, humiliating, and deadly withdrawal from Afghanistan in August of 2021. I think the overall lesson is that it is the perception of weakness that is provocative to this axis of aggressors. And what I think President Trump is facing now, again, which is much different from 2020 when he left office in 2021, is the degree to which this axis of aggressors has coalesced, largely based on their view that the West is weak, divided, and decadent. So I think what this raid shows is that we&#8217;re not weak, that we have the resolve to do things. Also, I think this raid, in combination with last year&#8217;s operation against the deep, buried nuclear sites in Iran on the back end of the IDF&#8217;s successful campaign, confirms that, hey, we&#8217;re not weak. But we are divided in their view. And, you know, the President&#8217;s comments about Denmark, you know, I mean, guys, I mean, Bill, stop scoring these own goals. The way you frame things, it all matters, because what we want to convey to China and Russia on the back end of this operation is, hey, we&#8217;re not weak, divided, and decadent. We&#8217;re unified. We&#8217;re unified on Ukraine as well. We&#8217;re unified on Taiwan and the Indo-Pacific. So anyway, I think there are some tremendous opportunities at this moment, Philip, because of the success of this operation. Again, the long-term prospects are not good. They&#8217;re going to be tough in Venezuela, but we could see it through if we want to, if we have the will to do it. But also, to show that we&#8217;re not divided, I think, is really important, because this axis of aggressors is actually quite weak at this moment, I believe. Russia&#8217;s economy is a disaster. Look at what&#8217;s going on in Iran. Their currency has utterly collapsed, the protests that are going on there. I was glad to see the President&#8217;s statement, hey, don&#8217;t go after the protesters, because they did set a record last year for the number of executions in Iran after the effective campaign against the regime and the nuclear and missile programs. And then, you know, they&#8217;re about to run out of water in Tehran. China has created huge vulnerabilities in their economy, in my view, in their race to surpass us. They have some coercive power over our economy, which was really stupid for us to give them. But I think the administration is working now to make those supply chains more resilient. I was really happy to see Secretary Bessent say, hey, we&#8217;re going to do this in two years. That&#8217;s kind of an American attitude on supply chain resilience. So, hey, we&#8217;re in this competition, and we need all hands on deck. So stop kicking Denmark in the ass. Let&#8217;s work together.</p><p><strong>Philip 48:47</strong><br>Friends, including some of our friends from that part of the world, on Denmark, in Denmark, Greenland, the Arctic. So what&#8217;s behind all of the rhetoric? Is it simply, is it? Why can&#8217;t we just have a friendly NATO transaction where we, the United States, supply a certain amount of personnel and capabilities in a treaty partnership with those in Greenland and Denmark? Why do you need to acquire it? Why buy the cow if you get the milk for free, so to speak.</p><p><strong>LTG. McMaster 49:22</strong><br>Yeah, it&#8217;s like 50,000 people, right? And so I think what is driving this in part, and this is, I think, a positive observation, is that as President Trump recognizes, even though his National Security Strategy was not as explicit as we were in 2017 about great power competition, he knows he&#8217;s facing China and Russia, these revanchist powers on the Eurasian landmass. The part of the globe that is immensely strategically important is that connection through the Arctic. He&#8217;s looking at the map. He&#8217;s a real estate guy. It&#8217;s like, hey, that real estate is pretty important to our defense. And also, he has this agenda for hemispheric security, for homeland security, missile defense. You can&#8217;t have effective missile defense unless you defend against missiles coming over from Russia, over the Arctic, for example. He&#8217;s seen the first transnavigation of a Chinese commercial ship over the Arctic in the last couple of months, and the so-called exploration they&#8217;re doing up there. So I think he understands the importance of it.</p><p>But with so many things with President Trump, what he wants is great. Reciprocity in trade, deregulation, economic growth, energy dominance, burden sharing in defense, securing the border, let&#8217;s do it. That&#8217;s all great. But how he goes about it can be counterproductive. If I had his ear for a minute, I would say, hey, you&#8217;re big on sovereignty, which he is. If you go back to the UN speech we drafted for him in 2017, that was the theme. We respect national sovereignty, especially nations that respect the sovereignty of their people. So if you&#8217;re concerned about Greenland, you&#8217;re concerned about the subversion of Greenland&#8217;s sovereignty and Denmark&#8217;s sovereignty. Let&#8217;s be on the side of that. As you said, set the security conditions by going back to a Cold War&#8211;era footprint in Greenland and Iceland, for example, or in Alaska, for Arctic security.</p><p>And if you&#8217;re concerned about the Panama Canal, be on the side of Panamanian sovereignty. You&#8217;ve got a friendly government in Panama. Say, hey, we&#8217;re concerned that Chinese companies that are not going to respect your sovereignty are in control of this strategic location. We&#8217;re on the side of Panama, instead of saying we&#8217;re just going to take it over. So a lot of this is really about the messaging, which I think can be counterproductive. A lot of it is fueled, in part, by a nativist and neo-isolationist impulse. You might say, how does that work? How can you be isolationist, anti-interventionist, and yet say we might have a military option for Greenland? The reason is that it&#8217;s tied to hemispheric and homeland defense.</p><p>There are a number of people around the President, and everybody kind of knows who they are, who are actually more isolationist than him but also more interventionist than him, because they frame everything through hemispheric defense. They have this nostalgia, a misinterpretation of the John Quincy Adams speech. Think Quincy Institute, think Defense Priorities, think how the Heritage Foundation has been taken over in large measure by people with this worldview. I think it&#8217;s a warped and old-fashioned worldview, because the great moats of the Pacific and the Atlantic don&#8217;t do for us what they used to do in the age of hypersonic missiles, cyber warfare, and everything else. So that&#8217;s where a lot of this comes from, that hemispheric priority. You can see the theme in the National Security Strategy, but essentially this interventionism grows out of a strain of nativism and retrenchment.</p><p><strong>Philip 53:39</strong><br>H.R., we have literally three minutes, and then I have to hand this over to Lisa, who&#8217;s going to wrap up in three minutes. Are you fundamentally more optimistic, less optimistic, or no change in your baseline about the state of American interests and the state of strategic deterrence vis-&#224;-vis our competitors and adversaries today, versus when you were in office several years ago?</p><p><strong>LTG. McMaster 54:09</strong><br>You know, I&#8217;m more optimistic that we&#8217;re now on a better path than we were on several years ago. I&#8217;m also more pessimistic because I do think the axis of aggressors is still emboldened based on the perception of our weakness. They base that perception, really, on their belief that we are, again, weak, decadent, and divided within the alliance, which I mentioned, but also divided within our own society. So it&#8217;s the vitriolic nature of our political discourse, the tendency of political parties to oppose anything, even good ideas. You know, get rid of Maduro, how could that be bad, right, given what this guy&#8217;s done? They think those divisions are indicative of our imminent demise, when in fact I&#8217;m optimistic because I believe our democracies are more resilient. I believe these authoritarian regimes are actually quite brittle. And so I think we&#8217;re going to win this competition. I begin seeing our society mobilized because we recognize the problems associated with defense. This is a big shift. I think after the massive reinvasion of Ukraine, before that we tended to see a soft-headed cosmopolitanism take over people&#8217;s view of the world. They thought we were all just going to get along as an international community. And so when I see companies like SHIELD mobilizing capital to strengthen our nation from a defense perspective, but also an economic perspective, and to maintain our competitive advantages, I think there is no substitute for the advantages of our free-market economy and our unbridled entrepreneurship. So I&#8217;m optimistic, but I think we have to get serious and stay serious about investing in defense, making our supply chains more resilient, invigorating our defense industrial base in particular, and regaining some of the strategic depth that is necessary to convince your enemy. As you alluded to at the beginning, Phil, this is a lot about deterrence. It&#8217;s a lot cheaper to prevent a war than to have to fight one, but we have to convince our adversaries that we&#8217;re capable of defending ourselves, that we&#8217;re capable of conducting operations at sufficient scale and for ample duration to deny them the ability to accomplish their objectives through the use of force. And this entails military capabilities, hard power, but it also entails competing below the threshold of a major conflict in the cognitive domain and in the economic domain. But I think we&#8217;re up to it. We&#8217;re up to it.</p><p><strong>Philip 56:43</strong><br>That&#8217;s very encouraging. It&#8217;s been a fascinating discussion. Thank you so much. This is the beginning of a dialogue for all of our friends at SHIELD and our investors. We have these types of discussions. There were some questions I was not able to get to. We will answer them and send you written responses in coordination with General McMaster. H.R., thank you so much. You&#8217;re a star, so we appreciate it.</p>]]></content:encoded></item><item><title><![CDATA[🎙️ Ep 14 - HawkEye 360: How to Build a Profitable Space Startup in National Security]]></title><description><![CDATA[Listen now | What does it take to build a serious profitable, sustainable, scaled defense tech startup?]]></description><link>https://maggiegray.us/p/ep-13-hawkeye-360-how-to-build-a</link><guid isPermaLink="false">https://maggiegray.us/p/ep-13-hawkeye-360-how-to-build-a</guid><dc:creator><![CDATA[Maggie Gray]]></dc:creator><pubDate>Fri, 19 Dec 2025 16:30:30 GMT</pubDate><enclosure url="https://api.substack.com/feed/podcast/182050337/ae8f6e839fdd7f53ec03fd444335d6a5.mp3" length="0" type="audio/mpeg"/><content:encoded><![CDATA[<p>What does it take to build a serious profitable, sustainable, scaled defense tech startup? In the newest episode of the Mission Matters podcast, <strong><a href="https://www.linkedin.com/in/david-rothzeid-7a116961/">David</a></strong> and I sit down with <strong><a href="https://www.linkedin.com/in/john-serafini-950793a/">John Serafini</a></strong>, the CEO and founder of <strong><a href="https://www.linkedin.com/company/hawkeye-360/">HawkEye 360</a></strong> and a partner at <strong><a href="https://www.linkedin.com/company/shieldcap/">Shield Capital</a></strong>, to discuss what it took to grow HawkEye into a profitable company with:<br>&#128752;&#65039; 30+ satellites on orbit<br>&#128176; Nine-figures of ARR<br>&#129309; Customers across the U.S. government and allied nations<br><br>In this episode, we unpack:<br> &#128313; What it means to &#8220;build a serious company&#8221; in defense tech<br> &#128313; Why trust, humility, and sustainability matter more than hype<br> &#128313; The realities of working in classified environments<br> &#128313; Lessons from the SPAC boom, capital discipline, and profitability<br> &#128313; Where the real white spaces in space tech still exist<br> &#128313; How to partner effectively with defense primes (without fear-mongering)<br><br>This conversation is a must-listen for founders, operators, investors, and policymakers building at the intersection of commercial innovation, space, and national security, and includes some hot takes from John as well.</p><p>You can listen to the podcast on <a href="https://open.spotify.com/episode/5cBT73vW2f6mGwuvAllCq4?si=TpzP18KOTZSZowF_1BnGpA">Spotify</a>, <a href="https://podcasts.apple.com/us/podcast/hawkeye-360-how-to-build-a-profitable-space-startup/id1807120572?i=1000741933526">Apple</a>, the Shield Capital <a href="https://shieldcap.com/episodes/hawkeye-360">website</a>, <a href="https://youtu.be/llUn6SzEnVI">YouTube</a>, or right here on Substack.<br><br>As always, please reach out if you or anyone you know is building at the intersection of national security and commercial markets. And please make sure to subscribe to the Mission Matters podcast to hear more stories of what it takes to build at the intersection of national security and commercial markets.</p><p class="button-wrapper" data-attrs="{&quot;url&quot;:&quot;https://maggiegray.us/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe now&quot;,&quot;action&quot;:null,&quot;class&quot;:null}" data-component-name="ButtonCreateButton"><a class="button primary" href="https://maggiegray.us/subscribe?"><span>Subscribe now</span></a></p><p><strong>Transcript</strong></p><p><strong>Maggie 00:19</strong><br>In this episode of the Mission Matters podcast, we&#8217;re joined by John Serafini, the CEO and founder of Hawkeye 360 and a partner at Shield Capital. Hawkeye 360 operates a constellation of more than 30 satellites that detect and analyze radio frequency signals from space, providing insights into activities that can&#8217;t be seen with traditional imagery alone.</p><p><strong>David 01:13</strong><br>Radio frequency, or RF for shorthand, is what we use to communicate with technologies like Wi-Fi, AM and FM radio, Bluetooth, LTE, and more. Anytime someone communicates using one of these technologies, a Hawkeye 360 satellite can detect their location, which provides signal intelligence for a wide range of mission sets useful to the intelligence community, the military, law enforcement, and non-government organizations, among others.</p><p><strong>Maggie 01:45</strong><br>For instance, it can help a customer monitor maritime activity like illegal fishing, or help a law enforcement agency gain visibility into trafficking routes or cross-border movements used by illicit networks like terrorists and narcotics smugglers. These actors may rely on tools like push-to-talk radios and satellite phones but can be difficult to detect using satellite imagery alone. Hawkeye 360&#8212;</p><p><strong>David 02:11</strong><br>&#8212;is the first truly scaled startup we&#8217;ve had on the Mission Matters podcast since it was founded in 2015. Hawkeye 360 has launched more than 30 satellites, achieved nine figures of annual recurring revenue from government customers around the world, and reached profitability. They&#8217;ve raised more than $400 million and grown to over 200 employees.</p><p><strong>Maggie 02:35</strong><br>John has a long history in the national security industry. After graduating from West Point, he served as an Airborne Ranger-qualified U.S. Army infantry officer for several years. He then received his MBA from Harvard Business School and joined the investment team at Allied Minds, a deep tech venture firm, before starting Hawkeye 360 in 2015.</p><p><strong>David 02:56</strong><br>I&#8217;ve had the pleasure of working with John for several years at Shield Capital on our space portfolio, and he is absolutely one of the foremost experts on how to build and scale enduring space startups. In this conversation, we dive into what it really takes to scale a space hardware company, how John evaluates space startups as an investor, the trials and tribulations of working in classified environments and with foreign partners, and along the way, John delivers some hot takes on the current state of the industry.</p><p><strong>Maggie 03:26</strong><br>Now on to the conversation. John, you personally have spent a lot of time building companies, investing in companies, and scaling companies. What would you say is the best piece of advice you&#8217;ve received over the years about building a company like Hawkeye?</p><p><strong>John 03:45</strong><br>I&#8217;ve been blessed with a wonderful chairman at Hawkeye 360, Mark Spoto from Razor&#8217;s Edge. They led our Series A round back in 2017. Mark&#8217;s been a great partner to me, and at the time, it was probably more of a flippant remark from his own thinking, but it really stuck with me. I was having a conversation with him a few years after we started the company about what metrics he really wanted me to focus on reporting to the board and what would be our quote, unquote KPIs at the time. I remember thinking through revenue or ARR or ACV, bookings and backlog, et cetera. He kind of stopped me, and again, he&#8217;d probably say it was a flippant remark, but to me, it stuck. He said, &#8220;John, just build a serious company. Just build a serious company.&#8221;</p><p>I think that was a really great piece of advice because it forced me to recognize that we&#8217;re not building widgets. We&#8217;re not building some nameless piece of enterprise software to be deployed by some nameless enterprise entity in the middle of nowhere. We&#8217;re building data and data analytics products that are delivered to the warfighter, to the intelligence analyst, to decision-makers who are operating in very difficult circumstances with no margin for error. Accordingly, our technology has to work the first time. It has to work every time. That mindset has to permeate the entirety of the organization and filter up to the KPIs that we care about.</p><p>From that small piece of advice grew my own personal thesis on how to build a real, serious company in the defense technology ecosystem. The first thing is you have to be trusted. You have to be trustworthy. This is a hard thing for young companies to understand. If you&#8217;re going to sell mission-critical functionality to customers like NGA, NRO, CIA, combatant commands, or their international equivalents, you have to be trusted. You have to do what you say you&#8217;re going to do. There can&#8217;t be any gap between what your capabilities are and what you claim you&#8217;re capable of doing. Customers have to believe not only in you as the CEO and your management team, but also in the integrity of your product.</p><p>The second thing is you have to be humble. I don&#8217;t mean humility in the traditional sense. I mean recognizing that you are one small component of many different products, services, and technologies supporting the warfighter or the intelligence analyst. They operate within complex systems that are often beyond your full understanding, systems you have to fit into, be compatible with, and interoperate with. Your technology has to be ruggedized. It has to be cyber-hardened. It has to be proverbially camouflaged to work in very austere and difficult environments. I like to say that the sun does not revolve around your startup. The sun revolves around the warfighter and the customer, and your technology must fit into the complexity of the systems they operate.</p><p>The third, and hardest for many peer companies to understand, is that you have to be sustainable. To me, that means you have to be profitable, and you can&#8217;t be dependent on one or two, or just one, source of revenue or customers. You need high-quality margins, the ability to attract sustainable and consistent capital, and a diverse set of inbound revenue to reduce exposure to any single customer or source. That&#8217;s difficult for startup companies to grasp.</p><p>When Mark said to me, &#8220;You need to build a serious company, a mature company, a thoughtful company,&#8221; it meant that we had to be trustworthy, we had to be humble, and we had to be sustainable.</p><p><strong>Maggie 08:16</strong><br>John, what&#8217;s a company that you admire, that you think embodies a lot of the principles of being serious and sustainable?</p><p><strong>John 08:25</strong><br>I think, I mean, it&#8217;s easy to say a company like SpaceX because they&#8217;ve accomplished so much in such a short period of time, but they&#8217;ve also had an ungodly amount of capital to grow with. At the same time, I appreciate that their growth has not been linear. Their first couple of years were really challenging, and they were true pioneers. So it&#8217;s easy to say SpaceX, but I also have a lot of respect for Peter Beck and what he has built at Rocket Lab. Not only did he build a national security oriented space startup company, but he&#8217;s been able to build it out of New Zealand, which is not exactly known as a bastion of defense technologies or a place with a huge local government requirements set for him to naturally fulfill. He&#8217;s had to build a company that not only has real functionality that customers can depend upon, but can also export that capability to the United States and other advanced economies where space based launch and other space based capabilities are in demand. None of that is easy.</p><p>We take for granted building space related companies today, which is a totally different environment from building a space company ten years ago when he got started. Back then, there were probably five or so venture capital firms that would take him seriously in a seed or Series A round, and even in a Series B round. Today, there are dozens, if not a hundred, that would take that meeting and sincerely consider financing his round. I&#8217;m also impressed by how he thinks ahead and how the organization thinks ahead. They&#8217;ve not only achieved a great amount of scale in the launch business, which is an extremely difficult business to be in and almost impossible when you&#8217;re competing against SpaceX and the scale they have, but he&#8217;s also been able to use that initial success in launch to move into other complementary business areas. That includes building spacecraft, building parts of the supply chain, and leveraging access to customers to contemplate becoming a constellation operator in other areas. All of these are complementary to his larger business thesis.</p><p>With a relatively small amount of capital and a public listing, albeit via a SPAC, which I think was a challenging path, and one where he could have IPO&#8217;d the company the traditional way, he&#8217;s built a lot in a relatively short period of time. So I tip my hat to Peter. Of course, I also tip my hat to SpaceX, to Gwynne and Elon, and to what they&#8217;ve collectively built. I think both of those companies are great exemplars for us to follow.</p><p><strong>David 11:23</strong><br>Yeah, John, I think that&#8217;s a great point on Rocket Lab and SpaceX. They&#8217;re certainly preeminent companies in the space economy and may be responsible for a lot of the progress that we&#8217;ve seen. You also have to mention that both have been able to orient themselves around the national security environment. You&#8217;ve been working in and around government for over two decades, both as an Army officer and now as an entrepreneur. Hawkeye 360 coincidentally started in 2015, the same year that the Defense Innovation Unit, then DIUx, got started. I&#8217;m curious whether it&#8217;s easier now to work with the Department of Defense and the intelligence community relative to when you started, and if there&#8217;s anything you&#8217;d like to impress upon other founders as they think about partnering with the department and the broader national security environment.</p><p><strong>John 12:21</strong><br>Well, to answer the first part, which is to compare and contrast the environment in 2015&#8211;2017, when we started Hawkeye, versus today. I actually started defense tech investing and company building all the way back in the 2010 timeframe. I could even tell you stories from the 2008 timeframe. Back then, defense technology as a category didn&#8217;t really exist. It was about guards, guns, and gates. That changed as commercialization of C4ISR became a thing, particularly with the advent of cybersecurity. When cyber became an investable technology area, people could put capital into what they perceived as enterprise software, see it adopted early by government entities that needed protection, and then use those bona fides to scale into the broader enterprise and into highly regulated industries. From my viewpoint, that was the beginning of the modern defense technology experience.</p><p>When Hawkeye was getting started, I would characterize the mindset as getting companies drunk on RDT&amp;E. What I mean by that is there were a lot of RDT&amp;E dollars&#8212;research, development, testing, and evaluation capital&#8212;sloshing around the system. Pentagon leaders and intelligence community leaders who wanted commercialization equated innovation and moving fast with simply putting more RDT&amp;E capital into the system and seeing what would happen. Ultimately, though, that just created an ecosystem where companies were jumping from one SBIR to an In-Q-Tel work program to a DIU contract and back again. They were never incentivized or provided the capital necessary to reach production contracts, where you could actually take advantage of the value created at TRLs three, four, and five, do the productization at six, seven, and eight, and then deploy that technology to actually help the warfighter.</p><p>I like to say that back then you had a bunch of startups getting drunk on RDT&amp;E work, skipping around, and not creating meaningful value. The naysayers would point to this and say, why are we funding all this work to get a company to TRL six, only for them to then need more money, pivot, lose an investor, or simply not be sustainable? What&#8217;s the point of the defense ecosystem, the intelligence apparatus, and the national security community starting to depend on these technologies if we can&#8217;t trust that companies will make it through the so-called valley of death?</p><p>That was the environment from roughly 2015 through 2019 or 2020. There was also a strong mindset that the U.S. government should not be in the business of picking winners. As companies graduated out of the RDT&amp;E phase, even when there were clearly capable firms, the government was hesitant to say, this is the one we need to scale, provide a production contract, and put into a program of record to support deployment to the warfighter community. No one wanted to make that call.</p><p>I saw some change during the Biden administration. The overarching philosophy became something like &#8220;buy what we can and build what we must.&#8221; I think there was a lot of lip service paid to that, but things got much better under the current Trump administration. People really got religion. It wasn&#8217;t just a mantra anymore. It became buy what we can, buy what we can, buy what we can. If it&#8217;s out there, affordable, capable, and the warfighter wants it, buy it, scale it, and get it to the warfighter as fast as possible. There were no caveats or excessive requirements placed on companies, and far less policy friction that made it difficult to achieve a program of record. It was simply, if you can be successful, we&#8217;re going to drop the safeguards and guardrails and put capital behind you so you can create value for the warfighter. That has been exciting.</p><p>Today, I think we&#8217;re in a golden age of defense tech opportunity, but it comes with a real &#8220;peeing in the pool&#8221; risk. As the community opens its arms and says we&#8217;re going to work with commercial at real scale, if one company screws up, it contaminates the pool for everyone else. It makes it much harder for CEOs and companies doing the right thing and creating real value to succeed. If someone lies, forgets their humility, fails to recognize that the sun revolves around the warfighter, or can&#8217;t be sustainable and disappears, the U.S. government won&#8217;t trust companies with programs of record if they might not be there a month from now. Best behavior across the entire ecosystem is necessary for all of us to succeed.</p><p>So that&#8217;s my answer. Back then, it was extremely hard to scale and very difficult to get through the valley of death. Companies made bad decisions, like becoming services providers, just to survive, because there weren&#8217;t viable programs of record to allow linear scaling. Today, it&#8217;s a very different environment. With a more aggressive and interested customer base comes access to more capital. What we&#8217;re really missing now, and I&#8217;m sure we&#8217;ll talk about this later, is exit opportunities, particularly in space. That has always been the challenge for commercial space: a lack of exits. That&#8217;s a natural consequence of having a smaller base of strategic acquirers, and it&#8217;s something we&#8217;ll have to work through as an industry to be successful long term.</p><p><strong>David 18:34</strong><br>Well, John, maybe we get into it. I know we definitely want to bring things up to the present day with Hawkeye 360 and the success you&#8217;ve had working with the national security community. Although I just can&#8217;t help myself. We could be in a golden age of defense technology and space technology, or we might end up in a bit of a golden pool. We&#8217;ll see how the good actors operate to make that the case. But maybe just talking about the SPACs of 2020 and 2021, right, when we had zero interest rates and money was just flowing from the government into people&#8217;s pocketbooks, creating a bit of a market frenzy. A couple of years later, after a bit of a fallow period, we&#8217;re seeing a real uptick in the marketplace. One of our portfolio companies, Apex, has raised over a billion dollars. Two space companies raised at three billion. There seems to be some significant momentum coming forward. And of course, how could I forget SpaceX signaling that they may go public in the next 12 to 18 months at one and a half trillion, with a T. So what can this current generation of startups learn from their predecessors who SPAC&#8217;d, including Rocket Lab in 2020 and 2021, and how should they think about ensuring they don&#8217;t make the same mistakes?</p><p><strong>John 20:03</strong><br>Yeah, so there is a lot of froth in the system. I would point out that you can probably make a case that SpaceX&#8217;s valuation is defensible based on cash flows. They have very meaningful cash flows and very meaningful revenue, unlike many of the other companies we&#8217;re talking about. Going back to point number three I made earlier, you have to be sustainable. Part of being sustainable is raising capital on the right terms that you can grow into and that allow you to make your investors money and your employees money without setting expectations that are simply unachievable, particularly once the larger macro environment changes.</p><p>Some companies, and I won&#8217;t point to the ones you mentioned because we have a financial interest in one of them and think very highly of the company, are raising capital simply because it&#8217;s available. At some point it becomes, well, if I raise at this level, you need to raise above me to prove a point, and so on. That becomes a tower of cards that&#8217;s going to fall down at some point. I think there was some of that in the lead-up to the SPAC boom in 2020 and 2021, where some of these space companies had raised private rounds they were never going to be able to grow beyond just by accessing private markets. They didn&#8217;t have access to the scalable amount of capital necessary to build their constellations. They had to start thinking outside the box, and for them, SPAC vehicles enabled a relatively painless pathway to the public markets, where they could market themselves on the basis of forward-looking projections.</p><p>That&#8217;s no longer the case, but it was at the time. It became an antidote for some of the sins of the past, in a way, allowing them to preserve an up round while getting a public listing and having everyone, quote unquote, make money on paper, at least for a short period of time. Before the 2020&#8211;2021 SPAC boom, the only really well-known SPAC success story was Burger King back in the 1980s. It&#8217;s just not a sustainable vehicle for accessing the public markets, and you wear that stink as a SPAC company for a long time. No one associates Burger King with that anymore, but companies that SPAC&#8217;d and are still around have seen depressed share prices because of their origins, and that&#8217;s been very difficult for them to shake.</p><p>Probably the two exceptions in the space industry are AST SpaceMobile and their friends at Rocket Lab, who frankly could have IPO&#8217;d the regular way, but I think they saw the ease of the SPAC transaction as very attractive at the time. To me, the SPAC boom is indicative of the fact that accessing the public markets is, in some ways, mutually exclusive with too many peer companies doing the same thing. The more companies that access the public markets, the higher the likelihood that overall quality goes down. You get lower-quality companies and less scarcity value on the public exchange for public-style investors.</p><p>As more companies SPAC&#8217;d, and as more companies contemplate going public in the future, I think it has a marginally deleterious effect on companies that are already public, as well as on those that want to go public later. That&#8217;s why you saw the SPAC craze peter out relatively quickly. Some companies that clearly were not prepared for the public markets took that route in late 2021, and that&#8217;s when the PIPE market dried up, redemption rates hit 90 percent on SPAC dollars, and it all went downhill in a hurry.</p><p>I am concerned about that in today&#8217;s environment as well. As companies that may be lower on the quality curve contemplate going public again, and we&#8217;ll take SpaceX out of this conversation because it&#8217;s a very special case, how are they going to perform in the public markets? If they perform poorly, and I won&#8217;t point fingers, what does that do to the companies behind them and their ability to IPO on high-quality terms? And what does it do to their ability to trade sustainably?</p><p>Ultimately, it goes back to point number three. If you&#8217;re going to sell defense technology companies and applications that matter, you have to be stable. You have to be sustainable. If your stock price looks like a zigzag, going up and down every other day because there&#8217;s no basis for the market to value you, no cash flows for the market to associate a fair value with, that&#8217;s a problem. That leads you to being the kind of company that could be fly-by-night and gone the next day. You need slow, linear, solid growth up and to the right over time. That&#8217;s what I&#8217;m trying to solve for at Hawkeye: how we continue to grow by accessing the types of capital available to us in a sustainable manner, for our company, our shareholders, and our customers.</p><p><strong>Maggie 25:40</strong><br>I want to turn back the clock 10 years or so, back to the early days of Hawkeye 360 specifically. I want to ask about how Hawkeye 360 was really formed. I know you were previously an investor at Allied Minds, which focused on investing in companies spinning out technology from academic or federal labs, and that the initial technology for Hawkeye 360 came out of a lab at Virginia Tech. Could you tell us a little bit about the story of taking a piece of IP and turning it into a scalable business, and what some of the challenges and opportunities are when building a company this way?</p><p><strong>John 26:22</strong><br>I had a great partner, a guy named Dr. Charles Clancy. Charles and I had built two other companies together, one called Federated Wireless and another called Optia Labs, that were doing very well in the 2015&#8211;2016 timeframe. Charles ran the Hume Center for National Security and Technology, which was a University Affiliated Research Center at Virginia Tech. I did a good amount of classified work on behalf of the National Reconnaissance Office. Today, Charles is one of the senior leaders at MITRE. I believe he&#8217;s the CTO and is doing amazing things for our country.</p><p>Charles had this idea, and there were two other gentlemen we worked with who helped found the company at the time, one named Christa May and another named Dr. Bob McGuire. The four of us came up with this concept. Ultimately, if you can take pictures from space, a company like DigitalGlobe at the time, now Maxar and since renamed again, was taking pictures commercially, as was Planet, which had just gotten started, and BlackSky, which hadn&#8217;t even been around yet. If you can get a license to image from space, whether electro-optical or synthetic aperture radar, and sell that to government and commercial customers, why can&#8217;t you also do signals intelligence, which is another highly valued modality of intelligence that can be gathered from space?</p><p>From my simple viewpoint, there are three interesting things you can do from a government perspective in space. You can take pictures, you can communicate, both of which have long since been commercialized, and you can analyze signals. We had been doing that for decades, but it had never been commercialized in the way communications and imagery had been. We saw an opportunity to operate in a white space that was unique. We could create space vehicles, satellites that were relatively inexpensive, and this aligned well with SpaceX initiating its transporter missions, where rocket launches became relatively cost effective. That, in turn, began the democratization of low Earth orbit, which previously just wasn&#8217;t available because launch capacity at reasonable prices didn&#8217;t exist.</p><p>We could build satellites relatively cheaply, get them on orbit relatively cheaply, and as long as the regulatory environment was conducive and the stakeholder community was interested, meaning customers across the defense, intelligence, and national security ecosystem, this made a lot of sense for us to pursue. It took us a while to build advocacy, particularly in the intelligence community, and to make sure people were on board with a regulatory environment that would support commercial signals intelligence. We got there over time. It wasn&#8217;t immediate. It really was pushing a rock up a hill for a long period of time.</p><p>That effort was coincident with our first launch. We got our first satellites on orbit at the end of 2017, early 2018. They were commissioned, and we became truly operational around the 2020&#8211;2021 timeframe, when we had enough clusters on orbit to drive down revisit rates. That was when we started to see real adoption, advocacy, and interest from the broader stakeholder community. It took time to build that engagement base. That doesn&#8217;t happen overnight, and it&#8217;s not just about working with customers. It&#8217;s the entire stakeholder environment. It&#8217;s engaging the executive branch. It&#8217;s spending real time on Capitol Hill advocating for your equities. It&#8217;s working closely with the customer base. There&#8217;s a whole ecosystem of stakeholders whose interests have to be understood and addressed to make something like this work.</p><p><strong>Maggie 30:11</strong><br>Speaking of the customer base, I know that unlike the vast majority of startups out there, most of the work that Hawkeye does is in the classified space. How can early-stage startups even get started working with classified customers like the intelligence community, and what are some of the technical and operational hurdles you&#8217;ve had to navigate to work with those kinds of customers?</p><p><strong>John 30:36</strong><br>Well, part of our value proposition, Maggie, is that we own and operate a constellation of satellites that are ours, right, and we&#8217;ve used over $400 million to build them. They&#8217;re inherently commercial assets, meaning that the data we collect is inherently commercial and shareable. Yes, we have to get ITAR licenses to be able to sell internationally to our foreign customers, but inside the U.S., what had previously been a highly restricted group of people who had access to signals intelligence data coming from national systems, we could provide our Hawkeye shareable data to them and everyone else inside the U.S. government. Everyone else is a U.S. citizen, and our allies can access it with the appropriate ITAR licenses.</p><p>So we do engage in the classified environment because our customers have a lot of classified equities that have to be taken into consideration, and there are requirements and certain information about what they want us to perform that can only be shared in the classified environment. But what we actually produce, the data and the data analytics, nine times out of ten, is an unclassified, totally shareable work product that is sold on an exceptionally high gross margin basis. So that&#8217;s the reality of what we do.</p><p>To answer your question, though, we did start needing to do a lot of work in the classified environment, and in my viewpoint, it&#8217;s exceptionally difficult to build technologies, products, or services that are going to serve the classified environment if you&#8217;re not a practitioner. If you&#8217;re some guy waking up on an arbitrary Tuesday in Silicon Valley who&#8217;s never served, never worked inside the classified environment, doesn&#8217;t have a clearance, doesn&#8217;t understand the requirements, and thinks you can hang out with your dog in your Silicon Valley garage and come up with some new classified technology that practitioners are going to immediately adopt and say, &#8220;This is the greatest thing ever,&#8221; you&#8217;re just wrong.</p><p>You can&#8217;t put yourself, the warfighter, or your investors in a situation where you&#8217;re trying to push something that might make sense to you, something you came up with in your garage, onto the requirements or conditions of a classified customer, because they&#8217;re just going to reject it. It&#8217;s going to be a waste of capital and a waste of time. Yet we see this quite a bit, where companies that don&#8217;t understand the environment under which these operators are conducting missions try to bring technologies they think will work in the classified environment, but they just don&#8217;t know. They don&#8217;t have clearances, and they don&#8217;t understand the unique circumstances and missions these folks are working under.</p><p>So I think the first answer is that you have to be taken seriously by being a practitioner. Ultimately, if you don&#8217;t have a clearance yourself, I think it&#8217;s really difficult to try to build a capability that will be used by those in the cleared environment. Obviously, if what you&#8217;re building is valuable, customers are going to come find you. Probably the best meeting place is In-Q-Tel. If you can get In-Q-Tel to be an intermediary to help vet your technology, match it against classified users, and help secure some kind of work program by which you can further develop and productize your capability and then deliver it to customers who might consider it, that&#8217;s a good mechanism. It&#8217;s been valuable for many, many companies, particularly those that Shield works with.</p><p>But outside of having that kind of intermediary, you can&#8217;t expect that there are customers waking up thinking, &#8220;Oh, I&#8217;ve got to go find the next commercial thing that&#8217;s going to solve my problems, and I&#8217;m going to give them an FCL so they can have unfettered access to our nation&#8217;s classified apparatus.&#8221; It doesn&#8217;t work that way, and folks need to temper their expectations if that&#8217;s what they think will occur.</p><p><strong>David 34:28</strong><br>Yeah, John, that&#8217;s great. And I think one of the areas this really boils down to is trust. In-Q-Tel, the investment arm of the Central Intelligence Agency, is certainly a great way to broker trust with the end customer. One other area that&#8217;s often talked about, or at least highlighted, especially with some of our other startups, is working with defense primes. For a lot of people, they get a really bad rap. They&#8217;re going to steal your intellectual property, they&#8217;re going to move slowly, they&#8217;re going to be a challenging partner, but it seems like you&#8217;ve done a really good job partnering with them. For other startup founders, how would you coach them in thinking about engaging with the defense primes?</p><p><strong>John 35:13</strong><br>People like to use the primes, like a Lockheed or a Northrop, as some kind of proverbial whipping child that they point to as the source of all evils. And the case of the matter is, yes, they move slower. Yes, they have different incentive structures. But ultimately, what they build works. There&#8217;s a reason why the M1A2 Abrams tank works like it does. Now, compare that against other countries and their defense industrial base. They may cut corners. They may not have the quality and QA/QC emphasis that ours does, and they may not be anywhere near as effective on the battlefield as the capabilities that we deliver. So what we have to do is find a way to marry the defense industrial base, who move slow and don&#8217;t innovate very well but build stuff that works and can be trusted to work in extreme conditions on the battlefield, with the left-hand side, the Silicon Valley&#8211;esque mentality where we&#8217;re going to leverage innovation, move fast, break things, and leverage private capital and intellectual property to create new functionality. We have to marry that together, taking interesting ideas and creating them in such a way that they can be trusted to work the first time and every time. Again, this goes back to taking care of the warfighter. They need a ruggedized piece of technology that is actually going to work. This isn&#8217;t nameless widgets that we&#8217;re building for some nameless enterprise customer. So I look at defense industrial base partners as phenomenal investors and phenomenal partners for building better productized capabilities that I can deliver to meet the customer&#8217;s needs. The defense industrial base has been working with the warfighter for decades, 50-plus years. They understand the requirements, the missions, the restrictions, and what it&#8217;s like to be on the battlefield. That company coming out of Silicon Valley does not. Maybe they&#8217;ve got a couple of veterans, maybe they&#8217;ve done some work in the past, maybe they&#8217;ve been practitioners, but they don&#8217;t understand it to the extent that the defense industrial base does. So how do you take the best of the defense industrial base and marry it with the move-fast, innovate-quickly mentality of Silicon Valley? I think part of the rationale is having those defense industrial base entities invest in your companies. For each of our financing rounds, all eight institutional financing rounds that we&#8217;ve done, just about all of them included a strategic partner. Some of them led those financings. Raytheon led our A3 round. Airbus led our B round. Leidos and Jacobs were meaningful investors in our C and D financings. We had Lockheed invest materially in our D1 round, and they&#8217;ve all been wonderful partners to work with. The idea that these defense industrial base companies wake up wanting to steal some arbitrary startup&#8217;s intellectual property and people is asinine. That&#8217;s just not how they work. They wake up wanting to take care of the equities of the warfighter and the American public, just as much as this new defense technology company ecosystem does as well. So I&#8217;ve taken the perspective that they&#8217;re not competitors. To me, they&#8217;re not the boogeyman. They&#8217;re good people. They know how to build great systems, and if I work with them, they can probably get my technology to the warfighter so I can actually create value faster, better, and stronger than if I tried to do it myself. I would say that strategy has worked for Hawkeye. It&#8217;s worked for other companies that we&#8217;ve seen replicate it. Awesome.</p><p><strong>David 38:52</strong><br>Well, just for our audience members, John, you highlighted getting an FCL, which stands for facility clearance, and that allows you to do classified work. Another acronym is ITAR, the International Traffic in Arms Regulations, which is the State Department&#8217;s program to protect sensitive technology from getting into the hands of our adversaries. For sensitive tech like the stuff that Hawkeye is building, you actually have to get licenses to work with international partners. But what would typically be an impediment or a massive hurdle, you&#8217;ve used and gotten through, and now you work with a lot of our allied partners and sell to them. So maybe you can talk a little bit about what that process has been like to allow you to take ostensibly sensitive technology and sell it to our foreign partners, not through something like foreign military sales, but actually going direct to them to provide the type of service and data that Hawkeye 360 uniquely collects.</p><p><strong>John 40:00</strong><br>When I was growing Hawkeye in its incubation stage, one of the things we heard a lot from potential customers and stakeholders was, &#8220;Don&#8217;t be a ward of the state,&#8221; meaning don&#8217;t create your company such that it&#8217;s highly correlated to the U.S. government purchasing it, because if the U.S. government stops, it goes away. You can&#8217;t put the government in that kind of position. Somehow that lesson has been forgotten along the way, and now you&#8217;ve got this whole crop of single-use technology companies that, should the U.S. government stop buying certain types of functionality from the defense tech ecosystem, are just going to fall away in a hurry. At the time, if we had architected ourselves to be wards of the state, we would never have gotten dollar one in revenue because we would have been pariahs. By virtue of showing that we could be sustainable outside of government anchor customers, I had to demonstrate that there was a diversity of customers for us. Not wanting to really focus on commercial industry at the time, and I still think it&#8217;s not the right area for us to focus, I went naturally to the international markets, and that was a great decision for us. In 2018 and 2019, we were fortunate to pick up a couple of real, meaningful anchor customers early on who wanted access to commercial signals intelligence because they&#8217;d never had it before. Some of them might have had rudimentary organic SIGINT overhead capabilities, but they weren&#8217;t sophisticated, and they were excited to get access to new forms of overhead signals intelligence. They were willing to spend significant amounts of money and pay a premium on pricing in order to do so, and that&#8217;s been a meaningful achievement for our company. I&#8217;m very proud of the fact that 50 percent of our revenue comes from U.S. government sources across a diaspora of different agencies and customer types inside the U.S. government. Similarly, there are dozens of customers for Hawkeye on the international side. Recognizing that it&#8217;s not easy to do this when you&#8217;re ITAR controlled, you have to get licenses, technical assistance agreements, and DSP-5s to be able to market your technology to international customers. You&#8217;re certainly at a disadvantage when you&#8217;re competing against international entities that can market ITAR-free capabilities and will do so. But the diversity benefit, and being able to command what I would call premium pricing on the international side, is rewarded with very loyal customers. What we&#8217;ve found is customers that are very sticky and, in particular, are willing to sign up for longer contract terms than on the U.S. government side. Ultimately, our business is kind of bifurcated. You&#8217;ve got U.S. government customers across a number of different buying entities, which tends to be shorter term with very quick turnaround. The sales cycle is literally negligible. It could be hours before we&#8217;re on contract, on requirement. On the international side, it&#8217;s a longer-term sales cycle. When you sell something to a country like the Philippines, for example, it takes a long time to manage that sales process. It&#8217;s not exactly linear, especially for an American company, but the contracts tend to be longer and the pricing tends to be better. It&#8217;s an interesting dynamic between the two, and having that diversity in our revenue base has really helped us.</p><p><strong>Maggie 43:25</strong><br>Hawkeye is definitely the most mature startup that we&#8217;ve had on this podcast. I know from some other interviews you&#8217;ve done that you&#8217;re at nine figures in revenue and have several hundred employees. I really want to spend some time talking about what it actually takes to scale a defense tech hardware company in a sustainable way. One of the first questions is, what were some of the unexpected challenges you faced in scaling up your technology, going from that first cluster that you launched to the twelfth cluster you launched earlier this year?</p><p><strong>John 43:59</strong><br>As I mentioned earlier, in 2015 and even into 2020, the number of capital providers for defense technology and space technology was negligible. We are talking about maybe a dozen by the 2020 timeframe. Finding people who were willing to do a Series B round was hard, but it was especially hard for a space technology company in the 2017 timeframe. Being able to go into that Series B round having taken all the technology risk off the table was really challenging as well. If you are going to be a space technology company, the only legitimate way to show that the technology risk is off the table by the time you do your Series B, which should always be the goal, is by having space heritage, putting assets into space, and making sure they work correctly over a long period of time. Today, you are seeing companies raising exorbitant valuations in Series A, Series B, and even Series C rounds without having much space heritage to support those claims, and I think that is a challenge. That dynamic did not exist seven or eight years ago.</p><p>We had to think very thoughtfully about how we were going to de-risk each component of our technology architecture. For us, that architecture is pretty complex. You are talking about a space component, the sensor that actually collects the data, which is flying in a collection of three satellites. You have to showcase three assets working in harmony to geolocate a signal from 550 to 600 kilometers in space. You also have to demonstrate the processing of that data, which is entirely complex, including the geolocation, the analysis, and the conversion of that data into something actionable. There is a tremendous amount of different types of intellectual property that has to be proven across the entire continuum of that technology set. It was not linear for us to simply check a box and say it was done and move on to financing. That was a hard thing to work through.</p><p>When I think back on what I learned, there are four things that really helped us. The first was starting with a base of employees that was right-sized, made up of thoughtful, mature individuals who were previous practitioners and who deeply understood the technology. Just as importantly, they understood the requirements and the environment the customer was operating in. You cannot have daylight between what you are building and what the customer needs. If you are trying to invent, in your Silicon Valley garage, what you think the warfighter needs and it is not aligned with the reality of what that warfighter actually wants, that is a real challenge. I use warfighter here as a proverbial stand-in for the broader U.S. government customer. Bridging that gap is very difficult, especially if you are trying to get to program-of-record type contracts that ultimately make the entire effort worthwhile. So the first focus was having a small cadre of committed, thoughtful practitioners.</p><p>The second was being very careful not to get over our skis and being thoughtful about how much overhead we took on at each phase of the company&#8217;s life. I have a just-in-time resourcing mentality. As we achieve milestones with customer X, Y, or Z, or technology milestones A, B, and C, then we take on additional overhead. Then we add headcount, then we open an office, and so on. You do not do it beforehand. A lot of companies get into trouble by growing overhead too fast, and then they find themselves having to reverse course and do reductions in force, which is painful. I never wanted to be in that situation.</p><p>The third was the good housekeeping of having a thoughtful fundraising plan and knowing exactly which milestones you need to achieve to unlock the next tranche of capital. That means engaging with a good cadre of investors who are waiting for you to hit those milestones and then actually hitting them on the timeline you told investors you would. Nothing generates investor interest more than someone doing exactly what they said they would do. Every investor should have a logbook that says, when this company comes to me for their Series A, I will look back and ask whether, when they were raising their seed, they did X, Y, and Z as promised. There is always room for explanations like something unexpected came up and we had to work around it or find another technical path, and I will always give people credit for that. But ultimately, if you do not have a track record of achieving the milestones you set, why would I, as a fiduciary of investor capital, provide you with more capital knowing you may not be able to achieve the milestones required to get to the next financing round?</p><p>Those were the four things I really focused on: having a small, committed cadre of practitioners; being disciplined and just-in-time with overhead and resourcing; having a well-thought-out, milestone-driven fundraising plan that is executed as promised; and finally, making sure that everything we do is highly aligned with the needs, requirements, and mission expectations of the customer.</p><p><strong>Maggie 49:13</strong><br>Speaking of major company milestones, you said in an interview earlier this year that Hawkeye is officially profitable. When do you think is the right time for hardware startups to focus on profitability versus growth at all costs?</p><p><strong>John 49:28</strong><br>Somehow, we&#8217;ve gotten into a mindset that it&#8217;s an either-or thing. It&#8217;s not. If you go talk to public equity investors, they&#8217;ve become almost schizophrenic. They want both value and growth, and you can deliver on that. There&#8217;s no reason why you can&#8217;t grow at 30 to 40 percent year over year and be profitable. If you&#8217;re growing at 60 percent but you&#8217;re deeply unprofitable, how does that math work? Ultimately, valuations really should be based on your cash flows. That&#8217;s how you ground valuation in reality, on the basis of cash flows and on the basis of EBITDA. We should be valuing later-stage companies, in D rounds and beyond, on a multiple of EBITDA. The only real questions should be the range of that EBITDA multiple and which year you&#8217;re using, whether it&#8217;s trailing twelve months, leading twelve months, or even two years forward, depending on the financing. To me, a sustainable company starts with an excellent cost structure. What are your gross margins? What is your EBITDA margin? How much are you spending in capex? How is that going to change over time? Are you going to be able to achieve free cash flow breakeven, not just EBITDA breakeven, but free cash flow breakeven? In the space industry, where you&#8217;re spending a lot of money on capex, when can you achieve free cash flow breakeven? When can I value you on the basis of free cash flows? Because if you don&#8217;t have free cash flows, I can&#8217;t really utilize a free cash flow multiple. To me, a company becomes mature when you can value it thoughtfully on the basis of its cash flows.</p><p><strong>David 51:08</strong><br>So John, I think that&#8217;s awesome to hear and definitely something other startups should take into account. For Shield Capital, you&#8217;re a bit of a talisman. You&#8217;re an active CEO and also an investor with us. What are some of the things you&#8217;re looking for in early-stage deals that space entrepreneurs should exhibit when trying to raise capital?</p><p><strong>John 51:36</strong><br>There are the obvious things, like whether this is a mature, thoughtful group of people working together in harmony to create something important. You can look at the team. You can look at whether the team has been successful in the past. Do they have a track record, and do they have a track record of working together? You can see these dynamics in pitches and diligence, whether the CEO and CTO are aligned. There are also intellectual property milestones and technology milestones, depending on the phase of development of the company. But beyond the technology and the early adopter metrics that every startup wants to flaunt, all of that can be gamed. Ultimately, what I really care about is this: if you build this thing, does anyone give a shit? Is it a big deal if you create it? If you use potentially hundreds of millions of dollars of venture and LP capital to build this ecosystem you&#8217;re conceptualizing in space, and you&#8217;re able to develop a commercial product to sell to government customers and others around the world, is it meaningful? Does it solve a real problem? Is it sustainable? Is it a functionality that will exist for a period of time and then be competed away because someone can replicate it quickly or because you lose your economics? That&#8217;s what I think about. It&#8217;s less tangible and totally intangible at the same time. It&#8217;s like that Supreme Court justice who said, how do I know pornography when I see it? I know it when I see it. It&#8217;s the same way here. If I can conceptualize what someone is building and know it&#8217;s going to be meaningful, that gets me interested. It has to excite me from that perspective.</p><p><strong>Maggie 53:26</strong><br>John, as we close out here, we want to transition to a couple of rapid-fire questions. So my first one is: what is a technology that, 20 years ago, you expected would be further developed today than it actually is?</p><p><strong>John 53:40</strong><br>That one&#8217;s easy for me. We built a company at Allied Minds called BridgeSat, which later became BridgeComm. I actually think the company just got acquired by Voyager. Its purpose was to commercialize optical communications, optical comms through lasers, from free space. We pulled a bunch of intellectual property out of Los Alamos National Lab, which were the leaders in developing quantum capabilities and had amassed a significant IP portfolio. What we found was that it was really, really difficult to build high-quality, small transmitters to push optical data, and no one had really invested the time to build the optical receivers needed to support that ecosystem.</p><p>You&#8217;re seeing that today with the Space Development Agency and the SpaceX Starlink constellation using optical relay networks, and it&#8217;s working really well. But it&#8217;s not working well for the rest of the space architecture, especially smaller spacecraft that can&#8217;t fit a materially sized optical terminal, even with a gimbal. I&#8217;ve been surprised that no one has really figured out how to package a small-scale optical transmitter in a way that truly commercializes optical connectivity at the scale we need. The better it is, the faster we can get data down to the ground, and the better the mesh networks will be.</p><p>It also amazes me that when I built Hawkeye in 2015, we counted one day and there were over 100 launch companies out there that had raised some amount of venture capital. It could have been seed dollars or something, but still, you would think that with all that innovation, all that capital, all that focus, and with the demand signal being what it is, there would be a lot more fully vetted and highly commercialized launch companies. Instead, you have this kind of monopoly of just a handful. It&#8217;s SpaceX, Rocket Lab at a premium, because it costs a lot to use a Rocket Lab dedicated launch, Firefly coming up, and people talk about Stoke, but I haven&#8217;t seen it yet because they haven&#8217;t demonstrated it. It&#8217;s just like, wow, with all that capital that&#8217;s gone into the sector, we really haven&#8217;t seen the results we were expecting 10 years ago.</p><p><strong>David 56:00</strong><br>Maybe for our next rapid-fire question, launch is certainly an area where we do seem to see a lot more pitch decks, and we&#8217;ve sort of stayed out of it given the trials and tribulations of others. What are some of the white spaces in the space domain that you see could be addressed by emerging startups, or what gets you excited about areas that have yet to be tackled?</p><p><strong>John 56:24</strong><br>Yeah, I mean, go back to the optical relay question. I think that&#8217;s interesting. There&#8217;s a fundamental problem with getting data down to the ground leveraging RF technologies alone. There&#8217;s only so much RF, only so much bandwidth, and only so many ground stations. The answer can&#8217;t always be ground station densification. The answer has to be more onboard processing in space in order to sort the data, process the data, and only bring down what you really need. And then we need better relay networks. We need better mesh networks that are available to all to get that data to the ground faster, because ultimately constellation companies&#8217; value is highly correlated to speed. The faster you can get that information to the warfighter, the better and more valuable it is. That&#8217;s certainly the case from Hawkeye&#8217;s perspective, and I&#8217;m sure it&#8217;s the same for many other intelligence modalities. So I think there&#8217;s white space to be developed around trusted relay partners and onboard processing technologies that can be leveraged by constellation companies and would be of interest.</p><p><strong>David 57:30</strong><br>Okay, and for your last rapid fire question, you can plead the fifth, though we&#8217;re hoping for the spice. The fate of Hawkeye 360 rests in the hands of working with one specific customer. Are you taking A, the United States Space Force, B, the intelligence community, or C, other?</p><p><strong>John 57:50</strong><br>I mean, obviously that&#8217;s a hard one to answer. I think ultimately there are a lot of different stakeholders that have to be addressed. It&#8217;s not just the warfighter. It&#8217;s the appropriators, and it&#8217;s the executive branch. To me, the ultimate customer is those stakeholders on Capitol Hill and in the White House, and the international equivalents for our other customers. So it&#8217;s a multifaceted customer situation. I like to say that when we&#8217;re doing international sales, we have to sell twice. We have to sell bottom up to the actual warfighter and the person who wants to build the spacecraft and the functionality, and we have to sell top down to get political support. So I&#8217;d say that political engagement really matters, and making sure that everyone is aligned with the interests of commercial technologies.</p><p><strong>David 58:49</strong><br>Well, John, you&#8217;ve been a successful investor, a great entrepreneur, and clearly maybe you could be a politician moving forward in life with an answer like that. Maggie, over to you to close us out.</p><p><strong>Maggie 59:02</strong><br>Yeah, John, thank you so much for coming on the Mission Matters podcast. We really appreciate your time and all the learnings from the past few years of working with you.</p><p><strong>John 59:10</strong><br>Thank you, guys. Great to spend time.</p><p><strong>Akhil 59:13</strong><br>Hey everyone, thanks for listening to the Mission Matters podcast from Shield Capital. Tune in again next month for another conversation with founders building for a mission that matters. And if you&#8217;re looking to build in the national security space, please reach out to us.</p><p>Top of Form</p><p>Bottom of Form</p>]]></content:encoded></item><item><title><![CDATA[🎙️ Ep 12 - L3Harris: Inside the Trusted Disruptor Strategy with CTO Andrew Puryear]]></title><description><![CDATA[How startups and defense primes can unite to bring innovation to the mission]]></description><link>https://maggiegray.us/p/ep-12-l3harris-inside-the-trusted</link><guid isPermaLink="false">https://maggiegray.us/p/ep-12-l3harris-inside-the-trusted</guid><dc:creator><![CDATA[Maggie Gray]]></dc:creator><pubDate>Fri, 05 Dec 2025 15:03:06 GMT</pubDate><enclosure url="https://api.substack.com/feed/podcast/180768799/1de8c9156145b8954604971ebb65fd97.mp3" length="0" type="audio/mpeg"/><content:encoded><![CDATA[<p>How can emerging startups and established defense primes collaborate to equip our warfighters with the technologies essential for preserving U.S. dominance on the battlefield?</p><p>In this episode of the Mission Matters podcast, we sit down with the <a href="https://www.linkedin.com/in/andrew-puryear/">Andrew Puryear</a>, the CTO of L3Harris, the 6th largest U.S. defense contractor, to discuss L3Harris&#8217;s &#8220;trusted disruptor strategy.&#8221; As part of this strategy, L3Harris partners with startups to bring cutting edge capabilities to the warfighter. We cover:</p><p>&#9889; How software-defined warfare will push the DoD from &#8220;months &#8594; minutes &#8594; microseconds&#8221;<br>&#9889; Lessons from Ukraine across EW, affordable mass, maritime drones, and integrated air defense<br>&#9889; Why open systems, digital twins, cognitive EW, and missionized AI will redefine military advantage<br>&#9889; What startups misunderstand about working with primes&#8212;and how to get it right<br>&#9889; Where the U.S. is ahead, where we&#8217;re behind, and what it will take to catch up</p><p>You can listen to the podcast on <a href="https://open.spotify.com/episode/6fQLx9OHmiiF9axhnwIUk4?si=1gS7r72oSjilpK4uBf8opw">Spotify</a>, <a href="https://podcasts.apple.com/us/podcast/l3harris-inside-the-trusted-disruptor-strategy-with/id1807120572?i=1000739787491">Apple</a>, <a href="https://shieldcap.com/episodes/l3harris">the Shield Capital website</a>, or right here on Substack.<br><br>As always, please let us know your thoughts, and please reach out if you or anyone you know is building in the national security domain.</p><p class="button-wrapper" data-attrs="{&quot;url&quot;:&quot;https://maggiegray.us/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe now&quot;,&quot;action&quot;:null,&quot;class&quot;:null}" data-component-name="ButtonCreateButton"><a class="button primary" href="https://maggiegray.us/subscribe?"><span>Subscribe now</span></a></p><p><strong>Transcript</strong></p><p><strong>Maggie 00:04</strong><br>In this episode of the Mission Matters podcast, we&#8217;re joined by Andrew Puryear, the Chief Technology Officer, CTO of L3Harris, formed six years ago from the merger of L3 Technologies and Harris Corporation. L3Harris is the sixth-largest U.S. defense contractor. It builds a wide array of defense products, including tactical radios, night vision systems, electronic warfare systems, rocket motors, and much more. L3Harris positions itself as the defense industry&#8217;s trusted disruptor, combining the reliability and mission understanding of a long-standing defense prime with the speed and innovation of a challenger. The strategy includes partnering closely with startups and emerging technology companies to accelerate capability delivery, break traditional acquisition cycles, and move new technologies into the hands of warfighters faster than the conventional defense industrial model. As part of this strategy, L3Harris established a strategic partnership with Shield Capital to gain access to disruptive innovators for technology transfer, teaming arrangements, direct investments, and partnered contracts. Since establishing this partnership, L3Harris has partnered with dozens of startups, including Shield Capital portfolio companies like SeaSats, Overwatch Imaging, and Code Metal AI. Andrew joined L3Harris three years ago and has been instrumental in driving the company&#8217;s trusted disruptor strategy and expanding its partnerships with emerging technology startups. Andrew has had a long career in the national security technology space, having worked as a technical leader at the Stanford Linear Accelerator Center, Sandia National Labs, MIT Lincoln Labs, MITRE, and Ultra Electronics, as well as serving as an Engineering Duty Officer in the Naval Reserves for more than 14 years. Andrew is one of the sharpest thinkers in the defense technology ecosystem, and I have personally learned a tremendous amount from my conversations with him over the past few years about where the industry and technology are headed. In this episode, we cover everything from the future of technologies like electronic warfare, attritable systems, and generative AI in the national security space to how startups should think about partnering with defense primes and much more. Now on to the conversation. All right,</p><p><strong>Akhil 02:46</strong><br>Andrew, thanks so much for joining us today. Super excited to dig in. It&#8217;s been awesome to get the chance to work with you over the past years here at Shield Capital. Let me start right now. You&#8217;re the CTO managing an amazing portfolio across technologies, but you started thinking on Vassar Street doing your PhD in electrical engineering at MIT, and now here you are leading initiatives across a variety of technology domains, from the traditional communications realm to AI to the platforms and payloads and sensors that make it happen. Let me ask you, when you&#8217;re not doing your leadership work and you do have a chance to get behind code or get on a chipboard, what gets you excited, and what do you still want to do technically that maybe you don&#8217;t have as much time for these days?</p><p><strong>Andrew 03:33</strong><br>Yeah, that&#8217;s a great question. So back to my time in the Stata Center there at MIT, I always loved that MIT was an integral part of inventing radar, right? And given those roots&#8212;those deep roots that MIT has in radar&#8212;and today&#8217;s current trends in artificial intelligence and machine learning, in my off time I build models. I fine-tune models that do everything from, hey, this is how you classify RF, to generating novel waveforms, whether that&#8217;s radar waveforms or comms waveforms. It&#8217;s just super exciting to apply something that was so important historically&#8212;a decisive factor in the winning of World War II&#8212;and apply modern technology to that space.</p><p><strong>Maggie 04:16</strong><br>Andrew, are you a vibe coder at all? Are you using Cursor or anything like that?</p><p><strong>Andrew 04:21</strong><br>Yeah, and I love the trend of vibe coding because it really does help accelerate workflows. I actually tell every engineer at L3Harris that they should be looking for how to use AI-enabled tools such as Code Metal, which is a Shield Capital portfolio company. How do you use a tool like Code Metal to accelerate your workflow so that we can be more productive as engineers? What we all want to do as engineers is deliver capabilities into the hands of the warfighter faster, right? And Code Metal allows us to do that. The vibe-coding ecosystem allows engineers and non-engineers alike to start to build code. In terms of whether vibe coding is high quality or not, you see various studies that have somewhat mixed reviews. But one of the things I&#8217;ve noticed in my career as I monitor AI is this: every time someone says, &#8220;AI does X, but it cannot do Y&#8221;&#8212;okay, AI can beat the world chess champion today, but it&#8217;ll never be able to do complex reasoning. A couple of years later, it&#8217;s able to do complex reasoning, but it&#8217;ll never be able to pass an eighth-grade science exam. A couple of years later, it passes an eighth-grade science exam. What I&#8217;ve noticed is that the time constant between &#8220;it can do this&#8221; and &#8220;it can&#8217;t do that&#8221; is shrinking over time. And so I&#8217;m very bullish on AI and its ability to transform and have a profound impact on the way that companies in the United States operate, the way that we fight wars, and the way that we live our lives.</p><p><strong>Maggie 05:49</strong><br>Andrew, one of the terms that we hear a lot, both in talking with folks in primes, in the government, and at startups, is the term &#8220;software defined warfare.&#8221; What does that term mean to you, and what role do you see for startups and primes within that future vision?</p><p><strong>Andrew 06:08</strong><br>Yeah, okay, so this is an important one. One of the United States&#8217; enduring asymmetric advantages is that we can innovate faster than anyone else in the world. Full stop. We innovate faster, and that&#8217;s incredible for our ability to maintain an asymmetric advantage. So what does innovating faster look like in the midst of the Fourth Industrial Revolution? It means deploying operational capabilities in microseconds, not months. We&#8217;ve got to go from months historically, to minutes, to microseconds. Software defined warfare, to me, is all about that: how do we deploy new capabilities into the hands of the warfighter in microseconds?</p><p>A couple of real-life examples: the kill web has to turn into code. We&#8217;ve got a sea of sensors out there looking for nefarious objects, and then a tremendous number of effectors&#8212;kinetic and non-kinetic. The decision logic to connect those together has to optimize for a tremendous number of things. If you have a large number of heterogeneous incoming threats&#8212;hypersonic, class-one UAV, cruise missile, and in cases we&#8217;ve seen recently, all of them simultaneously&#8212;a modern, mature kill web will sense the incoming threats and then optimize effectors for those heterogeneous forms so you maximize your probability of kill at the lowest possible cost. The cost curve is important.</p><p>To be able to do that and adapt, as soon as we deploy a kill web it will be obsolete, because the adversary will immediately start to adapt. We have to be able to do over-the-air upgrades. Radars, electronic attack modules&#8212;these sorts of things need to be updated with new techniques and new waveforms on the fly so we can act and react faster than any adversary.</p><p>I want to give one real-world example of software defined warfare. I&#8217;m going to pull from an exercise that was recently run: Talisman Sabre, a joint exercise between the US and Australia and INDOPACOM. One of the challenges they were trying to demonstrate at Talisman Sabre&#8212;and an area where we&#8217;ve been doing a lot of work with a product called DISCO&#8212;is this: currently, from the time an adversary deploys a new RF threat, like a radar we&#8217;ve never seen before or a new jammer that&#8217;s trying to jam our communications, to the time we detect that novel waveform, classify it, and then create a new electronic attack technique to counter it, takes months. That is far too slow.</p><p>With DISCO, if the adversary comes up with a new jammer, we&#8217;re able to detect, classify, and then create a new electronic attack technique or waveform on the fly, deploy it back to the edge platform in minutes, and we&#8217;re targeting microseconds. Something that currently takes the US and our allies months, we&#8217;re trying to compress to minutes and ultimately microseconds in the electromagnetic domain.</p><p><strong>Akhil 09:38</strong><br>That&#8217;s great, Andrew, and it&#8217;s something we did in the past during the Cold War. It was the blind man&#8217;s bluff across all domains. But to your point, it&#8217;s just getting faster, and the iterative process is only accelerating. I had two questions on what you just mentioned, which I thought were great. The first is this: you see AI and novel technologies&#8212;not even novel anymore, they&#8217;re here&#8212;in the commercial space and being applied in the perception space from a computer vision standpoint or in the multimodal space. But unlike startups, you&#8217;ve seen how this needs to get deployed at scale. What are startups missing when it comes to getting some of these software-defined applications ready for production scale with thousands of camera balls or potentially hundreds of thousands of sensors, which is the ecosystem we should have?</p><p><strong>Andrew 10:29</strong><br>Yeah, it&#8217;s a great question. One of the things that we focus on a lot at L3Harris is what I&#8217;ll call missionizing capabilities. So a startup will come with a capability, like a SeaSats UAV. It&#8217;s a small UAV about the size of a surfboard. How do you take that from &#8220;this is a really capable platform&#8221; and turn it into something that&#8217;s useful to the warfighter? You have to have resilient communications, and you have to have ISR assets, meaning intelligence, surveillance, and reconnaissance. That ties back to the EO/IR balls we talked about earlier, or SIGINT detectors and similar systems.</p><p>One of L3Harris&#8217;s sweet spots, and one of the reasons we&#8217;re so excited about working with Shield Capital portfolio companies, is our ability to work with a startup to operationalize and missionize their capabilities and get them into the hands of the warfighter. That applies to hardware, such as SeaSats or APEX, which we&#8217;re also working with, and to software as well. Overwatch Imaging is a good example. The DoD has very specific rules of engagement for authority to operate and related requirements. Thinking through the pipeline from having an eye-watering, world-class capability, through the ATO process, all while having the budget to do so, is critical.</p><p><strong>Maggie 11:56</strong><br>Andrew, I wanted to ask you about Ukraine in particular. What are some of the lessons we should be learning from the conflict in Ukraine, and what are some lessons we shouldn&#8217;t be over-indexing on from this conflict?</p><p><strong>Andrew 12:12</strong><br>Oh, that&#8217;s awesome. Do learn and don&#8217;t learn. Let&#8217;s do that. And I think that&#8217;s important, because sometimes we overfitted from the Gulf Wars, and we should not remake those mistakes.</p><p>So what have we learned, or relearned, from the war in Ukraine and the conflicts in the Middle East? First, mass and cheap autonomy can win. For many years, the focus was on exquisite, low-quantity precision missiles and precision strike. Now we&#8217;ve seen first-person-view drones and Shahed-class systems that, simply because of the cost curve, present a formidable challenge. Affordable mass with autonomy is certainly important.</p><p>Electronic warfare, or EW, is decisive in modern warfare. In layman&#8217;s terms, it&#8217;s the ability to jam, spoof, and survive in a contested spectrum. Systems are being jammed into the Stone Age. One way Ukraine has overcome that with FPV drones is by trailing a fiber because they cannot communicate in these contested environments. With the right communications and resilient approaches, it is possible to burn through the jamming the Russians are putting out, but at what cost? FPV drones are cheap. A high-end radio to defeat that jamming is not.</p><p>Layered, integrated missile defense works, but it must be affordable. We&#8217;ve seen this repeatedly, whether in Iran&#8217;s attacks on Israel or heterogeneous strikes involving drones and various missile types. Integrated air and missile defense absolutely works, and the United States and our allies are learning how to optimize these systems for current threats. But again, cost matters. A multimillion-dollar Standard Missile-3 or Standard Missile-6 for a Shahed drone is not sustainable. As a nation, we have to learn to mix effects in an optimal way: high-power microwave, laser, free-space optical laser, and other options combined with exquisite missile defense. The goal is to protect critical assets with the highest assurance possible but at a survivable cost.</p><p>Next, maritime drones have changed the naval calculus off the Crimea peninsula. These low-cost USVs, essentially missionized jet skis or Sea-Doos, forced Russian ships to redeploy away from Crimea and took many out of the fight. Some were destroyed, including the flagship, and others were pushed far out. At the same time, we do not want to over-learn this lesson. What works in a confined area like the Black Sea does not necessarily translate to the Pacific or Indo-Pacific theater. In some domains, maritime drones are critical. In a blue-water fight, you have a different operational picture.</p><p>Quickly, what do we not want to learn? I&#8217;ve heard rumblings that tanks and airpower are obsolete. I do not believe that. You still have to be able to deliver mass and lead on target. Tanks are not dead, but they will die without electronic warfare cover, deception, and combined arms integrated into a sensor-saturated fight. If you deploy a tank by itself, it will die. If you provide EW and the right ecosystem around it, it&#8217;s still part of modern land warfare.</p><p>We also should not conclude that exquisite systems are unnecessary. We have learned that over-reliance on exquisite systems is brittle against cheap mass and EW, but that does not mean abandoning exquisite platforms. We need a balanced portfolio of high-end exquisite weapons and lower-end, less capable but highly cost-effective weapons.</p><p>The key to all of this, and something we&#8217;ve talked about already, is intelligence and C2. Those are what allow you to combine effects in a way that keeps things safe at the lowest possible cost.</p><p><strong>Akhil 17:01</strong><br>You talk a lot about some great lessons there, both the ones that we should emphasize and the ones we should not. There&#8217;s a lot of learning lessons, and then there&#8217;s acting upon those lessons and actually being able to implement them at scale. To you, what are some really good success stories that you hold in high regard from past history where either the US &#8212; or maybe it wasn&#8217;t the US &#8212; was able to quickly internalize a lesson and then field what was needed from a technology standpoint, integrated with what the users and operators needed?</p><p><strong>Andrew 17:31</strong><br>Yeah, it&#8217;s a good question. And, you know, we are on a modern podcast here, but I want to go back. The United States has been doing this for a long time. Back in the early 2000s, the United States was fighting wars in the Middle East, and one of the biggest issues was IEDs &#8212; improvised explosive devices &#8212; which were having an outsized toll on American and Allied soldiers and sailors. I know the US Army had a huge effort to go out there and understand: what is this threat doing, and how is it having such an impact on our soldiers in the field?</p><p>What they did was deploy the MRAP, the Mine Resistant Ambush Protected system. It&#8217;s basically like a boat, so when one of these IEDs blows up, it vectors the force of the explosion off the side of the hull. Super interesting how they did it, and it was probably one of the fastest acquisitions of a major platform the US has done in decades. The point is that there are now all these new RCOs &#8212; rapid capability offices &#8212; and DIU doing excellent work, but the United States has been doing this for a long time. When sailors or soldiers&#8217; lives are in harm&#8217;s way, we absolutely figure out how to get it done.</p><p>I do see OTAs, Other Transactional Authorities, as a great way to move fast. While the authority to use OTAs has been codified in law for a while, the department is expanding their use specifically to buy commercial platforms. This is one of the places where L3Harris really likes to partner. The Defense Department says it wants to buy UAVs, commercial UAVs, commercial drones, these commercial things &#8212; but there still has to be someone who really knows how to take that commercial thing and adapt it. In fact, Joby is a great example. They make these commercial flying cars.</p><p>Joby is a super innovative company. They build commercial flying cars, and when we talked to Joby initially, we said, &#8220;Hey, this is an awesome platform that can bring a lot of capability to the warfighter. We would love to work with you, Joby, to figure out how we put resilient comms in here so that as soon as the adversary turns on the jammers, we&#8217;re still able to establish command and control. How do we put ISR assets on there &#8212; intelligence, surveillance, and reconnaissance? How do we put things like EW payloads &#8212; electronic warfare &#8212; on there?&#8221; That&#8217;s where a partnership between companies like Joby, or more broadly other commercial capabilities, can work with L3Harris through an OTA to get really eye-watering capabilities into the hands of the warfighter more quickly.</p><p><strong>Akhil 20:27</strong><br>Thanks, Andrew. I will say, on the MRAP note and referencing Secretary Gates&#8217; book, it did sort of take the Secretary to emphasize and prioritize initiatives like that. Hopefully things have changed. I&#8217;d be curious about your perspective: have you seen structurally, sitting where you are now, that the demand signal &#8212; not just from the operator, because you&#8217;re staying in touch with what is happening there, seeing how your technology is being used and where the limits are &#8212; and then the demand signal from the voices that matter, has it improved and evolved in the way that you would like in the last 20 years?</p><p><strong>Andrew 21:06</strong><br>Yeah, absolutely. It is interesting. At the end of the Cold War, the United States and our allies had a peace dividend, and we built an acquisition system over the years that was really focused on delivering a peacetime military. What&#8217;s happened is the increasingly assertive China and a major land war in Europe that, quite frankly, a few years ago was unthinkable. I think it has forced us all to take a step back and look at whether the acquisition system, as it&#8217;s structured today, is what we need &#8212; not just because the threat is changing, but because the technology is changing so incredibly quickly.</p><p>People ask whether this is the fourth industrial revolution or just another technology wave. Why is it actually an industrial revolution? To me, it&#8217;s the pace of change that drives why it is having such a profound impact on the United States and our allies.</p><p><strong>Maggie 22:01</strong><br>Andrew, speaking of some of these acquisition trends, one of the big buzzwords we hear with respect to acquisitions and the DoD budget is Golden Dome. I know that L3Harris is intimately working in the sensor space and the space domain. I would love to get your take on what exactly Golden Dome is, what it means in the first place, and where you are seeing opportunities for startups developing new technologies.</p><p><strong>Andrew 22:35</strong><br>Yeah, absolutely. Golden Dome is super exciting. As a technologist, it is super exciting, and I think it is also super important from a national homeland defense perspective. The architecture for Golden Dome is still taking shape, or if it has taken shape, I haven&#8217;t seen it yet, but we broadly know what it looks like and what functions it will have to perform regardless of the final architecture. A key part of this is that the earlier you can detect a threat&#8212; and not just one threat but many&#8212;the better. This is going to drive space sensing and custody. Space sensing and custody will proliferate across LEO and MEO with persistent tracking on orbit, fusion, and crosslinks to do all that.</p><p>I mentioned on-orbit fusion because I think it&#8217;s really important. Historically, if you didn&#8217;t have to operate on timelines that included hypersonics and react at machine speed, you could have an on-orbit sensor that detects a missile launching somewhere, pipe that information down to a ground station, process it, and then decide what to do. Honestly, that is just too slow. There will need to be the ability to deploy things like automatic target recognition to space so you can close the kill chain more quickly. Crosslinks are really important because, preferably, we will have multiple assets tracking these missile launches, and you can improve your probability of detection and correct classification by fusing all this data together. We will see things like optical crosslinks&#8212; which are incredibly high data rate&#8212;continue to proliferate so that we can do this on-orbit fusion, classification, and detection.</p><p>We talked earlier about battle management command and control, maybe in the counter-UAS scenario, but the same thing applies to Golden Dome. You have to have a high-assurance data fabric. The foundation of that will likely be things like optical crosslinks as the physical layer. Once you have that data fabric, you must be able to do AI-assisted track correlation and discrimination. These are easy problems when there is one object in the air, but imagine thousands: some hypersonic, some decoys, some UAVs with warheads. That is why you need AI-assisted tracking and correlation to discriminate between threats, decoys, and civilian air traffic.</p><p>Once you have all that and you are connecting the data and fusing it and identifying the tracks you need to prioritize, you must be able to pair those with shooters at a continental scale. This is not just a theater anymore; we are protecting the entire continental United States, Alaska, Hawaii, and hopefully all of North America. Being able to do that sensor-shooter pairing is a non-trivial problem even for AI, especially in an environment with incredibly high state space and sometimes unreliable information. Track quality can vary, there are decoys, and quite honestly, it&#8217;s just the fog of war.</p><p>So you have to be able to sense and track and then do the sensor-shooter pairing. Once you&#8217;ve paired it to a shooter, we cannot afford to have hundreds of millions of dollars&#8217; worth of shooters, where each interceptor is super expensive. We have to have an affordable effector stack. That includes hit-to-kill interceptors&#8212; we will still have to hit a bullet with a bullet&#8212; but we also need more cost-effective layers. We will need high-power microwave and lasers, particularly for counter-UAS and counter-cruise-missile saturation, so you can use lower-cost effectors and interceptors for volume and reserve the high-end interceptors for exquisite threats.</p><p>Underlying all of this is resilient communications and PNT&#8212;positioning, navigation, and timing&#8212; all incredibly important. I cannot overstate the importance of resilient comms. Back to your earlier question about what we learned and what we should not overfit from past conflicts: one thing we overfit from the Gulf War era was the assumption that we would always have electromagnetic superiority, which means uncontested communications. That will not be the case, and we have seen this in Ukraine. We are going to have to have resilient communications, which means spread spectrum, frequency hopping, and incredibly high-end systems to maintain connectivity.</p><p>The last thing I want to mention&#8212; because I&#8217;m an engineer&#8212; is digital engineering and test. This gets to our ability to iterate more quickly. We need national-scale digital twins so we can do everything from testing to, perhaps most interestingly, training sensor-shooter pairing algorithms via reinforcement learning. You only get one chance to do this in real life, so to train these algorithms, you need to run them millions or trillions of times in simulation.</p><p>You also asked about how startups can plug in. There are tremendous opportunities. At L3Harris, we are looking for startups to plug in everywhere we are plugged into Golden Dome. Data and AI are obvious areas. AI starts and ends with data and access to data, and to the extent that startups can build capabilities for sensor fusion and discrimination, these can be microservices within a broader architecture, especially when we can provide real datasets. The same applies to training non-kinetic effectors like high-power microwave systems. There are a couple of startups actively working in high-power microwave. And, gosh, I don&#8217;t want to sound like Austin Powers&#8212; or Mr. Evil&#8212; talking about &#8220;lasers on sharks,&#8221; but high-power laser systems will be increasingly important. In the startup world, that might mean companies developing high-power laser capabilities, but there is an entire system required to actually use them. For example, beam directors: if you have a high-power laser, you then need a mirror with a steerable beam director to aim it at a target.</p><p>Digital test ranges and manufacturing technology are also important. There is opportunity across the board.</p><p><strong>Akhil 30:00</strong><br>Andrew, so many awesome things right there&#8212;I don&#8217;t even know where to start. Let me dive into a couple of them. Let me start with SCA. You mentioned the comm-resilient piece. To you, that golden dome is not new in concept, right? We&#8217;ve been talking about it; I think <em>The Economist</em> ran a piece comparing Star Wars to Golden Dome. What has fundamentally changed that might make Golden Dome different today? And is the long pole in the tent, from your standpoint, the technology, the resilient comms, or something else?</p><p><strong>Andrew 30:31</strong><br>No. So I think we have all the technology to build Golden Dome today. That is true. We have everything from solid rocket motors that perhaps could survive in space&#8212;material advancements&#8212;to the sensors we need to detect these things. Really, it&#8217;s a monumental engineering effort to create a missile defense system that covers a continent. To me, it&#8217;s probably the ninth wonder of the world. The technology is there; it&#8217;s a question of how we integrate it and whether we have the national will. It&#8217;s like the space race. It took the will of a president to get to the moon. I think similarly here, it will take the will of a president to drive this forward.</p><p><strong>Akhil 31:23</strong><br>Thanks, Andrew. And on that note, you talk about digital twins. We think of this beautiful nexus between the physical and digital world. Can you unpack a little bit what you mean by digital twin? In the news you hear about the B-21 Raider being designed in the digital world. At the same time, a lot of us who have served or worked in the automotive space know that at some point you need to get the thing out into the world because you&#8217;re not going to be able to model everything. How are you all thinking about that?</p><p><strong>Andrew 31:52</strong><br>Yeah, a couple of things. To the extent that we can use digital twins to move faster, so that you can take your lumps in ones and zeros rather than in hardware and a full redesign, that&#8217;s where we focus a lot. At L3 Harris we are laser-focused on moving faster. The Navy and other services are saying the fight is tonight, and that&#8217;s how we use digital twins.</p><p>I&#8217;ll say the most exciting place for me in terms of digital twins and simulation is how we can use them for training and fine-tuning AI models. An example is in the RF space. Cognitive EW is increasingly important. Any waveform you deploy&#8212;radar or comms&#8212;the adversary will figure out how to jam it, and they&#8217;re deploying cognitive EW so they can adapt incredibly quickly. We as a nation have to be very good at generating new waveforms, new EA and EW techniques, and so on.</p><p>Back to digital twins: as a nation, we probably need to set up an electronic warfare simulation environment. The goal is to create AI agents for electromagnetic superiority. If you have a model you want to fine-tune for this complex space of electromagnetic battle management&#8212;where you have to communicate while an adversary jams you and both sides are adapting&#8212;you need an EM playground. But EM propagation is so complex that you can never train a model at full fidelity. Even with future computing, you will never do that. So what we&#8217;ll need is a digital twin with varying resolution.</p><p>You start with incredibly coarse resolution in the simulation environment and use that to get a gross training of your model&#8212;you run it a trillion times. Then you turn up the resolution by a factor of ten and fine-tune. Turn it up again and fine-tune. You take this model that started coarse and refine it. Remember how AlphaGo Zero was trained? The first generation of chess-playing AI relied on data scientists hand-coding techniques. Then someone realized it&#8217;s more interesting to have one AI agent play another without even telling them the rules. Very quickly, by running trillions of games, it reached superhuman capability. Now my iPhone can probably beat the best chess players because of reinforcement learning in a simulated environment.</p><p>Doing the same thing in the RF space will be increasingly important as we move into cognitive EW, cognitive comms, and cognitive warfare.</p><p><strong>Akhil 34:57</strong><br>Thanks, Andrew. Real quick, for those who aren&#8217;t as steeped in EW, what is cognitive EW?</p><p><strong>Andrew 35:02</strong><br>Yeah, so cognitive EW can mean a number of things. Very roughly, a waveform is the way that I communicate in the RF spectrum, the way that I communicate with you. FM radio is an example of a particular waveform. AM radio is another. 5G is another; it&#8217;s actually a suite of waveforms. Cognitive waveforms can mean a number of different things, and you can think of them in levels. A relatively basic cognitive waveform would be a cognitive frequency hopper. Let&#8217;s imagine I&#8217;m communicating with you on a certain frequency&#8212;one megahertz, for instance. It&#8217;s not a good frequency, but let&#8217;s imagine it. If someone starts to jam one megahertz, I&#8217;m going to jump to two megahertz. If someone starts to jam that, I jump back to one. If they&#8217;re still there, I&#8217;m going to jump to three. So the most basic cognitive EW involves clever ways to do frequency hopping and clever ways to do your modulation. I might switch from AM to FM, for instance. That would be your lowest-level cognitive waveform.</p><p>Some of the higher-end stuff&#8212;let&#8217;s call them generative waveforms&#8212;allow you to create the waveform on the fly, just like generative AI creates a poem on the fly that is optimized for whatever you want to optimize for. In this space, you can say, &#8220;I want to optimize for throughput given this specific jamming environment,&#8221; or, &#8220;I want to mimic 5G or Wi-Fi and hide in the noise.&#8221; Because generative waveforms leverage the most advanced AI, you&#8217;re able to change the objective function and do essentially limitless things with it. I&#8217;ve seen tests where these cognitive waveforms are able to outperform classical waveforms in very harsh jamming environments.</p><p>The reason they aren&#8217;t deployed to the edge right now is that they are incredibly compute-intensive. It takes quite a bit of compute to do this. But as compute cost comes down, I expect to see these deployed more and more&#8212;probably first through SOCOM and other early adopters, and then more broadly across the U.S. as cognitive waveforms and cognitive EW mature.</p><p><strong>Maggie 37:30</strong><br>Andrew, I want to shift gears a little bit and specifically talk about how you view startup&#8211;defense prime collaboration. I know L3Harris has really been a leader in this, and it has become a big part of your strategy as the trusted disruptor in the defense space. So maybe the first question I&#8217;ll ask is: where do you see opportunities for startups to really excel, versus what kinds of technology areas do you think defense primes will continue to remain dominant in?</p><p><strong>Andrew 38:06</strong><br>Yeah. I&#8217;ll say that defense primes, and where I put all of my cycles as the CTO of L3Harris, are focused on operationalizing AI. There&#8217;s some really interesting space here where the U.S. technology ecosystem, including venture-backed companies, can work with the larger primes. Why is this a good marriage? L3Harris is really good at having exquisite domain expertise. We spend a lot of time in customer spaces understanding their hardest challenges. We tend to have access to a lot of data&#8212;we build EO/IR balls, we build radars, we build radios. All this data can be used to take a model or a capability developed by a startup or partner and fine-tune it for a mission application.</p><p>The final thing we have as defense primes is real estate. I helped stand up and was part of one of the premier divisions in the National Lab system that does AI&#8212;the AI and Data Analytics Division at Pacific Northwest National Labs. They&#8217;re great at AI for national security and high-consequence environments. They have some of the world&#8217;s best data scientists and data engineers. Their challenge is access to real estate and access to operational systems. If you&#8217;ve got models, whether they&#8217;re coming out of the national labs or the venture tech ecosystem, you have to have places to actually deploy those so they can start to have an impact on the warfighter.</p><p>Missionizing AI requires us to be really good at selecting the right model. Not every use case is an AI/ML use case. So we need to be good at determining which startup model, open-source model, or partner model we want to adopt, how we fine-tune that model with real operational data, and then how we get it through the ATO process so that we can actually deploy it to the edge. Deployment to the edge is sometimes non-trivial. This is where Code Metal is helping us. It&#8217;s pretty easy to deploy AI to GPUs. It&#8217;s less easy if you&#8217;re in a SWaP-C&#8212;size, weight, power, and cost&#8212;constrained environment with only access to FPGAs. These systems need to be very power conscious because you&#8217;re on the edge, on a radio a soldier has to carry for 10 hours&#8212;or really 10 days. It has to operate for those 10 days. Imagine if your iPhone lasted for 10 days. I&#8217;d be much happier.</p><p>Code Metal helps us translate code from Python or MATLAB into embedded code on the edge&#8212;FPGAs and similar hardware. That&#8217;s where primes like L3Harris and others are focusing: operationalizing AI. Startups, on the other hand, bring novel AI/ML, edge autonomy stacks, and synthetic data generation. These are spaces where there have been tremendous commercial investments in Silicon Valley and the U.S. technology ecosystem. If you&#8217;ve got novel models, particularly ones that could work in SWaP-C environments, we&#8217;d love to talk and figure out how we can start the process of missionizing and operationalizing them.</p><p><strong>Maggie 42:00</strong><br>Andrew, how do you all determine when you&#8217;re going to partner with another company or startup versus when you&#8217;re going to build some of that technology in house? I know L3Harris has what, 10,000 engineers or something employed?</p><p><strong>Andrew 42:15</strong><br>Twenty thousand engineers. Yeah. And so it&#8217;s a good question. All right, so we would always rather accelerate, accelerate, accelerate. And the way that I look at partnerships with startups is that we have technology roadmaps, and our technology roadmaps actually don&#8217;t start with technology. If anybody starts talking to me about technology for a technology roadmap, they&#8217;re wrong. You start with a mission. These are the hard problems that we at L3Harris want to be able to contribute to. So that&#8217;s one end of the bound. The other end is what technology we have today, meaning L3Harris capabilities that we have right now. From that, I&#8217;ve got two endpoints. I&#8217;ve got the mission, the customer problem we&#8217;re trying to solve, and the technology we have today. That&#8217;s the gap. If there is a company that can accelerate the closure of that gap, then I absolutely want to talk to them today.</p><p><strong>Maggie 43:06</strong><br>What do you see startups most misunderstand about working with a large defense prime like L3Harris?</p><p><strong>Andrew 43:14</strong><br>Yeah, I think there&#8217;s sometimes a misperception that large defense primes don&#8217;t want to go fast. And to be honest, a company as large as L3Harris is not a monolith. There are parts that will still be slow, but by and large, we care about exactly the same things as everyone else in this ecosystem. We want to go fast and hard and solve hard problems. From the flip side, if I take that question from the other angle, I get a lot of misperceptions from my engineers about startups. Some of the misperceptions they have come from engineers who, particularly if they&#8217;ve never worked in a startup, see a startup almost as a supplier. The startup brings a widget, and the engineer says, this is five degrees off from the widget that I needed, sorry, don&#8217;t want to talk to you. What they don&#8217;t realize is that if they just engaged a little bit with the startup, the startup would be more than happy, on an incredibly short timeframe, to shift that five degrees and build something that is absolutely applicable to the problem the engineer is trying to solve, that gap they&#8217;re trying to close. A lot of my internal work at L3Harris is helping engineers understand that you&#8217;ve got to invest your time in startups so they understand the problem you&#8217;re really trying to solve. You also have to be conscious of their time horizon. If you&#8217;ve got a pursuit where it&#8217;s going to be a problem in three years and you&#8217;ll finally get money for it in eight years, that is not an appropriate place to engage a startup. So we have to be aware of what problems are amenable to startups in terms of what a startup&#8217;s traditional run rate is.</p><p><strong>Maggie 44:58</strong><br>What advice do you have for startups to work with a company like L3Harris? What can a startup do well, or what have you seen startups do well? Sort of the flip question to what I asked before, which is what do they not do well?</p><p><strong>Andrew 45:10</strong><br>Agreed. So startups that do well, and this is sort of the flip-side answer, are adaptable and willing to fit into, and I&#8217;m not going to say the L3Harris need, but the customer and mission need. That adaptability is incredibly important. I think it&#8217;s actually inherent in most startups&#8217; DNA. They don&#8217;t run agile. If you talk to a founder about agile, they&#8217;ll hit you. It is pivot, pivot, pivot until you find product-market fit. I would advise that startups not confuse a great demo with a deployable capability. You have to understand your concept of operations but also your concept of employment. Give us a call and we will help you understand the concept of employment. A lot of startups don&#8217;t have access to SCIFs and high-side information, so we can help shape your product in appropriate ways so that it is actually solving the problem the warfighter has and addressing the threat they&#8217;re facing.</p><p><strong>Akhil 46:20</strong><br>Thanks, Andrew. Maybe to flip it again, there&#8217;s a perception in certain spaces that the primes are like the Evil Eye of Sauron. They&#8217;ve existed for a while, they&#8217;re there. But I think there&#8217;s this interest from startups in some of the points you&#8217;re bringing. There&#8217;s also real value in finding the right partnerships at the right time and place to achieve effects ultimately for the mission. My question is, if you&#8217;re a startup, how should you be evaluating and what should you be expecting out of a partnership with someone that&#8217;s a lot bigger than you, who may have a direct relationship with the customer, when even the startup wants that direct customer feedback and engagement? How do you navigate the limited time a young startup has in finding which partnerships make sense and which ones are actually going to drive value across both organizations, and ultimately for those who need it most from a mission standpoint?</p><p><strong>Andrew 47:17</strong><br>Yeah, absolutely. I think you&#8217;re looking for partners who are interested in a true strategic partnership as opposed to a transactional relationship. That is really important. When you talk to various primes, make sure they&#8217;re willing to invest their time in you. I&#8217;ll give you an example. At L3Harris, we have internal money that we use to run things we call validation projects. If you come in, Akhil, and you&#8217;ve got a novel widget that you&#8217;ve invented or a software app, we invest our own money at L3Harris to figure out how that app can be used to fill one of those gaps I talked about to solve a hard customer need. That&#8217;s an example of a strategic relationship where we&#8217;re investing in the relationship, you&#8217;re investing in the relationship, and together we&#8217;re able to move faster and solve harder problems than we&#8217;d be able to do individually. I&#8217;m really looking for that. A lot of times when primes engage with startups&#8212;and I haven&#8217;t seen this at L3Harris, but I have seen it elsewhere&#8212;they want to be a bully around IP rights, like &#8220;We want to own IP rights.&#8221; What they don&#8217;t realize is that absolutely kills the startup. It makes them unappealing to investors. So watch your IP rights. Make sure the prime you&#8217;re working with is looking to generate mutual value for the prime, for the startup, and for the customer, and not just for themselves.</p><p><strong>Maggie 48:48</strong><br>If you had all the CEOs and CTOs, the senior leadership of other large defense government contractors, in a room, what advice would you give them?</p><p><strong>Andrew 48:58</strong><br>The first thing is definitely focus on open systems. The reason this is important is that the United States&#8217; asymmetric advantage is our ability to innovate faster, and open systems&#8212;while they take a bit more time up front&#8212;really open up their architecture on the back end. If some startup comes up with a new capability, because it&#8217;s an open architecture they&#8217;ll be able to plug it in quickly, get it operationalized, and make a real difference. Whereas if we have a closed ecosystem where everybody owns their own IP and data rights and nothing plays well with each other, we&#8217;re never going to get to that future where we&#8217;re able to rapidly deploy capabilities and iterate more quickly than adversaries.</p><p><strong>Akhil 49:47</strong><br>Andrew, maybe one level deeper on open architecture: is the government providing the right incentives for that ecosystem? And what would be the one policy change you would make? When you think about modular open architecture, people are trying to build a business that&#8217;s defensible and not dependent on year-to-year uncertainty about whether their system will survive. There&#8217;s a healthy tension between what a company needs to defend its position and what&#8217;s required to provide value and create the right incentive structure. How do you see that?</p><p><strong>Andrew 50:18</strong><br>I would say I&#8217;m never worried about defending anything. If you have to defend based on a closed architecture, then you&#8217;re not moving fast enough. Our strategy is to continue to move faster than anybody can adopt, and we will continue to do that. You also need to really understand where you make your money. You make your money off your implementation of the open architecture. Waveforms are a good example&#8212;we&#8217;ve talked a lot about communications waveforms. Many of them are open; they are government-owned protocols. That doesn&#8217;t mean L3Harris doesn&#8217;t make money off them. We still take that waveform, translate it into software, implement it on hardware, and sell an operational capability. Open architecture doesn&#8217;t mean you can&#8217;t make money.</p><p>What we need more of from our customers is consistency. Probably 90% of customers say &#8220;open architecture, open architecture, open architecture.&#8221; There&#8217;s a vocal 10% who say, &#8220;Well, with closed architectures we can go faster,&#8221; because they see the upfront initial investment&#8212;maybe you&#8217;re 10% slower&#8212;as the impediment. But let&#8217;s look at a concrete example. We talked about tanks earlier. You could create a tank that is a completely closed system. You don&#8217;t allow anyone to plug in a new EO/IR ball, nobody can plug in a new communications module. You can do that faster; you can deploy a closed ecosystem right now.</p><p>But let&#8217;s say you spent a little more time and built this on an open architecture, which means you can switch out modules. As a new radio comes online, one of these cognitive radios or cognitive EW systems, you just take out the old one and put in the new one. That could come from the startup ecosystem or from a traditional defense contractor. A new radio comes online, a new EO/IR ball comes online, and it allows a much faster upgrade cycle. In this tank example, you can see how the proponents of closed systems are right that you can get a fixed capability to the field more quickly, but the long-term ability to iterate and upgrade is far better with an open architecture.</p><p><strong>Maggie 52:31</strong><br>What&#8217;s a technology that you are bearish on in the short term but bullish on in the long term?</p><p><strong>Andrew 52:37</strong><br>All right, I did mention high-energy lasers and HPM earlier. There is still a way to go before those are real operational capabilities. I think everyone&#8217;s seen a couple of interesting prototypes and examples where people have shown, hey, we&#8217;re able to kill a UAV or do some other interesting things. Today, weather, power, and beam control are the limiting factors. In the future, these will be indispensable for a layered, cost-effective defense. The other is quantum. People tend to think about quantum in three buckets: quantum sensing, quantum communications and networking, and quantum computing. At some point, quantum systems such as quantum sensing with Rydberg atoms are going to far outperform RF antennas and RF capabilities for sensing, comms, and SIGINT. In the near term, though, I don&#8217;t see an impact in the next five or six years. So again, bearish in the near term, but long term these things are going to be differentiators and game changers.</p><p><strong>Maggie 53:41</strong><br>And I know you&#8217;ve been in the national security technology space for decades now. What&#8217;s the technology that you thought would be further developed than it actually is today, back in your days at MIT or one of the labs or elsewhere?</p><p><strong>Andrew 53:56</strong><br>The technology that I thought would be further along is true CJADC2. For those of you in this field for a while, it was net-centric warfare before CJADC2, and before that it was something different. We still fight in data silos with bespoke messages more than we should. Really being able to bring that &#8220;any sensor and every shooter, every sensor and any shooter&#8221; capability to the battlefield&#8212;I thought we&#8217;d be further along. It&#8217;s been a huge focus for the DoD for at least two decades, and I hope we continue to make progress around true CJADC2. Less developed but pleasantly surprising is autonomy at the edge. Small teams are absolutely deploying incredible capabilities. Everything from&#8212;gosh&#8212;we talked about Overwatch AI to Shield AI (not to be confused with Shield Capital) to Overland AI. These are just incredible advances in true autonomy at the edge. What are some tech&#8212;</p><p><strong>Maggie 55:02</strong><br>&#8212;areas where our adversaries are ahead of us in developing and deploying, and what will it take for the US to catch up?</p><p><strong>Andrew 55:13</strong><br>One place I&#8217;ll point out is hypersonics and long-range strike. So PRC and Russia&#8212;munitions like the DF-17. I will say that the United States, and we here at L3Harris Aerojet Rocketdyne, have eye-watering, exquisite hypersonic capabilities, with the ability to do computational fluid dynamics and advanced materials. The United States does have some incredible hypersonic capability. That said, in deployed, operational hypersonics, we are behind. We are absolutely behind. That&#8217;s the space where we want to keep up. Shipbuilding and the industrial scale and industrial might that China is able to bring to the table&#8212;our fleet growth is currently being outpaced by large numbers. Tactical electronic warfare&#8212;actually, I&#8217;ll lump these next two together: tactical electronic warfare and low-cost drone ecosystems. Currently, Russia is beating us there, and it&#8217;s largely because they&#8217;re actively engaged in a war in Ukraine. What this does for them is tighten their learning loop. They deploy an EW technique or system, and if it doesn&#8217;t work they are forced to continue to update and cycle it. Our EW capabilities aren&#8217;t nearly on the war footing that Russia&#8217;s are.</p><p><strong>Akhil 56:36</strong><br>Thanks, Andrew. I want to end where we started, with you being a technologist. If you had one extra hour in your busy day&#8212;you&#8217;ve got a ton of things, the leadership aspects of running the organization, the connecting-the-dockets piece, and then somewhere in there you get a chance to vibe code&#8212;what would you spend that extra hour doing, and how would you break that apart?</p><p><strong>Andrew 57:00</strong><br>You know, I think as technologists it&#8217;s easy to become enamored with the technology, and I spend an incredible amount of time, like I said, even developing my own models. If I could find an extra hour, I would spend that time with the operators, with the people who are actually using the technology. At the end of the day, as a CTO and technologist at L3Harris, I believe every engineer at L3Harris is here to solve hard customer problems. The better understanding I can have&#8212;and that every engineer can have&#8212;of what those problems are and how we might be able to solve them more creatively, the better.</p><p>I was recently talking with a customer, and they said, &#8220;Hey, Andrew, I just need more bandwidth. I need more throughput on these radios.&#8221; We talked for a little bit, and it turns out that&#8217;s not actually what the customer needed. They needed the right information at the right place at the right time. That drives you to think: yes, I could give you a radio with a bigger power amplifier and make this poor soldier carry around a big dish antenna. Yes, that could be a solution to that problem. But because we sat down and talked and understood the problem and the threat they were facing, it turns out the right answer is deploying intelligent agents to the radios to prioritize the data so they&#8217;re getting the right information at the right time to provide decision and information advantage. More time with the customer, more time understanding what they&#8217;re facing and what their threats look like so we can create better solutions&#8212;that&#8217;s where I&#8217;d spend my time.</p><p><strong>Akhil 58:25</strong><br>Awesome. Andrew, thanks so much for joining us.</p>]]></content:encoded></item><item><title><![CDATA[🎙️ Ep 10 - How Missile Defense Actually Works]]></title><description><![CDATA[Former MDA head explains Golden Dome, command and control, startups, and more]]></description><link>https://maggiegray.us/p/ep-10-how-missile-defense-actually</link><guid isPermaLink="false">https://maggiegray.us/p/ep-10-how-missile-defense-actually</guid><dc:creator><![CDATA[Maggie Gray]]></dc:creator><pubDate>Tue, 04 Nov 2025 16:24:49 GMT</pubDate><enclosure url="https://api.substack.com/feed/podcast/177913777/51cc67cbfefb1c80ec6f12e86e72735e.mp3" length="0" type="audio/mpeg"/><content:encoded><![CDATA[<p>There&#8217;s a lot of buzz these days around the future of missile defense, but not much discussion around how missile defense actually works. In this episode of the Mission Matters podcast, Matt and I sit down with Shield Capital Operating Partner and former Director of the Missile Defense Agency, LTG (ret.) Pat O&#8217;Reilly, to discuss the current state of missile defense and how it actually works. </p><p>We cover:</p><ul><li><p>How missile defense actually works, breaking down a) the threats b) the kill chain and c) firing doctrine</p></li><li><p>How missile defense has changed over the last several decades</p></li><li><p>The role of startups and emerging technologies in the future of missile defense</p></li><li><p>The state of our adversaries&#8217; missile and missile defense systems</p><p></p></li></ul><p>You can listen to the podcast on <a href="https://open.spotify.com/episode/6BjKYK4hhKSs09RaQVfuW3?si=7CW6ThJFRoOcYaEk21nYhw">Spotify</a>, <a href="https://youtu.be/4Y9UhewSsIo">YouTube</a>, <a href="https://podcasts.apple.com/us/podcast/how-missile-defense-actually-works/id1807120572?i=1000735228827">Apple</a>, <a href="https://shieldcap.com/episodes/missile-defense">the Shield Capital website</a>, or right here on Substack.<br><br>As always, please let us know your thoughts, and please reach out if you or anyone you know is building in the national security domain.</p><p></p><p class="button-wrapper" data-attrs="{&quot;url&quot;:&quot;https://maggiegray.us/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe now&quot;,&quot;action&quot;:null,&quot;class&quot;:null}" data-component-name="ButtonCreateButton"><a class="button primary" href="https://maggiegray.us/subscribe?"><span>Subscribe now</span></a></p><div><hr></div><p><strong>Transcript</strong></p><p><strong>Maggie 00:04</strong><br>In this episode of the <em>Mission Matters</em> podcast, we sit down with Shield Capital Operating Partner, Lieutenant General Pat O&#8217;Reilly, to discuss missile defense. Previously, Pat served as the three-star general in charge of the Missile Defense Agency, the Pentagon&#8217;s inter-service organization responsible for U.S. missile defense. Before that, Pat had a long career in missile defense. He was the program manager for several key U.S. missile defense programs, including THAAD, National Missile Defense, Aegis, Directed Energy, PAC-3, and radars and space assets.</p><p><strong>Matt 01:10</strong><br>Missile defense is a very popular topic of conversation in national security circles these days, primarily because of the Trump administration&#8217;s announcement for a Golden Dome, which is an air and missile defense system that would shield the U.S. from any threat.</p><p><strong>Maggie 01:26</strong><br>Yeah. I mean, I feel like every single time I go to D.C., it&#8217;s basically inescapable at any space event from hearing the words &#8220;Golden Dome.&#8221; But I don&#8217;t know, Matt, what do you think? Do people actually have a good understanding of what this might actually mean?</p><p><strong>Matt 01:40</strong><br>Well, before we did this interview, I certainly had gaps in my knowledge about missile defense and what a Golden Dome architecture could look like or cost. And when we started preparing for this interview, we realized just how complicated missile defense really is and how little we really knew about it. One important thing that I now better understand is just how difficult missile defense is to get right. It entails thousands of exquisite technologies working together perfectly for a span of a few very crucial seconds. Our missile defense posture today has roots not only in those technical challenges and what&#8217;s technically possible&#8212;it&#8217;s also been shaped by wider national security policies dating back to the Cold War. And I think those Cold War policy frameworks are still really important for understanding the state of missile defense today.</p><p><strong>Maggie 02:31</strong><br>Yeah, I will say Matt and I are both giant history nerds, so I always love to be able to dig back into Cold War history to understand why our systems are the way they are today. I&#8217;ll start by saying, you know, today, the U.S. really does not have a fully comprehensive air and missile defense system. The major policy framework that&#8217;s guided U.S. missile defense capabilities was the Anti-Ballistic Missile, or ABM, Treaty, which was signed by the United States and the Soviet Union back in 1972. The ABM Treaty restricted both countries from actually deploying anti-ballistic missile systems with the goal of preventing further acceleration of the nuclear arms&#8212;</p><p><strong>Matt 03:12</strong><br>Race. Wait, Maggie, can you explain that? Why would a treaty aimed at preventing an acceleration of the nuclear arms race focus on preventing countries from building up their defensive systems?</p><p><strong>Maggie 03:26</strong><br>Yeah, I think the idea here is that whenever one country built up defenses, another country would build up more missiles in order to actually counter those defenses. So it&#8217;s sort of an arms control treaty in reverse&#8212;that by preventing you from building defenses, it actually disincentivizes me from building more arms in the first place. The idea was that if neither country could defend against the other&#8217;s stockpile, neither would need to develop dramatically more missiles. But the U.S. ultimately pulled out of that treaty in 2001, as other countries like Iran and North Korea started developing their own ICBMs and nuclear programs, and the United States wanted to make sure we could defend against those systems with our own anti-ballistic missile systems.</p><p>So really today, the way to think about it is our system is designed to counter rogue threats&#8212;that is, a few missiles launched from Iran or North Korea, or a non-state actor, or maybe even an accidental launch from a larger power like Russia or China. But our system is not designed to counter a full-scale attack from a major peer adversary. Instead, we really have to rely on our nuclear deterrent to protect against a full-scale nuclear war.</p><p>So that takes us to Golden Dome. Today, a major part of Golden Dome&#8212;I think it&#8217;s actually officially called Iron Dome for America&#8212;is to be able to defend against any threat, whether that is a nuclear launch from China or a small drone launched by a cartel across the border. And in order to actually build out a system that really achieves those goals, it&#8217;s going to require new capabilities&#8212;and some capabilities that have never been deployed at scale before, like space-based interceptors.</p><p><strong>Matt 05:08</strong><br>And we&#8217;ll get into Golden Dome and space-based interceptors and some of these new capabilities. But first, in this episode, in order to understand what the future of missile defense might hold, we actually start with the fundamentals of missile defense. So first, we ask Pat about the types of missiles we defend against, different phases of a missile launch&#8212;including when a missile would be most vulnerable to being defended against and intercepted&#8212;and what missile defense systems we have to respond at each stage of a launch.</p><p>We talk about the different types of defensive systems, including both kinetic and non-kinetic&#8212;that&#8217;s interceptors versus directed energy&#8212;and we cover the core technologies that make missile defense possible along the entire kill chain: how we characterize threats with sensors, algorithms for sensor fusion, and choosing what we want to protect and prioritize with both human and automated decision-making.</p><p>Then we talk about why missile defense is so hard. We hinted at that earlier, with all the technologies that have to work well together and the idea of Golden Dome, including new capabilities like space-based interceptors. We conclude by discussing what technologies are still needed to improve and modernize missile defense and where startups and other innovative solutions can help.</p><p>And as we said before, throughout the conversation, we gained a much better appreciation for how complicated and difficult missile defense truly is to get right. We hope our viewers and our listeners do too. We&#8217;re incredibly grateful to Pat&#8212;one of the world&#8217;s leading experts in missile defense&#8212;for taking the time to explain to novices like us and our audience.</p><p>Now, on to the show. Pat, thanks for being here. You had a storied career in missile defense within the Army. How does one even get into missile defense? Did 18-year-old Pat know that he was going to start a long career working on missile defense issues when he started at West Point?</p><p><strong>Pat 07:01</strong><br>Actually, no&#8212;and thanks for having me here. But to answer your question, you know, in the Army, you&#8217;d see the old saying, &#8220;You do what you&#8217;re told to do.&#8221; And I had just finished teaching physics at West Point as a captain, and the next thing I knew, I was in an organization called the Strategic Defense Initiative Organization in the Pentagon in 1989. That was started by an initiative from President Reagan, and the Army did not have enough officers participating. So overnight, I found myself in the SDI Organization without any training or background. That&#8217;s how I got started, and I literally was the junior person in the entire organization.</p><p><strong>Matt 07:53</strong><br>Can you walk us through how you went from being the junior person in the entire SDI Organization to being the senior-most person in all of U.S. missile defense at MDA?</p><p><strong>Pat 08:04</strong><br>Well, like everything, things are controlled by Congress. I went to work one day and found out that the directed energy program that I was the program manager of had lost all its funding overnight. So then I went down the hallway and literally knocked on 100 doors to see if anybody needed help. There was a program called THAAD at the time&#8212;Theater High Altitude Area Defense&#8212;that was short some people, and I ended up working in theater missile defense. That&#8217;s how I shifted from my physics background and directed energy to missile interceptors.</p><p><strong>Maggie 08:46</strong><br>So, Pat, I want to start off just asking a basic question. You know, I think Matt and I seem to see missile defense everywhere these days. It&#8217;s in policy discussions in D.C., it&#8217;s in every other pitch deck&#8212;I feel like we see it especially in the space domain. But what are all the actual moving parts of missile defense? It&#8217;s a really complicated system. Can you just break down what actually <em>is</em> missile defense?</p><p><strong>Pat 09:15</strong><br>It actually is extremely complicated. There are thousands of technologies literally working together in real time for these systems to work. It can be greatly simplified, and I always recommend looking at it from three perspectives. One is the class of missile that you&#8217;re trying to engage. The second is the kill chain, or sequence of actions that are required to happen in order to destroy a missile. And then the third piece is the firing doctrine you use. So, with those three in mind, you can set up a framework that makes it much easier to understand what does and does not work for missile defense. I just want to comment up front: a lot of times, air defense, which is focused on anti-aircraft and drones, is intermixed with cruise missile defense, which is specific for cruise missiles, and that is also integrated into discussions about missile defense. Those are three different military capabilities, and they require different firing doctrines, different technologies, and different threats.</p><p><strong>Maggie 10:32</strong><br>Maybe we could start with that first piece. What are the different kinds of missiles we might be defending against in the first place?</p><p><strong>Pat 10:40</strong><br>There are two basic classes of these missiles that we&#8217;re most concerned about. There&#8217;s the ballistic missile, which, by basic physics, means that after it&#8217;s been launched and the booster burns out, it then coasts to its target. If it&#8217;s short range, it might be a 15-minute flight. If it&#8217;s a long ICBM, it could be over 30 minutes of flight, but it is just coasting, and it&#8217;s following basic rules of physics and Kepler&#8217;s laws, or laws of orbital mechanics. So you can pretty well predict where they&#8217;re going to go at any point in time. The other class of threat missile is the maneuvering threat, and they actually have either control surfaces or they have different types of propulsion systems on board that can steer them during flight. So it is very hard to predict where they&#8217;re going to be at a certain point in time. Hypersonic missiles that you hear a lot about today are that class of missile. But I will point out maneuvering RVs were introduced by the Russians, or the Soviets actually, in the 1970s, and since then they have been very hard missiles to intercept, because it&#8217;s unpredictable what their path is. Each missile characteristic, or a missile, is categorized by its range. You have short-range missiles that are 300 to 1,000 kilometers, intermediate-range missiles which are 2,000 to 5,500 kilometers, and strategic missiles are missiles that travel greater than 5,500 kilometers. There&#8217;s a reason they&#8217;re broken into those three categories. Number one is the speeds and the altitudes: are they flying inside the Earth&#8217;s atmosphere? Short-range typically fly inside the Earth&#8217;s atmosphere. Intermediate-range leaves the atmosphere, sure, short for a short period of time, and then it re-enters, and a strategic missile spends most of its time outside the Earth&#8217;s atmosphere. You will often ask, &#8220;Well, what about 1,000 to 2,000 kilometer missiles?&#8221; The reason they&#8217;re not covered typically is there was a treaty between the United States and Russia, and the Soviet Union for many years, that banned intermediate-range missiles. So there was very little development done in those areas, and typically the missiles today&#8212;there are very few that are in that range.</p><p><strong>Matt 13:22</strong><br>Just to clarify: you mentioned earlier ICBMs &#8212; is that the same thing as strategic or 5,500-kilometer-plus range missiles?</p><p><strong>Pat 13:32</strong><br>Yes. A strategic ICBM is a strategic missile. It&#8217;s given that range because it&#8217;s traveling between seven to ten kilometers a second, and that requires a completely different set of technologies.</p><p><strong>Matt 13:48</strong><br>You also mentioned cruise missiles earlier. Are cruise missiles part of these categories you described, or are they not considered under the same missile defense?</p><p><strong>Pat 14:00</strong><br>They actually have their own class of weapon system, because they&#8217;re so unique in having maneuvering airborne capability at the same time as the speed and the ranges of a missile. So cruise missiles are considered separate.</p><p><strong>Matt 14:18</strong><br>Got it. When we talk about missile defense, we&#8217;re talking about ballistics and hypersonics.</p><p><strong>Pat 14:22</strong><br>You&#8217;re talking about, yes, ballistic and maneuvering missiles of those three ranges: short, intermediate, strategic. Yes.</p><p><strong>Maggie 14:31</strong><br>And now, can you talk a little bit more about that second piece you mentioned, which is the kill chain and command and control?</p><p><strong>Pat 14:38</strong><br>Yes, the kill chain is made up of five different components. First is the sensor, which initially identifies a threat &#8212; a missile has been launched &#8212; and then starts to track that missile so that over time it can actually predict where that missile is going, especially if it&#8217;s a ballistic missile. Those sensors can be land-based, maritime, or space-based. An important part that&#8217;s often overlooked is the communication between these different components: they have to be secure, real-time communications that can handle a lot of data. The third piece is the battle management and control system. That&#8217;s the overall system that pairs together weapons systems to a particular threat missile that has been launched. The reason that is so important is, as I go back to what I said before, the ranges travel at different speeds and they have different signatures and so forth. Because of that, the interceptor must be paired so that it matches the type of capabilities that the range of the threat missile will have. For example, if you fire a short-range missile, that means it&#8217;s traveling most of the time through the atmosphere, so an exo-atmospheric interceptor would not have much capability. Therefore, you marry the Patriot system and the SM-2 missiles, which are built and designed to travel primarily in the Earth&#8217;s atmosphere. The intermediate-range missiles require a THAAD system or an SM-3 missile that is designed to travel at higher velocities, has more maneuverability, but operates in the upper atmosphere. And then the strategic missiles require a ground-based midcourse defense interceptor, which is designed to operate in outer space and literally can maneuver many kilometers in order to be able to hit something traveling at 10 kilometers a second. So the important point is to note that if you mix these up, you cannot be very effective: an intermediate-range threat missile, for example, would not be effectively countered with a Patriot system; a THAAD system wouldn&#8217;t be very effective against a strategic missile; and a strategic interceptor in GMD would not work well against the short range. So it&#8217;s very important that they keep track of what the inventory is, what the threats are, and which weapon system is being paired to which sensor or threat missile. Then, besides C2BMC, once that pairing has occurred, it then hands off the mission to the weapon system in order to allow a fire-control solution to be developed, and then that fire-control system is uploaded into the interceptor. The interceptor is launched; it has to take into account the flight time of the interceptor as well as the closing velocity and the flight time of the threat missile. What&#8217;s really important here is the concept of what we call the error basket. The error basket means we&#8217;ve tracked the threat missile and we can predict it to a point where we are able to fire an interceptor into this &#8212; as you could imagine &#8212; a basket, a three-dimensional basket in space, and that interceptor is flying towards that basket. By the time the threat missile arrives, the interceptor should be in the same location with enough maneuvering capability to counter any errors that occur in that trajectory prediction so that it can steer itself to an actual intercept. It&#8217;s quite amazing, because you&#8217;re intercepting something with closing velocities typically above five kilometers a second, and the size of a threat missile &#8212; if you look at them in the press or on TV &#8212; you&#8217;re trying to hit something that&#8217;s less than three feet across, and they&#8217;re trying to hit it from often launch points that are five to six thousand miles away. So this is a remarkable amount of technology that has to work in a precise way in order for that intercept to happen. And the final step of the kill chain is the kill assessment. It&#8217;s extremely important to determine whether or not you hit the target or whether you have to fire another missile at it. This becomes complicated when you have multiple threat missiles being intercepted in a close location because the destroyed missiles&#8217; debris is flowing in front of other missiles that are still coming in. So that&#8217;s quite a challenge to complete the kill assessment, but it&#8217;s extremely important. So that&#8217;s the kill chain &#8212; each one of those five steps.</p><p><strong>Maggie 20:06</strong><br>And maybe one quick question about the different kinds of interceptors. I know we&#8217;ve talked about this. There&#8217;s both kinetic interceptors and also some of these non-kinetic or directed-energy interceptors. Could you talk a little bit about those different approaches?</p><p><strong>Pat 20:24</strong><br>Yes. Well, the kinetic interceptor is extremely complex, but the technology is in hand in order to launch missiles. You do have to take into account the battle management, the firing doctrine, the flight time, the control of the missile, what altitude the intercept is coming at &#8212; all of that has to be calculated, and the interceptor has to be flown in a precise way in order for an intercept to happen. A directed-energy system obviously moves at the speed of light, and because it&#8217;s moving at about 186,000 miles a second, the fire control is much simpler. When you hit a missile, the nice part about a directed-energy system is you may not destroy it, but you may disable it. The beauty of that is that then it doesn&#8217;t break up and cause debris that makes it harder to hit other inbound threat missiles in the local region. So there&#8217;s a lot of benefit with directed energy. The issue has been developing that technology: getting ranges through the Earth&#8217;s atmosphere of hundreds of kilometers or longer, and the power required if you base it in space &#8212; how do you get that much laser or high-power microwave power in space? Those are all still technical challenges that have not been overcome.</p><p><strong>Matt 21:55</strong><br>So today are we mostly using kinetic interceptors, then, rather than directed-energy solutions? Or is it a mix? You mentioned the technology is not fully, fully ready on the directed-energy side.</p><p><strong>Pat 22:10</strong><br>For missile defense, it&#8217;s 99% kinetic interceptors.</p><p><strong>Matt 22:16</strong><br>And just one follow-up on something you said. You mentioned that if a kinetic interceptor intercepts a missile, it creates debris that makes it harder for future interceptors to intercept other missiles. Can you talk more about that? Why does it make it harder for other interceptors to work effectively?</p><p><strong>Pat 22:35</strong><br>Because it&#8217;s creating a shield of debris that, if you&#8217;re a radar/RF, acts as what we call chaff, and it causes reflections back and makes it very difficult to see through that chaff to determine where the actual oncoming missiles are that haven&#8217;t been intercepted yet.</p><p><strong>Maggie 22:59</strong><br>One more clarifying question on the world of the kill chain. Could you tell us a little bit more about the different kinds of sensors that we use to actually track these threats? Then how do we take the data from all these different sensors and actually make sense of it in the first place?</p><p><strong>Pat 23:16</strong><br>That&#8217;s one of the greatest challenges of missile defense, and it&#8217;s been focused on for decades: how to take not only different sensors, but each sensor has its own angle of looking at the threat target. Each sensor has a different spectrum it&#8217;s usually looking at, even the way the data is transmitted &#8212; it has different formats. Most of these sensors were either strategic or they&#8217;re airborne or they&#8217;re on ships, and they were all designed for different missions originally. The C2BMC system, the battle management and control system for missile defense, has to take into account all of these inputs and also the reality of geometry. If you&#8217;re close to a sensor that&#8217;s not high resolution, but you happen to be in a location very close to the threat missile that&#8217;s flying by, it may be your best sensor. Five seconds later, it may be a strategic sensor that&#8217;s 1,000 miles away that is your best. So the system has to continually go through and calculate what is the best sensor at that moment to use in order to predict the track so that an interceptor can be fired to it. The last point you made was extremely good: the question on fusing. There&#8217;s a lot of definition of fusing. Fusing a lot of times means make sure you pick the right sensor at the right time. But the real definition of fusing is that the accuracy of the combined data from all the sensors is better than any individual sensor. To achieve that is extremely difficult, and the promise of artificial intelligence and AI agents has made that more realistic, where we can come into these very precise calculations of where the missile will be in the future, given its trajectory and flight, just using sensors that have been used for years, and improving on the speed of those calculations and the actual fused accuracy of the resulting trajectory.</p><p><strong>Maggie 25:44</strong><br>And the way you&#8217;re describing sensor fusion here, you know, if I have a sensor on some ship somewhere, and then a sensor in space, and then a sensor on land, and I want to be able to combine all the data from all of them to get an accurate picture, like, what is the communications technology needed to manage all that data and make those decisions in real time?</p><p><strong>Pat 26:04</strong><br>Well, the network is extremely important in this architecture. And also you may have not only the particular sensors during the flight of a threat, you may have your best sensor because of its location, but also you may have it because it has an unobstructed view. Long-range missiles, you know, you have to deal with the curvature of the earth, and so a space-based sensor may give its first warning, and the next best warning comes from a sensor that&#8217;s at an allied location in another country. We had a recent example when we upgraded our sensors, originally back around 2000 or so. When we turned on some of these new high-fidelity sensors, we actually got some disturbing news when we were watching the space shuttle, where it appeared the space shuttle was cracking, was breaking up on us, and in reality the sensor was so accurate we were getting four or five returns off the space shuttle, whereas in the old ones, using the old algorithms, we&#8217;d get one return. So we&#8217;ve had a lot of exciting moments during that period of time. But the accuracy of these sensors is getting so good, and like you said, they need to communicate with each other. These networks are designed so that if only part of the network is working, it can still operate, and it&#8217;ll take its best guess at where the flight trajectory is on a threat missile.</p><p><strong>Matt 27:43</strong><br>Yeah, so we&#8217;ve talked now about the sensor fusion piece, the communications between all the sensors. And you mentioned that AI and agentic systems might be able to better make sense of all those sensors in the future, but today, once you have all that sensing data in one place, once it&#8217;s all been communicated with each other, how is the decision made about whether to engage a missile threat? Obviously, you don&#8217;t want to engage a threat that&#8217;s not actually a threat, like in the space shuttle incident you just mentioned. So how is that decision made, and the decision about which specific interceptor or countermeasure to use against the threat?</p><p><strong>Pat 28:24</strong><br>Well, first of all, there&#8217;s pre-planning before a missile defense architecture is established, and the most important part is to determine what are you trying to protect. So you have locations on the ground that are marked off that are what we call the defended area. And if the threat missile is obviously not flying into the defended area, we do not engage. We just let it fly and hit a target on the ground or the ocean that is not seen as an asset that has to be protected. So that&#8217;s the first thing. Second, you have to determine the type of missile &#8212; try to differentiate the different types of missiles that are out there, the threat missile, and figure out what it is carrying on board based on historical intelligence. And the third piece is to, as I said before, ensure that you have an interceptor that&#8217;s capable of intercepting that missile, and when you are going to engage it in flight. So this is all pre-programmed into the missile defense architecture, hopefully before an engagement even occurs.</p><p><strong>Maggie 29:46</strong><br>So we&#8217;ve now talked about the threat. We&#8217;ve talked about the kill chain. So the third piece that we need to understand about missile defense is the doctrine.</p><p><strong>Pat 29:54</strong><br>It&#8217;s the firing doctrine. And the first thing to look at in a firing doctrine is the phases of a threat missile. When a threat missile first takes off, it&#8217;s in the boost phase. Obviously its boosters are energetic at that point and usually cause a big infrared signature. Normally a space-based satellite will pick up that thermal signature and indicate a missile has been launched after a few minutes. By observing the missile&#8217;s trajectory, even in boost phase, you then determine whether or not it is going into an orbital trajectory, meaning it&#8217;s probably a satellite, or if it&#8217;s going into a ballistic trajectory, meaning that it&#8217;s probably a threat missile. That occurs in boost phase. One of the most important phases is right after boost. Right after boost phase, the threat reentry vehicle usually separates at that point, and you go into post-boost phase that lasts a couple minutes. At that point it&#8217;s the very beginning of its long coast towards its target, and that is a phase where you&#8217;ve had enough time to track the missile that it becomes predictable of where it&#8217;s going to be for the next minute or so, and you actually have a chance, possibly, of hitting a missile during post-boost phase. It&#8217;s also where it&#8217;s so early in the flight that it&#8217;s typically very difficult to deploy decoys or anything, so the missile is most vulnerable right after boost in that post-boost phase. Plus it&#8217;s extremely hot because it just flew through the Earth&#8217;s atmosphere, so it&#8217;s a very bright signature at that point. After it cools down and continues to coast &#8212; and sometimes the coast could be for 10 to 20 minutes &#8212; it goes into the mid-course phase, and that&#8217;s where it&#8217;s flying above the atmosphere. An ICBM, like I said, can fly for 10 to 20 minutes even before it starts reentering the Earth&#8217;s atmosphere. And when it reenters the Earth&#8217;s atmosphere, that&#8217;s the terminal phase, and that only lasts a few minutes, and it&#8217;s moving at extremely high velocity. You have plasmas being formed around the reentry vehicle; you have all of the disruption. It&#8217;s not a smooth flight &#8212; a lot of bumpy disruption occurs to those RVs as they&#8217;re coming through the Earth&#8217;s atmosphere, which makes it harder to hit at that point. So mid-course is a nice spot to hit it; it&#8217;s a relatively stable target. Boost and terminal are challenging.</p><p><strong>Matt 32:56</strong><br>Maybe to start to match the systems you mentioned earlier with some of these phases, I assume that you wouldn&#8217;t use the same interceptor at any phase of a ballistic missile&#8217;s trajectory. So could you talk a bit about what kinds of interceptor options we have at each phase of a ballistic missile&#8217;s trajectory?</p><p><strong>Pat 33:20</strong><br>Well, it often comes down a lot of times to geometry. If you happen to have an interceptor launcher that&#8217;s near the missile that&#8217;s being launched, you&#8217;re able to launch it, and you have a good chance of hitting it during post-boost. But that means you have to have a launcher that&#8217;s very close to where the threat missile is being launched from, and that is typically an Aegis ship with an SM-3 or an SM-2, or there&#8217;s a longer, higher-velocity Standard Missile. That&#8217;s what &#8220;SM&#8221; stands for; we have co-developed it with the Japanese, and that has the opportunity to hit missiles that are not strategic but in the intermediate range and speeds and velocities. So one way is to just be close to where the threat is. You can also do it with land-based systems, for example in the Middle East, where they locate them on the other end. You have what we call goaltending, and it&#8217;s like hockey. You don&#8217;t have to be at the goal, but it&#8217;s best to be in between where the shooter is and where the puck is going to travel past. So another place to focus your missile defense is around the defended area, as I mentioned before, where you want to intercept just as a defender would on a hockey team &#8212; a forward hits the goal.</p><p><strong>Matt 35:01</strong><br>Got it. So the first examples you gave where you have your interceptors close to the point of launch was for boost or post-boost phase, and then?</p><p><strong>Pat 35:12</strong><br>Well, post-boost. Boost phase is extremely difficult because you&#8217;re hitting something that is accelerating and usually out of reach. It&#8217;s being launched from a location that is safe for the threat &#8212; your adversary &#8212; so it is very rare you&#8217;re close enough to actually hit something in boost phase. Post-boost you&#8217;ve had enough time and it&#8217;s no longer underpowered flight, where you probably have a better chance. The most mobile systems we have for land for that velocity would be THAAD, and for maritime it would be the Aegis system.</p><p><strong>Matt 35:55</strong><br>So the reason that it&#8217;s more feasible to take out a missile in post-boost is because it&#8217;s now closer to where the interceptor is, or just because we&#8217;ve had more time to respond? Or&#8212;yeah, don&#8217;t totally understand why it&#8217;s easier in post-boost than boost phase.</p><p><strong>Pat 36:11</strong><br>Because you&#8217;ve had time to respond. You know, the boost phase is usually only a couple minutes, and now the&#8212;if you&#8217;re in the right location, the post-boost that&#8217;s flying near you, and so if you&#8217;re located correctly, depending on your intelligence ahead of time, you can be as close as possible. In the post-boost, you&#8217;re no longer in powered flight, and it&#8217;s fairly predictable where it&#8217;s going to fly, and you&#8217;ve had enough time, and it&#8217;s difficult to deploy decoys in the post-boost phase. You can, but they&#8217;re going to eventually become evident that they&#8217;re decoys in the terminal phase. Again, if it&#8217;s a short&#8212;if you&#8217;re worried about short-range threats, you can have the Patriot system there. The Navy has the Standard Missile 2 for that and for shorter range, and actually for air defense too, both of those systems. And then for mid-course, it&#8217;s either the SM-3 missile with the Aegis system on maritime ships, or the THAAD system for a ground base. Again, these interceptors are being used that way because the characteristics of the interceptor&#8212;the seeker on board, its guidance system, its control surfaces&#8212;are all designed for operating in a certain part of the atmosphere, and that&#8217;s why they&#8217;re paired up with threats that fly in that part of the atmosphere.</p><p><strong>Maggie 37:45</strong><br>I know today there is a lot of discussion about what it would take if we wanted to try and hit a missile in the boost phase. Like, is it even possible to do in the first place if that were a goal of trying to take these missiles out before they&#8217;re able to deploy multiple warheads or decoys or elsewhere?</p><p><strong>Pat 38:04</strong><br>So the challenge with boost phase is, again, first of all, you don&#8217;t know when it&#8217;s&#8212;once. You don&#8217;t know when it&#8217;s going to happen, and once it&#8217;s launched, you have very little reaction time. So it&#8217;s going to have to be an interceptor that can be fed information from a sensor that a launch has occurred and its path has been predicted, and it&#8217;s in a location, typically in outer space, that can reach the target within a couple minutes. So that&#8217;s extremely fast, which means you have to have a very high proliferation of these boost-phase interceptors on orbit so that they can actually, literally, reach their target within a very short period of flight time. If the threat missiles within that air basket and the interceptor is flying to that air basket, when it gets close to the air basket, the sensors turn on on the interceptor itself&#8212;the kill vehicle&#8212;and the kill vehicle guides itself into the path of the oncoming missile.</p><p><strong>Maggie 39:24</strong><br>Pat, what is the state of our adversaries&#8217; current missile capabilities? Have there been any major changes over the last couple decades? And, you know, what do we need to be prepared to defend against?</p><p><strong>Pat 39:37</strong><br>Well, the growth&#8212;the proliferation of ICBMs, in fact missiles of all classes&#8212;is very unnerving. Over the past 20 years, it&#8217;s been exponential growth, not just exponential growth on the black market and in indigenously developed missiles themselves, but also their ability to be launched off of mobile launchers. In the old days, very old days, when long-range missiles were launched off of launch pads, you knew where the launch pads were, you knew where to watch, and you could counter those launch pads if you had to. Today, many of the&#8212;even ICBMs&#8212;are on mobile launchers that can be hidden. They can be moved. They can be camouflaged. It&#8217;s very, very difficult to track where they are and know where they are ahead of time. So the system has to be basically able to react to them after they&#8217;ve been launched, because it is so difficult to find the literally thousands of long-range missiles that have now proliferated. It&#8217;s very well known that Iran has developed missiles, and years ago they tested many tens of missiles being launched simultaneously, so they have that capability. It&#8217;s well known. North Korea is continually testing their long-range missiles, although the testing for ICBMs is not that impressive yet, because it basically goes straight up and then comes straight down, which is reminiscent of our early missile tests in the 1950s, but they are making progress. And then Russia is using the historic Soviet missile arsenal that&#8217;s been developed. And finally, China has had a very large proliferation of long-range missiles on mobile launchers.</p><p><strong>Matt 41:51</strong><br>You earlier mentioned the Ground-Based Midcourse Defense system, which was, you know, the primary system used to take out some of these very long-range ICBM-type missiles. I guess the question is: is that system&#8212;which you mentioned we have some in Alaska and some in California&#8212;meant to stop an all-out, high-volume attack from a near-peer adversary like China or Russia? Or, you also mentioned some of the tests from Iran and North Korea, which presumably have significantly less developed ballistic missile capabilities. What kinds of threats are they able to take out in that regard versus not able to defend against?</p><p><strong>Pat 42:45</strong><br>In the case of strategic missiles, the U.S. Ground-Based Midcourse Defense system was set up by law&#8212;the 1999 Missile Defense Act stipulated it was designed to counter threats from Iran or North Korea or an accidental launch from Russia or China. The location of the interceptors themselves, especially in Alaska, which has 40 interceptors up there in the open press, and Vandenberg has four more, those are optimized for flights from Iran or North Korea towards the United States. Those locations are not optimized for a launch, obviously&#8212;just geometry&#8212;from northern directions toward the United States. So there is a limit to how far a missile can go and how fast the missile can go. That&#8217;s just basic physics and geometry that does limit the capability of those systems. I would also say that when you look at a missile to defend a city, that missile has to be extremely high&#8212;have extremely high reliability&#8212;and that is very difficult to achieve in a system that&#8217;s made up of over a thousand parts, which they are. All those components have to work perfectly. So statistically, you&#8217;re not going to achieve or can count on a 100% reliable missile. What that means statistically is, if you want to achieve 100% reliability, or close to it, you need to fire more than one interceptor at each incoming target. So that&#8217;s another consideration they have to have, which is part of the firing doctrine.</p><p><strong>Matt 44:44</strong><br>So, for example, if North Korea could launch 10 ICBMs and there are 40 interceptors in Alaska, that&#8217;s something like a four-to-one ratio of interceptors to missiles. But how much does the number of missiles launched matter relative to, say, the types of countermeasures that those missiles have, in terms of the reliability of the interceptors for actually countering that threat?</p><p><strong>Pat 45:11</strong><br>Well, the countermeasures are often described as balloons and other things, but in reality, actually using them is much more difficult. It&#8217;s hard to make them appear like an RV over a long period of time. You can fool them for a short period, but over a long, 15-minute flight, it becomes extremely difficult. And so our systems are developed in order to differentiate between the different types of objects that are up there.</p><p>That&#8217;s one thing. The other is, again, the reliability of these interceptors is taken into account to determine how many interceptors are fired. Part of the firing doctrine can be, if you have enough time, what we call &#8220;shoot-look-shoot.&#8221; You shoot at the missile and then determine the kill assessment &#8212; did you hit it? And if you didn&#8217;t, or it wasn&#8217;t successful, you have an opportunity to shoot again, the second shot.</p><p>Depending on the time of flight, the command and control system very quickly calculates the optimum firing solution, and you try to fire as few interceptors as you need to in order to destroy a missile.</p><p><strong>Maggie 46:34</strong><br>So, Pat, I want to shift the conversation a little bit to the hot topic of missile defense today, which is Golden Dome &#8212; or, I guess, the executive order is called Iron Dome for America. In reading this executive order, and I know it&#8217;s still kind of a new concept that has not been fully fleshed out yet, from your perspective, what is really the new idea here for this next generation of missile defense that we don&#8217;t have in our current missile defense system?</p><p><strong>Pat 47:05</strong><br>I think there have been some technological advances over the past few years with our sensor resolution, and the proliferation of commercial space is making affordable sensors flying at low Earth orbit, called LEO. Many of those satellites can now be put into space at an affordable cost because of the commercial reduction of launch costs. It used to be $20,000 to $30,000 a pound in the 1970s; today, it&#8217;s about $1,500 a pound on a Falcon 9, for example.</p><p>That&#8217;s a tremendous reduction in cost, allowing us to put a great number of sensors up there at low Earth orbit because they&#8217;re affordable. They can also be built so they don&#8217;t have to last 10 or 20 years &#8212; they can have a shorter life, return to Earth, burn up, and be replenished. That gives us a significantly greater amount of sensor capability to monitor the threat.</p><p>As we referred to before, the command and control system involves literally tens of thousands of calculations going on simultaneously in any large-scale attack. Using artificial intelligence, neural networks, and agentic systems, it&#8217;s greatly simplified the software architecture required and allows the command and control system to take in a much greater amount of input data to calculate.</p><p>In terms of the weapons themselves, the propulsion systems and so forth are pretty much standard &#8212; they&#8217;ve been developed over the years, particularly the kinetic interceptors. The one area I think could be different would be launching the interceptors from space &#8212; SBI again. That architecture would depend on what the threat is that it&#8217;s trying to counter and how many interceptors you need.</p><p>If you&#8217;re just trying to conduct a mid-course intercept from space, you don&#8217;t need as many space-based interceptors. If you&#8217;re trying to hit in post-boost or boost phase, you would need a tremendous amount of space-based interceptors so they&#8217;re close enough to the launch.</p><p>Those are some of the significant technical advances that have occurred. From the point of Iron Dome &#8212; as you referred to &#8212; I was involved in that development for many years in Israel. That&#8217;s a much smaller piece of ground you&#8217;re trying to protect versus, obviously, the geographic area of the United States. You&#8217;re fairly certain of where the threat trajectories will come from, so you can do goal-tending and other things.</p><p>As I said, to protect the United States, you have to be concerned about threats that could come from almost any direction. And again, if there are short-range threats being launched off, let&#8217;s say, barges or submarines or nefarious vehicles, you&#8217;re going to need an awful lot of short-range missile defense systems. Just by counting up the number you would need for Patriot, it would be a tremendous number of Patriot systems.</p><p>For strategic interceptors, you&#8217;d need a much larger number and they&#8217;d need to be located in places other than Alaska or Vandenberg. So, it&#8217;s a much greater undertaking.</p><p><strong>Maggie 51:24</strong><br>When officials go about designing a new missile architecture, what are some of the trade-offs that need to be made?</p><p><strong>Pat 51:32</strong><br>Well, first of all, it&#8217;s driven primarily by the threat &#8212; where they think the threat is. Second, it&#8217;s driven by what you&#8217;re trying to protect. High-value targets &#8212; typically military bases or assets that give us the capability to respond and deter a threat &#8212; are usually considered high-value targets, as are seats of government and population centers.</p><p>All that has to be taken into account to design the goal-tending between where the threat is launched from (or estimated to be launched from) and what you&#8217;re trying to protect on the ground. Then you decide where in that trajectory to place your interceptors, sensors, and so forth.</p><p>I will say, it&#8217;s hard to comment on Golden Dome at this time because the architecture has not been publicly released, so it&#8217;s very difficult to determine what factors were traded into that architectural design.</p><p><strong>Maggie 52:52</strong><br>So, as we look toward some of these future missile defense plans, as venture capitalists, of course, we have to ask the question &#8212; what role do you see for startups in missile defense?</p><p><strong>Pat 53:06</strong><br>I see several. First of all, we&#8217;ve talked a lot about calculations and computations that must go on in real time so that kill chain I described. If there are technologies or algorithms or software modules, genetic agents, things that are set up that can calculate faster and get to a good enough answer&#8212;every millisecond matters. That is one area where there could be a significant improvement in the firing doctrine, even using today&#8217;s interceptors, due to the speed that the kill chain can operate at.</p><p>The second one I would think is associated with that would be the different types of technologies associated with object identification and resolution of existing sensors today. Again, it&#8217;s driven by calculations, and so those are the principal ones. Propulsion systems are very capital-intensive, and they tend not to lend themselves to that. You can do it, but it takes&#8212;the safety factors are significant&#8212;that you have to take into account, and that drives the cost, and that drives the time that it takes to develop. Those are normally done by larger corporations.</p><p><strong>Matt 54:51</strong><br>Whether it&#8217;s startups or existing contractors, where do you see the biggest need for investment to improve missile defense technology&#8212;to have more reliable systems, systems that can counter a wider range of threats? You&#8217;ve mentioned many today that have room for improvement.</p><p><strong>Pat 55:12</strong><br>So, craftsmanship and quality control systems that are in a lot of the factories building the thousands of components that go into interceptors and the different parts of the missile defense system are key. That&#8217;s an area that&#8212;if you&#8217;re building, you know, a car in Detroit off an assembly line&#8212;the precision, the requirements for that quality control are tremendously less than trying to build what we would call a space-based or space-qualified component.</p><p>Technologies that can improve quality control, for example, may not sound like a flashy technology, but it is critical. The higher the reliability, the fewer interceptors you have to fire, and the greater the probability of defeating a threat launch. So that&#8217;s one example right there.</p><p><strong>Matt 56:18</strong><br>We talked a bit earlier about Israel&#8217;s Iron Dome, and obviously the executive order for Golden Dome is inspired directly by Israel&#8217;s Iron Dome. What are the major differences between the interceptors needed for Israel&#8217;s Iron Dome and the U.S.&#8217;s Golden Dome?</p><p><strong>Pat 56:39</strong><br>Because of the size of Israel, most of the interceptors used in Iron Dome are short-range interceptors, so they&#8217;re lower in cost. You can proliferate the number of them, and the sensors are within line of sight of the threat missiles, typically, so you don&#8217;t need a long-range communication chain.</p><p>In the United States, it&#8217;s obviously many, many times larger geographically, and the threats could come from a far greater number of trajectories. The ranges can vary greatly, and the amount of time you have to respond can be much less. It also requires a mix of interceptor types. The short-range around the coastline&#8212;you&#8217;d have Patriot or SM-2. Large cities would require THAAD or SM-3 if near a coastline. And ICBMs obviously are the only things that can counter those types of threats.</p><p><strong>Maggie 57:58</strong><br>Going back to looking at the international stage, we&#8217;ve talked a little bit about Israel&#8217;s current missile defense capabilities, but what do our adversaries&#8217; missile defense capabilities look like? And are there lessons that the United States should be learning from how others have designed their own systems?</p><p><strong>Pat 58:20</strong><br>Well, there are a lot of similarities with some of these systems to ours, which is quite interesting. I have literally shown Russians, many years ago, an intercept that they thought was done by the THAAD system, and it turned out it was a Chinese system. They were surprised by the advancement that the Chinese had.</p><p>The basic technologies of command and control and sensors and propulsion systems have reached the point where kinetic interceptor missile defense systems are proliferated, but primarily with only our larger, near-peer potential adversaries. They&#8217;re less seen in smaller countries.</p><p>The real concern is non-nation-state threat actors such as cartels and others, because of the proliferation of threat missiles being sold on the black market. Associated with that is the use of software and modules&#8212;and maybe AI, I&#8217;m not sure at that level&#8212;but it greatly simplifies the training required to launch a missile. You can be a fairly untrained person and successfully erect and launch a missile bought on the black market. That is a tremendous concern, because now you&#8217;re not dealing with a nation; you&#8217;re dealing with all of these other, as I said, non-nation-state threats.</p><p><strong>Matt 1:00:16</strong><br>Anytime we think about a new missile defense architecture, or making a change to it&#8212;thinking back to the ABM Treaty and limits to the amount of defenses that the U.S. and the Soviet Union would build to maintain deterrence with each other&#8212;how should we think about the ways our adversaries might respond to any changes to our missile defense architecture?</p><p><strong>Pat 1:00:41</strong><br>First of all, what I just mentioned is the greatest threat, because it&#8217;s really hard to deter a non-nation-state actor&#8212;some criminal group or so forth&#8212;that may want to hold a region hostage. We recently saw the Houthis, for example, threatening international shipping off Yemen for the last couple of years and the impact that has had. So the architectures now have to be extremely agile and flexible, to adjust to not only defeating missiles coming from a certain region but also focusing on the defended assets, no matter what direction they come from, which is a much greater challenge.</p><p><strong>Matt 1:01:33</strong><br>Great. Well, Pat, thank you so much for being here. We really appreciate it.</p><p><strong>Pat 1:01:38</strong><br>My pleasure. Thanks so much.</p>]]></content:encoded></item><item><title><![CDATA[🎙️ Ep 9 - Rangeview: Manufacturing in the Cyber Foundry]]></title><description><![CDATA[What will it take to actually bring manufacturing back to America?]]></description><link>https://maggiegray.us/p/ep-9-rangeview-manufacturing-in-the</link><guid isPermaLink="false">https://maggiegray.us/p/ep-9-rangeview-manufacturing-in-the</guid><dc:creator><![CDATA[Maggie Gray]]></dc:creator><pubDate>Tue, 28 Oct 2025 15:32:44 GMT</pubDate><enclosure url="https://api.substack.com/feed/podcast/177115096/9453834ad12be5034f51a7c65c0b16ae.mp3" length="0" type="audio/mpeg"/><content:encoded><![CDATA[<p>What will it take to actually bring manufacturing back to America? In this episode of the Mission Matters podcast, Akhil and I sit down with <a href="https://www.linkedin.com/in/cam-schiller/">Cameron Schiller</a> and <a href="https://www.linkedin.com/in/aedengasserbrennan/">Aeden Gasser-Brennan</a>, the founders of <a href="https://rangeview.com/">Rangeview</a>, to discuss the current state manufacturing in the U.S. </p><p>We discuss:</p><ul><li><p>What investment casting actually is and how Rangeview is revolutionizing the ancient manufacturing process</p></li><li><p>Why China dominates much of today&#8217;s manufacturing landscape, particularly in the world of consumer electronics</p></li><li><p>How modern defense manufacturing today differs from the manufacturing we did during WWII</p></li><li><p>How industrial policy combined with new technologies can help bring manufacturing back to America</p></li></ul><p>You can listen to the podcast on <a href="https://open.spotify.com/episode/17YgRbq3BHHmmTPvDzrIAR?si=MVFJt-7DSpuSGsQkKI3Qig">Spotify</a>, <a href="https://podcasts.apple.com/us/podcast/rangeview-manufacturing-in-the-cyber-foundry/id1807120572?i=1000733827896">Apple</a>, the <a href="https://shieldcap.com/episodes/rangeview">Shield Capital website</a>, or right here on Substack.<br><br>As always, please let us know your thoughts, and please reach out if you or anyone you know is building in the national security domain.</p><p class="button-wrapper" data-attrs="{&quot;url&quot;:&quot;https://maggiegray.us/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe now&quot;,&quot;action&quot;:null,&quot;class&quot;:null}" data-component-name="ButtonCreateButton"><a class="button primary" href="https://maggiegray.us/subscribe?"><span>Subscribe now</span></a></p><div><hr></div><p><strong>Transcript</strong></p><p>Maggie 0:00</p><p>In this episode, we&#8217;re joined by Cameron Schiller and Aeden Gasser-Brennan, the founders of Rangeview, a startup revolutionizing investment casting through novel 3D printing techniques that are enabling the next generation of autonomous systems and advanced manufacturing. Investment casting is an ancient process&#8212;it&#8217;s been around for thousands of years&#8212;used to create everything from jewelry to jet engine components. But despite its importance in manufacturing critical parts for aerospace, defense, and automotive industries, the fundamental process has not changed much since the 1960s. Meanwhile, the U.S. has lost over 100 investment casting foundries since 2001, creating a strategic vulnerability at a time when our defense systems are becoming more complex and our adversaries are modernizing their manufacturing infrastructure.</p><p>Akhil 01:20</p><p>What&#8217;s particularly striking is how this old-school manufacturing process has become a bottleneck for innovation. As companies like SpaceX, Tesla, and Varda&#8212;as well as more established aerospace and defense companies&#8212;are pushing the boundaries of what&#8217;s possible with modern systems, they&#8217;re discovering that traditional manufacturing just can&#8217;t keep up. They need components with complex internal geometries that are really impossible to create using conventional casting methods&#8212;think turbine blades with intricate cooling channels or missile components that need to be both lighter and stronger than ever before.</p><p>Maggie 01:53</p><p>Enter Cameron and Aeden, two college students who saw an opportunity to bring this ancient industry into the digital age by combining custom 3D printing with advanced material science. Not only are they making the casting process faster and cheaper, they&#8217;re actually enabling an entirely new set of designs that were physically impossible to manufacture before. It&#8217;s not just about efficiency&#8212;it&#8217;s about unlocking new capabilities for America&#8217;s most innovative defense companies. Cameron and Aeden, thank you guys so much for joining us.</p><p>Akhil 02:22</p><p>Awesome, guys. Cameron, Aeden&#8212;so excited to be here with you. It&#8217;s been awesome to see the journey from your Berkeley lab a couple of years ago to where you are now. It&#8217;s been great to see what you&#8217;ve built and how you&#8217;ve executed. Before we dive into all of that&#8212;and honestly, maybe share with a good amount of the listeners what investment casting actually is&#8212;let&#8217;s actually start geopolitically.</p><p>So, over the last couple of weeks, a lot has been happening in terms of geopolitics, tariffs, and the state of the nation&#8217;s industrial resilience. To start, where do you think we are in terms of the state of U.S. manufacturing? We can dive beyond generalities since you&#8217;re living it on a day-to-day basis. Where are we at? What&#8217;s your assessment, and where does your work fit in?</p><p>Cameron 03:10</p><p>Well, the state that we&#8217;re in is&#8212;everyone listening, take a look around right now and see if you can find anything you can confidently point to that was made in America. It&#8217;s not great. Slowly, over the past 20 years, we&#8217;ve let it all slip overseas through globalization and the whole story of how we got here. The truth is, we&#8217;ve really hollowed out our industrial base for the promise of more freedom and flexibility&#8212;and what we got on the other end was a supply chain that&#8217;s more fragile than ever.</p><p>The great Americans responsible for making all the stuff underpinning our critical defense systems&#8212;and everything else in life&#8212;are retiring. Most of them are on their way out or already gone, and there are fewer and fewer people to make the parts we need. Those parts are mostly made overseas. So, for defense and energy applications&#8212;where we&#8217;re tripling the energy usage needs with the AI boom coming&#8212;there&#8217;s just no supply chain on the back end of it.</p><p>I&#8217;m excited to talk about that in more depth today. I think most folks don&#8217;t know just how bad it&#8217;s gotten, and that could be a real awakening for us if we ever need to pull that lever and start making lots of parts the way we used to.</p><p>Akhil 05:02</p><p>Definitely. And Cameron, it&#8217;s not just necessarily the globalization piece. Having watched you over the last couple of years, it&#8217;s also about the ability to innovate&#8212;the fast feedback cycle between new, novel systems and platforms, both civilian and military. It&#8217;s kind of hard to do that when you&#8217;re shipping a part every week or two from somewhere else. The cycle time to accelerate innovation isn&#8217;t just about production, but the unique design aspect as well.</p><p>Cameron 05:24</p><p>Yeah, that&#8217;s exactly right. That&#8217;s a big point that a lot of people are starting to pick up on now. When you&#8217;re building a system, the first thing good engineers do is engineer iteration rates. The easiest way to collapse iteration rates and reach higher levels of innovation is to bring manufacturing as close as possible to the final design space. Some of the most innovative folks out there are actually doing their own manufacturing. They understand the constraints of the system they&#8217;re building.</p><p>There&#8217;s this great art that&#8217;s been lost in America now, which is called DFM&#8212;or &#8220;design for manufacturability.&#8221; At a cultural level, it means understanding how something actually gets put together. We&#8217;ve lost that a bit. And believe it or not, most innovations happen in the design space of manufacturability. You can&#8217;t just make something new&#8212;you have to make something new that can move its way into the world. Understanding manufacturing is critical to innovation, and the way you understand manufacturing is by doing it. We need to do it so we can collapse those design iteration rates and really bring the best and brightest designs to the end user&#8212;the warfighter.</p><p>Aeden 06:31</p><p>I think there&#8217;s a point to be made here. Early on, when we were starting the company, one of the clear indicators that the old paradigm was collapsing&#8212;the idea that we&#8217;d do all the design here in the U.S., ship the manufacturing drawings overseas, and make all the money because we controlled the designs and the brand&#8212;was the rise of Chinese consumer electronics companies killing their American counterparts.</p><p>The greatest example is DJI, right? DJI&#8212;which is now obviously extremely relevant militarily&#8212;started as a consumer electronics company. Why does DJI do so well? It&#8217;s a good question. Why were they so much better than all the American drone companies, at least for a while? The answer is that they could manufacture everything down the street. Their iteration rates were incredibly fast. They could do more technically interesting things at lower cost and get those to market faster.</p><p>If you&#8217;re a manufacturing company&#8212;or a company that makes a product&#8212;your advantage is the ability to iterate quickly. That was a clear indication that something was wrong. The theory was that with America&#8217;s great universities and engineers, we&#8217;d build the best products. But that doesn&#8217;t work if you can&#8217;t manufacture those products in-house or iterate and develop quickly.</p><p>Maggie 07:43</p><p>And why is it that we lost so much of that capacity? And, you know, what are the levers that we are actually able to pull to bring that back to the U.S.?</p><p>Aeden 07:54</p><p>So, I have this kind of saying: the right industrial policy is the one that actually changes the unit economics of manufacturing in your country. Everything else is a short-term solution. As long as it&#8217;s actually more expensive to manufacture here, new manufacturing won&#8217;t come back.</p><p>I&#8217;m a bit of an outspoken believer in tariffs because tariffs do this, right? Strictly, it is more expensive to manufacture here. But if you&#8212;well, I think China&#8217;s a great example. It&#8217;s really worth looking at what worked so well. Obviously, it started with labor; that&#8217;s why we started sending things overseas. But over time, China&#8217;s real advantage today is that they are consolidated and have a ton of things in close geographic proximity. They have this ability to get things quickly, build new things quickly, and deploy new technology out to the factories quickly.</p><p>Maggie 08:47</p><p>They can literally walk down the street and talk to their friend who&#8217;s actually doing the castings or forging. And then redesign a part in the course of a couple days or hours.</p><p>Aeden 08:56</p><p>Exactly&#8212;and not only that, they can go down and buy the ceramics feedstock from their friend three streets over, and the mine that&#8217;s making the raw iron is only a few miles away. So this real consolidation of all these different causes in close proximity is the real benefit.</p><p>I think this is a huge project to build back in America. We had this&#8212;America was the king in manufacturing up until around the &#8217;80s or &#8217;90s. I think you have to start in the places that have some sort of DoD significance, where the interest is already there from the government. You need to start with who actually wants the manufacturing back the most and start building capacity there.</p><p>There&#8217;s a flywheel to get started: if you start in the processes that are most critical for the people who care, those processes will make it cheaper to do all the other processes here. There&#8217;s the idea of a learning curve, but there are also compounding learning curves in manufacturing. The more of everything you do, the cheaper it gets. The more things that are adjacent to what you&#8217;re doing, the cheaper it gets because you share labor and equipment, and things are amortized over more parts.</p><p>I think the policies the government has pursued have been a little misguided in a few key ways. One is that the government is really good at funding development&#8212;they love funding development&#8212;but there&#8217;s an issue: a lot of things get developed with government money and then never go to production. There aren&#8217;t enough incentives to actually build capacity.</p><p>If I were to change our industrial policy, it would be less about development contracts or qualification contracts and more about: if you build this amount of installed base capacity, we&#8217;ll fund your CapEx, or this becomes a tax write-off, or something to that effect. That actually changes the economics, as opposed to funding a million early-stage development contracts proving out new technology.</p><p>This happens again and again&#8212;America develops amazing new technology, and China implements it at scale. America invented the CNC machine, and yet, I don&#8217;t know what percentage of CNC machines are in the U.S. This will keep happening so long as the government just funds development.</p><p>China is a great example: funding CapEx and providing cheap government financing really does drive growth in manufacturing because it&#8217;s geopolitically relevant for them. It&#8217;s geopolitically relevant for us too. I think we&#8217;ll start to see this happen more and more, but historically we&#8217;ve focused too much on funding development instead of scaling. What we should really be doing is scaling more similar processes that have less of a technical moat&#8212;less difficult to develop&#8212;and focusing on building lots of capacity.</p><p>Akhil 11:30</p><p>Aeden, here we are talking about manufacturing &#8212; your focus on investment casting. There are probably folks listening in, or even, frankly, when I first met you, I had to learn a ton about what investment casting was and what you&#8217;re doing with it, what&#8217;s novel?</p><p>Aeden 11:42</p><p>Yeah. So I&#8217;m going to walk through each step of the process and explain what we do, what an official foundry does, kind of explain it from the customer&#8217;s view, right? Because that&#8217;s who matters at the end of the day.</p><p>So, you&#8217;re a customer. You want to make a part. You come with a drawing, CAD file, budget, requirements &#8212; density requirements, mechanical properties of the part, what kind of processing is allowed, what shape it is, how we measure that shape &#8212; all these things, right?</p><p>And you start out at a foundry. We do the same thing. We look at this and say, &#8220;Okay, how are we going to make this part? How are we going to set it up? What&#8217;s the right process to make this?&#8221;</p><p>For us, it&#8217;s largely similar across a lot of parts. Foundries, though, are actually very different. So, they&#8217;re making some tool to start &#8212; a big block of metal &#8212; and that block of metal has the shape of the part cut into it. Usually it&#8217;s actually tweaked a little, because the part might deform or change shape during the process.</p><p>The foundry starts by making a wax pattern. Rangeview doesn&#8217;t do this. The foundry makes the wax pattern, then assembles a bunch of these patterns together.</p><p>If you want to make a spoon, you have a wax spoon. You may take a bunch of spoons and put them together &#8212; they&#8217;ll have a wax tree feeding them. You&#8217;ll see this big wax tree that holds a bunch of wax spoons.</p><p>Next, you dip that in a ceramic coating &#8212; usually dip, dry, dip, dry &#8212; it takes a few weeks. What you&#8217;re doing is building up a layer, like a clay layer, on the surface. Then you melt all the wax out, burn the remaining wax again, and finally fire the ceramic shell.</p><p>You&#8217;ve got basically a big, complex mug &#8212; a strong ceramic mold.</p><p>What Rangeview does is make the mold directly. We print direct molds, so we skip all those steps &#8212; all the manual labor &#8212; and, really importantly, we skip all the variability in the final part that comes from human decisions. You want the technical characteristics of the part to be driven by software and machines, because then it&#8217;ll do the same thing every time. Your tolerances are much tighter, and you can rely on the process more.</p><p>At the end of that whole process, you&#8217;ve got a part inside a big ceramic cavity. Then you pour metal into it. There are a variety of different casting processes &#8212; Rangeview works with one that produces reactive or very high-temperature alloys. You pour the metal into this mold, remove the ceramic after it cools, and you end up with a single part.</p><p>You throw away the ceramic each time and remake it for every new mold. That&#8217;s how you make the part.</p><p>Then you cut the part off the tree and do a ton of post-processing &#8212; you might take X-rays of the part to look for porosity, coat it with a penetrant to show cracks, cut some parts apart to pull mechanical tensile bars and test strength. Then you&#8217;ll heat treat, machine, and coat them. Generally, at that point, you&#8217;ll have a final part.</p><p>So, the whole process traditionally involves all this fixed tooling to make the part. For us, it&#8217;s the same process every time &#8212; we directly print the ceramic mold. It&#8217;s a process we&#8217;ve built in-house, and it allows us to make different parts without changing any tooling.</p><p>Today, the U.S. has offshored almost all of its investment casting capability. Investment casting is used in enough of these &#8220;commodity&#8221; capabilities that people have said, &#8220;Well, this isn&#8217;t defense-critical, maybe we can push this overseas.&#8221;</p><p>But there are a lot of cases where people actually got exemptions to manufacture critical parts overseas because it was cheaper. Investment casting is full of labor &#8212; the traditional process has hours and hours of manual work. You might have 40 hours of labor going into a part that fits in your hand. So, in that case, it really matters if you can save another $20 or $30 per hour of labor. When you have a very unautomated process &#8212; which is the traditional method &#8212; that&#8217;s a huge factor.</p><p>Akhil 15:35</p><p>That&#8217;s awesome. It sounds like the previous instance hasn&#8217;t changed for thousands of years &#8212; some sort of wax base to ceramic, you pour metal into it, and&#8230; great.</p><p>Aeden 15:46</p><p>Yeah, it started with beeswax and river sand &#8212; that&#8217;s how this process began.</p><p>Akhil 15:50</p><p>And critically, now you&#8217;re able to, because you&#8217;re 3D printing and designing this in a digital foundry way, actually make a whole new set of complex geometries that you can pour whatever you want into, correct?</p><p>Aeden 16:01</p><p>Yeah, and we&#8217;re enabling a whole bunch of designs there that you couldn&#8217;t make in the traditional process. Those are some of the most exciting parts we make. And it&#8217;s also worth saying that almost every one of those post-processing steps I described are generally done by people.</p><p>So, the way you cut the casting off in a traditional foundry is a guy sitting on a saw. This is a horrible job, right? It&#8217;s a super dangerous job. It&#8217;s super loud, the saws break and send bits flying&#8212;you know, people die doing this. It&#8217;s really a horrible place to work. It&#8217;s not somewhere I&#8217;d want to work. It&#8217;s not somewhere I&#8217;d want my kids to work.</p><p>And it&#8217;s the same thing with everything else&#8212;the person grinding the part, the person heat treating&#8212;it&#8217;s a bunch of people stacking parts in a big furnace, closing the furnace, opening the furnace. In our factory, almost all of this is done by a machine. The person is programming the machine, setting it up to do a new part, but they&#8217;re not the one actually cutting the part or grinding it. That&#8217;s all done by a robot, really, at the end of the day.</p><p>The traditional process to make any of these parts&#8212;and any of the traditional competitors&#8212;has a very inflexible process that cannot be changed without huge budgets. You&#8217;re making a part, you want to make it slightly differently, you want to iterate on a design&#8212;it could take six months, a year, two years.</p><p>The second piece is there&#8217;s a huge amount of extremely skilled labor that goes into this, and it&#8217;s really hard to scale. So, if you&#8217;re an investment casting foundry and you want to get bigger, you want to double your capacity&#8212;there are no people you can hire. These people have all retired.</p><p>So, the things that are built are factories that are not dependent on specialized human labor to make components and are not dependent on tooling to make parts. What these foundries look like is&#8212;you want everything to be made by computer. How can you give the computer the tools to make your casting?</p><p>We use a variety of different processes that make sure each manufacturing process in our factory is software-defined. This starts with making molds. You want to make sure the molds can be made in a software-controlled way. We&#8217;ve done a huge amount of innovation on the process there&#8212;in the equipment and the materials&#8212;to make sure that when we make a mold, there&#8217;s no fixed point associated with it, and you&#8217;re forming it all digitally. The same thing applies to every single piece of equipment and process that comes after.</p><p>Then you&#8217;ve got eight or nine steps in our process internally to do that, and for each one, we have a digital definition. The machine is running with telemetry going back to the system and running to the prescriptive definition that we&#8217;ve given it for that process. This includes things like pouring&#8212;what temperatures you pour the metal at, how fast you pour it, what kind of environment around the metal, the vacuum levels, and things like that.</p><p>The big thing is: our factory is not running on highly specialized labor; it&#8217;s running on software-controlled equipment. I can form different parts with just changes in software and without retraining people. So that gives you the high level&#8212;I can dive into all kinds of details, and I&#8217;m sure Cam can talk to that.</p><p>Akhil 18:51</p><p>Super, super helpful. Maybe one more high-level&#8212;just walk through, if you can, even just a couple of the steps from design to 3D printing to cast. What does that sort of look like?</p><p>Aeden 19:01</p><p>So, traditional process here&#8212;and what an average aerospace customer does&#8212;is they want to make a turbine blade. They have some preliminary design, and they want to get into production. First, they have to get to design validation. The goal is they want to be making turbine engines in six years, at rate.</p><p>Generally, what will happen is they&#8217;ll go out to as many foundries as they can and try to find someone who will bid the part. The first surprising thing is that most of the parts get no-bid most of the time, because most foundries are overbooked and don&#8217;t have capacity&#8212;and also can&#8217;t scale. They&#8217;re stuck because of their labor.</p><p>So, the first process of design, at least for you as a customer, is to try to find someone who will bid on your part. You might not have a finished design at this point, so you&#8217;re going to tell them, &#8220;Hey, look, I want to make a few of these. I want to do some prototyping.&#8221;</p><p>Generally, they&#8217;ll give you back two really important quotes. One is your upfront quote, and the other is your piece price. The upfront engineering and tool making might be $300,000 for a part and might last six to eight months. Then you&#8217;ll go into that and also provide a huge amount of technical documentation.</p><p>For each of these parts, if you&#8217;re making a turbine engine, you might have 100&#8211;200 pages of technical documentation for a single small part. That&#8217;s a contract between the design engineer and their requirements and the foundry. What the foundry is agreeing to is: &#8220;I&#8217;m going to meet all of these requirements.&#8221; It might take many iterations to meet those requirements.</p><p>For the foundry, every single one of those iterations means iterating on tooling, retraining people to work on the new parts, and trying to hit those requirements&#8212;and that&#8217;s what stretches it out.</p><p>For us, when we receive something, we&#8217;ll ingest it, do some design, and essentially just put it straight onto our printers, which make the molds for the casting&#8212;and then get results quite quickly.</p><p>Akhil 20:47</p><p>And these are 3D printers, right? Standard 3D printers.</p><p>Aeden 20:51</p><p>So yes, we use a bunch of in-house developed materials and processes to make these castings and molds. Essentially, we&#8217;re forming the geometry that&#8217;s going to form the part with a printer. The end part is actually just a normal casting. So, unlike a lot of the additive processes&#8212;the metal 3D printing processes&#8212;there&#8217;s no requalification, there&#8217;s no retesting. The material properties are the same as these casting alloys that have been developed for 50 years, and then we get a part straight out of that process. Maybe that gives us a high level; I can dive into more details.</p><p>Cameron 21:28</p><p>Thanks, Cameron. I can come back to you on the discussion we were having around the iteration cycle. Can you walk through an example&#8212;whether it&#8217;s a real or hypothetical customer&#8212;how you would have done here, both Digital Foundry and the novel casting process? The full lifecycle has just allowed for that incredible acceleration in both speed and scale.</p><p>Yeah, absolutely. And I&#8217;m not able to use direct customer names in the line of work that we do, but I&#8217;ll give an example of something that we see happen and how ultimately it results in, you know, American supremacy on the battlefield.</p><p>So, as Aeden was speaking about a little bit earlier, when you&#8217;re making a part, the end designer is actually just delivering the capability. And that capability may be, you know, let&#8217;s build the engine that can fly the furthest. Let&#8217;s build an engine that can fly the fastest. And ultimately, that comes into a balance with reality and physics. When you try to put those metal particles through their paces in a jet engine, it&#8217;s going to be how hot you can get it.</p><p>A really common one that we see&#8212;because we do a lot of turbine blade work&#8212;is: what is the exact shape of that turbine blade? We&#8217;ve gotten good at simulating physics to some level to help us figure out how the air might flow through that turbine blade. But the real way to figure it out is to put it on the test bed and let it run. The simulations are never perfect. Simulations are only as good as the data you feed them, and so there may be a few variations of how that blade should be shaped that a designer is looking to go through. What they&#8217;re really trying to figure out is what shape is going to be the best for production on this engine.</p><p>Every form of manufacturing has some inflexibility associated with it. The way to think about this in manufacturing&#8212;the term is called tooling. Tooling can be hundreds of thousands to millions of dollars to set up a set of machines to do a set of instructions. And this tooling is hardcoded&#8212;it&#8217;s coded in the actual cavities of the molds that you&#8217;re producing. So when you ask that tooling to do something a little bit different&#8212;to figure out if that little bit different shape on the blade results in a little bit more or a little bit less performance&#8212;you have to pay hundreds of thousands or millions to change it. But once you&#8217;re in, you&#8217;re good to go.</p><p>The qualification process of a lot of these components often involves changes. And when you move that tooling from a physical world to a digital world, you unlock a whole other world of possibilities&#8212;not just for cost reduction, but for achieving the optimal design.</p><p>Now, there&#8217;s this other kind of intricate layer that&#8217;s starting to come into play as America becomes more serious about producing. This is maybe a bit more general of a comment on the state of the DoD world right now, but lots of folks are delivering to kind of low-rate initial production. But a lot happens when you go into full production. We&#8217;re talking about what is the capability&#8212;not just to make engines that fly as far as possible, but how many engines can you really make a year if you had to make every single engine that you could? It&#8217;s a different scenario when you have to hit full production.</p><p>In many cases, when people are designing today for these flexible manufacturing technologies, they&#8217;re using a different manufacturing technology. You might metal 3D print something, because then your tooling is digital. But when it comes time to make full production, you&#8217;re moving to a traditional form of manufacturing&#8212;you&#8217;re moving to casting, you&#8217;re moving to stuff that just scales. So one thing a designer has to look at is how serious they are about production. And if you&#8217;re serious about production, you&#8217;re going to design to the constraints of the manufacturing technology that you use to scale production.</p><p>This is one of the core beliefs that we coded into our technology stack. Our technology is capable of iterating on quick-turn qualification to allow that part designer to get the shape and the blade that they want. But at the flip of a switch, they can go to full-range production with the same constraints&#8212;the same casting constraints. We don&#8217;t have to change our blade thicknesses. We don&#8217;t have to change our overhang angles. It&#8217;s directly the same manufacturing technology.</p><p>And then I&#8217;ll give you another one, which is on the tail end of this. We&#8217;ve seen this with past sustainment issues before, but at the end of a lifecycle, you store that tooling. And you store that tooling on a wall while you&#8217;re making the next, newest, and greatest part. That tooling, believe it or not, will get lost, rust, or wear down. The tools wear down over time. And when you go to pull that part back off the shelf&#8212;when you need to make 14 joysticks because a plane is down and that joystick has to be remade to put it back on&#8212;you have to build up that $100,000 tool and that million-dollar tooling all over again, just so that you can serve a hilariously low quantity that the industry calls alien castings. They literally call them alien castings, or these onesies, twosies that they need just to sustain stuff.</p><p>So you have this other flexibility request on the tail end of these programs. And once again, this is what we&#8217;ve designed our production technology to do. And I think the bigger picture, when you zoom out from all of this, is you&#8217;re looking at manufacturing holistically. You look at the problem&#8212;it&#8217;s not just about making one part, it&#8217;s about making a process that can consistently make things at scale. And that&#8217;s what Rangeview is about.</p><p>Akhil 27:35</p><p>About. That&#8217;s right, and that&#8217;s your sort of idea to speak of the digital or cyber founder, Cameron. What&#8217;s the Cyber Foundry? What&#8217;s the vision for it?</p><p>Cameron 27:43</p><p>Yeah, Cyber Foundry is Rangeview&#8217;s first product. And the Cyber Foundry is simply a factory that is making America&#8217;s most critical componentry with the workforce that America has and with the technology that we invent here. So it&#8217;s a collection of custom-built processes, materials, and equipment to make a digital file of a part&#8212;which we&#8217;ve gotten really good at building in America&#8212;into an actual part, a real part that can be certified and clicked into a plane, ship, or vessel, and unlock the capability of those systems that we&#8217;ve designed so well but have been hampered by not being able to be made. You know, unlock that problem for the U.S., DoD, and our other partners.</p><p>Akhil 28:43</p><p>Awesome. That&#8217;s from digital design iteration, digital manufacturing, and then actually the real hands-on production.</p><p>Cameron 28:51</p><p>Every stage. I mean, our factory is just as much of a computer as it is a metal-shaping device.</p><p>Aeden 29:00</p><p>Yeah, I think it&#8217;s worth saying a big part of our philosophy is that the next generation of American manufacturers has to have a huge amount of engineering expertise in-house. You&#8217;re not going to innovate on process if you don&#8217;t have the expertise on how your process works. And it&#8217;s really important that the manufacturers&#8212;not just the designers, but the actual people designing the process, building the equipment, setting up the factory&#8212;know what&#8217;s going on and are incredible engineers.</p><p>Maggie 29:23</p><p>What role do you see for new technologies in accelerating reshoring of manufacturing capabilities to the United States? And what are those technologies that are actually going to drive those trends?</p><p>Akhil 29:39</p><p>Yeah, and maybe, Maggie, in addition to that, to your earlier answer, Aeden, we can&#8217;t necessarily replicate what other nations are entirely doing, right? We have certain advantages here. And you guys, among many other things, are innovating from a technological standpoint&#8212;from both a digital and physical standpoint&#8212;the software-defined aspect. So, a little bit of an addition to Maggie&#8217;s question: how much can we actually rely on technological innovation as part of it, and then what else needs to be done?</p><p>Cameron 30:07</p><p>So, technology is the way forward. It is the only way forward for us. But that&#8217;s a great American trait&#8212;America knows how to do that, and it&#8217;s not that complicated. The first thing you&#8217;ve got to do is pull your manufacturing technology into the 21st century. I mean, it would blow you away if you walked into a foundry today. All the folks&#8212;the heat-treat shops, the anody shops&#8212;all those folks need to pull their furnaces into the internet. They need to bring laptops into the work and just run it the way a modern company is run. And so I don&#8217;t think that&#8217;s reinventing the wheel; I think that&#8217;s getting more focused into the industry.</p><p>So, you know, it&#8217;s tough because the factory owners&#8212;that was a bit of our origin story. We were just two robotics guys, gonna sell robots to factories. What a journey. You know, we thought that. We thought that manufacturing was further along and was just ready for someone to sell robots. But the truth is, they didn&#8217;t even have outlets on the walls. So we had to go down to the studs and start there. So, you know, I don&#8217;t think it&#8217;s reinventing, no. And there are many companies doing this right now. I mean, go look at SendCutSend&#8212;this amazing company that chose their manufacturing technology.</p><p>That&#8217;s a good way to think about manufacturing too: at a company level, you go to the processes. You know, manufacturing is down bad as it is in the country&#8212;it&#8217;s actually still a bigger market cap in America than all of tech combined. And so if you think about it, you can&#8217;t compare a FinTech company with a healthcare company&#8212;they&#8217;re completely different sectors and completely different things. And manufacturing&#8212;the process&#8212;is the sector.</p><p>So there&#8217;s this amazing process, sheet metal fabrication, where you&#8217;re making stuff like doing origami with really strong paper. There&#8217;s this company out in Reno that just figured it out. You know, the founder&#8217;s a software engineer that came from doing SaaS work, just wanted to help his country out, and he&#8217;s built this amazing shop that&#8217;s, yes, software-enabled, but it&#8217;s just the modern tools of manufacturing put into a process.</p><p>I think a lot of this is going to come. I think this is what&#8217;s happened elsewhere. There&#8217;s this strategy that China used when Xi Jinping was building&#8212;it was an actual initiative you can look up&#8212;it&#8217;s called the &#8220;Made in China&#8221; initiative. And they very cunningly required American firms, in order to access the cheap labor and other subsidies associated, to partner with a Chinese factory partner to learn what they were doing.</p><p>And of course, we now learn what happened: we taught them all how to do it, and then they kicked us out. Uber&#8212;this happened with Uber, this happened with Google&#8212;they were operating in that market, they told them how to do everything, and then it was just a one-for-one move over. Chinese factories are probably running the best processes right now in the world.</p><p>So I&#8217;ve seen a few places where you can flip the script and say, well, there are some great Chinese manufacturing approaches&#8212;all the equipment is modern. You go buy the best manufacturing equipment. We didn&#8217;t just lose our factories, right? We lost our equipment. There are no factories to sell to college or business.</p><p>So, if you want to see what a really good piece of modern industrial equipment looks like&#8212;natively digital&#8212;it&#8217;s got an Ethernet plug, goes straight to the modem and the router (which is why you have to be careful). But just go look at the way those machines are built overseas. So maybe there&#8217;s an opportunity there.</p><p>But we really don&#8217;t have to reinvent the wheel. We just need to get a lot of folks interested in doing this again. I think Aeden is totally right&#8212;you set that up by getting the unit economics right, and the unit economics are really, really wrong. Technology won&#8217;t do it alone, unfortunately. I wish you could innovate your way out.</p><p>But, you know, if you do a little bit of Excel, it&#8217;s frustrating. You look at some of these parts&#8212;the part costs more to make in America, if you just paid for the electricity and the metal, than it does to have a fully turned part in China. Unless you can develop technology that makes the metal free or the electricity free, or a 99% reduction in labor because you have this perfectly automated factory&#8212;or equipment that costs $1 because you figured out how to scale this stuff to the moon&#8212;it doesn&#8217;t matter. You&#8217;re still losing. That&#8217;s because of subsidies. That&#8217;s because of vertical integration. I mean, it&#8217;s been weaponized. We&#8217;ve totally, totally, totally come up against weaponized industrialization overseas.</p><p>Akhil 35:12</p><p>Yeah, Maggie and I come from the other part of California, the Bay Area, where you can&#8217;t throw a rock without talking about AI. There are aspects of AI&#8212;or let&#8217;s just call it software-defined generally&#8212;but as you look at the sort of AI space, a lot of it&#8217;s digital, but fundamentally a lot of it&#8217;s moving to the physical world. What actually makes sense? And I hate using AI as a sort of, you know, &#8220;we sprinkle it in our coffee,&#8221; but where does it make sense to actually apply either a machine learning or some other artificial intelligence capability when it comes to the physical data?</p><p>Aeden 35:44</p><p>So, the truth is, it&#8217;s much harder to build stuff in the physical domain. It&#8217;s much harder to build stuff in the physical domain when you have extremely safety-critical applications depending on it, right? And so it&#8217;ll be a while before an AI system can make a decision that is accepted by, you know, one of the, as we talked about, conservative aerospace primes. That said, there are so many parts of operating a factory that are not as critical, where it comes in first in places where then things are going to get verified by a human, eventually verified by a test. And so, you know, we do all kinds of things at every level of this&#8212;from extremely simple things like how we inspect parts. There&#8217;s a whole bunch of things that are normally done by a human, verifying that a certain number is less than a certain number and greater than a different number, right? And we do a lot of that with software and a lot of that with, you know, I don&#8217;t want to call it AI, but more sophisticated software systems, often that are trained on a lot of data. And it&#8217;s the same kinds of approaches at the very high level. And we&#8217;ve started to toy around with, you know, an LLM that has access to a huge amount of the data in the factory. Is it making all the critical decisions today? No. Will the software get there and the technology get there so that it can sometime in the future? I actually think probably yes.</p><p>Cameron 36:55</p><p>So AI is only as good as the data that it&#8217;s fed, and the amount of data that we have, for instance, in something like self-driving cars, is orders of magnitude above the amount of data that we have on part making. The first problem is, part-making data is in the heads of humans that are retiring right now. Like, this is the first problem&#8212;let&#8217;s get these into the computers, right? And then after that, we can start to put sensors in place and directly train that system. So I think a good goal is for computers to know just as much about part making in a few years as they do about driving cars.</p><p>Akhil 37:38</p><p>When you talked about addressing this via technology, processes, and people, I want to actually come to the people part&#8212;and we can dive into more of the other two. People&#8212;I&#8217;d love to get your take on talent, what you just talked about. But actually, first, I want to come back to your story of you both in Berkeley, working on robotics. I remember first meeting you all one summer on Shattuck, at UC Berkeley, in, you know, a small little place. Share a little bit about where you came from. You shared that initial story about, you know, wanting to sell robotics, and then you turned into casting. What was that story like?</p><p>Cameron 38:15</p><p>Yeah when you met us at Berkeley we, you know, we were in a garage&#8212;one of the garage startups. So, in a garage before Berkeley, it was a huge upgrade at this old Sprint store in downtown Berkeley. Border does, because Berkeley is a crazy place to build what we&#8217;re building. But yeah, you&#8217;re right, we met you there&#8212;it was a great day. Yeah, yeah. I mean, we wanted to reindustrialize America, and we thought that the way to do it was by building robots. And I think a lot of folks see this right now, where, you know, we just have to add modern technology. We have to automate. We have to bring robots in and have the robots do the human tasks. We charged you that Rangeview was actually Rangeview Robotics&#8212;that was our formal name there.</p><p>Akhil 39:01</p><p>And that came up because you both were robotics champions in high school, right? Two at one point&#8212;is that right?</p><p>Cameron 39:07</p><p>Yep, yep. We were competitors, and Aeden and I have known each other for a very long time. Yeah, we did competitive robotics against each other &#8212; you know, Los Angeles BattleBots, the fighting ones on TV. Even before that, Aeden and I did a lot of high school robotics. And by the way, amazing program &#8212; talk about getting started early. I don&#8217;t know if I&#8217;d be doing this, or if you&#8217;d be doing this stuff, if robotics wasn&#8217;t a big part of the early education system. And it&#8217;s amazing. There are some fantastic people who built that whole system out &#8212; FIRST, back to robotics. There&#8217;s a lot of great stuff. China&#8217;s doing a really good job at robotics education too. DJI actually built probably the best robotics student competition in the world called &#8220;Masters,&#8221; and it&#8217;s incredible. You know, there are roboticists in China who are held to the cultural significance of, like, a quarterback in America.</p><p>Akhil 40:04</p><p>That&#8217;s crazy to me. You&#8217;ve got Texas football, and then you have a DJI roboticist.</p><p>Cameron 40:09</p><p>Yeah, a little bit different in America. You know, it&#8217;s hard because Aeden and I were definitely on the nerdier side growing up. So, you know, I wouldn&#8217;t say that people &#8212; put it this way &#8212; people weren&#8217;t inviting us to parties because we were good at robots. Maybe one day that&#8217;ll change. It depends on how much we really need robots to build. I think we really need them to be built.</p><p>So yeah, competitive robotics &#8212; that was it. But we looked at it and we said, wow, we need to decouple from labor. There&#8217;s no way America, with our way of life, will ever be able to support the hourly rates of overseas labor. And if we&#8217;re going to automate manufacturing, this is the big question. Everyone wonders, &#8220;Why manufacturing in America? Why don&#8217;t we nearshore to another country?&#8221; But the truth is, if you decouple labor from the manufacturing cost function, it doesn&#8217;t matter where you make it from a cost perspective. And where you make it will bring all the jobs &#8212; the people that build the factories, the people that build the robots.</p><p>That still means that people are critically important, but their value is being accrued in different or complementary portions. Think of it this way: think about a farmer. A farmer is an amazing roboticist. They&#8217;re doing the work of thousands of people with one big tractor. The tractor maker didn&#8217;t replace those jobs &#8212; the farming industry and agriculture created abundance everywhere. And we can go out and specialize and do all these great things. But what you&#8217;re doing is giving a human leverage.</p><p>The comparison I made on manufacturing in America is that it&#8217;s critically important that that leverage becomes American leverage. So we have to build factories here &#8212; not factories for everything. We don&#8217;t have to make plastic forks. There&#8217;s some stuff that, you know, we should share across the globe. But for what we&#8217;re working on, we chose very specifically to work on the things that America deserves to be excellent at.</p><p>Akhil 42:25</p><p>So you went from Rangeview Robotics to Rangeview.</p><p>Cameron 42:30</p><p>Yeah, we just lost &#8220;Robotics.&#8221; It&#8217;s like, just Rangeview.</p><p>Akhil 42:32</p><p>It&#8217;s cool, but you haven&#8217;t necessarily lost that mission, because a lot of the components you&#8217;re now providing will absolutely carry forward, whether it&#8217;s robotics or just the autonomous systems wave of the future.</p><p>Cameron 42:36</p><p>Robotics is in our DNA. Yeah, that Rangeview Robotics is in our DNA.</p><p>Aeden 42:41</p><p>It&#8217;s worth saying that the counterfactual between two people losing their jobs to robotics is not actually &#8220;automation or no automation, jobs or no jobs.&#8221; It&#8217;s actually, &#8220;We don&#8217;t do manufacturing in the U.S., and no one gets any jobs,&#8221; or &#8220;We do it here, and it supports people at the labor rates that they want to be paid here.&#8221; It&#8217;s either good jobs or no jobs. That&#8217;s the only counterfactual that there really is.</p><p>And so it&#8217;s a huge part for the factory to have very few low-wage, low-skill positions, right? This is not what Americans want to do. It&#8217;s not what the nice factories are going to be like. And it&#8217;s not actually how you make good parts at scale. You don&#8217;t want to be reliant on people that aren&#8217;t that motivated to be there to make your parts.</p><p>Maggie 43:23</p><p>So, you know, at least my sense from the outside is that the manufacturing industry &#8212; the aerospace and defense industry &#8212; is a pretty conservative industry. What does it actually take for you guys to build trust with these customers and for them to entrust you with building some of their most critical components?</p><p>Cameron 43:40</p><p>Yeah, I think Aeden&#8217;s got a really good bit on this, so I&#8217;ll give it to him. But these systems already exist. Actually, there&#8217;s an entire quality industry whose whole job is to take the liability of ensuring that a part does what you say it will do. And that is something from day one we have designed for, because there have been other innovations that have been hung up on this&#8212;saying, &#8220;Well, if we just make a cool enough thing, people will want it.&#8221; The truth is, you have to be able to prove that that part will behave the way you say it will in order for it to have real value over time. So I&#8217;ll kick it off to Aeden here for comments on qualification and what that all means.</p><p>Aeden 44:23</p><p>Yeah, no, it&#8217;s actually a good question, because I think there&#8217;s a lot of noise that comes from a lot of new manufacturing technologies about how hard it is to qualify. I&#8217;m actually a little bit less sympathetic than you&#8217;d think to this. I mostly think this is the case of that technology not actually performing. If you actually have the data to show that your process produces parts that are good enough, you probably don&#8217;t have a huge issue qualifying. The issue is when you fail spec and you need someone to change their design or redesign their system&#8212;and that&#8217;s where big problems show up.</p><p>And so for us, a big thing is, you know, we&#8217;re not doing level three. We&#8217;re not doing some new process that requires totally new design allowables and new designers to be trained up. Because the truth is, those adoption curves are extremely long. I mean, that&#8217;s what&#8217;s happening in metal 3D printing, right? You&#8217;ve just seen these companies that have amazing technology&#8212;I mean, I love laser powder bed infusion&#8212;but it&#8217;s not a technology that&#8217;s going to scale immediately to cover the whole industry, and it certainly isn&#8217;t going to scale to cover the parts that were designed in the &#8217;70s. And you know, the designers are not only unwilling&#8212;they&#8217;re actually not even working anymore. They&#8217;re retired. You&#8217;re not going to change those parts.</p><p>And so the way that aerospace works, right, is there are these long, long campaigns to make sure that your part meets specifications. There&#8217;s this contract between you and the designer, and you just go through the test. If you pass the test, it&#8217;s objective. And so for us, the huge thing is always talking to designers to understand what they need before we&#8217;re even making parts, and making sure that we&#8217;re building a factory that goes in that direction. But the truth is, if you make a technology that has advantages&#8212;if you have cost advantages and can meet all the technical requirements&#8212;there aren&#8217;t actually so many issues. The issue is when you&#8217;re trying to do something new that pushes the designer in the wrong direction.</p><p>Akhil 46:00</p><p>And it&#8217;s not just the cost and technical requirements. You are fundamentally, with the way in which you orchestrated your digital range of your boundaries, able to make novel points.</p><p>Aeden 46:11</p><p>So that&#8217;s the biggest thing. The biggest thing is when someone designs a part, goes through a long simulation and testing campaign, and then says, &#8220;Okay, we need to make the first prototype,&#8221; and they can&#8217;t make it. This is a huge problem. It&#8217;s the exact same case as the designer having to redo all the work, change the design, reduce capability.</p><p>And so the greatest customers that we work with are the ones that went to somebody else who couldn&#8217;t make it, and now only have one way to make it&#8212;and we&#8217;re enabling something huge for them. Not only are we faster and cheaper, but we&#8217;re also enabling the missile to have 10% higher thrust, 10% higher range, and higher reliability. Maybe the cost is lower because they can do one part instead of five in some cases. Those are really the best cases for us. That isn&#8217;t everything, but when we can do that, it&#8217;s a huge benefit for everyone.</p><p>Akhil 46:53</p><p>Aeden, are you seeing&#8212;you mentioned their scalability, right? And the actual ability&#8212;and Cameron were discussing earlier Freedom&#8217;s Forge, right? For those, I think we&#8217;ve talked about it before. Awesome book, and a good complement, a good sister book, is Arsenal of Democracy. The benefit we had during that period was that there was this two- to three-year, if not longer&#8212;really ten-year&#8212;period before December 7, 1941, where we in the United States, because of what they were seeing geopolitically, were actually already putting in motion the movement toward scale, right? I mean, you saw Ford already start converting some of its plants toward B-24s; you saw the work on Liberty ships. Obviously, that was a different year, different era. But are we seeing&#8212;the question I have is&#8212;are we seeing on the end-customer side the actual drive and demand beyond low-rate initial production, beyond just prototyping, to actually drive the rest of the manufacturing enterprise upstream to facilitate that?</p><p>Cameron 48:01</p><p>No, I mean, we gave it all up. It&#8217;s not here. When you don&#8217;t make consumer goods here because you&#8217;ve hollowed out the consumer base, you don&#8217;t have that surge capacity anymore, right? Who&#8217;s gonna build this stuff? The factories&#8212;and the factories for those parts&#8212;aren&#8217;t here. Even if a Ford is assembled here, they&#8217;re getting a Bosch component from a casting house that&#8217;s often in Taiwan, or often China, or often Mexico. Once again, a lot of this stuff&#8212;they&#8217;re screwdriver factories. So when you shut off that spout, like in the case of, you know, if a balloon does go up&#8212;I don&#8217;t think if a balloon goes up, the faucet&#8217;s gonna probably be shut off&#8212;and they&#8217;re gonna be in the supply chains that exist under the all-American factories that exist today. So, you know, they&#8217;re making a car in Detroit, Michigan. That car is not being made with parts that are from Detroit, Michigan. It&#8217;s unfortunate, but it&#8217;s just the place that we&#8217;re in, and so we need to shift that back.</p><p>But I don&#8217;t blame them, because that part can&#8217;t be made on good margins at a good price with the weaponized subsidies that have been leveraged against us&#8212;and it really exists in the shadows because we still think that these cars are made in America, for the factories that haven&#8217;t moved yet, right? You know, most folks are just looking at that level, saying, &#8220;Okay, well, you know what, factories for car making are still in America.&#8221; But the ones that are here&#8212;Tesla is an outlier, for sure. Tesla makes, I think, something like 70% of their cars with American parts.</p><p>But, you know, the hard parts are really&#8212;you know, if you just go on a quick deep dive here&#8212;neodymium magnet production: almost all neodymium is processed through China, or through some stage of the neodymium process. The furnace step and magnetization step are done almost exclusively in China. There are a few neodymium magnets that are, you know, all through NATO and allied supply chains&#8212;and, you know, the prices are more than 15x what you&#8217;ll find in America.</p><p>But when you talk about these factories and the surge capacity, you aren&#8217;t able to say, &#8220;Hey, you&#8217;re making alternators for a Ford. Now go start making motor components for these new autonomous systems,&#8221; or even your old legacy systems. There is no supply chain shift. It just doesn&#8217;t exist.</p><p>Akhil 50:57</p><p>It&#8217;s compounding. It&#8217;s not only there. The other aspect&#8212;I can&#8217;t just turn a Model T plant or a Ford car plant into a B-24 production line. It&#8217;s just not&#8212;if you want American parts, indeed, right? I mean, we&#8217;re doing things that are arguably a little bit more complex, but your underlying point is, even regardless of that, we don&#8217;t have the capacity. We&#8217;ve hollowed out the capacity here to be able to do it all the way upstream.</p><p>Aeden 51:23</p><p>It&#8217;s also worth saying that modern defense systems, I think&#8212;the difference between a modern defense system and a car, and a World War II defense system and a car&#8212;I think the World War II B-24/Ford maybe a little closer than the modern systems. Like, modern defense is much closer to consumer electronics, right? It&#8217;s lots of complex electronics, lots of complex sensors and cameras, navigation, right? This is closer to an iPhone than a car, and we don&#8217;t make any iPhones here, right? Maybe we make some cars here, but the consumer electronics supply chain has really been built overseas, and it&#8217;s really coming to what the latest defense systems are as well.</p><p>Akhil 51:59</p><p>Yeah, so if you guys had to&#8212;you were czar for a day&#8212;and you had two to three things you could do to reshape or reformat the manufacturing base here, what would that sort of look like? And maybe some specific sub-questions there: would it be centralized, decentralized? Would you have edge nodes where it&#8217;s closest to the potential user or operational standpoint? Obviously, we&#8217;re talking about civilian and military buy capacity&#8212;that&#8217;s it. It doesn&#8217;t matter, whatever incentive structure works.</p><p>Cameron 52:34</p><p>Buy capacity. Buy as much capacity as possible, and have contractual obligations on that capacity to go make the things that might be needed in the case of, you know, a surge scenario. But there needs to be&#8212;like, at the end of the day, someone&#8217;s got to make the parts. And the way that parts get made is because you have machines and people that know how to use the machines, and one day they&#8217;re cranking out one thing, and the other day they&#8217;re cranking out another thing. And that doesn&#8217;t exist because of the economics right now. So we have to at least match the subsidies of our adversaries to ensure that we have that when it comes time.</p><p>But we have to start doing this now. The lead times on these factories are not a year&#8212;they&#8217;re not even two years. I mean, in some cases, our foundries are looking at procuring equipment that takes over two years from order to making the first parts. So this is a decision that you have to make even before you want the ability to use it or not. So you have to get on it quick.</p><p>But I think the most certain path to maintaining the capability that is required&#8212;or building the capability that is required&#8212;is to buy capacity. I think the DOD can do this through a series of preexisting mechanisms or through some new mechanisms. DPA Title III is a really great one with good history here, but it needs to be hyper-specific capabilities. So we&#8217;re choosing a process, we&#8217;re choosing a partner, we&#8217;re choosing an application that&#8217;s proven to make sure that the execution side of this really works, right?</p><p>This is one of the great things about a factory&#8212;you can&#8217;t really put makeup on a part. The part passes qualification, and you made it in X amount of time with Y amount of throughput&#8212;or not. You can buy a factory that makes 12,000 doohickeys of X type for Y platform. In the case that platform needs to be scaled to 12,000 units a month, you don&#8217;t have to make that right now. You can use that capacity to build something else with a similar set of requirements, and that will feed back into the American private economy. But you need to have the option to be able to flip that switch. And today, you don&#8217;t have that option because you don&#8217;t have that capacity.</p><p>Maggie 55:04</p><p>So I know you all hosted INDOPACOM Commander Admiral Paparro at the factory a couple of months ago. I&#8217;m curious&#8212;how is DoD thinking about a capability like Rangeview in a future conflict in the Indo-Pacific in particular? And how will a conflict like that need different kinds of manufacturing capabilities than, say, what&#8217;s happening in Ukraine or the Middle East or elsewhere?</p><p>Cameron 55:33</p><p>The Navy can&#8217;t get parts right now. I mean, a sub will come back, a ship will come back, and there will be no way to get a part back on that system except by cannibalizing another system. There are some crazy statistics out there for just how bad it&#8217;s gotten, but the easiest way to look at it is: for these new programs, there&#8217;s a lot of funding behind them&#8212;throwing a lot of money at trying to build submarines. And if you look at the difference between the shipbuilding capability that America has versus our adversaries, it&#8217;s astonishing.</p><p>And if that&#8217;s new stuff&#8212;if that&#8217;s where everyone&#8217;s focusing&#8212;imagine just how bad the sustainment and maintenance component is. That&#8217;s one of the biggest things that Paparro was interested in when he came by our foundry and saw our technology. I think the flexibility of Rangeview&#8212;offering a capability that can one day be making critical components for the private sector, then shift when a submarine comes in and needs a ball valve to be able to make that part on the spot&#8212;is a massive capability that no other casting technology currently offers the Navy.</p><p>Akhil 56:55</p><p>Yep, and there&#8217;s a litany of congressional reports, and obviously the last reconciliation bill reflected a lot of the need to sort of recatalyze that. Specifically, Cameron, to what you just talked about&#8212;if a commander like the Indo-Pacific Commander, or just the DoD in general, wants this flexibility, does it matter where it&#8217;s produced?</p><p>And what I&#8217;m getting at is: do we need some sort of edge manufacturing capacity? Does it matter where it&#8217;s put? And does it actually make sense? If we want to try and build that out&#8212;exactly&#8212;you&#8217;re not going to print drones on the battlefield. It&#8217;s just, you know, it&#8217;s actually more wasteful to send raw manufacturing goods to those printers. Manufacturing doesn&#8217;t have an above-100% yield; it has less than that. So there&#8217;s waste generated.</p><p>Cameron 57:42</p><p>Right. So it is more space-efficient and more material-efficient to actually send preprocessed goods to the end-use point than to ship the manufacturing plus the raw goods to that use point.</p><p>And, you know, I&#8217;ve heard a few arguments&#8212;&#8220;Well, what if the need changes? What if one day we need a drone that can fly 500 meters, and another day we need a drone that can fly 1,000 meters?&#8221; The work that goes into a drone design to achieve those two capabilities is not work that can be done on the battlefield. That&#8217;s work that&#8217;s done preprocess. They might load up some instruction file to the system, but the truth is that instruction file&#8212;whether it&#8217;s the printer&#8217;s job or the whole factory&#8217;s job&#8212;can be programmed somewhere else.</p><p>And you can, you know, send 500 drones of one type and 200 drones of another, and the difference in that flexibility is far more beneficial than if you instead had an edge-deployed system that touted bringing that flexibility out of you. I don&#8217;t think we&#8217;ve really seen it&#8212;look at Ukraine. Ukraine is not printing drones on the battlefield. Ukraine is shipping shipping containers filled with thousands of these systems, fairly&#8212;at least relatively&#8212;close by from where those production facilities might be.</p><p>Aeden 59:17</p><p>I mean, I think there&#8217;s a pretty good razor as to when some sort of edge manufacturing makes sense. And actually, there&#8217;s great precedent for this, right? We&#8217;ve had machine shops on aircraft carriers since they were new&#8212;since World War II.</p><p>The case that matters is if you have a very, very big, expensive system that can be taken down by one or two spare parts. Those cases are the rare ones when you want a little bit of edge manufacturing, because it will not be cheaper&#8212;it will be much more expensive. It will be much more painful to operate. The logistics of getting materials and maintenance to the actual edge manufacturing site are going to be ten times worse than they&#8217;d ever be on the mainland.</p><p>But it&#8217;s occasionally worth it if there&#8217;s a really, really big system that needs to be kept up. And so there are some narrow cases. Most of the time, though, you really want a nice, safe, big factory that doesn&#8217;t have to worry about operational security, doesn&#8217;t have to worry about being bombed, doesn&#8217;t have to worry about, you know, the humidity changing because they&#8217;re on a tropical island and there&#8217;s a rainstorm. That&#8217;s what you don&#8217;t want.</p><p>In general, you want a big workforce. You want to be able to replace people quickly&#8212;if someone gets sick, really obvious things. That&#8217;s how you get to efficiency, and that&#8217;ll be the bulk of all manufacturing forever. There are special cases, though, when for really big, expensive systems you need to keep them up, you need to turn them around quickly&#8212;and there, edge manufacturing is a great solution.</p><p>Maggie 1:00:33</p><p>What do you think is most misunderstood about manufacturing and reshoring from outsiders?</p><p>Aeden 1:00:40</p><p>I think there&#8217;s one thing to say, which is that people picture manufacturing as, you know, just another thing&#8212;like it&#8217;s just another industry. And I think when you actually start to get into what manufacturing is, manufacturing is building the physical world, right? That is what manufacturing is. The breadth of different kinds of processes, different kinds of things that are done, and the dependency between those&#8212;and how much, you know, having a mine in a particular place can affect the price of valves&#8212;is mind-boggling to a lot of people. And I think, you know, people forget, it&#8217;s not just one process. It&#8217;s not just like fixing magnesium supply in America does not fix the magnesium casting supply, nor does it fix the helicopter gearbox supply problem, nor does it have anything to do with the helicopter gearbox inspection problem, which are all distinct, huge problems with thousands of people that work on them in the U.S. And I think it&#8217;s often forgotten, just the scale of these things, because, you know, people don&#8217;t see factories all the time. They don&#8217;t walk down the street. They don&#8217;t have friends that work in factories, right? We don&#8217;t have this&#8212;especially if you go to the coastal cities&#8212;this is nowhere to be seen. And so I think people just lose some of the scale effects of what are all the things that are going on, and how they depend on each other, and how complicated it is to change something in manufacturing, right? If you want to change where something is manufactured, there&#8217;s a lot of different pieces to it. I think that&#8217;s a pretty big one.</p><p>Cameron 1:02:01</p><p>For some context, helicopter gearboxes are oftentimes magnesium. They&#8217;re a very big supply chain problem. So just to connect that a lot&#8212;like they&#8217;re all magnesium problems&#8212;but, you know, there&#8217;s probably a billion-dollar business in multiple of those magnesium problems.</p><p>Maggie 1:02:20</p><p>What advice do you guys have for other founders looking to build either in this manufacturing or national security, defense industrial base space?</p><p>Aeden 1:02:30</p><p>Never build a cost model. Just do it on vibes.</p><p>Cameron 1:02:40</p><p>Build a cost model day one. Update it every time anything changes. We&#8217;ve already created so many competitors. Like, literally within two days&#8212;but, like, literally, we were ready. There&#8217;ve only been like two founders that just 100% exist because we existed, right? So, I mean, even if we say build a cost model, don&#8217;t go build robots day one&#8212;that&#8217;s a good one. We&#8217;ve really spent hundreds of thousands of dollars on that lesson, right? Like, that&#8217;s actually a pretty big lesson. Purchase Rangeview&#8217;s system.</p><p>Aeden 1:03:12</p><p>Don&#8217;t build software. Build an actual company that makes parts. You know, build a factory. Those are up there.</p><p>Cameron 1:03:19</p><p>Yeah. So for other startups&#8212;focus on how many parts you make a day. That&#8217;s the metric of success that matters. We need parts, not tools for someone else to maybe use. Go make parts. Make parts yourself. Go make a factory. Don&#8217;t build software for a factory that may want to use yours. Factories don&#8217;t want to use software. This is why we&#8217;re in this space. Go build a factory and make lots of parts, and make your internal success metric proportional to how many good parts you&#8217;re shipping a day.</p><p>Akhil 1:03:48</p><p>Who are you looking forward to come join Rangeview?</p><p>Cameron 1:03:52</p><p>Oh, anybody who&#8217;s tired. Anybody who&#8217;s tired of, you know, working on stuff that might not matter as much. And not to say&#8212;it&#8217;s important that the work you do matters. I think you&#8217;ve got to wake up and look around and say, beyond the money, what are you doing? Your career is going to take up the vast majority of your life, right? What are you doing with that career? What are you doing with the world? And if you&#8217;re an engineer&#8212;a really principled, strong mechanical engineer, software engineer&#8212;if you love to learn about castings, please, I didn&#8217;t want to plug it here, but our website has a careers link. You click on that&#8212;we&#8217;re expanding our team like crazy. If you want to build custom vacuum induction melters, if you want to come work on the next generation of 3D printers, you know, if you&#8217;re excellent at what you do, I would love to speak with you, and we can build this cyber foundry together.</p><p>Akhil 1:04:58</p><p>Awesome, Cameron. Yeah, where&#8217;s the company going to be in a couple of years? What&#8217;s the vision?</p><p>Cameron 1:05:05</p><p>Yeah, I mean, well, we need another Westinghouse, don&#8217;t we? You know, we need someone that&#8217;s making the world&#8217;s stuff. And I think that&#8217;s going to end up with folks that understand the new paradigm. I think that&#8217;s folks that understand modern technology as it relates to manufacturing and folks that understand automation. I think we&#8217;ve got a pretty amazing team here, and I think everyone here is doing it for the right reason. So I&#8217;d hope to be making a lot of parts.</p><p>Akhil 1:05:33</p><p>Awesome, awesome. Well, Cameron, Aeden, this has been awesome. Thanks so much for taking the time. Excited for what you&#8217;ve already built, what you&#8217;re unlocking both in what can be built going forward, what is impossible, and what can be scaled going forward. Excited to be part of the journey with you.</p>]]></content:encoded></item><item><title><![CDATA[🎙️ Ep 8 - Seasats: Scaling Persistent Maritime Autonomy]]></title><description><![CDATA[Encounters with Chinese destroyers, how maritime autonomy differs from Waymos, and more...]]></description><link>https://maggiegray.us/p/ep-8-seasats-scaling-persistent-maritime</link><guid isPermaLink="false">https://maggiegray.us/p/ep-8-seasats-scaling-persistent-maritime</guid><dc:creator><![CDATA[Maggie Gray]]></dc:creator><pubDate>Fri, 12 Sep 2025 14:46:13 GMT</pubDate><enclosure url="https://api.substack.com/feed/podcast/173418621/86a4c710e97167532136c0f4cf92f6b1.mp3" length="0" type="audio/mpeg"/><content:encoded><![CDATA[<p>Why don't we see autonomous boats sailing around San Francisco Bay the way we see Waymos (and soon, Robotaxis) all over SF? In the latest episode of the Mission Matters podcast, <strong><a href="https://www.linkedin.com/in/matt-kaplan-86107a177/">Matt Kaplan</a></strong> and I sat down with <strong><a href="https://www.linkedin.com/in/mikeflan/">Mike Flanigan</a></strong>, the CEO of <strong><a href="https://www.linkedin.com/company/seasats/">Seasats</a></strong>, to discuss the current state of maritime autonomy (and why the tech is harder to build than a Waymo!)<br><br>We cover:<br>&#128741;&#65039; Open technical challenges in building autonomous boats (computer vision, power management, "long tail challenges," and more)<br>&#127464;&#127475; The asymmetric advantage small, cheap USVs provide the <strong><a href="https://www.linkedin.com/company/us-navy/">US Navy</a></strong> compared to large aircraft carriers and destroyers (like the $1B Chinese destroyer a Seasats Lightfish encountered on a mission last month...photo below)<br>&#127482;&#127462; The role USVs have played in the Russia-Ukraine conflict<br>&#9889; And much more...</p><p>You can listen to the podcast on <a href="https://open.spotify.com/episode/0f2SavowUNpzg3T7sy6Z2t?si=gfMYDCwvRqKluaBDVAOI_Q">Spotify</a>, <a href="https://podcasts.apple.com/us/podcast/seasats-scaling-persistent-maritime-autonomy/id1807120572?i=1000726396929">Apple</a>, <a href="https://shieldcap.com/episodes/seasats">the Shield Capital website</a>, or right here on Substack.<br><br>As always, please let us know your thoughts, and please reach out if you or anyone you know is building in the national security domain.</p><p class="button-wrapper" data-attrs="{&quot;url&quot;:&quot;https://maggiegray.us/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe now&quot;,&quot;action&quot;:null,&quot;class&quot;:null}" data-component-name="ButtonCreateButton"><a class="button primary" href="https://maggiegray.us/subscribe?"><span>Subscribe now</span></a></p><div><hr></div><p><strong>Maggie (00:04):</strong> In this episode, we're joined by Mike Flanigan, the CEO of Seasats, a startup building the future of autonomous systems for the ocean. I'll say Seasats is definitely one of my favorite portfolio companies, in part because I think it's one of the easiest of our portfolio companies to explain to people who work outside of this industry. They're building some super cool stuff. In short, Seasats builds solar-powered autonomous drone boats that sail themselves thousands of miles across the ocean.</p><p><strong>Matt (01:06):</strong> Yes, and the Navy has decided it needs a lot of autonomous boats. One thing that struck me learning about this space is that the unmanned surface vessel industry isn't actually new. I mean, you can go all the way back to World War Two, where several major powers used USVs for offensive operations, minesweeping, and even dummy practice targeting. And then 80 years later, you have this operation in the Black Sea in 2022 where the Ukrainians used remotely controlled drone boats to sink part of the Russian Black Sea Fleet, and it's considered this watershed moment in maritime autonomy. And now Congress, the U.S. Congress, is planning to allocate nearly $2 billion for USVs. So I think there's this important question of why now? What about future conflicts makes these platforms so important? And why haven't cheap, unmanned, and autonomous vessels been adopted at a large scale before? Thankfully, today we have Mike on the show to explain this unique moment in maritime history, both technically and geopolitically, and what it all means. Seasats is one of the leaders in maritime technology, so we're super lucky to have Mike here today. Mike, thanks for being here.</p><p><strong>Mike:</strong> Absolutely, thanks for having me on.</p><p><strong>Matt:</strong> Let's start there. The USV industry isn't new. So why is there so much momentum for the industry today, both technically and strategically? Why was the Ukraine war the first time that cheap USVs were used for such an important strategic effect?</p><p><strong>Mike (02:41):</strong> Good questions. Yeah, as you pointed out, Matt, the USV industry has actually been burgeoning or growing for a long time. It's kind of been this building momentum, or maybe tension, of like, okay, the commercial market value has always been there. It's very expensive to do anything on the ocean, which we can get into later. But the technology tipping point, I would say, has been held back. And then one of the interesting things about the Ukraine-Russia war is that full-scale conflict releases some of the rules of engagement. And that actually suddenly crossed us over the point where unmanned systems become incredibly effective and revolutionary, game-changing overnight. I think when the very first videos were hitting Twitter of USVs sinking Russian ships, it was like, okay, the next day at conferences in D.C. and San Diego and California and really around the world, people are talking about this. They're like, okay, we need to change what we're talking about because everything has changed for maritime. So I think that is really what led to the tipping point, kind of unleashing it.</p><p><strong>Maggie (03:48):</strong> Mike, maybe could you differentiate? I think we have both USVs, unmanned surface vessels, but then also ASVs, autonomous surface vessels. So where actually is the tech today? What's actually being used on the battlefield, and where are we heading?</p><p><strong>Mike (04:06):</strong> Yeah, that's a good one too, Maggie. So USVs has been the traditional term, particularly for the Navy. They've gone with unmanned surface vehicles or vessels&#8212;it changes a little bit. We like to use ASVs to distinguish the autonomy. It's like, hey, you don't always need a human in the loop. I mean, some things are really bad. A human in the loop would be someone needing to take active controls just to continue the mission. Imagine someone who's holding down the go stick&#8212;that's a human in the loop. Human on the loop would be someone monitoring to make sure that it's doing the right thing, and that would be a USV. And an ASV would be like, okay, maybe the ASV is conducting its own mission, potentially without communications, and then it's pinging back information and asking for decision-making input. So really, an autonomous system, as far as we know&#8212;particularly some of the kinetic USVs that have been used&#8212;would probably be properly termed USVs. They're using video feeds to conduct targeting where an operator is watching that feed, directing the vessel, and conducting final guidance maneuvers. And that's both in the Black Sea with Ukraine as well as in the Red Sea with the Houthis, as far as we can tell.</p><p><strong>Maggie (05:20):</strong> And why move towards ASVs rather than just stick with these remotely piloted USVs?</p><p><strong>Mike (05:27):</strong> Yeah, so on that one, it's interesting. Ukraine-Russia is totally the modern lab in terms of warfare and what's changing incredibly rapidly. One of the open pieces of contention is people saying, like, hey, don't over-learn from Ukraine. I would say that there's&#8212;I'm more usually in the camp of, hey, those people are usually in a traditional camp and have something to lose if things change and everyone wakes up to that. But one example where that's probably accurate is, okay, for a real near-peer competitor, let's say a global threat like China, really you're probably going to be dealing with very sophisticated systems like intensive jamming, intensive electronic warfare. So a USV might not be appropriate because those links are very easy to pick up on in maritime and to cut and to sever and to disrupt. So you might need the autonomy. And I would say in terms of getting to&#8212;the second reason for needing autonomy is for persistence. If you think about it, you have this scaling problem. At Seasats, we build these very long-duration, very long-range platforms. If we put out 1,000 USVs or ASVs, sorry, and they're out there for months at a time, well, it's very unscalable to then have a whole bunch of human operators watching. You really want someone doing that command-level intelligence.</p><p><strong>Maggie (06:54):</strong> So what is the state of tech&#8212;I guess first I'll ask&#8212;of our adversaries? I know you mentioned China, you mentioned Russia. I know the Ukrainians are using some of these more remotely piloted systems. Where are our adversaries in both developing and then deploying maritime autonomy today?</p><p><strong>Mike (07:12):</strong> Well, one thing's for sure: definitely China is the manufacturing leader of the world, like it or not. And so, particularly if you look online, the number of USV systems that are getting proliferated by China is actually massive and at incredibly cheap price points. They're not all&#8212;or the majority of them don't seem like very sophisticated or useful products. But at the same time, it's kind of like there is a quality to quantity, if there's just thousands of really kind of crappy systems. Well, you do need to contend with those. I think that's one of the things that the U.S. in particular has learned. If we're talking about the state of technology and affairs, we'll go from&#8212;let's say we just touched on China, which I'd say is mass manufacturing. In the Red Sea, the Houthis are launching relatively cheap drones, like missiles, and then also USVs, and some really interesting USVs in their attacks on&#8212;you know, terror attacks on global shipping. But if you look at them, it's like these are very much like maritime IEDs, like improvised explosive devices. You've got fishing boats loaded with explosives with decoy things in the front to look like a human driver, to create confusion and uncertainty. Unfortunately, even such crude systems need to be countered by usually more sophisticated systems. So the U.S. ended up in this very difficult cost equation where it's like using expensive missiles to shoot down very cheap drones. So that's a problem.</p><p>In Ukraine, I would say that they're at a little bit more of a sophisticated level with their maritime technology, where, despite them being remote, they've shown definitely the world's leading implementation of USVs. I mean, they're launching 10 drones at a time to go do things. They're swarming Russian ships, taking out propulsion first, and then striking critical equipment second, and doing follow-on strikes. As well as now, Ukraine has again kind of opened up the history books and made everyone look because they then mounted aerial vehicles and are launching long-range USV missions with aerial strikes at the end into Crimea. And then taking that even further is kind of like, what is the logical counter to USVs? Typically aerial vehicles, and really helicopters are able to match speed and probably have the best gunnery and perspective advantage to stop USVs. Well, then the Ukrainians added surface-to-air missiles and even, I think maybe an FPV&#8212;but I might be wrong on that&#8212;but at least a surface-to-air missile and took down a helicopter and then took down a fighter jet. So now it's like, okay, even those counters don't make a lot of sense. So definitely, the pace is changing extremely quickly. I would say Ukraine is definitively the leader in this space, even if what they need to do due to their ongoing war is maybe not what the U.S. needs to focus on.</p><p><strong>Maggie (10:02):</strong> So then, where is the U.S. Navy in this whole ecosystem, in terms of actually adopting USVs and/or ASVs at scale?</p><p><strong>Mike (10:14):</strong> Yeah, well, there's certainly a lot going on. The U.S. Navy has a lot of folks, a lot of logistical power, and a lot of budget to be spent on trying to solve problems. I would say it's been fractured and very spread out between many different groups, whether that's Service Warfare Centers, autonomy-specific groups, innovation-specific groups like DIU&#8212;you name it. It's kind of like this was getting worked on in a ton of different areas. There have been recent big bets with the Replicator program by DIU and Hellscape. I would say that one of the common threads is everyone's aware that it needs to move faster.</p><p>And one of the things that I definitely see from the Seasats perspective, because we actually work with a large number of the different Navy groups, both through their exercises, through combatant commands, and through field operations&#8212;one of the things that I would say is a common thing that a lot of the folks within these groups know, the service members, is like, oh, we need to be testing in more realistic ways. The whole innovation cycle&#8212;the DoD is very focused on solicitations and big bids. Unfortunately, that lends itself really well to lobbying and marketing clout and the fanciest proposal winning, and it does not lend itself well to effective, cost-effective, and mission-success-based products. So when we do see the DoD do kind of testing, I think sometimes the results are surprising. We can't talk about them all right here, but one or two of our customers, more in the special operations side of things, we've seen do straight-up competitions and end up with some very interesting results that are not always the biggest names who have raised the most money.</p><p><strong>Matt (11:59):</strong> Super interesting. I want to kind of pivot to the platforms that Seasats builds. To your point, Mike, on some of the customers you work with and the platforms that Seasats builds, and what use cases you guys are focused on. So yeah, we've all seen in the news recently that Seasats successfully sailed a Lightfish from California to Japan autonomously, and then separately, I saw you guys released a photo that was a high-resolution image of a Chinese destroyer in the South China Sea. Those seem like a big deal to us who are outside the companies and the government organizations that are working on these problems. But can you contextualize that a bit for us? Are these things that every company is doing, and what do these announcements tell us about Seasats' capabilities and what you guys are designing your platforms for, and why?<br></p><p><strong>Mike (12:53):</strong> Yeah, thanks, Matt. It definitely, I would say, is a big deal. It's pretty exciting. Our company was excited, tons of our customers were excited, and tons of people who just follow the industry were excited. I think one of the reasons that this is a big deal is if we look historically at what programs have been able to do cross-ocean missions, they're all large. We're talking about 200 to 300-foot ships, typically. That's the amount of material and resources required to cross multiple thousands of miles.</p><p>It's an interesting problem because for the Navy in general, these oceans are both historically a great protector of the United States and any country that has big oceans. It's like, okay, someone has to cross that whole ocean. In the investment world, we use the word "moat" to indicate a very small ring of water around a castle or a defensive piece of technology. It's like, if you have an ocean protecting you, someone has to cross entire oceans to get there, and they need a way to get across. You need heavy equipment to be moved. So typically it's required massive ships and equipment.</p><p>I think what was very important and kind of contextually relevant for the Seasats cross-ocean mission was, hey, we're showing that very small vessels can do this. And in today's day and age, with satellite technology, RF sensing, et cetera, big things are very visible. The world's never been so transparent, and so ships that it used to be that aircraft carriers could go hide in the ocean. You know, in the war in the Pacific, Japan and the US were going around and didn't know where each other's ships were. We had to send out scouting planes to spot the fleet and then go engage. Now that's changed. With the proliferation of low Earth orbit satellites and the intelligence agencies getting very good at their jobs, everyone kind of knows where the big ships are. They even know where the bases are. This is becoming a massive problem for the DoD in general.</p><p>So for small things to be able to do these missions is very important, because we're showing hey, small things that cannot be tracked are very hard to disrupt and are very inexpensive to build. So the cost equations on our side can be very, very relevant to today's missions, because you can cross entire oceans. You can go put them within a couple feet of a key area with great precision. So it's certainly kind of changing the understanding of what is possible.</p><p><strong>Matt (15:19):</strong> So it seems like, from what you're saying, the unique value proposition of Seasats is doing these long-range, high-endurance missions that are typically reserved for orders of magnitude more expensive and significantly more visible ships. Really, that's kind of the key advantage you guys have built. Is that fair to say? And are these the types of use cases you'll stick to in the future, or do you plan to expand the technology and product suite to other parts of the maritime domain as well?</p><p><strong>Mike (15:53):</strong> Yeah, I would say maybe I'll answer the future expansion second. But I think the first part you hit is really good there. It's like, okay, things that were typically much larger and more expensive. So you asked about the Chinese destroyer that we had this 20-minute encounter with on the Pacific Ocean journey. Well, typically, a destroyer like that, once a carrier strike group goes out to sea, they're not going to encounter anything except for other large vessels, maybe occasionally long-distance ocean-going commercial shipping traffic. But it's kind of an empty world, except for these other large capital assets. No ships out to sea are, frankly, as low cost as a Seasats Lightfish.</p><p>So the fact that we're able to be out there and say, like, hey, you have to contend now with the fact that you don't just have to have your watch on high alert when you're within 100 miles of coastline. It's like anywhere in the ocean, we can proliferate ASVs and both deliver high-quality, high-resolution, near real-time intelligence, and potentially also layer in offensive effects if necessary. So really, it kind of changes the dynamic. Just looking at that one specific one, a Chinese Type 055 destroyer that costs nearly a billion dollars to build&#8212;it's like $930 million. A Lightfish sells for $250,000, so it's actually less than that. But really, the asymmetry there is very remarkable.</p><p><strong>Matt (17:26):</strong> So on what you guys are sensing in the ocean side, one example is sensing and being able to detect and characterize a Chinese destroyer. What are the other use cases for having this proliferated constellation of really cheap, low-visibility ASVs that you guys make?</p><p><strong>Mike (17:53):</strong> Yeah, one of the fun things is we started the company very much in the commercial space, and so we've done work from subsea mapping, which is important for construction of offshore oil and gas, offshore wind, for monitoring pipelines. We've done work for the fishing industry, like shellfish monitoring, monitoring water quality. Unfortunately, every year someone gets poisoned by shellfish that have toxic water in them. And so being able to monitor those things in real time is very impactful.</p><p>We've talked about industries that drive the maritime economy. There's a whole range of these things. It's a pretty exciting and interesting world. People, particularly on the security aspect, has gone up a lot in recent years. You know, it used to be that folks would build things in the ocean, and then it's like, well, it's safe just because it's in the ocean. Like you lay down an internet cable or a pipeline or build a dam, and it's like, well, no one's gonna mess with this. It's all the way out there. That has certainly changed. There's a lot of gray zone conflict of people sabotaging equipment. And so now we're getting a lot of outreach from commercial companies asking us to do what is essentially very routine security jobs. It's like, hey, we just want data analysis and very timely warnings so that we can protect what ends up being many hundreds of millions of dollars worth of critical nation-state infrastructure.</p><p>On that side, it's very fun because we're definitely in the lead in terms of commercially viable technology. Unlike US Navy technology, there's a lot of stuff that's focused on pointy, full-on warfare. However, most of those products don't have the safety systems, the liabilities, or just the commercial viability to be at all relevant to the commercial industry. Many of them talk about dual use, but realistically, we don't see a single sale that they can point to in the commercial space. And that makes sense, because the commercial world is much more sensitive to ROI and actual stuff just making practical sense to a layperson, rather than the harder mission, but a very different mission, of delivering ordnance on a target.</p><p><strong>Maggie (19:54):</strong> Yeah, Mike, speaking of those commercial use cases, I mean, I think about the autonomous vehicle industry in San Francisco. Matt and I both live in SF. I know we both take Waymos all over the place, and from a non-expert's perspective, this seems like a harder problem&#8212;getting cars driving on the streets of San Francisco, where they might hit somebody walking in the middle of the street, or where there's gonna be random U-Hauls just parked in the middle of the street or whatever. The open ocean seems like it would be an easier&#8212;which I put in quotes&#8212;problem, or technical problem. So I guess, why are we seeing the maritime space sort of lagging behind the ground vehicle space when it comes to deploying autonomy? Is this a regulatory thing? Is it actually a technical thing? Is it just a market-based question? What's your perspective on that?</p><p><strong>Mike (20:48):</strong> So I would say, to answer that in two different lights, the hardware problem on a lot of the different things, I would put open ocean maritime robotics closer to the space industry, like satellites and such, rather than the autonomous car industry. But I do think the autonomy is directly related to the autonomous car industry. So let's talk about that first.</p><p>I think that something that was interesting that we saw with the autonomous car industry is everyone kind of thought that it was gonna be pretty easy&#8212;that was like, oh, we can solve this right now, in maybe the 2018 timeframe, kind of the breakout of some of the new machine learning models. It's like, wow, computer vision is so much better, neural nets&#8212;we're just gonna smash this. And there's a huge surge of funding and companies, and then, really, none of them solved it. And the only ones we have left are Waymo and Tesla, who are actively duking it out in relatively confined rollouts. You know, Waymo is kind of like a very progressive, building chunk by chunk very reliably, and Tesla is kind of still this big unknown of like, are they suddenly going to unlock full vision-based, incredibly affordable autonomous driving? We'll see.</p><p>In the maritime space, we have the same problem. What held them up, what killed all those companies, I would say this is a long tail problem. So the problem is that 99% of the driving is easy and solvable, and they probably all did solve it quite well, but that 1% chance of like, okay, kid runs out from behind a car, and a human driver is incredibly good at identifying in milliseconds and then jamming on the brakes, and we come to expect that out of autonomous systems. We don't want to let an autonomous system out on the road that is just a terrible driver in these really important moments.</p><p>Maritime has the same long tail problem. Okay, a kayaker comes up, a jet ski comes up, a tanker is crossing on a windy day through a tight canal, and there's a sailboat coming, and it's like the rules of the road say that one should give way to the other, but a captain or a mariner or pilot needs to make a tough judgment call to say, like, ooh, I would rather let us bump than cause the situation like the Suez Canal or the Ever Given that got stuck. You name these massive maritime disasters&#8212;they're really tricky. They're basically these maritime situations that still have really high, critical, important moments, but now it's actually much harder, because instead of having a massive bulk of training data to get through the bulk of this, there's very little. It's very low volume, and it's a false sense of security. Like you can go out and operate for months and say, oh, we have COLREG-compliant software. And it's like, no, they probably don't. They just had very few interactions. And anytime someone gets nervous, they switch on a Starlink and just watch the cameras and do a little nudging if they need to. So I think that long tail problem is the tricky thing that's holding up maritime.<br><br><strong>Maggie: </strong>Mike, what&#8217;s a COLREG?</p><p><strong>Mike:</strong> COLREG&#8212;thanks&#8212;the collision regulations. These are a set of guidelines about how vessels on the ocean should interact with each other, and it's the International Maritime Organization, or IMO, that published them, jointly with a bunch of different nations, I don't know, maybe 50 years ago or something. And yeah, ASVs have been struggling with them ever since.</p><p><strong>Matt (24:08):</strong> Yeah, going a bit deeper on the tech stack, I want to better understand where Seasats comes into this. You talked about being the only company in the military maritime space that also has a commercializable product. You said you started commercial, have commercial customers, and then that would seemingly give you a lot of technical differentiation in the intelligence and surveillance and reconnaissance ISR missions, right? Could you talk a little bit more about what differentiates Seasats technically from other companies in the maritime space or from legacy ship companies, and what are the hardest parts of that tech stack you guys have built? What are the hardest challenges you've had to solve?</p><p><strong>Mike (24:58):</strong> So I'll start with the traditional companies and then move towards some of the newer companies. I would say the traditional differentiation is that in maritime, to build these ASVs, and I'm going to keep it focused on the offshore, so offshore and longer endurance missions where you need to be out for more than one day, greater than 24 hours, and operating at least a mile offshore. When you do that, you go from hundreds of competitors down to just a handful that say they can do it, and even fewer that have proven they can do it. We're probably talking about a single hand's worth of companies. The field thins dramatically.</p><p>Why is that the case? It's because you need to solve a wide array of problems and you need to be competent, or even expert, at all of them. You can't just be good at one or the other. So there are a lot of boat building companies that say they can build autonomous boats, but if they don't have modern software, they don't have great electrical engineers, they don't have the full expertise that these autonomous systems require, then they just don't succeed. It's a good looking boat, but it doesn't actually do what they need.</p><p>There are other companies, like in San Francisco, where I've seen some startups that pop up and say we know software and we're going to build a sweet autonomous boat because boats are easy, and it demos really well. But you see 8020 aluminum, which is a very common prototyping aluminum, like rickety stuff bolted together, ripping around for demos in the bay, and that's essentially irrelevant to the real mission. Until those companies recognize that they need to hire really good mechanical engineers, really good naval architects, and even really good electronics and electrical engineers, they won't succeed.</p><p>You can't just find off-the-shelf solutions. If you just buy a Jetson, like an NVIDIA Jetson, that typically sucks five to twelve watts. Doesn't sound like a lot, but most PhDs in autonomy have not considered power consumption being a problem. If you're out for days and days and days, you need to manage your power budget. You need to switch things on and off. You need to handle different communications networks. Just the number of problems you need to solve is massive.</p><p>Even just communications, which I just mentioned there, if you just run Starlink all the time, it's 60 watts. Now maybe you're having to run a gas generator. But guess what, if you run any type of internal combustion engine like gas or diesel, you typically have a person service those every couple hundred hours to change the oil and change the seals. Even our cars do not run close to that long, even though automotive is one of the highest reliability industries in the world, and they need a lot of servicing.</p><p>So I think the problem here, technically, is that there are a lot of things to solve, and it's very easy to start, but it's really hard to finish. It's just another one of these long tail problems. It's really hard to get to the last couple percent, and those end up mattering in the ocean industry.</p><p><strong>Matt (27:42):</strong> Yeah, I think that's a super interesting point about how to build autonomy. From what you're saying, what I'm taking away is that to build autonomy, it's not just a software problem, but especially in maritime, it's a hardware problem as well. But I feel like we see companies in the space who are saying, "Hey, we know how to build boats. There are a lot of people out there who know how to build boats. We don't need to reinvent the wheel. We're just going to build the software that retrofits those boats, or maybe we make some slight modifications to handle the power, the comms, or the other problems you just talked about. But we're not going to have a proprietary design for our vessel, because people know how to build boats." So could you talk more about why it's really important to be the ones building the boats yourself? Why not just retrofit boats with software kits and maybe a few other things that help you monitor and manage things like power and comms?</p><p><strong>Mike (28:41):</strong> Yeah, that's a good question. And you know, if we could buy boats off the shelf that did the missions that we needed, we absolutely would. We joke all the time that we would love to outsource more. We wish we could outsource more.</p><p>One of the things that Seasats started with was these man-portable boats. Some of our very first government customers were special operations, and they had these hard requirements of, "Hey, we need to be able to show up to a location and with just people, get this thing into the water and start the mission, and do that without lining up a crane or a forklift." So that immediately puts a very hard requirement in terms of how much weight is acceptable.</p><p>And so for us, we end up very much in this composite, very compact space, trying to build these really long range, really capable stealth platforms. And they have that weight and size limit. Now because of that, we have to pack all this stuff in and do all this design work. And really, we have to own the entire solution. It's not okay to throw it over the wall and say, "Well, someone else will hopefully solve that," and then have a vendor send it back and it's a little bit too heavy.</p><p>That has led us to a point where we're now winning sole source awards, and where our customers tell us, "Yeah, you know, there's nothing else out there that is that size, that capable, with that range and has proven performance. It just doesn't exist." You can look at the trade space, and there are dozens and dozens of companies, and they make big things, they make fast things, they make short range things or small things, but nothing that hits both of those requirements.</p><p>The cool thing is, I didn't realize, and I don't think we realized, just how helpful this would be for commercial market growth, because it turns out that shipping around the world is a huge pain. And if you can make something small and portable and very capable, then you can also ship it really affordably. So we get a lot of contracts where they say, "Hey, we need to do this thing in this other country, and we have six weeks to do it." And there just are not many options for what you can actually commercially air ship around the world. We're right at the limits. We already have to have people who are really experts in shipping, logistics, going through customs, doing all this stuff.</p><p>So yeah, it turns out the size and weight, I kind of like to think about this like cell phones or computers. You know, it used to be that you had giant computing rooms, and then it was like, "Hey, now it's only the size of a fridge." Then it's like, "Oh, now it's the size of a refrigerator or a microwave," and now it's in our phone. And it's like, okay, if it's smaller, you can scale it better and faster. So really, everyone would do everything as small as possible if they could. Typically, you go bigger if you have to. So the smaller the better. It's just that it requires a lot more engineering.</p><p><strong>Matt (31:18):</strong> Yeah, I imagine on the US government side, there would be a lot of contested logistics interest in a platform that can not only be shipped overseas easily, but in some cases, can ship itself overseas easily. Is that something that your customers have gotten excited about?</p><p><strong>Mike (31:35):</strong> Yeah, I think that's a cool one. Because in contested logistics, okay, how do we maintain a fighting force, or standing force when we've got conflict with an adversary and where supply lines are not as easy? You know, you can't just fly a big cargo plane in or send a big boat. It's going to be a target.</p><p>Well, the cool thing about the stuff that we're doing, if it's really long range and small, is we can change its logistics balance, both in terms of maintenance. You know, it's like, "Oh hey, that might be difficult to maintain, right?" Well, what if you only have to maintain it twice a year? If you maintain it twice a year, it's like, well now, I mean maintenance every six months, sure, just stockpile a tiny pallet, and you're good for multiple years. So you totally delete this problem by making the things be very, very long endurance and self-reliant.</p><p>And then the second one, like you mentioned, is they can just go super far. So it's like, great, you can basically get into contested areas, and the smaller, the better. I think signature management is a huge thing that people are learning in terms of unmanned systems.</p><p><strong>Matt (32:33):</strong> Yeah, I wanted to ask just another quick question about how you're designing for persistence. The Trans Pacific mission, what was the one where you went from California to Japan? What was the hardest thing to get right technically to make that mission successful, and from a design standpoint, what did you learn from it?</p><p><strong>Mike (32:58):</strong> Here's the thing about all these challenges - there are the problems you don't want to solve, and those are probably the ones that are most important. You could build the boat lighter, or you could build the boat faster, but you really need it to work day in and day out, so you have to respect those constraints and requirements.</p><p>Our vessel is actually a hybrid vessel. Not many people know that. People either think it's an electric motor that's battery powered and forget that all the solar panels actually harvest an enormous amount of energy when you're very efficient with your power budget. For many months, you need solar power. But it's also hybrid - it uses a fuel cell, and that's really important because it has the ability to work for weeks even if it's very cloudy with big storms. For other applications that are carrying high power, high draw payloads like electronic warfare payloads, they require hundreds of watts. You can only do that and then recharge quickly if you have a hybrid system.</p><p>That required a lot of engineering. When we did our first prototypes, it was not hybrid - it was pure solar electric. We realized from doing missions that we needed to tackle this hybrid challenge, and we invested in it. It took a ton of engineering. Some of the cross ocean missions actually unveiled things about those hybrid systems that you're only going to learn when you have boats out in massive storms and huge waves. You have to decide how to choose the right level of simplicity versus complexity. If you make the design decision to add some actuator to close some air vents, that adds configuration management, extra parts to build, and extra failure modes. You need to carefully weigh the decisions to add those things. Those open ocean missions are really where we prove that stuff out, where we validate our design and share it with the world so that people know what the status of this technology is.</p><p><strong>Maggie (34:53):</strong> How do you guys go about actually building some of the machine learning models and tools that you deploy on these systems? I know you mentioned, and we've heard from others, that there is a big shortage of maritime data to train something like a computer vision algorithm. There's only so much real world testing you can do. What does that pipeline look like, from data preparation to training to testing, simulation, and evaluation?</p><p><strong>Mike (35:21):</strong> Well, I think we're fortunate that the machine learning world as a whole has moved forward massively. We leverage open source models. We take the best in class, and then we have our own data libraries that we've built up. Then we fine tune and train to a maritime perspective that's relevant to our boats, because it's all about matching data distributions. If you take the best Tesla model and then ask it to do something random in your house that it's never seen before, it's probably going to do poorly because it just hasn't actually seen that type of data before. Having on-target data is really important.</p><p><strong>Maggie (35:56):</strong> Is that just data that you guys have collected, or are you using simulation or synthetic data?</p><p><strong>Mike (36:01):</strong> Yeah, typically for us right now, we've evaluated synthetic data, but currently we have this advantage where we have boats all over the world, and they've been out there for years. In some cases, we have a lot of data, and we're getting more every day. Our amount of data is accelerating. Currently, the best data is real data. I anticipate eventually we're going to use synthetic data to replicate certain specific things that are really hard to see variety in. But right now, we're sitting on a very good host of data, and we're even doing some data collection contracts for other folks in the industry because they say, "Hey, we don't have a way of getting this affordably." So right now, we're putting out a lot of data.</p><p><strong>Maggie (36:41):</strong> And then are you doing all real world testing, or are you also doing testing in simulation?</p><p><strong>Mike (36:46):</strong> We do a ton of simulation, as well as accelerated hardware-in-the-loop testing. That's very common in automotive and aerospace. I will say, with some pride and joy, that back when I was writing software at Seasats in the very early days, one of the things I contributed was writing our simulation engine - our first simulators. That allows us to test a huge amount of our code without the software ever knowing that it's not actually out in the real world. You can simulate sensors, you can simulate comms jamming, you can simulate a lot of things. Then we pair that with real world validation, because certain things like comms degradation - there are tools to simulate them, but a lot of times they're not quite accurate to the real world.</p><p><strong>Matt (37:27):</strong> You mentioned that you now are actually selling some of these data sets to other customers who want to use it to train their maritime autonomy stacks. To me, that seems like something that can serve the whole industry and potentially be a large part of what your company does itself, just because of the unique data quality and quantity that you're collecting out on the ocean. How do you see that in terms of being part of your product offerings in the future? Is that a big part of it? And secondly, are you planning to deploy missions for the express purpose of collecting data that you can sell, or is this just downstream of having a bunch of Seasats out there conducting missions that you're able to sell the data from?</p><p><strong>Mike (38:14):</strong> It started as the second, where it was a downstream effect of already having the boats out there doing something, but it's definitely moving towards the first, which is specific missions tailored towards getting specific data and then being able to sell that data stream.</p><p>When we started the company, our name - the abbreviation is Seasats, but the long form is C Satellites, C Satellites Inc. We were in a space-based accelerator, Tech Stars, and we had early investors and advisors who were all out of the space industry. They really saw what I fully believe in, which is that this is going to transition to the point where these USVs are very much treated like satellites. We have fleets of them out off coasts, off Economic Exclusion Zones, able to provide continuous, affordable, high resolution data.</p><p>The people that need it - Coast Guard, Border Patrol, DEA, mapping services, fishing industries - they subscribe to that data and say, "I need to know when someone crosses into this area." We become the contractor that keeps the satellites working. We maintain the boats, we improve the autonomy, we handle collision avoidance, liability, all these different things, and we just provide uptime. We've done that pretty successfully for the US Navy and for a couple of commercial customers in a few different cases, and they've always been really happy, and we've always been really happy because it's a great business model.</p><p><strong>Maggie (39:36):</strong> Mike, have you all had to go through the process of actually integrating some of your systems with DoD systems or with Navy systems and some of their data feeds? I know we've heard - we just did a podcast earlier with some technical leaders in the Navy - and they said integration is one of the number one challenges that they see startups and honestly primes alike manage. I'd just love to hear about how you all have gone through that integration process.</p><p><strong>Mike (40:04):</strong> Yeah, I listened to that episode with Justin and Artem, and I totally agree. The integration problem is super key. Luckily for us, we knew this industry&#8212;we'd been in the space for about five to ten years specifically before starting Seasats. And so integration was something we took seriously from the beginning. One way to solve that is making sure that you have very open APIs at the endpoints where they need to be met. So we spend a lot of time writing software to integrate with systems like Minotaur Lattice, L3Harris systems, Copiers, AFS&#8212;you name it, all these different common operating and common intelligence or collaborative autonomy systems. And we've integrated with close to ten at this point, and it's always pretty easy for us. We use standards that are well known, government developed, and are easy to work with.</p><p>You know, I also really enjoyed that part of the podcast, which asked the question about just how hard it is to get onto Navy ships, or how hard it is to integrate with operational units. And I think one of the things that was recommended on there&#8212;I forget whether it was Justin or Artem that recommended it&#8212;was to initially go for standalone systems, because it's easier to get the paperwork approved, and then later move to fully mature, super tightly integrated systems. That's the route that we went, and it has been successful. We've managed to get Seasats onto grey hull Navy ships in important parts of the world. And it's always done because, basically, people realize the critical need. They realize the capability that a Seasats system can offer. They look at its size and say, "You know what? We can slap that in this area, have minimal approvals necessary, operate it slightly in parallel, and it offers the military a unique capability." And so that's how we've gone about integration. And then now that we're at the phase of larger sole source contracts, we are bridging some of those tight integration efforts where the government invests in saying, "You know what, this can be something we're gonna have for five to ten years, and we need to wrap it in tighter."</p><p><strong>Maggie (42:02):</strong> Speaking of some of these government developed standards, I know one buzzword that I hear a lot is MOSA&#8212;Modular Open Systems Architecture. I'm curious&#8212;I've heard maybe mixed things, both positive and negative about it. I'm curious, is that real? Is that going into effect? Is that something you all are working with? Do you have any thoughts on it?</p><p><strong>Mike (42:20):</strong> MOSA and UMAA get tossed around a lot. What's UMAA? UMAA is&#8212;I'm gonna mess this up a little bit&#8212;Unmanned Maritime Architecture, something like that. But I would say MOSA is the closer of the two to being a good, realistic thing. I would say MOSA in intent is excellent. We try to be accurate with our stuff, so we say that we're a MOSA-designed system, because they want to know that it's modular, open systems architecture, and absolutely Seasats&#8212;we design everything around that. We've carried probably forty different mission payloads from unique different companies doing unique effects. It's probably higher than that now. I wouldn't be surprised if we're over fifty, but every one of those requires&#8212;if you haven't designed in a modular, open way, every one of those is a custom engineering project. I mean, I've had folks from Navy Information Warfare Center say, "Oh yeah, typical sensor integration could be a million dollars and take half a year to a year." We do it in a day or two, and sometimes we don't even charge because, you know what? We just want our library to grow. If it's a mission value-add sensor, we want to add it to our platform. We're just gonna do this as fast as possible. So MOSA is important. UMAA is important. I would say sometimes in the technical details, those things kind of miss the mark. They get a little overwritten, a little over-prescribed, but the intent is correct.</p><p><strong>Maggie (43:43):</strong> Another technical question that I had was, how are you all seeing LLMs and transformers play a role in maritime autonomy? Are you all actively experimenting with this, and where do you see the most promise for this technology?</p><p><strong>Mike (44:02):</strong> Yeah, we definitely do experiments because there are certain parts of the autonomy perception stack that we have done LLM-style, or these new large transformer models. And you know, the initial results are super promising. Because this is a long tail problem, they're not quite there where we've deployed them to vessels where it's like, "Okay, we're gonna have to invest some time to get that right." I'm super excited on the LLM side, in particular, because we spend so much time&#8212;we get a lot of compliments, we don't advertise a lot about our user interface, but we get a lot of compliments from customers saying, "Oh wow, this is super intuitive. This is one of the best things in the industry." I mean, I've heard this from competitors as well. They say, "Oh man, how'd you guys get that so clean?" I think the future of UX is gonna be LLM-based&#8212;you're just gonna talk to this tablet the same way you'd talk to a person. You'll be like, "Hey, it's getting dark. Should you change anything in your sensor behaviors?" And rather than trying to make this intuitive through traditional interfaces, it's just gonna prompt you with the correct settings, or it's like, "Hey, enter a stealthy observation mode. Hey, we're entering a contested area. Set yourself up properly." And I think that will be totally enabled by LLMs. And I'm super excited to see that workflow improve.</p><p><strong>Matt (45:17):</strong> I want to ask about price and cost. We talked earlier about the Ukrainian drone boats and sinking the Russian Black Sea Fleet. The cost asymmetry there is enormous, and those boats cost around two hundred thousand dollars or something like that. And then, you know, I was reading a Reuters article the other week that was talking about some of the challenges that the DOD has been facing with our own small USV industry. And it was saying that those platforms cost a million to two million dollars, and it very starkly drew the contrast between those costs and the cost of the Ukrainian platforms. Why is there that cost asymmetry between what Ukraine is spending versus what the DOD is spending? Why can't we pay one-tenth the cost that we're paying now and buy ten times the vessels? And then also, just curious, how do you think about the right way to price these platforms more broadly?</p><p><strong>Mike (46:14):</strong> Yeah. So, you know, I think that Ukraine is in a unique scenario, because they're in an active war&#8212;every dollar, every round, every life matters. So they need to make really conscious decisions. They don't have the luxury of time or space to potentially get something overpriced, to invest in something that doesn't have an effect. It's that "a bird in the hand versus two birds in the bush" thing&#8212;they're taking birds in hand all day. And so, you know, it's interesting&#8212;when they put out their open source, crowdfunded initiative for, I think, the Magura platform, which was the very effective USV for driving back the Russian fleet. According to open source, available information, they're releasing those at two hundred and fifty thousand dollars, I believe. And so it's like, okay, that's a pretty good analog. They wouldn't post that number if they thought that was wildly overpriced, because they're opening up to the world being like, "Hey, help us fund these things." It's not like they're soaking up huge profit margins there. They're trying to drive ahead in a war. So I think that's a good reference point to recognize that maritime is hard. You need a lot of these systems to work. You need waterproofing on almost everything, which drives down the volume and increases human touch time. So maritime is expensive. Ukraine is probably a bottom price&#8212;that's probably the simplest systems that you can make, even though, to their credit, they're the most sophisticated in the world in terms of effectiveness.</p><p>In terms of the US, you know, I think that article quotes a Saildrone platform at maybe two million dollars&#8212;I'm just quoting what they put out there. I think there's some challenges here where it's like, okay, the US DOD is very used to asking for very high-end capability, so it's gonna be more expensive, and they're preparing for very high-end conflict. So it's like, okay, you need really sophisticated systems. They're definitely gonna be more expensive than the cheapest possible systems on the market, which let's just call Ukraine or China. So it's some price between two hundred and fifty thousand dollars and we don't know what the upper end is&#8212;maybe it's two million dollars.</p><p>How we think about pricing is from a commercial value stance. It's like, okay, could we realistically just replace this boat with people and contractors and go do the mission? And if you're in the millions of dollars range, it gets hard to justify. You can do that really effectively with just commercial solutions. And frankly, yeah, I think that also becomes a crutch. If you think about the liability&#8212;I don't know who the CFO is at Saildrone, but if you tell the CFO at Seasats or Saildrone, "Hey, we're going to be driving around a two million dollar asset offshore, unattended. It's just gonna be floating out there for days," they're gonna be like, "Ooh, what's our financial risk liability position on this?" And suddenly it's like, "Well, how about we have a couple hundred dollars a day chase boat out there with a crew to attend it." And now, once you got this chase boat out there, then it's like, "Well, we can also have a backup comm system. We can do all these things." You end up in a totally false, fake, basically testing environment, because you always have someone there to baby the system and to bring it home. You don't need to get good at navigating remotely through channels and difficult things, because you basically have a human to kind of watch it. So I think that's a problem with these really expensive systems&#8212;they get expensive, and then they get babied during testing.</p><p>So we were really aggressive about keeping our price low. And right from the start, we were doing fully unsupported test missions, and we could only do that when we were bootstrapping and starting this off of extremely small amounts of angel funding. We couldn't put out a multi-hundred-thousand-dollar system because we didn't have hundreds of thousands of dollars. We had to be confident in our equipment at very low price points.</p><p><strong>Matt (49:55):</strong> Do you think that the fact that the US is looking for boats that have more autonomy capability on the software side is making their platforms more expensive? Or are there parts of the technology stack that are more sophisticated than what the Ukrainians are using that make it necessarily more expensive?</p><p><strong>Mike (50:15):</strong> More sophisticated? Probably yes. Whether that's more mission effective is the open question. It's like, okay, who can complete missions better? Which is what you need at the end of the day. If you just want a nicer car, then you can always go up. You can be like, "All right, I want a Porsche or a Ferrari or McLaren"&#8212;you can spend more money if you've got more money to spend, and if you want nicer things to buy. I don't think inherently the software needs to be that expensive. Yeah, it's not a very hard computer vision problem, so I don't think it needs to be as expensive as it is. I think the prices will come down, and that will put pressure on companies to find viable price points and viable dual-use solutions, or to go out of business or have down rounds. We'll see what happens.</p><p><strong>Matt (51:00):</strong> Last question on the lessons from Ukraine. You talked earlier about how you balance learning and not over-learning. Are there lessons from Ukraine in the maritime space that you think don't apply, specifically don't apply to a US future conflict, or how the DOD thinks about its posture and maritime autonomy?</p><p><strong>Mike (51:25):</strong> Yes, absolutely. I think that a lot of folks saw the Ukraine very successful defense and offense with their USVs and said, "Ooh, we need exactly that." I would say it's very worth remembering&#8212;Ukraine was a defensive nation fighting a war against a much larger aggressor, and in an all-out war scenario. I like to consider this back to wars in the Middle East, like Iraq and Afghanistan, with roadside IEDs or improvised explosive devices. The IED problem was a massive problem to US forces. But there were not a dozen IED startups that were like, "Hey, we should be building IEDs for the US." It's like, no&#8212;cheap defensive weapons are not what the US invests in. We typically are investing in precision strike missiles, aerial systems, et cetera, that also have really advanced safety systems, for morality purposes, like last-minute aborts and things, which drives up the cost.</p><p>So I'd say now the US is in the unfortunate situation of potentially facing near-peer conflict where it's like, okay, we can't have as exquisite systems&#8212;economics are a real factor. But at the same time, I don't think water-borne IEDs, super cheap, kinetic solutions are really the right place for the US to invest in. I think we need to look at those lessons and build new ones, or build more appropriate things to integrate into US doctrine.</p><p><strong>Matt (52:53):</strong> Transitioning now to some rapid-fire questions as we get close to closing out here, what's been the biggest surprise building Seasats?</p><p><strong>Mike (53:03):</strong> Maybe just the number of places and the number of needs and things we'd get involved in. I think Elad Gill's startup handbook, or whatever that book is, talks about not realizing just how big the world is. And that is totally true. There are so many people who reach out to us on literal cold inbound sales, and I'm like, "I did not know they would need autonomous boats."</p><p><strong>Maggie (53:25):</strong> What's the most surprising one of those, if you can share?</p><p><strong>Mike (53:28):</strong> Jellyfish detector. We didn't know if this was a joke or not, but it turns out that nuclear power plants are typically by water sources, and they have big water grates. And if you get a big plume of jellyfish that float along on currents, then they'll clog the grate, and suddenly you'll have everyone panicking about a nuclear meltdown because they can't cool the plant fast enough. And so these folks building power plants were very seriously contacting us in the early days, and doing presentations around using fleets of Seasats to provide early warning for underwater jellyfish swarms. And we were like, "Wait, really?" Yeah, we thought it was a joke at first. That's definitely the weirdest.</p><p><strong>Maggie (54:04):</strong> What's your hottest take about the current state of defense tech or maritime autonomy?</p><p><strong>Mike (54:11):</strong> Ooh, there's so many hot takes. Okay, here's one. I think that there should be way more testing. Everyone is excited&#8212;I think what has really happened, why are defense companies clustering and racing to Ukraine? Besides protecting democracy and helping a nation protect their sovereign borders and stuff, it's because they've become the de facto testing lab for the world in terms of defense systems. What's the big shame to me is that the US has so many regulations that we have failed to create effective test environments in the US. And I've talked to folks in the government about this, and folks who are trying to reshape things, and my conclusion is often like, "Gosh, we should probably raise some money and just purchase some private land, or purchase some areas and just run a commercial testing facility." Because it's crazy that we're so bad at this. I mean, I love looking at Zipline drones. They couldn't get FAA permission to do early UAV stuff in the States, and so they just went overseas to do testing, delivering important medical supplies, where they could do it.</p><p><strong>Maggie (55:15):</strong> How far out do you think we are from being able to take an autonomous cruise ship?</p><p><strong>Mike (55:20):</strong> Oh, I love this question. I can't say never, because that surely is wrong, but I'm gonna go fifty-plus years. Oh man, I know that might sound like I'm a pessimist. It's not for technology reasons. It's just like airplanes&#8212;commercial airliners have been able to automate the entire flight, the takeoff and the landing, for a long time. But we need pilots for liability, for responsibility&#8212;there's so many reasons that humans are so good and versatile. When you're talking about big cruise ships, it kind of just doesn't make sense. Someone's telling me they're gonna get rid of the final crew on these super tankers, and it's like, really? There's only fifteen people on there, and they're transporting&#8212;what?</p><p><strong>Maggie (56:03):</strong> What about a whale watching boat, like there's ten of us on here, sort of thing?</p><p><strong>Mike (56:08):</strong> Okay, okay. We have toyed about offering around Mission Bay beer cruises, where our autonomous boat just tows people around with tubes and coolers full of beer, because we've done that for ourselves, right? This was kind of a fun gimmick&#8212;we should have people get toured around for romantic cruises with no driver. That might be sooner. We could do that kind of whenever you want, if you want to Venmo us, we could probably do it once illegally.</p><p><strong>Matt (56:27):</strong> Specifically in the USV space, what's the most commonly misunderstood viewpoint about the industry?</p><p><strong>Mike (56:39):</strong> I think the one&#8212;this is just like, over and over, I beat this point&#8212;but I would say just that the demos are done on days when everyone wants to go to the water. It's sunny, it's nice. If it rains, it pours, there's bad weather, and then everyone doesn't do it, and it's like, "Oh, that doesn't make sense." And so often the tests are scripted. It's like, "Okay, and now the bad guy is gonna come and we're all gonna point the cameras, point the weapons, and report our duties." It's just totally fake. And so the combatant commands are actually really the point of the spear, in my opinion, on this, because they're out there doing missions in the world, oftentimes that are not scripted. It's like, okay, trying to stop smugglers, trying to stop conflicts and being in kind of more contested zones, even. I saw an article where someone was like, "Hey, we should be using this as a more aggressive testing environment, because we're trying to stop smugglers." And it's kind of separated from adversaries. That makes total sense to me. Anything that can make it more real is critical.</p><p><strong>Maggie (57:39):</strong> What advice do you have for other founders looking at starting a company in the national security space?</p><p><strong>Mike (57:44):</strong> Find amazing investors and teammates and advisors who get how long it's gonna take and how hard it is, because maritime defense is a problem where you can't just be good at one thing. You need to be kind of amazing at one thing, which is what gets you your differentiation&#8212;that classic startup ten-times improvement, to get people to try it. But then you really can't suck at anything else. It's like, if you're bad at contracting, if you're bad at legal, or if you're bad at some core competency in your technology stack, then it's just kind of doomed for failure. You'll never get all the way there because you basically need to be good enough at everything. And I think the only way to do that is to have a good team, and that counts all the way to the investor network, which, you know, Shield Capital is a phenomenal investor. Nice plug for any startups looking for capital.</p><p><strong>Maggie (58:37):</strong> Well, on that note, Mike, thank you so much for coming on the podcast. I definitely learned a lot about the world of maritime autonomy, and really appreciate your time.</p><p><strong>Mike (58:46):</strong> Totally. Thanks for having me on, Maggie and Matt. This is a lot of fun. Glad to be on here and glad to get to share a little bit about what's happening.</p><p class="button-wrapper" data-attrs="{&quot;url&quot;:&quot;https://maggiegray.us/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe now&quot;,&quot;action&quot;:null,&quot;class&quot;:null}" data-component-name="ButtonCreateButton"><a class="button primary" href="https://maggiegray.us/subscribe?"><span>Subscribe now</span></a></p><p class="button-wrapper" data-attrs="{&quot;url&quot;:&quot;https://maggiegray.us/p/ep-8-seasats-scaling-persistent-maritime?utm_source=substack&utm_medium=email&utm_content=share&action=share&quot;,&quot;text&quot;:&quot;Share&quot;,&quot;action&quot;:null,&quot;class&quot;:null}" data-component-name="ButtonCreateButton"><a class="button primary" href="https://maggiegray.us/p/ep-8-seasats-scaling-persistent-maritime?utm_source=substack&utm_medium=email&utm_content=share&action=share"><span>Share</span></a></p><p class="button-wrapper" data-attrs="{&quot;url&quot;:&quot;https://maggiegray.us/p/ep-8-seasats-scaling-persistent-maritime/comments&quot;,&quot;text&quot;:&quot;Leave a comment&quot;,&quot;action&quot;:null,&quot;class&quot;:null}" data-component-name="ButtonCreateButton"><a class="button primary" href="https://maggiegray.us/p/ep-8-seasats-scaling-persistent-maritime/comments"><span>Leave a comment</span></a></p><p></p>]]></content:encoded></item><item><title><![CDATA[🎙️ Ep 7 - Building the Software Defined Navy]]></title><description><![CDATA[Maritime computer vision, generative AI, resilient communications, and more&#8230;]]></description><link>https://maggiegray.us/p/ep-7-building-the-software-defined</link><guid isPermaLink="false">https://maggiegray.us/p/ep-7-building-the-software-defined</guid><dc:creator><![CDATA[Maggie Gray]]></dc:creator><pubDate>Tue, 12 Aug 2025 15:03:07 GMT</pubDate><enclosure url="https://api.substack.com/feed/podcast/170769712/326a511a14242cc9ad16d05f97a1e42a.mp3" length="0" type="audio/mpeg"/><content:encoded><![CDATA[<p>The Navy will play an integral role in any future conflict in the Indo-Pacific. China is rapidly building the world&#8217;s largest navy and is experimenting with all kinds of cutting-edge tech. But what is the state of the U.S. Navy&#8217;s tech stack?</p><p>This month on the Mission Matters podcast, we sat down with <a href="https://www.linkedin.com/in/justinfanelli/">Justin Fanelli</a>, the CTO of the U.S. Department of the Navy and PEO Digital, and <a href="https://www.linkedin.com/in/artemsherbinin/">Artem Sherbinin</a>, the CTO of the U.S. Surface Navy to discuss the future software-defined Navy. We cover everything from computer vision deployment in the maritime domain to why technology will matter in a conflict with China to what &#8220;software defined warfare&#8221; actually means.</p><p>You can listen to the podcast on <a href="https://open.spotify.com/episode/3Rh5Rf7AayLhQwDHnFQ1z4?si=MXJzJSTiRe2NWFdknrJZfw&amp;nd=1&amp;dlsi=8e3a861148b34381">Spotify</a>, <a href="https://podcasts.apple.com/us/podcast/building-the-software-defined-navy/id1807120572?i=1000721642821">Apple</a>, <a href="https://www.youtube.com/watch?v=p3cHZGEuge8">YouTube</a>, <a href="https://shieldcap.com/episodes/navy">the Shield Capital website</a>, or right here on Substack.<br><br>As always, please let us know your thoughts, and please reach out if you or anyone you know is building in the national security domain.</p><p class="button-wrapper" data-attrs="{&quot;url&quot;:&quot;https://maggiegray.us/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe now&quot;,&quot;action&quot;:null,&quot;class&quot;:null}" data-component-name="ButtonCreateButton"><a class="button primary" href="https://maggiegray.us/subscribe?"><span>Subscribe now</span></a></p><div><hr></div><p><strong>Maggie </strong>00:30</p><p>Welcome to the Mission Matters podcast, a podcast from Shield Capital where we explore the technical opportunities and challenges developing and deploying commercial technology to national security customers. In this episode, we're joined by Justin Fanelli, the CTO of the Navy and technical lead for PEO Digital, as well as Artem Sherbinin, the CTO of the Surface Navy. Justin and Artem are two of the key technical leaders bringing the Navy into the 21st Century. Now, Akhil, I figure this conversation probably hit home especially hard for you based on your first hand experience with the current state of technology in the Department of the Navy, from your time as a Marine back in the day.</p><p><strong>Akhil </strong>01:31</p><p>Yeah, thanks, Maggie. You know, preparing for this discussion did, in fact, remind me of my brief but very memorable time aboard naval shipping and really experiencing firsthand the technical challenges facing our maritime forces, whether that's planning and executing as a disaggregated force under limited communications and, oh, while having to use systems that have to survive the salt water the extreme of the maritime space. I think also what makes this conversation particularly timely is just everything happening in the world right now. Justin and Artem are at the forefront of making the Navy more lethal and capable in confined waters like the Persian Gulf and the Red Sea, as well as being able to do things like maintain presence and deter our adversaries in the vast expanses of the Pacific Ocean. And so this conversation is going to cover all of that, and I'm excited to get into the nitty gritty details of deploying computer vision for maritime to what technology looks like in potential conflicts with peer adversaries, as well as what software defined warfare actually means.</p><p>Yeah. Artem Justin, I think this will be a little bit of a unique podcast for us. We've spent the last couple episodes really diving deep technologically into some of it, but I think we'll have a chance to kind of hit that intersection. You guys both come from deeply technical worlds, but are also involved in managing technology adoption. Before we get to the latter, though, we'd love to ask you both a softball question, what's the one tech area, application sort of challenge that keeps you up at night, that you can't read enough about and that you're really trying to get your hands around.</p><p><strong>Justin </strong>03:04</p><p>For me right now, resilient comms is actually finally starting to get resilient comms. And so resilient comms used to mean like two and now we can be way more diversified in the different inputs, but I'd say that there are a lot of folks who are kind of nascent, or these communities didn't used to talk to each other. And so when I was at Davos this year, we said, oh, it was unthinkable for the space folks and the 5G folks to have conversations just maybe 18 months ago. And so how do all of these different communities of interest blend to solve harder problems together? It's a great time to be a versatilist, and I think there are more of them coming together, and that's going to result in to me, new protocols, new interfaces, and then ultimately new opportunities for deploying capability faster and solving effects problems in more creative ways.</p><p><strong>Artem </strong>04:10</p><p>If you ask two Navy people, what the hardest technical problem is, the answer always comes back to integration. Integrating with like large legacy capital assets is always hard, especially if they're made by like a prime contractor using whatever it is, resilient, comms, AI, software, hardware, anything, integration will always end up being like the hard problem to solve.</p><p><strong>Justin </strong>04:36</p><p>Now that said, this could be there are reasons to believe whispers that this could be the golden age of integration, because of what we're seeing with generative AI, because of model context protocol and a few other things that are coming out. And so if I don't know, 70 cents on the dollar goes to integration. And, and folks who are using specifically on the software development side, the vibe coding tools and things like windsurf or other products to go much faster, if we level that up in a significant way for interfaces and we can really go after the bottlenecks across the board. I would love to have someone who's listening to this podcast say, &#8220;Hey, we've done this for a defense application, and here is the time we've saved.&#8221; We've seen one offs, but benchmarking that and then making that the new baseline would be a real win.</p><p><strong>Maggie </strong>05:46</p><p>So Justin, you're telling me your vision for the future the Navy is just vibe coating our way into the future of conflict.</p><p><strong>Justin </strong>05:55</p><p>That is another interesting topic. I think what we said was, if we can 1/10 or 1/20 integration complexity based on applying solutions that we've seen other places, then perhaps the sky's the limit.</p><p><strong>Akhil </strong>06:15</p><p>That's great. Justin. In order to do that, we actually have to get some of these applications and protocols on network, on the environments that we need to but I concur with you. I mean the future in which we can collapse the data fusion, ETL, network to network collaboration is pretty awesome, but I know both of you work a lot of issues related to actually deploying software and adopting technology at scale to your point. Artem, you didn't really answer the question on integration, on tech area, but is the, is your focus still around the integration piece, or is there a specific tech area that has gotten you excited?</p><p><strong>Artem </strong>06:57</p><p>Yes, integration is always a focus specific tech area. You kind of hinted at it at the at the end, there is data integration. It's not particularly sexy, like ETL is a somewhat of a solved problem, right? Lots of options, ranging from Qlik to Etlworks to etc. But, you know, Foundry from Palantir, but it's a skipped step, right? The entire department is very hyped up on AI. The entire US government is very hyped up on AI. None of that matters if your data isn't right and if you have not solved the data integration problem. So I would say that's my kind of favorite problem to work on, because it combines sort of all three aspects of my job, technical, policy and, actual implementation. All three of those have a part to play there.</p><p><strong>Maggie </strong>07:45</p><p>I want to take a step back and really set the stage here. You know, why does all of this matter in the first place? You know, what is the state of geopolitics with our adversaries? What is the Navy's role in a potential conflict and like, like, why does it matter for us to rethink the way we design our force right now? And is there a sense of urgency?</p><p><strong>Artem </strong>08:10</p><p>Defense tech is really hot right now. I think that's why you guys started a podcast. And there's the reasons for defense tech being attractive to venture capital are different sometimes than I think the reasons that we need new technology, but those two are intersecting, right? If I look at the last, the last five years of venture investing, you had this big peak around 2020, in in SaaS, right, Software as a Service things. And then it just took, like a nosedive right around COVID. That money had to go somewhere, and it conveniently found its way in defense and around 2021, and 2020 to 2023, you see this just huge uptick in VCs investing nearly across that those three years, nearly $150 billion, so nearly $150 billion in private capital invested in defense.</p><p>At the same time as that's happening over in the public sector, you see this like big push of, hey, we really, you know, across political parties, across government agencies, whether you're in defense, commerce, the intelligence community, everyone's sort of coalescing around one singular strategic challenge, and that's the at the moment, peaceful rise of the People's Republic of China. And so I think that the reasons that defense tech is hot and the reason that the government said, Hey, China's a problem, were probably different. But now we're all on the same team. Now we've hit the intersection point. We're all driving towards the same problem.</p><p>So I think we should really understand that problem well, and I'll break it down like very simply, the leadership of the People's Republic of China, right the Chinese Communist Party, and specifically their president and general secretary of the party, Xi Jinping, has publicly stated that they have objectives to reshape the international world order that's currently led by the United States and our Western allies, and that they publicly have stated that they would like to reunify with Taiwan. Those are two very big strategic challenges of the United States, and so from a national security standpoint, it is our job to field the very best military that we can to deter those potential objectives of the Chinese Communist Party. Why so I think that's why that matters and why those two spaces have come together.</p><p>What does all that mean next for these spaces? It means that right now, we're in a really critical time period to do to bring in that technology and execute deterrence. There are a number of factors ranging from more conflict around the world, economic stagnation and deflation inside of China that's potentially driving leaders to make maybe even rash decisions, and a military on the United States side that is more expensive and by uh, by extension, smaller than it ever has been. At the height of the Cold War, we had 800 ships under Reagan in the 1980s today we have under 300 we said we want 350 we only build one and a half destroyers a year, and roughly the same submarines. The Chinese build three. So in this present moment, all of those factors have collided. And so not only is it critical that we get these technologies in, there's also just an immense amount of urgency to do.</p><p><strong>Maggie </strong>11:33</p><p>So what is the current state, as far as we know, in the open source domain of our adversaries&#8217; adoption of next generation maritime technologies that would be relevant to the Navy, whether that's autonomous systems or AI or others? And how does the US stack up?</p><p><strong>Artem </strong>11:52</p><p>So the our number one adversary, as we've talked about a lot, is the People's Republic of China, and they have a concept that is actually, you know, riffs off of the US system of winning the Cold War called Military Civil Fusion. Military Civil Fusion is the Chinese looking at how the US won the Cold War, which is through by, you know, world class companies in Silicon Valley bringing technologies like the microprocessor to life, and then the government adopting the microprocessor and sticking it into weapon systems like, you know, cruise missiles and dumb bombs, and making them smart cruise missiles and very smart bombs, right?</p><p>So the Chinese looked at this and said, hey, the United States is, like, really good at the diffusion of technology. We should do that too. And so they developed military subtle fusion, which is this idea that Chinese companies work directly for. You know that their work directly supports the technologies being developed for the People's Liberation Army, which is the Chinese military. And they're doing this across the board in in areas ranging from energetics to, you know, rocket propulsion, to AI to autonomy, and you know, some examples include, in the open source you can find Chinese specifications for a software defined warship. In fact, they launched a medium, unmanned surface vessel for experimental purposes that meet some of those specifications. So that's a real example of that partnership coming to bear. The good news is the United States is just far better at this, right? We have a long history of taking, you know, innovation and fielding it for military advantage, and I feel fairly confident that we'll be able to continue doing that.</p><p><strong>Maggie </strong>14:00</p><p>What do you feel like the US most misunderstands about our adversaries approach to military technology?</p><p><strong>Artem </strong>14:10</p><p>Man, that's a tough question. I don't think that there's something we don't understand. I think we're just in the middle. It's hard to be number one for a long period of time, right? The United States has not had a competitor peer adversary since the fall of the Soviet Union in 1991 and today we do and when I say peer, I mean, this is, this is the first time I could, you could really say peer competitor. When you look at the Soviet Union by scale of military they were a peer competitor, but in every other aspect of intrastate competition, they were not. They were a near peer. China is most definitely a peer the GDP of China in. Uh, is just a smidge below ours. The GDP per capita is actually, you know, far lower, but the actual overall GDP is is just below ours. So China is the world's second largest economy. They are the world's largest Navy. They are the world's second largest army, right By every metric they are, they are close to us. And we have no institutional memory of facing a competitor like this, since probably the time of the American Revolution, where, you know, Britannia ruled the waves and was the global superpower of the day. So since that time, the US has never faced a competitor that could match us and actually exceed us in areas like industrial output. That has just never been the case. And so it's not necessarily that we misunderstand something about our adversaries. It's that we're facing a completely new kind of adversary.</p><p><strong>Maggie </strong>15:54</p><p>So one of the big topics of conversation that I know you and I have discussed, and I think is a hot topic right now in the broader defense tech community is, what lessons should we be learning from the war in Ukraine as they apply to a potential future conflict in the Indo Pacific, and what lessons should we not be over learning?</p><p><strong>Artem </strong>16:17</p><p>So I'll start with the easy one is, what should we be learning, and it aligns well with what I said before: Software Defined platforms are critical and cycle times of change are faster, largely driven by the software defined platforms those changes occur on. We're seeing that across the board on legacy things like tanks which have to be modified, like the physical tank has to be modified because of the advent of first person view drones and top down, you know, top attack munitions, all the way to electronic warfare systems, again, more of a Software Defined Platform than an analog tank. But the chain, the rate of change is just so much faster. And I suspect that any fight in the Indo Pacific would encounter something very similar in this very rapid rate of change.</p><p>What lessons should we not be taking away? There's a statistic thrown around all the time that 70 to 80% of Russian casualties today and Russian Ukrainian casualties on the front line are the result of first person view drones. I won't comment on the factual basis for that statistic itself, but the idea that all fires are now based on drones is probably an overreaction and an end and a bridge too far. One of the reasons that Russia just yesterday, from the filming of this podcast, launched over 300 drones at Kiev, and just under 70, I think it was 64 cruise missiles, as reported in the in the economist this morning was that Russia can produce more Shahad drones than they are roughly at a rate of 300 every three days. Then they can produce cruise missiles. So drone warfare is not necessarily just a function of the fact that this is the new way of war. Drone warfare in Ukraine is a function of what those countries can produce. And I suspect a fight in the Indo Pacific would look different. Moreover, the fight in the Indo Pacific will be between large capital assets, primarily armies, are still going to clash on islands, whether that's on Taiwan or other parts of the Western Pacific, but at the end of the day, it will be ships and aircraft that have the lead, and that is just going to be a fundamentally different conflict.</p><p><strong>Akhil </strong>18:49</p><p>As we maybe switch a little bit to the actual adoption, the actual technology, and then managing technology adoption, I'm reminded by a story from the turn of the 21st Century, a young Lieutenant William Sims, which is a classic case study of the Navy basically rejecting new innovation. Right for the listeners out there who don't know the story, basically, this young lieutenant out in the Philippines, stationed in the western Pacific in 1900 learned about this new technique around continuous aim fire for basically gunnery. The Navy spent a year saying this is probably not going to work. Did their own flawed tests, and it basically took this young lieutenant writing a letter to then Theodore Roosevelt, who was one of the assistant secretaries, to get him to elevate this to a level that needed, needed to be elevated and ultimately adopted. I think there was some wild statistic of a 500% increase in gunnery accuracy in the Navy by this one sort of technique that was initially outcasted. And so I think there's an argument to be said that the Navy, in particular, over its history, the Navy has had a real challenge when it came to adoption of new technology or just new practices, whether that's because of some of the legacy institutional culture or something else.</p><p>I'd be curious one, the Navy has changed a lot since 1900 it is actually, in a lot of ways, at the forefront of what geopolitically is happening from an experimentation standpoint, and where the potential points of friction, points of conflict are, and so I'd be curious to get, maybe to start off, a high level take on, how would you would assess the way in which the Navy has tried to adopt new technology or new novel techniques? Where do you think we can still go if there's one or two areas to really spend our time, spend our focus, if you were going to spend only had one hour or one marginal dollar, where you'd spend that time to enhance and increase that way in which we adopt technology.</p><p><strong>Artem </strong>20:56</p><p>I'll start with the last question. First, if I had to pick one place that I would change how the Navy adopts technology. I would say that every platform should be software defined, right? We historically, you know, we've, we've heavily vertically integrated our platforms, whether that's a ship or an aircraft. It's usually made by some more, you know, Prime Vendor, that prime vendor, will deliver the hardware, and that hardware, in order to put software on top of it, will have some sort of proprietary interface. And occasionally they need to have data rights. Occasionally we won't, even if we have data rights, we'll have to pay for like the decoder ring to be able to like interface. Those two things together, and they're very tightly coupled. And unlike an iPhone, or, you know, modern consumer electronics, benefits significantly from vertical integration. We found that defense things don't so effectively. Building software defined platforms on open source, like protocols with like open source code is, I think, the future, and we already, we already seen this in Ukraine, where software defined platforms ranging from drones to electronic warfare systems are updated overnight with new code, which in turn leads to some sort of operational outcome that should be our gold standard. You know, every night a ship is in contact with an, you know, an adversary potentially in a high end fight, and that ship just gets better because we deploy new code to it. So that's, that's the one kind of vision of the future I have. Going back into the past, the Navy has struggled with technology adoption. I think the sim story is just one of dozens the and I would point to kind of three high level things of what, what makes working with the Navy potentially challenging from a technology integration standpoint. The first is that large capital asset bit that I mentioned earlier. 70% of the Navy's budget goes to, you know, ships, aircraft, carriers, submarines, airplanes, etc. That's different than the other services. Akil, you're a Marine. 65% of your services budget goes to humans, right? So we're used to buying things. We're not used to buying software. And the second is, the Navy has a unique culture of, you know, kind of bottom up innovation, but that means that, you know, top down is hard, and that dates back to the notion of independent command at sea, and the idea that, you know, ship captain goes over the horizon and loses communications with everybody and just has to make decisions on their own. That's created kind of a centralized command and control system and a very hierarchical approach to, like, how our service operates. That's hard. We're working on getting better. Thanks,</p><p><strong>Akhil </strong>23:42</p><p>Artem, I wanted to pick up quickly on your software defined portion one, I think spending more time in the space. I think folks sometimes get what software defined means to be actually wrong. So I want to really, really distill what to you is software defined in the military context. And maybe as part of that question, you talk a lot about open source and being able to iterate constantly. Are we always going to be at concentration tension with the DevSecOps process of how we ensure whatever that means on the security side, with our ability to continuously iterate and ship and commit code on a nightly basis at scale.</p><p><strong>Artem </strong>24:22</p><p>So software in the military context, Software Defined warfare refers to the idea that your hardware platforms are getting better on a on a rapid rate, so in hours and days vice months and years because of the deployment of software to those hardware platforms. So just like a Tesla or your refrigerator potentially gets a software update overnight, and that piece of hardware now has new functionality, we want to see that in the military domain and adaptation is, you know, the. Uh, the side that adapts the fastest in conflict wins. Historically, adaptations came in the form of doctrine, tactics, techniques, procedures, or potentially rolling out a new technology. You know, the tank replaces the horse today, adaptation means deploying code, and in turn, the deployment of code drives those other changes. It drives tactics, techniques and procedures. It drives doctrine, it drives training, which is kind of a it's a new paradigm, and it has really changed the character of war.</p><p><strong>Justin </strong>25:33</p><p>So building off of that just a little bit, Artem is invoking both Darwin and then Krepinevich, right? And so this goes from the species to the Origins of Victory all the way to getting very wonky like DOTMLPF, here's the point: Maneuver warfare became the primary mode of marine philosophy, essentially like execution 1989 that scaling out and applying to technology as we've watched the wave of software grow is something that needs to be more tightly approached. And so what we've seen there is that the this OODA loop that so many people talk about is very measurable in terms of how long it takes to adapt. And so when you mentioned Sims, looked at the 500% there's a lot of talk, there's a lot of activities, but ultimately, the time it takes to turn a ship, or the time it takes to change the way that we are defending or countering is a very measurable thing. And so we talked about software defined warfare. Obviously, that's the fastest moving piece. I'd say just extending that a little bit modular across the board is particularly important.</p><p>So depending on how we do interfaces, including hardware, the more of these components that are swappable, the better. So we have a new line of ship builders the ability to navigate for autonomy or with or without GPS, are open questions. The idea of doing this vertically is an open question. And so we've seen some success with, for instance, In Q Tel, taking Anello Photonics and saying, Hey, instead of your Alt-PNT solution, swap that out and then swap in this new piece of hardware like that. Ability to mix and match all the way through hardware is ultimately something that I think is going to be extremely important to adaptation.</p><p>And so we have a few adaptation cells. We have one that we work with within the seal community. We have a few back office technical teams, and those are days and weeks mix and match that's extremely important, especially if we're not getting live production contact, and so I would say that watching this and being able to make those trade offs in real time is something that is allowing this bottom up to be pulled all the way through something we already knew there are often really good solutions closer to the problem, right? You're more likely to solve a problem if you're in it than if you're in some building Far, far away. But how long does it take to make through and how many letters do you have to write to Congress or somebody else? Well, we want that to be more data driven.</p><p>There's an obvious difference between private sector and public sector. Public sector is not measured on return on investment. Historically, there's no good sense or way of doing that. And so when you say something is five times better, that's really impressive. But like, the denominator is not standard at all. And so we've standardized the denominator to say if you are changing outcomes in a significant way, it's less important where the solution comes from in terms of where in the stack, and more important that you're moving the needle for the war fighter and so like a tactical example of this is occasionally, we'll use KPIs that specify how something works in the requirements document. And so we'll say there needs to be this upload speed and this download speed, but also we're specifying that we need coax cable at this installation. And the reality is we just need connectivity. And so what we've recently done. One is allowed for proliferated Low Earth Orbit and to compete with traditional, wired and so all this across the board, hardware and software, where outcomes are the basis for acquisition and scaling decisions, everyone is better off.</p><p><strong>Maggie </strong>30:20</p><p>Could you give a story of a time when fielding a software defined system really made a difference in some environment?</p><p><strong>Artem </strong>30:31</p><p>I think the best real world example for today is Ukraine. We brought that up, but I'll use a relevant example from the US Surface Navy. Our ships since October of 2023 have been an active engaged in active combat operations in the Red Sea against the Houthis, which are an Iranian backed militia movement in Yemen. The that means that our ships, for the first time since World War Two, have been under, you know, inside of the weapons Engagement Zone of an adversary for a consistent period of time. And so we've at, you know, at the filming of this podcast, we have engaged roughly, you know, 300 plus air breathing threats. So that's, that's a lot of data points. And at the start of that conflict, it took us weeks to get data off our ships. We have since gotten that down to days. We want to get that down into hours. And the data from those ships has improved. You know, when it gets back to CONUS to the United States, it has improved everything on the spectrum, from the tactics that those ships are using to shoot down those threats, all the way to the actual radar systems on board the ships where we have analyzed the data, sent a software update back on a CD. You know, ideally it would go over the air, but baby steps, sent it back to the ship, and then and the ship's radar systems have improved. So that's just one example of a software defined, you know platform yielding a measurable, you know impact and in combat.</p><p><strong>Justin </strong>32:10</p><p>And so there are there EW cases. There are also just infrastructure and connectivity cases that kind of allow everything above those to improve. And so we weren't doing a ton of telemetry a few years ago. And so at this point, the way this works CONUS and OCONUS is we're watching those flows proactively. We can do a cyber example after this, but now, instead of using phone calls or emails as the trigger for where connectivity problems exist, we're extremely proactive, and we can Do hot swap redirects or load balancing proactively, and so in this particular case, this is a re envisioning on how we modernly manage the highway for which all of the cars and bits and flows operate. I would say that prior to a couple of years ago, that wasn't pro grade, and now it's first in class.</p><p><strong>Maggie </strong>33:30</p><p>As we talk about fielding more of these software defined systems. What does that mean for the current capabilities that we have? You know, does this mean we need to throw away all of our aircraft carriers and F 35 and field just armies and armies of USBs and UAVs. Or does it mean something different? And if it means something different, you know, how do we envision kind of the future of this software defined force?</p><p><strong>Artem </strong>33:56</p><p>I really love this question, because we hear this, the Navy gets this, I think, more than the other services, because we are so platform centric. We get told all the time that, hey, the character of war has shifted towards autonomous systems that are software defined. You can just throw out all the expensive manned things, the F 35 there was a prominent tweet that suggests that those could be replaced. You know, the $135 million F 35 could be replaced by the $10,000 hobbyist drone, and that just isn't the case.</p><p>What we have found in our war games is that generally, when we face off against a peer competitor, that is usually the People's Republic of China, our program of record force, meaning the things we have today, our aircraft carriers, ships, submarines, et cetera. You know, occasionally win, occasionally lose. We want to win every single time. And when we war game that same scenario and add these new capabilities, these software defined capabilities in a hybrid fashion. So the traditional manned platforms operating with an unmanned system. So think in F 35 operating with a collaborative combat aircraft, a large Navy destroyer operating with a medium unmanned surface vessel, which itself has a fleet, its own little flotilla of small unmanned service vessels. When we war game that hybrid force against the, you know, the People's Republic of China, we come out on top more often than not. And so that's the Surface Navy strategy: how do we feel the best hybrid force? And if you and we've had that consistent message for a few years now, because we recognize that you're not going to replace these orange capital assets, but you need kind of a high low mix, which is a Cold War term of a small number of high end exquisite platforms and a large number of low end tradable systems.</p><p><strong>Justin </strong>35:47</p><p>And so that barbell strategy, I think, applies a number of different places, right? Ultimately, it's as much an economic strategy as it is a technology strategy. But where that plays out, or where that bears, I mean, we can double click on kind of any domain. And so, let's say, from a logistics perspective, how many different government off-the-shelf applications do you need? Ultimately, the way that I'm viewing this, and we have a number of now memos and invitations to say, let's not just let commercial in, but let's do one-to-many replacements. And so we're piloting commercial capabilities, but they go so much better when someone says, &#8220;Here are the seven aspects of logistics IT that we can wipe out from a GOTS perspective with one COTS application.&#8221; If we don't have time for BASF to do, to harken back to the early 90s, that says we make everything a little bit better but we don't replace anything, that's not good enough. And so we are looking for divestments across the board, even if they're not apples to apples.</p><p>Another example of this is software-defined, but perhaps with a little twist. I recently was with the strategic submarine PEO, and they were working with Gecko Robotics. Within that Gecko Robotics example, I asked, &#8220;What are you replacing?&#8221; They're replacing manual action. They're replacing services. They're replacing, and with that, getting both productivity gains and safety gains. So this is a place where, between maintenance, cleaning, and manufacturing, we had one way of doing things, and we would like to open the door to say: we will give you our problem and you figure it out. Or we will give you how we're doing this right now, and instead of just incremental improvement, what is your horizon three solution for doing this differently?</p><p>The hardest part here is that it is not intuitive that there are incentives for people to change the way they work. We know there are mavericks, 10 to 15% of any organization, willing to work against their own self-interest for the greater good. We have an incredible mission, one of the best imaginable. We've catalyzed that into 15 to 20% of groups that are willing to do more work and adopt commercial solutions or think creatively about something. It's almost always more work at first, both for the company bringing it in and for the PM and support staff reimagining all these different pieces. Most people would prefer to do things the way they&#8217;ve always been done. But if there are more groups who want to be pilot leads and accelerate commercial adoption, then, as Steve Speer, professor at MIT, says, great organizations always look for the suck. There's suck in every organization, and you can always find the weakest links.</p><p>If we're doing this quantitatively, and we're saying either look at the numbers or talk to a sailor or Marine, where are the pain points? Then, how do I extrapolate that to a solvable technical problem and scale it across the board? We can have fewer systems that perform at a higher level, combining hardware and software. This is a time for reinvention, and we can do that quantitatively, even from the outside in. So whether it&#8217;s more private than public sector, we are pulling them through, or, like the earlier point, it&#8217;s someone at the ground floor who sees something, tries it, and then we scale it. In both cases, we now have the ability to stamp something as an enterprise service. Across the board, those can be apples to oranges, as long as they have calories, as long as they nourish. We're ready to make those trades.</p><p><strong>Maggie </strong>40:36</p><p>So I wanted to ask this is kind of on a on an earlier point that we were talking about in terms of integrating these new technologies with our existing program of record force. I want to see if one of you guys could maybe tell a story of a startup or company that did a particularly good job doing that, and, you know, maybe what were some of the steps that they had to get through, like, you know, step one, what's required to even integrate with a data source coming off of a ship or an aircraft carrier. What's kind of you know, hardware edge, compute constraints do we have or access do we have? You know, what kinds of AI models do you have? What kinds of data do you have? I know Artem. One of the things we've talked about is computer vision and some of the challenges of doing that at sea. So I wanted to see if maybe you guys could just give us, like a life story, life cycle, of what it looks like to actually integrate a system with the program of records force that we have today.</p><p><strong>Artem </strong>41:36</p><p>So I'll start with saying it's not a zero or one, like, you're not totally air gapped and you're not totally integrated, right? There is a spectrum in between. And I think the success stories we've seen in the last two years are sit in that middle area where we've delivered some kind of in the case of computer vision, some CV models to our ships and those models you know, live and operate in inference on commoditized commercial hardware, and that hardware, in most cases, is air gapped from the rest of the combat system. Is the best thing possible, like for us to connect those absolutely is, could we deliver the commoditized hardware and the model to the you know, to run at the edge in a month, as opposed to going through a three year long integration process? Yes, and so that's why we chose the like in between solution where an operator is kind of looking at a laptop, as opposed to looking at like their display in the combat information center as part of the Aegis combat system.</p><p>So in that particular example, that's a like in between integration story. But we've also seen examples where we've done the full integration work from start to finish, to bring some AI models to our combat system, and that involves working with the prime contractor that delivers that combat system. That means the working with a third party that does the integration work, because that prime contractors code is in, like Ada or in Fortran, which, like, for those that don't know that Fortran is the was the DoD is, like, proprietary code base the so that's why you need, like, all of those moving pieces, and that took a couple years. I'm being non specific on the industry partners, just due to the classification of the work involved. But the we've done both, we're doing more of the first and the first is what I urge most like startups to do right? Startups want to get a product out and make sure it's usable, or get an MVP out. You're not going to integrate with an F 35 or an armor cost destroyer in a month. So get some standalone hardware that maybe has like, one integration point with, like, if you're moving data, maybe you use the ship's routers and switches, but you're not tied into the combat system, or you're delivering a model, but you're running on your own hardware, as opposed to the ship's hardware. Yes, that's a limitation of working with the Navy, but I think it's one that we're working towards overcoming,</p><p><strong>Justin </strong>44:17</p><p>And then on another ship, example, but not weapon systems, CANES. Within CANES the Consolidated Afloat Network Enterprise Services, this is the largest chipboard network, and it's where between some NIPR and some SIPR. So some some unclass and some classified functions that we have a lot of different capabilities running on one backbone and one set of computing. And in this particular case, we have taken some of the capabilities that are virtualized, and tried to, in a lab, find more efficient ways to do them again, one for the price of multiple and swap those in. And so we've now unleashed some COTS vendors to look at a native capability within canes and replace that in a virtualized fashion, and just kind of hot swap those. And so that's something that we're getting a little bit better at.</p><p>We're also doing that with flank speed edge that more modern hardware. And so between those two, here are ways that we can take external software capabilities and pull them in and lower the time to integration on that that is, to me, repeatable. And then this, I'm going to call back to the initial point where we said, like, integration can go way differently. The when I started doing that type of work 18 years ago, when I was actually doing ship installs, we had a binder, and you had to follow all of these steps, and you're in the operating system and you're, you know, swapping from Solaris to like other like lower down components. How all of that goes forward is, is something that we've toyed with streamlining. I think that looks very different in the next year and to this point when we look at what can be replaced, the more that we sandbox that up, and the more that we can invite people through structured challenges to figure out what they can divest, instead of doing a one for one request to divest. Then this became, this becomes like downhill running.</p><p><strong>Maggie </strong>47:20</p><p>What do people outside of the Navy or the Department of Defense most commonly misunderstand about Navy or DoD tech adoption as a whole?</p><p><strong>Artem </strong>47:34</p><p>I think the I know we've talked so much on integration, and I hate belabor in this point, but I think people really misunderstand how hard it is to put something on a warship. You are not just like you're not bolting a computer to the side, right? I mean, even to upgrade. Justin, at some point, talked about the afloat OT and IT infrastructure on ships to replace that. That means cutting a hole in the side of the ship, taking out a bunch of server racks and then putting them back in. That's not like a week long process or a month long process. That's 180 day long process. And so technology integration with the DoD is hard. It's not just hard for the for for the technical reasons I just described. It's also hard because of our risk tolerance.</p><p>Remember that when you're delivering, you know, if you're a startup and you're delivering a capability to a war fighter, that means that there's a human being, you know, an American sailor, soldier, Airman or marine or guardian from Space Force, who is potentially in close contact with an adversary trying to kill them. And so our risk tolerance and our threshold for something working is just so much higher than deploying an app, and you know it being buggy and potentially not working, and you know you losing some stock points that day on the on the Dow because of that higher risk threshold, you know, we're really, we are going to test, you know, do Test and Evaluation in a way that maybe mimics industry in terms of process, but it has a longer timeline and has some extra steps, and you really have to think carefully about how that technology will be used, especially when it fails, and what failure looks like, because failure can be catastrophic.</p><p><strong>Maggie </strong>49:26</p><p>So you're telling me all DoD software completely bug free, running perfectly smoothly.</p><p><strong>Artem </strong>49:30</p><p>Yeah, it's excellent in every regard. No, in fact, what I'll say is the DoD sometimes mistakes process, like, the process through which we follow like, let's say you're getting an authority to operate an ATO, which means your application has been designated as, like, cyber safe by the DoD, because we like, read all of your source code, and then we've like, now, like a human being read all of your source code and then we deploy it to a secure. Environment that doesn't magically like, mitigate cyber risk. Similarly, writing a requirement by committee and having like 10 people on the committee like, say, thumbs up to the requirement in the Navy. We call them requirements, resources boards that doesn't like, magically de risk the technology. And so I would say we mistake our processes as being risk mitigators, and true risk mitigation is like a very sound technical implementation.</p><p><strong>Maggie </strong>50:30</p><p>Are there any special considerations that startups need to consider when building for the Navy, as opposed to some of the other DoD services?</p><p><strong>Artem </strong>50:40</p><p>The Navy is very again, because of our, you know, large capital assets occupying most of our budget. And large capital assets are not built by startups. They're built by traditional prime vendors. And the defense primes refer to companies like Lockheed, Martin, Raytheon, General Dynamics, Boeing, etc. When you build for the Navy, you really have to your technology is going to interface with the technologies made by those vendors. You're not just building to interface something with a common API that you can just find the API key online and you're like, good to go. You're building on top of, you know, decades of legacy hardware and software. So you're going to have to, you know, we talked about interfaces are hard. You're going to have to really work with those prime vendors and build partnerships at like a human level, with those engineers who, you know, painstakingly, over the course of decades, have built the world's strongest military, and today are also striving to bring in new technology.</p><p><strong>Maggie </strong>51:48</p><p>Artem, you know, one of the major themes that we have been discussing this conversation is, how do we get commercial technology that that we already sort of know works, or more or less works, into the Navy and the Department of Defense. Can you maybe share an example of a technology that we think of as mature, but that maybe has some unique considerations or challenges when applied to the maritime domain? Yeah,</p><p><strong>Artem </strong>52:17</p><p>A problem that's really near and dear to my heart because of my time working on, you know, supporting Maven is computer vision, and I think that this is a largely believed to be a solved problem in Silicon Valley, right? AlexNet, 2010 you know, since then you have, I mean, almost everything, whether it's your iPhone or your vehicle has, like, some sort of CV model, like running very effectively with, like, just great F1 scores. You're detecting everything, and we think of that as a solved problem.</p><p>Well, when you pivot that same technology to the maritime domain, it is absolutely not a solved problem. It is on the cutting edge of DoD AI problems, because, for one, you don't just have 1000s of ships going around with cameras producing model ready data that you just feed into an open source model, like YOLO v10 and say, like, oh, look, I now have computer vision at sea, right? So you have an absence of data. You're also not you're also dealing with, like, a really unique environment with significant background noise, atmospheric changes that you just don't encounter in the, you know, the regular just if you're a car driving down a street.</p><p>So really great example, computer vision in the maritime domain of a commercial technology that is a solved problem, but requires some additional steps when you're looking to work with the DoD. And this is why partnership is just so important, right? The DoD is the world's largest I'm not 100% certain on this, but I feel confident enough to make this statement. We own the most data of you know, ships floating in the ocean. I feel fairly confident in us saying that, and so you want to do a CV for horizontal motion imagery at sea. Come work with the DoD, right? There's a partnership. Figure out which prime vendors you need to partner with, because they're the ones deploying those electro optical or infrared sensors at sea today, and then figure out which government labs have dedicated, you know, decades of research to this problem that potentially, you know, it doesn't have a commercial application today, and so a normal startup just wouldn't go after it, but the government labs, which have those, like, long, 10, 20, year horizons, did choose to go after and have done a lot of like, great research to really help us feel these capabilities.</p><p><strong>Maggie </strong>54:44</p><p>So now this is a question I have to ask, because I'm sitting in San Francisco, and all anybody ever talks about is generative. AI, where are you seeing the most interesting and exciting use cases for generative AI, in the Navy today?</p><p><strong>Artem </strong>54:59</p><p>Man, there's. Much I can say about generative AI. All right, so the first is, the first is that the government is not immune to there are no special like special use cases that are exclusive to the government on generative AI, most of the things that are adding value in the commercial sector, I would say, like RAG as a as an example, right, basically, search your own documents, or, in some cases, right, search your own knowledge base. So instead of doing a SQL query, you're now having a, you know, a conversation with a model. Those are like the areas where the government is seeing the most use, which is a one for one, analogous to what we're seeing the commercial space.</p><p>How do I see generative AI more generally, in the competition between the US and China in the military space? I think is actually a more interesting question. The United States labs such as Open AI and Anthropic have really been focused on the model and really being on the cutting edge of model development in China, with the exception of the innovations we saw with deep seek r1 you're seeing a lot of emphasis on the actual commercialization of the technology, and that's a problem, because historically, if you look at how a technology, especially a generalizable technology, like electricity, and today, like AI, has won a great power competition, it was not the country that developed the technology first, or even the country that refined the technology first that won that great power competition, it was the country that was able to diffuse the technology and yield outsize economic benefits as a result. And I'm not so sure whether you're a shareholder of a Fortune 500 company, or you're the leader of a government agency, such as the Department of Defense, you're really seeing that, you know, significant return on investment today, or the diffusion of that technology today. Conversely, on the in China, you're seeing significant diffusion of AI into all sorts of technology verticals. And you know that that that doesn't bode well for long term Great Power Competition,</p><p><strong>Justin </strong>57:26</p><p>there are still folks who are clinging on to building things in government that probably shouldn't be anymore, and so we've explicitly stated that we're going with a fast follower first strategy as acquisition, as the 18 program executive offices within Department of Navy, five of them have shifted over to portfolios that we can make better buying decisions based on capabilities and effects. As that shifts, we want to both reward the people who are contributing from every aspect of that as well as the ones who are actually doing, making the difference. So doing what we have requested and what the Secretary of Defense has requested and what the President has requested. And so the PM of Lionfish, small and prime small USV and Dragonfish, large UUV. These are cases where PEO, USC and UWS are trying to pull in different things, and that may even compete with something that's happening in a lab or internal development. But those shifts right now are either going into overdrive or we're not moving fast enough.</p><p><strong>Maggie </strong>58:45</p><p>Yeah. Justin, thank you for naming a few folks that you're seeing who are who are really doing a good job right now when it comes to fielding the systems that we're going to need in this increasingly geopolitically complicated world I wanted to see you know, could you maybe tell us, what about those organizations has been so successful, and what can the rest of the Department of Defense or the Navy learn from some of these success stories?</p><p><strong>Justin </strong>59:19</p><p>Yeah, so number one, trying to do something new alone, the first time that we endeavor, it rarely works well unless we have a really strong partner. In all three of those cases, Captain Alex Campbell at DIU was involved. This is a person who gets it. This is a person who is bringing the weight of that organization, who has been interacting with industry in a mature way. It doesn&#8217;t take a whole program office to agree. What I have seen is that it just takes an O-4, O-5, O-6, or a courageous civilian to say, &#8220;Okay, we will figure out how these compare, and we will show that even if it is not a perfect fit, there is likely a requirement or capability needs statement that will allow us to do things differently.&#8221; Translating the technology into outcomes where it is affecting results in a more significant way allows us to provide top cover.</p><p>I will use a specific example. We had an O-6 who was a CSO on a carrier, and he said, &#8220;Send me what you are doing for the ashore systems. Send me a hyper-converged infrastructure stack to my carrier and we will deploy that.&#8221; There was a lot of paperwork, like Akil and I were talking about, because this is not how it is supposed to work. Sometimes people get bogged down with emphasizing every aspect of process as opposed to the outcome. This was a combination of heads down, nudging through&#8212;it is always more work than you expect&#8212;and then wavering and justifying. Part of the way we justified it was by showing the difference it was going to make. This was not just about being the loudest voice. These were two senior people saying, &#8220;Here is the baseline for connectivity on ships right now. Here is what that is doing from a quality of life and quality of service perspective. And here is the difference we can make.&#8221;</p><p>That leap still required influence, but we had the numbers. Captain Kevin White made it happen on one ship, and I believe it was the documentation from that case showing that it was a thousand times better for connectivity and user experience&#8212;one of our outcome-driven metrics&#8212;that led to deployments on five more carriers, and then to Flank Speed wireless. The capability we are talking about, known as &#8220;Sea to Sailor, edge afloat and ashore,&#8221; is now turning into a fully scaled capability at a high level, and it happened very quickly.</p><p><strong>Artem </strong>1:02:39</p><p>The best partnerships in government like to get tech in government are obviously partnering with commercial that's a given. That's partnership number one. And then inside of government, you need kind of three groups, right? And then the so the end user, meaning the war fighter, the sailor on a ship, the Marine in the field, the airman on a maintenance line. And then you need the acquisitions community to help you bring the, you know, the commercial thing, in. And then you need a resource sponsor. So that's somebody sitting in the Pentagon that's willing to do the mountain of paperwork that Justin described in order to make sure that this capability that is clearly measurably better than what we had before actually gets into the budget and stays funded for the long term, you have to have all four of those. And I think we've become really good at a, you know, the flywheel effect of building those teams, you know, be and those, those private, public partnerships,</p><p><strong>Akhil </strong>1:03:39</p><p>If you had a single slide to articulate one metric for your respective office. What would that metric be?</p><p><strong>Artem </strong>1:03:48</p><p>We&#8217;re in the government. We love slides. If I had to pick one thing&#8211;</p><p><strong>Akhil </strong>1:03:52</p><p>I know, I asked you for a single one slide, not 40 slides here.</p><p><strong>Artem </strong>1:03:57</p><p>Well, you know, we if I had to pick a metric, it would be how few slides we use to get something across the finish line. Bit of a joke there. But the I would say today, we measure things by what Justin hinted at, cost, schedule, performance and cost is how expensive a thing is. Did we go above or below budget? Schedule is, was it delivered on time or usually, the answer is no. And performance is, did you meet a requirement? And what that means is, did you meet the mark, according to a piece of paper that was likely developed five to 10 years ago, that isn't how we want to judge success. We want to judge success by operational outcomes. And so if it's a piece of software, if it's a user facing piece of software operator input would be like number one, meaning, like, here's how I used to do my job. Here's how I do my new my job now, because right, like, you're delivering a software application, the process is the product you're changing how that that operator is doing something and. Then number two, closely behind it would be like the real world operational impact if I'm delivering a new, let's say, command and control user interface for unmanned systems. Was I able to a group of sailors? Were the sailors able to control 10 robots before this, and now 20 robots, and now the robots can swarm, because it used to take 10 clicks, now it takes two. Those are the kinds of metrics that I'd like to display on that slide, user facing and operational outcomes.</p><p><strong>Maggie </strong>1:05:33</p><p>Can you tell us about a startup, or maybe a VC backed startup that has been particularly successful building and deploying technology for the Navy, and what can other startups learn from what they did in order to achieve success?</p><p><strong>Justin </strong>1:05:49</p><p>When you say building and deploying technology for the Navy, let's talk about cases where, like they're building and deploying capability and the Navy is making use of that. So maybe Project Ammo for MLOps, where we had a decent amount of in house software, and then, kind of like a coagulation of COTS, we had companies like Domino Data Labs and Latent AI that were doing commercial work that said, we do this for pharmaceutical and healthcare. We can do ML, we can do machine learning operations for defense functions better than you can build something up yourself. And so there was a Hey, meet this team, work on this problem, take a look at our algorithms. And so that relationship grew. They showed the difference that they were making. They brought that business mindset where they could show, here is the difference that we're making.</p><p>And then they did something else, that is an unlock, which is they found other people's money to apply to the problem, and so they applied to the APFIT program, and got a plus up there that was significant, that helped, certainly the Navy, hopefully also the Marine Corps. And as that group showed the difference they were making, understood who the players were, applied their knowledge and experience from other sectors, and then found funding for that valley of death until we can get them into the larger scale, like sustainment budget, like those are the big factors for how they can make that difference, and now they've also bought enough time to show here how outsized effects can come out of their next batch of work.</p><p><strong>Artem </strong>1:07:53</p><p>I'll use two really quick examples. One is a hardware example. The Navy brought in Saronic to build the prime. Which prime is a DIU Defense Innovation Unit contract for small unmanned service vessels, sUSVs, a year ago, we did not have, you know, 1000s of attractable sUSVs vs a year from now, we will when we actually ran the prime solicitation, Saronic had not built the Corsair, which is the boat that the Navy is buying in mass so, in fact, that company actually did not exist three years ago. And the idea of using a small, fast moving boat to blow up large capital warships didn't exist, you know, at in the same way that it does today. And so Saronic is a great example of a hardware company that's that the Navy has brought in, adopted the technology and is now developing the tactics and standing up, we've actually set up two unmanned surface vessel squadrons, so two new units that didn't exist. You know, even one of them didn't exist a month ago. So that's the rate of change here.</p><p>And then the second, a software example that's like, really a success story. Justin mentioned MLOps, I'm an alum of something called Project Maven and DoD, which was the application of computer vision to overhead intelligence gathering satellites, overhead imagery satellites. The success of Project Maven is that the government set up a data environment and gave a bunch of industry partners, ranging from large companies like Microsoft down to small startups like modern intelligence access the same data and said, compete and build us the best models. And so that's a success story for two reasons. One, we brought in a bunch of new entrants into the defense industrial base, companies that previously wouldn't have been able to work with the department defense were because of the technical implementation of this program. And the second is, we're bringing market forces into government, right? So instead of competing, usually, the government can have. One program of record to build a missile. Well, wouldn't it be great if there was one program of record, but like five missile vendors below them, all building and competing with each other, and that's the that's the environment we set up for Maven for the delivery of computer vision models into DoD, and that is now the joint program of record for automatic target recognition in the Department as a result.</p><p><strong>Akhil </strong>1:10:22</p><p>Justin, Artem, as we're kind of coming up on time here, I wanted to come back to maybe your thoughts and perspectives to give to the startup and sort of industry community. Artem, I thought you made some great points about aligning the right incentives between venture capital that's spending more time in the space the government that has a real need based upon geopolitics and industry who wants to get involved, either because of the mission or something else. Sometimes those alignments can be a little bit unaligned. And so curious to ask you a little bit maybe just generally, I'm a new startup in this space. You know, what are? What are some pieces of advice for startup founders in particular that might be thinking about getting into the government space or working on a really tough and important national security problem set?</p><p><strong>Artem </strong>1:11:10</p><p>I think it might surprise folks, but the best piece of advice you can give any startup founder, I think, is always know the problem you're solving, and really like, know the people whose problem you're solving, that isn't always super obvious in government, when you look at the government and you look at the DoD, the DoD is the single largest employer in the world, right? So where do you even begin? Like, who is your end user? Which problem? Let's say you're really passionate about solving an electronic warfare problem, you could go talk to a requirements officer in the Pentagon, somebody at the Washington Navy Yard that works in a program office that buys things, or like a Navy SEAL at a unit somewhere deployed forward, deployed in the western Pacific. All three of those could potentially be some semblance of an end user. So it can be challenging to figure out who you really need to talk to. I'd say my number one piece of advice is find, start with that person closest the edge, right, the operator in a camouflage uniform, you know, ideally on, you know, active duty orders somewhere forward deployed, is the is the end user. No matter what, you know, a program office will tell you that they're not responsible for buying things like the person at the edge isn't responsible for buying things. That's okay. You should still be talking to them, because that's whose problem you're solving.</p><p>And the second piece of advice is that it's going to be a long, long game, right? Defense is a slow defense is slow moving capital, right? We operate on, on what are called FYDPS, right? So we operate on these, like long capital cycle times. So recognize that you know, if you're solving a defense problem, not only are you choosing to solve one of the hardest problems out there, both from a technical standpoint and from a delivery of a capability standpoint, and also some of the most important problems, I might add, you're also dealing with slow money, so persistence is going to be key. And I would say those are my two big, big pieces of advice.</p><p><strong>Justin </strong>1:13:25</p><p>On that last piece, it's you have to be impatiently patient or patiently impatient. This to say, like even if it's slow, there is work to do every day, and I would put a bulk of my effort talking with people who get it. And so whether they're we're using unleashed Mavericks, or if they are thinking about problems, traditionally, you're unlikely to change their mind if you want to spend time talking to people who have done things the other way. That is good community service. But if you find people who are fellow travelers, who are wanting to be commercial adopters, who are disruptive, you will notice that, and that's where I would dedicate my time. It's a kind of like table stakes, to have something that is too good to be ignored. It is table stakes to, in my opinion, have something that you can turn off when you find what you're solving and you're close to that problem, and you have people with the light bulb over their head, and they get it with you, then work with them to denote what is severable and what you can carve out in fiscal year 26 fiscal year 27 fiscal year 28 until we get that refined budget, and so we should be turning off or replacing capability and solving problems at the same time. So you have to do the gain creation and the pain reduction at the same time in order to walk the walk. Otherwise, you have to tell your investors, hey, will they really like it, will see something in three years. If this is a contact sport, if you are not severing something in the meantime, then you're probably at the wrong part of the snack.</p><p><strong>Maggie </strong>1:15:31</p><p>If you were granted three wishes from a genie, and you could only use them to advance the state of DoD tech adoption, what would you wish for?</p><p><strong>Artem </strong>1:15:39</p><p>Do we both get three, or do we get three total?</p><p><strong>Maggie </strong>1:15:43</p><p>Okay, you guys can both get three.</p><p><strong>Justin </strong>1:15:46</p><p>All right, that's a nice Genie.</p><p><strong>Artem </strong>1:15:48</p><p>That is a nice Genie. I like, yeah, it's like, there's a queue for the genie, and each person gets three wishes. This is great.</p><p><strong>Justin </strong>1:15:54</p><p>Down. I think we should both get three and then decide a consensus, three.</p><p><strong>Artem </strong>1:16:00</p><p>I like that. My number one is that the entire that every program manager in the government is tied to the hip to an operator that is ideally, like, under the age of 30, just like brand new thing has not seen how we've always done it, and is just eager to, like, try new things, and so that each program manager, one is tied to the hip to an operator. So they're solving that operators.</p><p>Problem number two is that that program manager is doing it with commercial tech. Instead of looking at something in a government lab or looking to do like a five year or 10 year acquisition, they're looking to, like, bring in a thing that's ready to go off the shelf today.</p><p>And the third is that the government has more flexibility. And specifically, when I say the government, I mean the executive branch, has more flexibility to move money around inside of the execution year. And what that means is, Justin talked about, like fiscal year 28, 29 that's like, where our heads are right now, like when we're in the Pentagon, we're thinking about those, you know, what we're going to buy five years from now? That's kind of a ridiculous model. We should be thinking about what we want to buy right now, because we don't know what the tech is going to be five years from now. So I hope that genie lets me move different, you know, money around today to divest from Legacy things and recapitalize that money immediately to a new thing using that program manager that's that knows commercial tech and is tied to the hip to an operator.</p><p><strong>Justin </strong>1:17:30</p><p>I think those are really good. If there's anyone who's listening to the show who either has done Maverick things that we haven't documented or wants to please reach out to us on LinkedIn, if you're outside or Teams, if you're on the inside. We We want to expand the Unleashed base so that we can show just a compounding return on investment from hearts and minds to effects across the board. Now is the time.</p><p><strong>Maggie </strong>1:18:04</p><p>Thank you guys so much for coming on the show and sharing some of these great success stories.</p><p><strong>Akhil </strong>1:18:09</p><p>Hey everyone. Thanks for listening to the Mission Matters podcast from Shield Capital. Tune in again next month for another conversation with founders building for a mission that matters. And if you yourself are looking to build in the national security space, please reach out to us.</p>]]></content:encoded></item><item><title><![CDATA[🎙️ Ep 5 - Geopolitical Briefing: The Israel–Iran Conflict with VADM Kevin “Kid” Donegan (Ret.)]]></title><description><![CDATA[This episode of the Mission Matters podcast features a conversation between Shield Capital Managing Partner Philip Bilden and Vice Admiral Kevin &#8220;Kid&#8221; Donegan.]]></description><link>https://maggiegray.us/p/ep-5-geopolitical-briefing-the-israeliran</link><guid isPermaLink="false">https://maggiegray.us/p/ep-5-geopolitical-briefing-the-israeliran</guid><dc:creator><![CDATA[Maggie Gray]]></dc:creator><pubDate>Thu, 10 Jul 2025 15:02:09 GMT</pubDate><enclosure url="https://api.substack.com/feed/podcast/167908499/c9089c8d4eb56c76c2cea94052bf8e19.mp3" length="0" type="audio/mpeg"/><content:encoded><![CDATA[<p>This episode of the Mission Matters podcast features a conversation between Shield Capital Managing Partner Philip Bilden and Vice Admiral Kevin &#8220;Kid&#8221; Donegan. This episode covers everything from: </p><ul><li><p>The role of cutting edge technology like cybersecurity, drones, and AI in the conflict</p></li><li><p>The current state of Iranian proxy forces in the Middle East</p></li><li><p>How the conflict in the Middle East compares to Ukraine</p></li><li><p>And more!</p></li></ul><p>You can listen to the podcast on <a href="https://open.spotify.com/episode/3PiXoHuqZrKLcSmOqJqH3L?si=kOdudoDNSOuLq3AgmbPFMg">Spotify</a>, <a href="https://podcasts.apple.com/us/podcast/geopolitical-briefing-the-israel-iran-conflict-with/id1807120572?i=1000716523469">Apple</a>, the <a href="https://shieldcap.com/episodes/donegan">Shield Capital website</a>, or right here on Substack.</p><p>As always, please let us know your thoughts, and please let us know if you or anyone you know is building at the intersection of national security and commercial technology. Tune in next month for our next episode!</p><p class="button-wrapper" data-attrs="{&quot;url&quot;:&quot;https://maggiegray.us/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe now&quot;,&quot;action&quot;:null,&quot;class&quot;:null}" data-component-name="ButtonCreateButton"><a class="button primary" href="https://maggiegray.us/subscribe?"><span>Subscribe now</span></a></p><div><hr></div><p><strong>Maggie </strong>00:00</p><p>This episode features a conversation between Shield Capital Managing Partner Philip Bilden and Vice Admiral Kevin &#8220;Kid&#8221; Donegan. It's a little bit different from some of our past episodes. This one definitely sparked the Model United Nations kid within me with my love of geopolitics back in middle school and high school. This episode does not feature a conversation with one of our portfolio company founders, rather Admiral Donegan, breaks down the current state of the conflict between Israel and Iran. And you know, of course, we have to talk a little bit about the role that technology played in that conflict. We discussed cybersecurity, drones, AI, etc. We cover everything from the current state of Iranian proxy forces in the region to how this conflict differs from the war in Ukraine, I learned quite a lot from this conversation. So really, really appreciate you setting it up, Philip.</p><p><strong>Philip </strong>01:30</p><p>Oh, it's a pleasure, Maggie. Congratulations to you on these wonderful podcasts. I'm a big one of your biggest fans. So this is a different format. This was a moderated discussion that I had the privilege of hosting Admiral Kid Donegan, call sign &#8220;Kid,&#8221; it's funny, in the Navy, Top Gun pilots and other aviators all have these wonderful call signs. So we didn't discuss how he got his call sign. That's always somewhat personal issue, but we'll leave that for another another discussion. Maybe you can get it out of him in your in another one of your podcasts. I've known, I've known the admiral for well over a decade. He and I had the pleasure of working together on what was called the Chief of Naval Operations executive panel in his last two years of a four decade distinguished career as one of the senior most Navy and military leaders. And we talked about the Mideast then, and it has only become more more relevant in recent years. And in fact, the the two weeks that surrounded the beginnings and then the cease fire of the Israel and Iran war, the so called 12 day war. Admiral Donegan and I were discussing what was happening as it was happening. And in fact, on the weekend that the United States took action to intervene and to take out the nuclear sites. The admiral was actually in the Middle East. He was in Bahrain where he was there talking to very influential national security leaders, and I was concerned for his safety, and so thankfully, he made it out of that airspace and back to the US with, I think, about 48 hours before we had the webinar. So I think you're the you know, the podcast in this format is going to be highly informative for anyone who wants to understand what were the preconditions of this war action, what were the what was the assessment of the execution of the war plan, both by the Israeli military and intelligence community as well as by the United States, with our friend, General Dan Caine, a former SHIELD venture partner, now serving as the senior most military advisor to the President on all matters military, but in particular on this extraordinary operation called Operation midnight hammer. So it's a fascinating one hour discussion, and I think your listeners are going to really enjoy it and learn something.</p><p>Thank you for joining us, and it's such a privilege and a pleasure to be with my friend and mentor of many years, Admiral Donegan, who I had the true honor of serving with on the Chief of Naval Operations executive panel at the very end of his distinguished four decade career in the Navy. The admiral has served in the Middle East and meaningful leadership positions. We're going to hear more about that today, and I think that will help. I. The context to understand some of Admiral Donegan, unique and timely perspective. So kids, so good to see you. Thanks for doing this, and I greatly appreciate it. I will just want to remind the the attendees that, in addition to your distinguished service. You were actually just in the Middle East prior to the cease fire during combat hostilities, and a two Sundays ago, you and I were on text message on signal, the encrypted app, and I was inquiring as to your safety, given that the Iranians decided to take counter measures, counter offensive measures, with 14 intercontinental ballistic missiles raining down very close to you, on us, installations in Qatar. So maybe that's a great place to start. Can you just describe, you know, recent activities, you know, from your being in the region, your where you're, where you were formerly in command positions, and maybe let us know what you were doing, to the extent that you can?</p><p><strong>VADM Donegan </strong>06:14</p><p>Thanks, Philip, it's always great to be doing, being involved with anything to do with SHIELD. You're right. Philip, I happened to be in Bahrain on a trip unrelated to necessarily the ongoing conflict. Was fortunate enough that flights flew and I was able to get there. And then, of course, my main job there was to meet with the senior leadership of that country on other matters. But of course, with given all that was going on, we spent a fair amount of time discussing the current, current conflict. Interesting enough, Philip, that was, you know, the very first time that I think I was deployed to the Middle East, was 1983 and it was because the Iranians were refusing to let international inspectors in to look at their nuclear sites. So it's pretty incredible that this Iranian situation that's on the front pages now has its roots in decades of history in the region. So bottom line, I was there on other business, but was fortunate enough to get a chance to engage with leaders. I go to the Middle East on a regular basis, predominantly the United Arab Emirates and Saudi Arabia. In this case, it happened to feed Bahrain. So that's why I was there. And my wife wanted to know what I was doing there, of course, when all these things broke out, but she thought that stuff was over.</p><p><strong>Philip </strong>07:38</p><p>Well, you certainly have a very timely perspective. In addition to all that you did in uniform, maybe you can just talk a little bit about your command responsibilities during combat operations in the Middle East, specifically with Iraq and Afghanistan, and what it means to be an operations officer within Central Command, the combatant command responsible for the Middle East area of responsibility, as well as commander of the Fifth Fleet, you know, part of the numbered naval maritime fleets in the US Navy. What does that involve? And you know, really, What? What? What has changed over that time to where we are in the last you know, 12 day war, as it's been called.</p><p><strong>VADM Donegan </strong>08:26</p><p>Yeah, that's super you know, the perspective that I'll give you is one from studying and being in the region a long time. As I mentioned, the first time I deployed, I was a young junior officer to the Middle East, but I also commanded a strike fighter squadron there during operations Desert Storm, and what came after, I commanded an aircraft carrier that was deployed during the peak of the Iraq and Afghanistan war. And as you mentioned, I worked as the CENTCOM Director of Operations. And I guess to put that in simplest terms, I worked for both General Petraeus and General Mattis as their Chief Operating Officer at the peak of the wars in Iraq, when we had 100,000 troops in Iraq and 60,000 troops in Afghanistan. And then we shifted that to go to zero troops in Iraq to 93,000 troops in Afghanistan, all while we were fighting al Qaeda in both Pakistan and Yemen. So that's the stage that I looked at. And one of my predominant jobs, then, when I was director of operations in Central Command, was the Iranian problem set. And as matter of fact, on my it was back in 2010 when I first started there, that this weapon systems and capability that you saw put into play, this, this penetrator weapon was developed, and we actually ran exercises to test it, and then we ran exercises to simulate the entire operation, including launching B twos and flying them halfway around the world to practice this mission. As you can imagine, that's gone on now for some time, and then later, when I got to. Bahrain. I lived there for three years during the time when you saw the rise of the Houthis, one of Iranians proxies come up, and it was my ships that got attacked, and we retaliated against the Houthis with TLAM strikes against the Houthis. And that was back in 2015 so the perspective that we'll talk about today is based on all of that experience. So to speak, Philip, I don't usually talk about that in that kind of detail, but to help, since there's many in the audience that don't know my background, that's that's we'll be talking about. That's the basis that I'm looking at, or the lens that I'm looking at things through today.</p><p><strong>Philip </strong>10:38</p><p>Yeah, completely understand and appreciate that, and thank you for kind of defining terms and the like for the non military in our audience. So Admiral, yeah, here we are at the end of a 12 day war. We're less than a week into a cease fire, and yet there's been extraordinary military and intelligence and technological activities since the October seven Israeli conflict with with Hamas. But as you just referenced, going back to when you were in uniform, the activities in preparation for the US intervention involving the b2 and the bunker buster have been going on for over a decade. So this is an extraordinary set of events, measured in years, but also in days and weeks. Where are we now? You know, as you assess all of this with respect to the viability of a cease fire, holding the nuclear non proliferation assessment of you know what damage you know has been done to Iran's nuclear facilities, and really just reflections on the past couple of weeks it's been changing by the by the day.</p><p><strong>VADM Donegan </strong>12:09</p><p>Well, well, super Philip, what I'll do is I'll take that question in three ways, one in a broad perspective about what's the Middle East look like now, and why is it so different than it was before October 7. I'll dive in a little bit and talk about, if you like, the my assessment of the nuclear capability now, after what's happened that Iran possesses, and then I think it's logical then to kind of move to the ceasefire and if that's going to hold, and what that, what that looks like in the broader perspective. But first, just to set the context, you know, the framework of the Middle East for years, Iran was a country that really didn't spend its fortune on building the best military. Instead, they built really good defensive capability and a really good ballistic missile capability and drone capability. In other words, they built the missile side, not the rest of the conventional arms, and then separately, they built something called proxies. And these are elements that work in one way or another, by and large, to the same purposes for Iran that were spread around the region. And they use those to do their bidding, and then claim when they use those forces, it wasn't them that was using them. So those forces that were their key proxies were Hezbollah, Hamas, the Houthis and militia that they have in both Iraq and Syria, just to name a few. And then they have sleeper cells in other places, including the United States. And those would be the arms that if Israel or the United States would do something, those would be the arms that would reach out and touch back on Israel. Hezbollah would launch 1000s of missiles they had, potentially into Israel, or bases would be attacked that the US owned, if they used facilities. We saw that when they went and attacked a base that we had in Jordan. We've seen them do it in Iraq. So that was the stage that Iran had. That was the power that they had. Well, what's happened since October 7 is the Israelis, by and large, with us, support, certainly, with our equipment and our kit, were able to destroy Hamas. They were able to decimate Hezbollah in a matter of days, including killing all their key leadership, so much so that Hezbollah hasn't done one thing in this into retaliate against Israel since Israel and Iran had been at this attack, the US went in and did a pretty good job weakening the Houthis. And then another thing happened, Iran's closest, really, and only ally in the Middle East, Syria Assad, got driven out of power in a matter of days and had to seek refuge in in Russia. And so now a country that would have been aligned with Iran on this time is sitting not just on the sidelines, but vocally against the regime in Iran. So if you look at that and now combine it to what the Israelis did. Right during this 12 Days of War, they did a couple things. They went in and, of course, took down all their defensive systems. They did that back earlier when there was a previous strike. But then they went in and finished that job off. So they quickly got complete air superiority over the corridors they wanted to operate in Iran and then the Israelis took out key leaders. This is significant key leaders across the Iranian military force, but especially what's called the IRGC or Quds Force, that's the arm of the military that runs all those proxies and owns all those missiles. In other words, they went out there and decimated these and killed these leaders, where they slept in their residence, where they worked, when they were commuting, and they took them out. And if you can imagine how destabilizing that would be, at the same time, they attacked all the missiles and systems and what would be the backbone of support, the places those things are built and manufactured, where more can be replenished. They destroyed those missiles and systems in their own country, while they went after the nuclear sites, with the exception of Fordow, which was deeply buried. And then we saw the United States go in and use that system that you described against it. So what you have now is an Iranian regime that is attacked in the following way. Their military was weakened, their IRGC Quds Force especially weakened. And now that's weakened the Iranian regime, but it's still there. The regime is intact. And so that's the stage that everything's set in now is a tremendously weakened Iran, but you also heard the Supreme Leader step up and say, we won, and that's because his bar for victory is regime survival. Basically, he stood up to the blows that the Israelis could do, the blows the American could do, and is still in control of his country, and all the rest of the stuff, though we build that over time, is the lens that they look at it through, and that's kind of the stage we're in. And that brings us to the nuclear site assessment. But let me stop there before we talk about that, and see if you have any questions on that frame setting.</p><p><strong>Philip </strong>17:17</p><p>Sure we'll come back to regime status, whether Khomeini will be able to retain his power. You have some insights into some of the diplomatic initiatives with the US administration and the Israeli leadership, so we'll come back to that. But I would like you to touch upon before we go to nuclear, what you saw in the use of technology, techniques, procedures that just led to this extraordinary set of events where the United States, well Israel and the United States, jointly controlled the airspace and had decimated much of the senior leadership of the Iranian Quds guards, and really put a sense of panic in the Houthis in terms of, were they next on an exploding pager?</p><p><strong>VADM Donegan </strong>18:10</p><p>Super, yes. So, you know, this gets to the heart of SHIELD, really, Philip, when you talk about it, you know, with SHIELD&#8217;s, focus being on, on, on autonomy, and being on space, and being on AI, being the enabler for all of those and how they can, how they're coming together for the future. What you saw the Israelis do was facilitated by all of those things. Think of the ability and the deep penetration that the Israelis must have had into the Iranian network to be able to know where all their leaders were at that given time that they needed to know. In other words, and it wasn't just one, it was all of the leaders. Another example, as you mentioned, was their ability to get into the supply chain of Hezbollah, probably equally into the Iranian supply chain, we just haven't heard that. And how do they access that? They assess that access that through some human intelligence, but predominantly electronic intelligence that comes from space. It comes from systems that can understand signals intelligence, but also can understand how networks are put together. So think about cyber right? So clearly, the Israelis had to have access where they penetrated all those networks of the Iranians and then exploited them to understand not just where they were, but what they were doing and how they were making decisions. And then, and then, when they went to employ they didn't just take take the systems out by flying overhead at 40,000 feet and dropping bombs. You probably saw that they had forward deployed elements in the host country of Iran, that deployed drones that helped finish off the integrated missile defense systems, anything that was left from what they took out before. They took that out before their fighters ever got to the airspace, using the same kind of things you saw the Ukrainian Jews, but on on steroids. So then, then what else? Of course, they denied the they would deny, then to blunt any attacks that were coming back on them. They deny. They use those same kind of systems to deny the Iranians the ability to do precision targeting with GPS type denial systems and such. On the inside, the Iranians were doing similar things, denying GPS signals. But the but the kit that the US used was able to be much more. I mean, that the Iranians used could work through all of that problem. So in essence, you saw cyber, you saw space, you saw AI all put to use. Because if there's one thing the Israelis are experts at, it's integrating all that information, infusing that phenomenal intelligence they gathered to make sense out of a picture that they could then exploit in their combat operations.</p><p><strong>Philip </strong>21:02</p><p>Yeah. Well, thank you for that. It's not by accident that we see as SHIELD. A lot of fascinating companies started by Israeli former military technologists, entrepreneurs, so you were very early to introduce cyber into Central Command. That was one of your duties and innovations as the Operations Officer, technology has changed rapidly and in that time. But how would you assess the use of cyber specifically among all the other asymmetric technologies that we saw and maybe didn't see, but no, we're, we're operative in this operation.</p><p><strong>VADM Donegan </strong>21:45</p><p>Yeah, I'll have to be careful here, because I was intimately involved with the planning for the operations that we would do here. That, as you can imagine, intertwined the National Security Agency operations, which, which worked for the intelligence community, with CENTCOM, which are the employers of all that, right? And if you think of cyber, you have to think of it. Everyone likes to think about the offensive capabilities of cyber, right? And, and you can go in there and like the Stuxnet virus, and destroy centrifuges without ever having to put somebody on the ground,</p><p><strong>Philip </strong>22:20</p><p>One of the earliest Israeli use of cyber against Iranian nuclear proliferation going back over a decade.</p><p><strong>VADM Donegan </strong>22:29</p><p>That's right where they entered a particular set of malware directly into the control systems of the centrifuges can cause them to spin up at a higher rate of speed and basically destroy themselves, if that makes any sense. So one of the things that that's always at play when you have that's the things that people think are the cool things related to cyber. But cyber has many other uses. It has the capability of giving you access, to listen and understand and then further develop networks. And AI gets applied to that, and now you have a much Completer picture of how Iran does things, how they supply things, how you learn their supply chain. And so the other side of cyber is to defend, but it's also to use those accesses to understand so then you can take apart the enemy. And so I would say that when we were in the initial phases of bringing cyber into our operations, everyone wanted to go to that offensive side. But as you can see, the way the Israelis used it there, there was probably offensive elements of their cyber, but the key elements of their cyber was to under to use it as access to understand and augment the things you're getting from space and signals intelligence and stuff, when you actually can, can, can use it to to understand exactly what the enemy is doing, how they're communicating with each other. And now imagine you're one of those Iranian senior officers or generals and all of your buddies got killed, and now they promote you. You don't know what means you can talk on that isn't being listened to, and you don't want to be the next one to go away. And you don't know who even you can talk to, who's a good guy and who's a bad guy. You don't know how the Israelis are getting information on where you are, and you don't know what, who you can give an order to that won't be overheard. So you can imagine the paranoia that it would put in place. And think about that as an amazing use of cyber that isn't necessarily talked about when you get a glom on to we can take out the centrifuges.</p><p><strong>Philip </strong>24:38</p><p>It's basically a psychological operation in cloaked in technology, Admiral, you were going to discuss the nuclear status now with the three destroyed sites. We're still awaiting, I guess external intelligence on the battle damage assessments, the so called BDA. What's. Your take. I mean, you were involved in the initial planning, you saw what happened. And I want to also ask you, what's your assessment of the Commander in Chief, leadership and Chairman of the Joint Chiefs of Staff and just executing the US part of the operation in this surprise operation Midnight Hammer?</p><p><strong>VADM Donegan </strong>25:22</p><p>Well, it's interesting to bring that up, because, as many of you know, Dan &#8220;Raisin&#8221; Caine is the chairman now, and he was, you know, he was formerly associated with SHIELD, so Philip, you know him. Well, some of the others out there may not have met him, because he had to step away from that role when, when he took that job. But there's no tougher job than the chairman. When you have a crisis like this, the chairman's job in that time is to is to take the options that the combatant commander, this case, Central Command brings to present to the President. Because what a president wants isn't an answer to the problem. He knows the problem exists. He wants a range of options to choose from. And if you can imagine in this situation, President Trump had many options to choose, including joining Israel, right up front, right and being part of this operation, or, if not joining them, how do at what time should he join? Should he join at all and nd is there, if we join to what level do we join? Do we join? Take for do or join more broadly? And what's our role in defense of Israel? All of those things together are what general Caine would be talking to the president about, and he'd be helping him understand those are called courses of action, which ones the president chooses. Like any CEO of a company, he's not going to want just one option. He's going to want to understand the range of options he can employ and have the right advice on which ones of those so general, Caine isn't controlling operational forces, quite the contrary. He's advising the president on helping him select those, those range of courses of action that would be in the national interests of the United States. And we saw how that played out.</p><p>The President didn't choose to join Israel on the front end. He chose to let Israel play this out. We did, of course, provide them the kit, provide them the weapons. We probably collaborated on intelligence. Maybe we collaborated on air to air refueling and things like that, but we weren't directly over Iran with them initially, and then there was a choice made to go in and finish the nuke sites off, but we also defended Israel. We were active participants in in keeping the hundreds of missiles that were fired at Israel, and blunting that effort to significantly reduce their effectiveness when they got to Israel. So let's talk about the nuke site. There's lots of press about it, and lots of people that want to tell you this or that, fundamentally, Iran's if you have to look at Iran's nuclear program, not as one thing, in other words, not as what's in for do you have to look at it as, what if the entire program that gets you to a nuclear weapon, and that includes the centrifuges that spin uranium to get it to the right level and purity that you want right? It also includes, though, the technology to put that on some kind of delivery device. It includes the technology to make the bomb. It includes all the scientists that have knowledge of it. It includes the other leaders that run the programs. And if you put that all together, and you look at what was attacked and what is gone today, Iran's nuclear program as it existed is gone. What remains are elements of it, if that makes any sense. But the string of programs, the entire program itself, is no longer in existence. What is there are there's, there's probably a certain amount of of uranium that's enriched to 60% that is somewhere however, we may find out that the lion's share of that is buried in the taunts, and some of it is probably buried at for do. Their ability to spin centrifuges, to get uranium above 60% is damaged in some way, their key leadership that runs all these programs is gone. Their ability to make the actual bomb itself, the metallurgy and all that goes with that has been decimated. It doesn't exist anymore. So that's how I can make this statement. Over time, we'll understand how much of Fordo was gotten at. Now, not being an expert, and I don't see the BDA today, what we did wasn't designed to collapse the entire internal, all the tunnels that exist in for, do we were, what was, what that operation was designed to destroy those centrifuges that that could spin uranium to a higher level. And as you heard the International Atomic Energy Organization say, uh. They're 100% assured that those centrifuges can't do that anymore, because their tolerances are built that they can't take vibration. They're built to these super tight tolerances because they spin at super high speeds. And if you can imagine, it doesn't take much to damage that. And then when it's damaged, they become unrepairable. So look at the program that way, as opposed to, oh, is it for dough, etc. And think of Natanz. When that site was attacked, it may be years before anyone can even go in there, because there was uranium stored there, and all of that is now buried, and what's contaminated with alpha particles, they may not be able to go in and even inspect it. Does that make sense?</p><p><strong>Philip </strong>30:41</p><p>It makes perfect sense. Thank you for that assessment. So regime stability or instability, it's your guess is going to be better than most. This is something that's very difficult to plot out, but you spend a lot of time thinking about these issues in uniform and actually in some of your post Navy career life on various policy boards. What are the prospects for Khomeini's regime to remain intact now that their largest source of leverage, the nuclear blackmail you know, has been severely degraded, right?</p><p><strong>VADM Donegan </strong>31:25</p><p>This is a real interesting question, so I'll frame it this way, anytime the United States is involved in trying to impose a regime change, we really weren't successful, except you could argue once with Japan, and that's because of unconditional surrender that happened, and we rewrote a constitution for the country and helped implement it under MacArthur, spoke to Germany, again, an unconditional surrender, but maybe less successful, because we only got the world, only got about half that right at the time, and Germany got split up, and it Didn't work out the same way. But beyond that, our track record for regime change is not good, and the reason is because it's very difficult, it's impossible, probably, to build a military plan that can get you regime change. What you really want in Iran is a revolt, right? You want the people of Iran to cast the leader out, and then that puts you in a different stage. It's unlikely to have that happen in Iran, at least in current times, so that may come over time, but it's unlikely, and that's because the regime has built a system, a network of command and control, that suppresses any kind of revolt early. And I'll give you one example, if you remember the women's issues that came up that started to gather attention about a year and a half ago, and and everyone thought this was going to be the beginning of something in a matter of a few months, that was put down, and it's put down with the regime that roots that out as systems. And and people know that if, if they get vocal, them, not just them, but their families, end up in prison and jail and off somewhere. So, so the regime change thing is, is not something you design a military operation for. What you can do is topple a government and have a failed state, right? And so could that happen? It's unlikely now, because the Supreme Leader is still there, and if he were to be killed as an individual, that mechanism for the would still exist with a different leader.</p><p><strong>Philip </strong>33:33</p><p>So you and I have had some discussions recently about the role of the Trump administration having a restraining influence on the Israeli leadership? Do you want to just provide a little bit of color there?</p><p><strong>VADM Donegan </strong>33:50</p><p>Well, one of the problem, you know, one of the most interesting relationships that exist is probably the one between Bibi, Netanyahu and Trump. But no one really knows what that relationship is, except the two of them. But it certainly had, you know, it's, it's had its ups and downs, but where, where they collaborated, you know, you'd have to argue has been in this operation was, well, right in the end, Israeli did the lion's share of the fighting with us, kit, and when needed, of course, you know, campaigned hard to have the US do what they could do in Fordo. Not that the Israelis didn't have a plan on for dough, but they knew they couldn't be as successful probably, as we. We could and the US did choose the operation to go after for dough. But after that was over. I thought that, you know, the US was really clear that we weren't going to be in it to go much farther than that, that that's where we wanted to go. And then President Trump wanted to influence Netanyahu to cease the fighting at. That point that that the nuclear program was decimated enough, as I described, and, you know, and we were sharing, of course, and had the same intelligence the Israelis had, and, and at the time, he probably understood the, you know, this revolt versus regime change problem set that I described, because everyone's been studying it hard and convinced Netanyahu to stop at the same time, though, Netanyahu, just days before, was indicating, even before that, that he was going to that they had probably achieved the key objectives that they wanted to and I'd say this, that I don't think the Israelis would stop if they hadn't successfully gotten through everything that was on their list that they believe that they could still get at. So that kind of brings us to the ceasefire. Philip, which is, I would say that it's, you'd have to look at it. It's probably a one sided ceasefire. The Iranians have stopped. The Israelis are watching. They're doing their own BDA, they're understanding. And I believe that in their mind, they reserve the first right of refusal to go back in there if they find something that they should have gotten that didn't get serviced. I hope that doesn't happen, because I think, you know, there's a great opportunity for Iran to be at a table now, somewhat disadvantaged, but we have to be cautious, because Iranian, the Iranians, if there's one thing that they're experts at is negotiations. They correct. They are really good at that, and they understand the interplay of the international community very well, and use and use that, you know, use entities against each other to buy them time reconstitute and rebuild and those elements of the nuclear program that remained, and other things that they have, they're bargaining chips now for them at the table,</p><p><strong>Philip </strong>36:47</p><p>You had mentioned previously, sleeper cells in the United States. How concerned should all of us as Americans be whether, and this would not have been the first attempt by the Iranian regime to have assassination efforts against specific leaders.</p><p><strong>VADM Donegan </strong>37:11</p><p>So now, a matter of fact, as you know, the Iranians tried to years ago, had tried to assassinate an, you know, an Arab leader here in the United States, it was failed and foiled in but the example you know that that whole operation is is what they have as part of when I mentioned proxies and goods force and terrorism, it's why the United States designated the Quds forces a terrorist organization, because they do have those sleeper cells out there. And they're not just in US countries. They're in our allies countries. They're in Arab countries. You know they and what I what I can say about it, is you can never say they're not you know that that's not an issue, but you can imagine it couldn't be higher on the priority list of the United States intelligence services, the Israeli intelligence services and the intelligence services of our allies and partners, and no matter what you see at summits and G sevens and such about people not getting along, the one place that the collaboration across intelligence agency is, is, is, is intertwined, is when it comes to counterterrorism and the passing of this kind of information. So I won't say, Don't worry all as well. There's just not some business, not a reason for Iran to do that right now. They're in a position now to to negotiate from what they believe, where they still hold some cards to play. One of them is, do I even participate with the, you know, Atomic Energy Commission? Do I walk away from, from the nuclear proliferation treaty that allows inspectors to come in? That's a card to whatever is left to their of their nuclear program to to the other things, like the other weapons they have. The Israelis destroyed a lot of their long range ballistic missiles and drones, but they still have 1000s of missiles that can range all the Arab countries that are virtually untouched other than their leadership and command and control has been attacked.</p><p><strong>Philip </strong>39:20</p><p>So okay, let's talk a little bit about your relationships and perspectives with Gulf allies. We've talked a lot about Israel, but MBs and Saudi, the UAE, Bahrain et cetera. And then I want to expand the aperture to think about what's happening in North Asia, with China, as well as the current and active hostilities on the European continent, with Ukraine and Russia. And what lessons are being drawn from the military and political leaderships in those areas based on what they're seeing on the ground in Israel?</p><p><strong>VADM Donegan </strong>40:00</p><p>So if you can imagine, and you're a you're a China, you know, or you're a Russia, you're looking at this whole operations through a different lens than we just discussed, right? So let's take your Putin for example. You're somewhat ecstatic because you're going to have a free hand while this is all going on, to continue your operations that you know, when the world tends to jump on one problem at a time. And so for if you looked at the news cycle and the attention of world leaders during these 12 days, there was little about Ukraine going on. And even though the horrific things Putin was doing, he continued to do so for so from that lens, you know, Putin is watching this, comforted that the attention isn't on him at that moment in time. But if you're China, it's a different lens. First of all, you get the majority of your energy from the Middle East. So you don't want there's lots of talks about Straits of Hormuz closing, you don't want that happening. So you're behind the scenes ensuring that you can still get your oil and energy right, and they pay for it at a regular price to the Gulf nations. A large portion of the GDP of both Saudi Arabia and the UAE, and to some extent, Qatar, comes from dollars paid by the Chinese for that energy, then the China gets at a huge discount the black market oil that Iran is not supposed to sell. They're selling that crude to the Chinese. So basically, you want the Straits of Hormuz open. So does Iran, because they continue to then get money from the Chinese, who are the only folks really buying that oil from them. But the other thing you're looking at in China is you're looking at two things, Ukraine and this war, and seeing different ways of warfare being fought. In Ukraine, you saw this innovative use of drones, innovative use of technology, commercial Fast, fast fast reaction time to refine weapon systems and make them work to where the Ukrainian was. The Ukrainians were able to decimate the Russians Black Sea Fleet without a navy, right? That's innovation, but now you watch what the Israelis did, and see this way of war fighting that not only went in and took out targets, but did it from internal to the country and decimated leadership at the same time with with precision accuracy and get into the supply chains. So if you're China, you're probably looking at all of what you see and saying, okay, you know any future war is going to have dimensions that I better really understand my vulnerability to before I take that step going forward. And then one you didn't mention is North Korea. So if you're the leader in North Korea, your lesson is clear. Uh, never give up your nuclear weapon. So, you know, thinking you better and you better be careful where they are.</p><p><strong>Philip </strong>43:09</p><p>Ukrainians would agree with that. Ex Post Facto after the fact, yeah, yes, yeah, yeah, massive leverage. Uh, given up, or, you know, at risk.</p><p><strong>VADM Donegan </strong>43:20</p><p>If we talk about our Arab nation partners, let's just talk two of them for a second, Philip, because I think they're super important to especially to SHIELD and and those in tech, you know, between Saudi Arabia and and the UAE, you have two of the largest investors in tech in the world, right, the and they've decided both those countries to go all in when it comes to moving forward with the United States in the development of AI and and you're not going to see a change to that and that it means their sovereign wealth funds are looking at in different ways. Saudi Arabia is doing it different than the UAE. Are looking at the right firms to be involved with in the United States and globally, but specifically in the United States, to get on the cutting edge, and they want to be part of it early, so they can have claim to the utilization of it if needed, of those capabilities as they're developed, if that makes sense, and it can be by having part ownership, or it can be by co-development, like G42 is doing in Emirates.</p><p><strong>Philip </strong>44:33</p><p>Fascinating, because you were very early to identify G42 specific to the UAE in their artificial intelligence ambitions. So I suspect you would agree with the overall assessment that these asymmetric technologies that are fundamentally commercially developed technologies by mostly startup founders, scrappy startups coming out of. University labs and the like, as opposed to large research labs, you know, DARPA being, you know, the prototypical one going back from the Cold War. Um, and not necessarily coming from large defense primes. So these technologies are, were very much on display. They're not going away. That's why we set up SHIELD to go after them. But you know, we when we when Raj Shah and I decided to do SHIELD several years ago, before actually having a fund business and a full team. This was before Ukraine. This is before what we just saw, and it's unfortunate that the world's going in this direction, but that's not our decision. It's going in this direction. You and I were talking earlier about alternatives to GPS. Can you just share what happened when, when you were in the region last week in terms of your lack of GPS and how that even happened?</p><p><strong>VADM Donegan </strong>46:06</p><p>Yeah, sure. Before let me just finish one thought that you just brought up there, and then we'll do the GPS piece. What's crystal clear to me that the reason that you're seeing this heavy investment in AI being to the earlier stage companies is because it's about speed to innovation, right? It's about the it's about what you saw in Ukraine, right? How can I take something and rapidly develop it? And when you talk about primes, it's harder for them to have that same cycle of speed, and although some are are working on it. So what the, what's, what's really cool about this is these Arab nations, especially the UAE and Saudi have decided, when it comes to AI to invest, to be with the United States and not China and and that was a hard, singular decision that they made. MBZ in the UAE, made that decision to step away from China and join with the US, because they see the future being in those same companies you described. If that makes sense, they know that we're going to do it not just in the right way, but will also be profitable, and will, our American businesses will drive it to the right answer, right So, and they couldn't get that with China. There's no way they could get that and and, you know, NBC was supposedly said it was easiest decision. MBZ is the leader of the United armor Emirates. It was the easiest decision he made to align and make sure G 42 his work was with the United States and not China. So GPS, you know, is interesting because it's kind of indicative of technology, right? It's what allows our weapon systems to be super precise, right? And there's different ways to guide, etc, but the advent of GPS weapons changed warfare right before to get a weapon on a precise target, you needed a laser. You needed something because the inertial measurement units weren't as precise, right? They could get it through the window of a building, you know, to hit this particular whatever. So, but then what came up, just like you see in drone technology now, counters to that, right? So, okay, if I have something I want to protect, I can put GPS jammers all around that target, and then it can never be struck to the precision that the weapon system could have. It may get close, but it may not get as precise as they want it to be. And think about a bunker busting bomb trying to hit one tiny little shaft to get to go down as an example. Well, when I was in the entire time I was in the Middle East, my iPhone here, and I've got it in front of me, it never told me where I was accurately for the duration of that conflict, and the time was never corrected. You know, I was in Iran one day and in Europe the next day. Because obviously, you know the coalition forces, the you know, the allies of the US are using GPS jamming so that the Iranians can't target but the Iranians were also using it, and they were using it in the waters of the of the of the of the Arabian Gulf. And if you go and just do a Google search, you'll see that there have been almost ship collisions and ships going off course that are trying to drive back and forth through the Persian Gulf because GPS isn't working anymore, or wasn't working. Reports are now. It's kind of back to normal, and they also so that kind of technology is classic. We see the same thing in drones, right? Drones have a capability. So where's the technology going in drone defense, right? And how do I counter the drones? And then it's just the technology starts to just build on itself, but, and those. Countries that understood it, like the United States, we can still deliver those precision munitions where we wanted to, despite GPS jamming and Israelis using us kit, were able to do the same thing.</p><p><strong>Philip </strong>50:10</p><p>Fascinating. Admiral Donegan, thank you so much. This has been a fascinating conversation. You and I get to have these frequently, but for many of our investors and friends, this is rare and is certainly privileged. I am much more optimistic today than I was even a couple of weeks ago, just given the massive shift in facts on the ground in a volatile part of the world, I think there are many lessons on deterrence that are being absorbed, as you point out, with adversaries the United States that will take note, the technologies that Shield Capital is supporting are very much on the ascendant. Going to be increasingly important. And you know, good guys and bad guys may have access to it, but we're supporting the good guys and mission matters. That's why we do this, in addition to generating returns for our investors. So just want to thank you and very grateful for everything you've done for me personally and for Shield Capital, and I hope you'll be at our California event so that some of the people that you haven't met are able to spend time with you.</p><p><strong>VADM Donegan </strong>51:27</p><p>Well, thanks. I'm also optimistic, Philip, I think, from the Middle East, time will tell on how we capitalize on what's been achieved. Be careful, though, the Iranians, you know, want to slowly rebuild and you know, and that can happen over time. They got a big hurdle to get through, but there's tremendous opportunity now for maybe sustaining this change in the Middle East for the good.</p><p><strong>Philip </strong>51:53</p><p>Fantastic. And with less than two minutes, I think we'll leave it there. Shield meeting, start on time and end on time, sir, thank you so much. Greatly appreciate it. Thank you.</p>]]></content:encoded></item><item><title><![CDATA[🎙️Ep 4 - Obviant: Building the Decision Edge for Defense Acquisition]]></title><description><![CDATA[In this episode of the Mission Matters podcast, David and I speak with Brendan Karp, the CEO of Obviant, a startup building a government market intelligence platform.]]></description><link>https://maggiegray.us/p/ep-4-obviant-building-the-decision</link><guid isPermaLink="false">https://maggiegray.us/p/ep-4-obviant-building-the-decision</guid><dc:creator><![CDATA[Maggie Gray]]></dc:creator><pubDate>Wed, 25 Jun 2025 15:43:41 GMT</pubDate><enclosure url="https://api.substack.com/feed/podcast/166768174/7eec62d9dd9f648fe2a61e72dee6977a.mp3" length="0" type="audio/mpeg"/><content:encoded><![CDATA[<p>In this episode of the Mission Matters podcast, David and I speak with Brendan Karp, the CEO of <a href="https://obviant.com/">Obviant</a>, a startup building a government market intelligence platform. In this episode, we discuss:</p><ul><li><p>How Obviant is building the &#8220;source of truth&#8221; for DoD budget, contract, and program data&#8212;replacing PDFs and spreadsheets with structured, searchable intelligence and providing its customers with a decision edge</p></li><li><p>The painful reality of legacy DoD software systems like ABIDES and DTS, and why commercial technology should be powering national security workflows</p></li><li><p>How the DoD is rewriting acquisition playbooks&#8212;embracing OTAs, CSOs, and the software acquisition pathway to bring in non-traditionals faster</p></li><li><p>And more&#8230;</p></li></ul><p>You can listen to the podcast on <a href="https://open.spotify.com/episode/5fYCDqs3ItBWxK32594RZu?si=jHWcO1gkRrC8fc9d3KUYcw">Spotify</a>, <a href="https://podcasts.apple.com/us/podcast/obviant-building-the-decision-edge-for-defense/id1807120572?i=1000714465312">Apple</a>, <a href="https://youtu.be/zvUq1DalvhE">YouTube</a>, the <a href="https://shieldcap.com/episodes/4-obviant">Shield Capital</a> website, or right here on Substack.</p><p>As always, please let us know your thoughts, and please let us know if you or anyone you know is building at the intersection of national security and commercial technology. And Obviant is hiring! Please reach out to their team if you are interested in working in the future of DoD acquisitions intelligence. Tune in next month for our next episode!</p><p class="button-wrapper" data-attrs="{&quot;url&quot;:&quot;https://maggiegray.us/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe now&quot;,&quot;action&quot;:null,&quot;class&quot;:null}" data-component-name="ButtonCreateButton"><a class="button primary" href="https://maggiegray.us/subscribe?"><span>Subscribe now</span></a></p><div><hr></div><p><strong>Maggie </strong>00:00</p><p>Welcome to the Mission Matters Podcast, a podcast from Shield Capital where we explore the technical opportunities and challenges of developing and deploying commercial technology to national security customers. I'm Maggie Gray</p><p><strong>David </strong>00:16</p><p>I'm David Rothzeid</p><p><strong>Maggie </strong>00:19</p><p>And we are your hosts from the investment team at Shield Capital. On this podcast, we discuss the technical challenges of developing and deploying commercial technology to national security customers, as told from the founder's perspective.</p><p>In this episode, we're joined by Brendan Karp, the CEO of Obviant, a government market intelligence platform. I had a lot of fun co hosting (and also a little bit interviewing) this podcast with my colleague David Rothzeid, who led this deal at Shield Capital. He really could have actually used this product back when he was an acquisitions officer in the Air Force, so he was the perfect person to have on this podcast talk about the exciting world of government, acquisitions, contracts, budgeting, data, etc.</p><p><strong>David </strong>01:16</p><p>Well, Maggie, I gotta say it was an absolute honor to finally come on to the esteemed Mission Matters Podcast, especially Yes, to talk about a company like Obviant that may appear mundane to the casual observer, but for those of us steeped in this national security government procurement system, this is truly critical, especially if we're going to achieve efficiencies in government and better outcomes for taxpayers and for startups that are trying to sell compelling technology into the government apparatus For those who don't know, but maybe you do, because you're listening to this podcast, the procurement government procurement system is made up of 1000s of different systems and information sources. Alarmingly, some of it still runs on paper and spreadsheets and is siloed off in hundreds of different databases. And you know, just for an example, the upcoming $1 trillion defense budget, yeah, it's going to be delivered in 1000s of pages of PDFs. And you know, for Obviant, they're tackling this problem by building the data source of truth for programs, acquisition, organizations and budget data for all of the Department of Defense, they've built an AI platform that creates a common data operating picture with incredible workflows on top of that data foundation. And I'm just really excited for that conversation we had with Brendan.</p><p><strong>Maggie </strong>02:38</p><p>David, Brendan, so great to have you guys both on the show today. We have Brendan Karp here from Obviant, the CEO of Obviant, and then David Rothzeid from the Shield Capital team is joining us today for this special episode on the world of DoD budgeting and contracting and acquisitions. Thank you so much for coming on the show. I want to just start laying the groundwork. You know, can you tell us a little bit about what is Obviant and, you know, how did you get into the world of government contracting in the first place? It's not exactly the sexiest topic that you can end up in.</p><p><strong>Brendan </strong>03:15</p><p>No, definitely not. There's not, typically not how I describe it, you know, I think it's a it's a really niche but, but somewhat important thing is, especially as you think about the budget and the acquisition side of it. So I'll give a little bit of background as to why I chose to focus on this problem space.</p><p>So I grew up in the DC area, in around the beltway, but actually had no exposure to government whatsoever, right? I grew up in a family with no government involvement, and you know, the last company I was building, last startup, most of that business was in the private sector, funding early stage technology companies. However, we scaled a $20 million Homeland Security innovation program where we would take those same non traditional companies and fund them around mission needs. And that was my first exposure to public sector problem sets. And I was hooked, because for me, it was this amazing intersection of getting to build but for a problem that actually mattered, right, like the public sector mission sets, we got to focus on for that program, first responders, homeland security use cases, was incredible.</p><p>And the flip side of that story, though, is that although is a ton of fun working on those problems, it felt like punching a pillow at times, trying to make progress. And I think anyone, and especially I know David, will resonate with this. Anyone that's been part of the government acquisition or innovation ecosystem feels that right. So, flash forward. We scaled that program great. The impact, honestly, was somewhat limited by that acquisition process, and I knew I wanted to build a company from zero again. And the thing that was missing for me in every other space that I explored, whether it was enterprise SaaS or otherwise, was that mission piece like that was really real for me, of like, why am I going to wake up every morning and want to work? On this problem set, and it was the impact. And so for me, it was kind of a no brainer at that point to focus on the government space and take all those learnings in that experience that I had building that last company and do this specifically in defense and national security, because I truly felt that this was the highest order problem of our time to work on, and that's what drove me to start avian and work on this, this challenge.</p><p><strong>Maggie </strong>05:23</p><p>And David, you led this investment at Shield Capital, along with Mike Brown. What got you so excited about this space? You're obviously an expert in the acquisition space. What about Obviant really stood out to you?</p><p><strong>David </strong>05:36</p><p>Well, thank you, Maggie. I think expert is definitely in the eye of the beholder, but I have had the privilege of being in this defense acquisition system for quite a long time, and I will say very rarely in my you know, I guess 15/16+ years of being around defense acquisition rarely have ever come across somebody who was like a complete independent party, didn't grow up in the system, wasn't an acquisition or a contracting officer, and really understood the subject material and not just that, like the high levels of, oh, the defense industry base, it's shrinking. Oh, the defense industrial complex, it's challenging to work with. Oh, I've, you know, tried to work with it, won a contract or didn't win a contract, and it's terrible. Like no Brendan truly understood some of the insides and outsides. Like, I think, the first time we met, we got very wonky on the what's called a DoDAAC, a DoD activity, address, code, and I would be hard pressed to find 5% of acquisition officers in the military who know what a DoDAAC is, right. So like some of this nuance stuff that I knew that what Brendan was building would be very compelling. And I will say at first, when I started exploring this space of what are all the tools out there that can help a company understand the marketplace, right, the federal marketplace, at first, it was, who can I partner with on behalf of Shield Capital for all of our portfolio companies and try to get them a discount? And when I met Brendan, it turned into, okay, how can I be a partner and collaborator with Brendan on a full time basis, ideally, through an investment to help accelerate the opportunity that's in front of us to really build out the source of truth around government procurement data.</p><p><strong>Brendan </strong>07:37</p><p>What one thing I gotta call out is, I think that that is I think that that is the one and only time that having knowledge of what a DoDAAC is has actually gotten me points, because it is a terrible party trick otherwise.</p><p><strong>David </strong>07:49</p><p>So, yeah, I wouldn't bring it up too often otherwise,</p><p><strong>Maggie </strong>07:53</p><p>So Brendan, can you tell us a little bit about what is actually the state of tooling to track DoD contracts and budgets and acquisitions today, both within the US government and in the private sector, and how is Obviant really pushing forward the state of that tech? And David, I don't know if you have any horror stories here from your time In government, if you want to chime in with anything like that.</p><p><strong>Brendan </strong>08:26</p><p>Yeah, I think just, real quickly, and then I'll let David speak to some of those horror stories, or whatever you want to call it, you know, truly appreciate, you know, all the belief and conviction that David and you and the team at SHIELD have had in us. But you know, that was always our goal, right? Was like to that point where he was able to look and look and say, this person or this company gets it right, was always like, how do we build this for the people that know this system and have a deep level of empathy for them, of like, are working it inside and out every day, and represent the data in the way that they wish they had it right.</p><p>And so to your point on, what is the landscape of tools that is a lot of the challenge is that the way that folks like David and others who have been in those chairs, right, the tools they wish they had don't often exist. It's often PDFs or spreadsheets, phone calls to other people who have information that they don't, right, and then separated different enclaves and systems that don't talk to one another. So, not only is there a base level access to the data problem, right? So we don't even have access to that, and that takes weeks, months to coordinate that for much of the information, which is open source, by the way. The second level is then, even if we had access to it, the tooling that we're used to in the commercial sector, right? You think of like something like air table in terms of how you can manipulate simple data sets or build your own database, you know, analytical dashboards. None of that really exists in the form that we have in the commercial sector, side, in the government.</p><p><strong>David </strong>09:47</p><p>Yeah. I mean, I'll just go back to my time at the Pentagon. We used a system called ABIDES, which stands for automated budget, interactive data, enterprise system. It recently got replaced in 2022 with its with a new thing called program and budget enterprise system. But ABIDES was built in the 1970s It was DOS based, and you had to, like hit F2 and F7 to move through it. And this is how the budget was built, program element by program element and then rolled up into some other system at OSD, and then sent off to the office of management and budgeting OMB. And it was just sort of like, like you had defense contractors in the Pentagon solely for the purposes of being able to, like, maneuver with that type of a system. So, you know, it's really not a surprise that the Department doesn't necessarily understand everything that's going on when you're still constrained to systems and large parts that were built, you know, in the 1970s on these mainframes that really should have gone away a long time ago.</p><p><strong>Maggie </strong>11:05</p><p>So Brendan, tell me why is Obviant need to exist in the first place, and who are really the different kinds of users that you guys are targeting?</p><p><strong>Brendan </strong>11:16</p><p>Yeah, so go back to what I was talking about a little bit ago, right? Which is like, how does this process actually play out right now? So if we talk about the acquisition process, where is the funding? What budget is available? What are the different programs that that funds? What who are the organizations and the people that actually own those programs? What is, what does Congress think about that? And how are they changing that money, adding to it, subtracting from it, and then the company's capturing it. All these questions are surprisingly difficult to answer, right? And most people can't get the answers, not that they don't know how to but it takes a long, long time to do it.</p><p>Just answering one of those questions could you take you weeks of if you're on the outside of the building, diving through 15 different PDF documents, three different websites, Googling on, you know, on searching on Google, or looking through LinkedIn to kind of connect those dots and all that information exists out there in this weird mix of structured and unstructured format, right? So there is no actual source of truth to actually follow the money, and so that first archetype that I'm speaking to is on the private sector side. And when we started Obviant, that's who we thought we were solving for.</p><p>But what we quickly realized is that same problem is equally as acute within the building right like to make critical decisions, and if you're in David's shoes to actually execute acquisition or innovation programs, you don't have that data at your fingertips, and so what do you do? You have to do that same research process, dig into different systems or make phone calls and try to get that data from other people right. So what we do is, we ingest all that information, so we pull from 1000s of different sources, like an open source intelligence company, right? And fuse that all together into an actual source of truth, right? We use AI and machine learning to actually structure and connect that data up.</p><p>And so who that benefits is that we've realized is on the private sector side of things. We can help a company understand what is their execution roadmap, where is their capability relevant? Where can they solve problems, and where's their funding for it, from an investor standpoint too, where are the largest markets and where are the trends going? Where should we deploy capital? And then within the government, it's actually how to execute efficiently, manage their portfolios, collaborate, understand where there might be duplicate efforts and could be, could be, you know, working together. And lastly, one of the biggest things is technology transition. So we're funding all these different capability areas, but where is their long term sustainment funding and partners that we can work with? And so kind of tying all that together, right, if you listen to that, that all those parties are asking similar questions from different angles, and it all kind of boils back to this fact that there is no common operating picture, from a data standpoint, for them to ask those questions and get an answer in a structured, organized way.</p><p><strong>David </strong>14:12</p><p>Yeah, that was masterfully said Brendan, and couldn't agree with you more. You know, the way that the DoD on the inside, it is organized around different functional areas. And so if you were to say, what is the budget for this grouping of programs around this technology area, and who are the organizations that are executing, it would be a very manual process to put it together. In fact, it would come from some sort of a request for information on one of those terrible systems that, you know, does taskers, and then, you know, would kind of filter out to a bunch of people like me, you know, like a former O-4 or O-5, that are, you know. Providing oversight for a myriad of different programs. And then we would reach out to the outstations you know, and say, hey, does this thing you know, is it? Do you think your program subscribes to it?</p><p>And maybe I'll just give like a specific example, when I was still in the building, the Undersecretary for Research and Engineering highlighted 14 critical technology areas, you know, things like biotech and hypersonics and artificial intelligence and cybersecurity. And the way that the Department kind of rolled up how much funding was going into these different technology areas was by asking all the different like program elements. You know, how much of your budget is AI, how much of your budget is hypersonics? Of course, like the program I was on, we had $0 in hypersonics, but my program was the advanced battle management system, right? Which was the Air Force's major investment into Joint All Domain Command and Control, which was another amorphous topic. I sort of, I don't know, I don't know how much of my $5 billion budget over the future year defense plan is associated with artificial intelligence, but I gave a number.</p><p>And so it's like these types of things that where what Brendan is doing is taking the actual data that is being executed against these contracts and lining it up to the organizational structure and the people that are executing them and the programs that Congress cares about. And I guess what, creating this, this taxonomy whereby you can understand what these similar but not necessarily functionally aligned elements are telling you and at a high enough level, you can really derive some valuable insights. And so whether you are a program manager doing market research around a solicitation topic area, and you want to know who are all of the performers that have executed against these types of capabilities in the past. Or you just want to get better insight into how much funding is going into these types of capabilities, you know, based on actual data that is being executed against, whether it's in, I forget what the Federal Procurement Data of FPDS, right? You know, you can start to get real meaningful understanding of what's happening in the Department, and that can greatly inform where you choose to apply your resources or how you do your evaluations.</p><p>And then on the VC side, like, totally agree. You know, if we're seeing, you know, how many counter UAS companies do we see Maggie, like, so many, and how much actual budget is going towards this area? Like, not that much. Or if they are, who are they going to it tends to be the large defense primes. You know, it becomes a bit of a challenge to make an investment here, because one the total addressable market isn't that big for who you would expect to be the largest buyer, national security. And it seems like it's got pretty well locked down with the defense prime. So, you know, these are just ways that we can help inform our startups, you know, or inform our investments, and then help our startups think about how they can penetrate the defense industry, the defense procurement system.</p><p><strong>Maggie </strong>18:32</p><p>I'm curious Brendan, how does Obviant actually maintain its database for these insights? You know, I'm thinking about the President's budget request just came out, and they're devoting a lot of resources to programs like Golden Dome. And I know this is a new term, but it's probably going to actually incorporate a lot of existing and future programs. Like, how do you guys think about organizing that data for something like that?</p><p><strong>Brendan </strong>18:56</p><p>That is one of the key questions we get all the time is one, A) how do we organize it? And B) how do we keep it up to date and make sure it's accurate? And so one thing that I think is really important, so obviously, startup urgency is critical, right? And moving fast and with incredible speed. But I also felt that building this space, you have to build something that really works, right? Like vaporware in the government market does not work, right? And that there are real mission use cases that has to be dependent on and so for us, we actually went heads down and did nothing but data engineering for a year to figure out how these data sources were structured, how we could accurately represent them, and build the pipelines and structuring mechanism to actually keep that up to date, right?</p><p>So, to your point, you've called out a few of the larger sources that we pull from, but there's also 1000s of other sources that we have to ingest to populate that, that core data structure and the schema, right, that underlies everything that we do here at audience. So to your point on, how do we keep it up? Keep it up to date? Well. We're constantly going out there and collecting more information, right, but making sure that when we do structure it, that it is at parity and we can trace it back to a source of truth, that this exact piece of a PDF or this point in a video hearing, right? And then now, because we've done that, we can consistently add to it, right? So how do we keep it up to date for existing sources, that just happens in the background. But now, when we work with folks on the government side or within industry that say, Hey, we also have all of our own data that we want to understand. What that means against the information that you collect, we want to rationalize that out against the acquisition landscape. It's easy for us to bolt that onto that data structure, kind of in a secure environment for them to unlock their own insights from it.</p><p>So the data engineering challenges is where we started, actually, before we launched a product, to make sure that we had that. And along the way, we've had to really solve some of these more complex natural language processing problems to take these amorphous concepts, right? And my favorite is contested logistics. What is contested logistics, right? It is the big buzzword. It is the it is one of the top priorities right now. But knowing that contested logistics means these 10 things which have these other seven components which relate to one another in that taxonomy tree, those are some of the hard things that we've had to do to not only A) ingest and structure the information, but then B) can, you know, continuously translate against it to unlock what people are looking for.</p><p><strong>David </strong>21:27</p><p>Maybe Maggie, if you don't mind, I'd love to ask Brendan a question. So, say the DoD came to you and they were willing to give you some of the inputs that would go into their systems of record. Because right now, you're only seeing the stuff that's publicly available, which in a lot of cases can be very rich, because these are contracts, right? And contracts, it's a double ledger. So like, you know, there's real money going in, and people are signing their names. So like, trust me, like it's very real. But what about getting the inside some of the messiness as the programs are being developed, or, you know, with in the services themselves, they're doing gives and takes, and then the budget rolls up to OSD, and they're doing more gives and takes, and then it goes up to OMB, and they're doing more give and takes, like, with that sort of insight, you know, what do you think something like Obviant could do for the Department?</p><p><strong>Brendan </strong>22:32</p><p>To that exact point, that's where I get really excited, right? Is that really, it's, a data challenge, and then how do we actually build the workflows and the product outcomes that that meet the day to day challenges that we face in the Department, right? And so to your point, you know, fusing government data, whether that is the programmatic side of things, or, you know, solicitation, CSOs, to what we were talking about, that that they might issue, and understanding what is the full pathway with that. You know, some of the things that we can unlock that we get excited do, get excited one, one piece right now is just following the money audit. Right?</p><p>We talk about audit a lot right now in terms of ensuring that the DoD finally passes an audit. That's one area. Can we trace the dollars all the way from budget through to contract execution and understand where that money went? You know, another big one that I think is super top of mind is that, when we're talking about developing non traditional capabilities, that oftentimes starts out in the R&amp;D side of things, but what is the transition pathway for that? Right? So you fund these non traditional companies, it is fundamentally an equal parts collaboration. So like, how do you work within the building, but also to in order to collaborate effectively, you need access to the data to do that. So if you're able, at the outset, to understand, I'm funding the CSO as company, right, and I'm within one of the R&amp;D organizations, there's realistically one of two, three transition pathways that that's going to follow to PEO missiles in space, right? Or, you know, IWS on the Navy side of things.</p><p>So really like solving these data problems and getting access to some of the other information, which, which we're working on right now with the government, can unlock a broad range of use cases, everything from the financial management side of the house and just portfolio, but all the way through which, which I'm personally most passionate about is that capability development side. How do we make sure that we actually take these capabilities that exist in the private sector and make sure they don't just die on the vine, but they actually get into the hands of the end users, and critically at scale?</p><p><strong>David </strong>24:32</p><p>So if I heard you correctly, you know, go back to April 2023 when Jon Stewart interviewed then SECDEF Kath Hicks on fraud, waste and abuse and the inability of the DoD to pass an audit, you think, with the power of Obviant, you know, at its disposal, and granted, would take some time, but you think the DoD could maybe actually pass a financial audit?</p><p><strong>Brendan </strong>24:58</p><p>What I would say to that is: what gets me really, really excited is the opportunity to partner with folks like that, right, and hopefully reach that outcome together. So I think that you know so much this is back to, you know, the product and capability and culture side of things is that taking a great, phenomenal, high performing team, which, which we think we're building here at Obviant, and pairing that with folks on the inside that feel the exact same way from the mission side of it and reaching that outcome. I think anything is possible. I really, really, really do.</p><p><strong>David </strong>25:28</p><p>So you know, all audits aside, Brendan, maybe you can highlight how your current customers are leveraging you today and extracting a lot of value. And if there's any anecdotes that you want to share, we'd love to hear it.</p><p><strong>Brendan </strong>25:44</p><p>Yeah, for sure. I think that is the most rewarding part. Is like when you're able to be part of building a product and you actually see it make a difference, right? Like it's producing the outcomes that that you, that you hope it would free user. And so I'll talk about a similar thing across all three sides of our customer base and on the company side, right?</p><p>We had a fast growing defense technology startup, right? Think Series B onward, that has a capability, and they weren't quite sure how they could actually make that hop over to the program of record side and into the program office, right? And as we know, that's a multi year battle. It takes a lot of different pieces that you have to connect and stakeholders. And so what we were able to help them understand is that for their capability, where do they actually mesh, right? And in this particular instance, that they fit in a couple of intelligence oriented program offices across the DoD and in particular, they were able to understand that this one program office had some very early RDT&amp;E funding, and that RDT&amp;E funding was actually being allocated for an emerging program, right? And it hadn't turned into a program of record yet. And so really early on in its life cycle were they not only able to understand A) where their capability maps, but B) understand something that is capturable, see all the atmospherics around it, and the current players in that program office, where the strategic thinking was going there, and how they're speaking about this, and then even down to the exact stakeholder to engage with. And what we found is that that actually put them in the running to get a contract with that organization right.</p><p>And so that exact thread of basically taking something from capability all the way down to execution is playing out with investors and funds that we work with, where they say we want to make an investment in offensive cyber, right? What is all the money out there? And then who does that drill down to from an execution standpoint, and can we get to conviction there, right? And even on the government side, if you're developing that capability from the other side of the coin, right? You possess that early stage funding, and I'm the one that's prototyping these intelligence capabilities. You know, how do I take that all the way through to actually identifying my transition partner, right? Who is the organization that can actually fund this through sustainment, being able to power those kinds of workflows are the success are the success stories that have just been unreal to be part of.</p><p><strong>David </strong>28:04</p><p>Yeah, that's awesome. I've definitely used the tool a few times to sort of really understand how much success a given company has had in a given area, and then been able to then also see other organizations that they're not working with, and be able to point them in that direction, and it's only with a few, you know, semantic queries pretty, pretty simple, I guess. What would you say to companies that are interested in using something like Obviant, but maybe a little bit reluctant from from the spend standpoint, and maybe you could also highlight, like, what's the earliest stage company? What's the latest stage company currently using your platform today?</p><p><strong>Brendan </strong>28:48</p><p>Yeah, yeah. So we've worked across that entire spectrum, right from early early stage companies that have just gotten their first SBIR awards and are already thinking strategically about, well, what is my transition plan? What is my transition pathway, and what can I capture along the way to get there right, and then all the way up to the top 10 primes right that we work with? So what we found is, for us, it's always been, I said this at the outset, how do we take the workflow and the knowledge that the experts like you David, have in this space, right? People that know this market like the back of their hand, and how do we democratize that and just make it dead simple and easily understandable and a beautiful product that that that folks can leverage and make it intuitive so working across that spectrum, right? Obviously, budget and spend tolerance is vastly different, and one of the things that's always been really important to us is making sure that we build a business model that can accommodate all sides of that spectrum. However, what I will say is, at the end of the day, it's you're making a long term investment.</p><p>And one of the things that we hear, oftentimes, that companies in the defense market have to do is engage on the Hill, and engage on the Hill, and engage early and. Oftentimes that entails hiring a lobbyist, and that is not cheap. But the thing you oftentimes hear is, if you don't do that, though, your upside is inherently gonna be capped, right? And where you need to get to without that congressional engagement is gonna be super hard. And we think that that program office problem, right, and the funding, identifying that and running a strategic business development process is the same way that, if you're not investing in it early and continuously and running that effort in parallel with the immediate things, whether it's SBIRs or OTAs or otherwise, at the end of the day, you know you're gonna have to be playing catch up over the long run, and it's a critical competency that you have to build early on.</p><p><strong>Maggie </strong>30:38</p><p>So I want to take some time to really talk through some of the big changes that have been happening in the acquisitions and contracting space over the last five or six months or so. Right here we have two of the experts in DoD acquisitions and contracting. So I want to take the time to really break down some of these big changes. So Brendan, can you talk through what are you seeing as some of the most important or impactful initiatives coming from the administration thus far? And can you break down what do they actually mean for both, I guess, traditional defense primes, for the DoD and for this new generation of startup?</p><p><strong>Brendan </strong>31:23</p><p>So I like to think about it in a couple of different realms, right? So one is really the how we buy side of things, right? And the how we buy has to do with more of the regulations and the processes around that. The other side of things, I think it's important to touch on, which is the what we buy, right? And that's this discussion that we're having right now is shift from these large platforms to commercially available items, products, and what we actually need for the future from a national security standpoint, and the two are deeply related, right? So that first part of things is how we buy, right? And you saw this with the executive order around rewriting the FAR, right, something that has been around for decades and decades and decades, which I'm sure David can tell us lots of frustration stories about, can you define, define the far what does that mean? I will, I will defer to David on the actual definition on that.</p><p><strong>David </strong>32:15</p><p>Sure it stands for the Federal Acquisition Regulation. It is about 3000 pages around all the things you can and cannot do when acquiring goods and services for the government. So extends beyond just the Department of Defense, it's for all federal agencies in the executive branch. And then, of course, beyond just the Federal Acquisition Regulation, the DoD has the DFARS, which is another set of tombs, further refining things that are more bespoke and specific to the DoD. Not to be outdone, the services tend to have their own, you know, variations and variants on this document. And then, of course, you get down to the individual programs. And they have their cultures, their guides, their instructions. Lo and behold. You know, it's easy to see why the culture of compliance sort of permeates across the entire acquisition workforce.</p><p><strong>Maggie </strong>33:09</p><p>And I assume, David, you've read the full FAR, cover to cover.</p><p><strong>David </strong>33:13</p><p>I have not read the entire thing, but I am pretty good at most of the various parts of it, right? It's broken up into all these different parts. And so at times, I have dug in and really tried to hone in where, you know, I can find exceptions for things.</p><p><strong>Brendan </strong>33:29</p><p>And that's one of the reasons so, the last thing he just said there, and why, I think it's wanted to defer to him to define that right, like exceptions for things, right? In order to be able to navigate that effectively and actually drive change. You have to know, within this 1000s and 1000s of 1000s of pages framework, know what part of it you can actually use to get done. What do you want to get done right and find the exceptions within it. So back to kind of your original question, Maggie. One is this rewrite of the FAR and then two, one of the other big things is, is, is, is promoting things like the software acquisition pathway, right, or commercial solutions openings, right, which David and the team at DIU years back pioneered and actually started right. So this idea of we can leverage these other authorities, different than the far right, other transaction authorities, etc, to actually accelerate the acquisition landscape. This is a huge shift in terms of the way that acquisition is done. And the big area that that's being pointed at back to that, that other category here, of what we buy, the big area that's being pointed at, commercial solutions, openings, again, is commercial technologies, things that can be adapted towards mission needs, or non traditional startups that we can bring into the fold on prototyping agreements that are these more lower cost or adapted solutions that actually meet the capabilities that we need today, not three years out, or 40 years ago, from a major platform standpoint.</p><p><strong>Maggie </strong>34:59</p><p>So Brendan. And you mentioned the commercial solutions offering a couple times now, but I want to take a step back from some of the acquisitions contracting jargon. What does it actually mean to buy commercial and why is that even important in the first place?</p><p><strong>Brendan </strong>35:15</p><p>What this is essentially saying is that if there is commercial, if there's a commercial alternative, right, and technology exists in the commercial sector that we can either leverage or adapt, right? We should be doing that which, which makes sense, I think, like one of the, one of my, one of my favorite, uh, unfortunately, anecdotes is, like a number of folks that I've talked to who are still active duty, they talk about how difficult the payroll process is, right, like how awful the experience around payroll is, of like, missed paychecks or having to go back and request pay that's been missed or time off. And that, what does that tie back to? That oftentimes ties back to these massively complex, custom built systems, right, where the private sector, again, has built some of the best in breed, right?</p><p>You think about companies like ADP and on the on the startup side of things, what we know is like a Rippling or Gusto, right? The the sector has been building these systems and, and so this, this whole shift, is to say, Well, can we leverage things like that, right? And, and, if not, off the shelf, adapt it right again, from a prototyping standpoint, to meet the mission needs, right? So when a commercial alternative exists, can we leverage that? Because what I think it's a shift to say is that there are certain things, absolutely, from a basic research or a custom, you know, needs standpoint, that should not, cannot and will not ever exist solely in the commercial sector. But there's a whole lot of things that the government does right, and the government needs, excuse me, that exist in the commercial sector right now that the incentive is out there for the commercial sector to develop that is the best in breed that leverages, you know, top engineering talent across the board and capital incentives from investors that the government can benefit from, right? And get that at not only a lower cost than it would be to build these systems over time, but a far superior capability, because the private sector is going to maintain that and upgrade it.</p><p><strong>David </strong>37:09</p><p>Maybe my favorite anecdote that Brendan you were just highlighting around payroll, which, yes, is an absolute nightmare, and I had to call on the phone more than a few times to figure out my MilPay back in the day, especially when you move from organization to organization. Well, you know the defense travel system DTS is probably the bane of a lot of military and civil servants&#8217; existence that was designed, developed by Northrop Grumman. I don't know if you knew that they were, you know, known for their travel website, ferocity. I mean, I thought they were more about building weapon systems, but yeah, Northrop Grumman won the contract to build defense travel system in 1998 so this is pre dot-com bubble now, and they've gone on to win task orders, you know. And it still remains to be the same system that is quite cumbersome. So much so that if the, you know, I'm still in the Reserves at the Pentagon, and if the Reserve said, David, you can no longer drill locally to where you are, because I live in Washington, DC, you now need to go to, I don't know, say, Wright Patterson, Air Force Base. So now for my reserve duty, I'd have to engage with something like DTS to get over there. I would definitely at year 18, almost to 20, I would say, sorry. You know, it's not worth it, because that system is just so brutal to work with.</p><p><strong>Brendan </strong>38:42</p><p>And I think it's back to your question, Maggie, right on, you know, the experience on this and what does this buy, commercial meet all mean, all this ties together, because what we're talking about is, how do we bring these non traditional commercial companies into the fold, right or accelerated pathways? Well, are those like, how do we actually get them on contract? Then, if they have to go through a multi year contracting process, or the acquisitions officer doesn't actually have the tools in their toolbox to work with them quickly on prototyping for that solution, so these things really all kind of converge.</p><p>And back to, you know, a lot of what we focus on is, well, how do we identify those capabilities. How do we identify the acquisition pathways? Well, what funding is available, right? So on the government side, how do we actually tap funding to leverage this? Like, where is there money in either my budget or elsewhere that I can partner with to do this? And it's equally as challenging on the private sector side, not only is it a Pathways problem, but it's also a demand signal problem, right? So from the private sector, how do they know that this is a problem worth solving, right and worth focusing on, meaning that if I have an expense management platform or a travel systems platform, how do I understand what, what millions or billions of dollars there is for me to capture in the DoD to go after? That and adapt my solution and justify that to my investors, right? There is no source of truth for that is one of the hardest parts. So I think, like all of these things again, really tie together is everything from the approaches to, if we're aligned on the approaches and we and we fix a lot of the authorities and regulations around that, conveying that demand signal is equally as important so that people can execute on both sides of the equation.</p><p><strong>Maggie </strong>40:24</p><p>So how can we actually measure the effectiveness of the administration's new initiatives around streamlining defense acquisition? How do we know if rewriting the far or pushing the commercial solutions offering software acquisitions pathways actually makes a tangible difference in the state of acquisition efficiency, and</p><p><strong>Brendan </strong>40:48</p><p>That's one of the challenges that that we're hitting head on right, which is there is an easy way to understand when we leverage the software acquisition pathway or we leverage CSOs, what does that actually translate into down the road, right? So let's just pick an example here. Let's say a lot of the C-UAS efforts that we hear about, right? That&#8217;s counter small unmanned aerial systems. So think a lot of the things that we hear about in terms of small, commercially available drones that folks are using, that we have to defend against. Currently, a lot of the times we're using missile systems that cost, you know, upwards of 1,000,002 million bucks a pop, to take those out, right? And, and so, how do we bring into the fold more affordable alternatives to that that, again, might be commercially available and, but there is no way to track that great we leverage the CSO right now.</p><p>What did that translate into a year, two years, three years down the road, right? What percentage of the overall capability that was fielded can we attribute back to that original OTA? Or if an OTA started off in prototyping, right, which means more that R&amp;D stage, did that OTA transition to production? Was it fielded at scale? And one of the core problems, and this is what we're hitting head on, is that data is not either a structured that way, or structured to begin with, because, again, A) it might only be in a PDF or a contracting document and B) there's no traceability between those handoffs, right? So the R&amp;D organization that might issue that prototyping agreement. There is no data source of truth between that and the production organization, whether it's a program executive office or otherwise that fields it.</p><p>So to your question on &#8220;Well, what is the effectiveness of these things?&#8221; That's a lot of what the Department is trying to figure out on its own end right now is, well, what is the pull through and the follow through of when, when we use these new methodologies, what is the overall success rate in terms of companies that are transitioning to programs of record? And it starts with the data right? And because the data is not set up to answer those questions, and then we're not manipulating it, we're not able to get a clear picture of that.</p><p><strong>Maggie </strong>42:55</p><p>Brendan, where are we today in terms of using some of these more innovative contracting mechanisms, like OTAs and CSOs. And where do you expect us to be within the next few years?</p><p><strong>Brendan </strong>43:11</p><p>I&#8217;ll start with the end state. And I think exponentially different, right? I think that we are at the beginning of really you look at kind of things like the CSO and you can go back from there. You know, consortia is the first models of leveraging this right at some level of scale, but we've really only scratched the surface. If you look at OT, other transaction awards, in the last year or so, in both years, it's less than 5% of all awards issued by the government in terms of dollars, right? Less than 5% of money is going to these innovative mechanisms. So if we look at all the discussion and the talk about defense tech and leveraging the software acquisition pathway and CSOs and OTs, it is still such a very, very small piece of how we actually contract today.</p><p>However, with the momentum that we're seeing and the discussion around it, and the actual policies that we're putting in place, I think that that looks exponentially different if we look three to five years down the road in terms of how, not only the percentage at which that we leverage these authorities, but also the outcome that it can drive. You know, if you look at the number of venture backed companies, non traditionals, that have transitioned to a program of record. And I think that this is and I think that this is correlated, there's less than a dozen right that have actually gotten Program Office contracts like we are still so so much in the top of the first inning in this transformation.</p><p><strong>Maggie </strong>44:35</p><p>What will it actually require within the DoD to take these top down directives and actually make them a reality and a part of the culture across the organization?</p><p><strong>David </strong>44:48</p><p>I think it requires a lot of training, and then I think it also does require more publicizing of the anecdotes that are going well. Other transactions have been in the Department as an authority since the mid 90s. One of the biggest programs to leverage it was called Future Combat Systems, FCS, and it was like this massive, multi billion dollar program that the army was going to sort of digitally revolutionize all of their capabilities. So it was a hardware, software, data like, I mean, it was kind of this crazy program, and it failed spectacularly. Now, if you go back to Rick Dunn, who's the greatest historian of other transaction authority, because he did bring it to DARPA in 1989 and then helped shepherd it into the DoD after that. You know, he will tell you that program was only an OT in name. But if you look at the terms and conditions of the contract, if you look at the milestones and how it was executed, and Boeing, I believe, was the primary contractor, it was only, it was only OT and name it really had nothing. It did not leverage the value proposition of that authority. And so, you know, these things go, they ebb and they flow based on how successful or not successful things are. I think we need to just sort of mandate it, as we are seemingly doing. But then really take you know, to the craft and teach and and celebrate the successes and showcase. You know what is, what is good look like, and I think that's kind of how you move the Department over time.</p><p><strong>Maggie </strong>46:34</p><p>Brendan, what would you say is your most controversial hot take about DoD, acquisitions, budgeting, contracting,</p><p><strong>Brendan </strong>46:43</p><p>Yeah, to be honest, not really a hot take guy, yeah. Prefer to just focus on the execution side of it. But I'll probably kick this question to him, because I'm sure he might have one.</p><p><strong>David </strong>46:54</p><p>You know, in spirit of Maggie, your question, one thing that has me a little bit concerned, and I haven't heard a lot of people talking about it, is with the people taking the return to the office and then being offered the fork in the road. A lot of great contracting officers, acquisition professionals have taken it, and I am concerned that the most innovative ones who should be awarding the contracts in this new, like mandated way, leveraging, you know, underutilized contracting vehicles, like other transactions, etc. I'm afraid that we're going to have a bit of a glut in awarding contracts and getting non traditional companies into the industry base. So a little bit of, you know, cutting our nose to spite our face with what we're trying to do in the Department, I think it'll get worked out. But maybe something Brendan, if you wouldn't mind, highlighting, like, you know, is there a way to sort of see a trend analysis around some of these policies being enacted, and whether or not they're having the necessary effect or the velocity of contracts being awarded, is that maybe gonna shrink or not meet the same pace as previous years?</p><p><strong>Brendan </strong>48:17</p><p>Yeah, and I think that what you're speaking to, there's tracking what the downstream effect and outcome is, right? And this is one of the things that we find that in order to do that. So the platform that we've built right, allows decisions to be made more effectively at every level, right? And so whether that's downstream from the end user or technology transition, right, if you're a program manager, all the way up to the headquarters level to understand, well, whether it's at the services or DoD right, what are the implications of the changes that we make. And so to that same anecdote that I like to speak to is that OTAs are currently much less than 5% of all award values right annually. The same thing, we can look at the data here to understand, when we make a policy decision or an HR decision over here, what is the impact in terms of contract velocity, right? And we can look at that information understand, has that dipped, has that gone up? Did we see an impact on these more innovative mechanisms that we wanted to use? And I think what I would say is that all ties back to the thing that we're so focused on. Is, how do we not only make this data accessible, but then do analytics right and manipulate it in a way that gives us the answers that are timely and critical to the actual decisions that need to be made that are gonna that are gonna transform this how we do business at the Pentagon.</p><p><strong>Maggie </strong>49:36</p><p>What advice do you have for other startups building in the national security space, other than &#8220;buy Obviant,&#8221; which is obviously a given.</p><p><strong>Brendan </strong>49:46</p><p>No, I appreciate that, you know. And then I love to hear David's take from the other side of the investor angle and government side. You know that? I think that the biggest thing is like be strategic, and play the long game, right with what you're doing. Know that signing up to build a company is a 5 to 10 year journey, right? And in this case, it is that and then some meaning that you might not see the payoff until three to four years into that journey, right, in terms of exponential returns. And so the biggest thing, I would say is really like, you know, focus on something that you're truly passionate about, and that, you know, you feel that you have a connection to from the mission side of it, and know that you're playing the long game, both in terms of building, not only building the company, but also in terms of how you think about how you're building that product and executing the sales motion that everything that you need to do in this space, I think, needs to optimize for what that long run is.</p><p><strong>David </strong>50:47</p><p>That's awesome. Brandon, I guess, yeah, for me, advice for other startups: have a co founder and choose them very carefully, because it is a really hard, long journey, building something from scratch, trying to convince customers to try you out, trying to convince investors to take to collaborate with you, and then trying to hire employees right to go on that journey. And I think a lot of times companies where the co founders just aren't totally in lockstep, it can be really, really challenging for the future success of the startup.</p><p><strong>Maggie </strong>51:24</p><p>Brendan David, thank you guys so much for coming on the show.</p><p><strong>Brendan </strong>51:27</p><p>Really appreciate. Maggie,</p><p><strong>David </strong>51:30</p><p>Yeah, awesome.</p><p><strong>Brendan </strong>51:30</p><p>Thanks so much for having us.</p><p><strong>Akhil </strong>51:35</p><p>Hey everyone. Thanks for listening to the Mission Matters Podcast from Shield Capital. Tune in again next month for another conversation with founders building for a mission that matters. And if you yourself are looking to build in the national security space, please reach out to us.</p>]]></content:encoded></item><item><title><![CDATA[🎙️Ep 3 - Unstructured: Building the Infrastructure to Win the AI Race]]></title><description><![CDATA[In this episode of the Mission Matters podcast, Akhil and I speak with Brian Raymond, the CEO of Unstructured, a startup building the future of data tooling for generative AI, transforming unstructured data into structured data that can be used by AI models.]]></description><link>https://maggiegray.us/p/ep-3-unstructured-building-the-infrastructure</link><guid isPermaLink="false">https://maggiegray.us/p/ep-3-unstructured-building-the-infrastructure</guid><dc:creator><![CDATA[Maggie Gray]]></dc:creator><pubDate>Fri, 23 May 2025 16:02:30 GMT</pubDate><enclosure url="https://api.substack.com/feed/podcast/164138316/dd0185b9d5ae6e84293cc76d7b0d09e6.mp3" length="0" type="audio/mpeg"/><content:encoded><![CDATA[<p>In this episode of the Mission Matters podcast, Akhil and I speak with Brian Raymond, the CEO of <a href="https://unstructured.io/">Unstructured</a>, a startup building the future of data tooling for generative AI, transforming unstructured data into structured data that can be used by AI models. </p><div class="captioned-image-container"><figure><a class="image-link image2 is-viewable-img" target="_blank" href="https://substackcdn.com/image/fetch/$s_!rrNs!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F227fd846-47e8-4679-8d72-09a880356eac_1920x1080.jpeg" data-component-name="Image2ToDOM"><div class="image2-inset"><picture><source type="image/webp" srcset="https://substackcdn.com/image/fetch/$s_!rrNs!,w_424,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F227fd846-47e8-4679-8d72-09a880356eac_1920x1080.jpeg 424w, https://substackcdn.com/image/fetch/$s_!rrNs!,w_848,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F227fd846-47e8-4679-8d72-09a880356eac_1920x1080.jpeg 848w, https://substackcdn.com/image/fetch/$s_!rrNs!,w_1272,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F227fd846-47e8-4679-8d72-09a880356eac_1920x1080.jpeg 1272w, https://substackcdn.com/image/fetch/$s_!rrNs!,w_1456,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F227fd846-47e8-4679-8d72-09a880356eac_1920x1080.jpeg 1456w" sizes="100vw"><img src="https://substackcdn.com/image/fetch/$s_!rrNs!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F227fd846-47e8-4679-8d72-09a880356eac_1920x1080.jpeg" width="1456" height="819" data-attrs="{&quot;src&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/227fd846-47e8-4679-8d72-09a880356eac_1920x1080.jpeg&quot;,&quot;srcNoWatermark&quot;:null,&quot;fullscreen&quot;:null,&quot;imageSize&quot;:null,&quot;height&quot;:819,&quot;width&quot;:1456,&quot;resizeWidth&quot;:null,&quot;bytes&quot;:278320,&quot;alt&quot;:null,&quot;title&quot;:null,&quot;type&quot;:&quot;image/jpeg&quot;,&quot;href&quot;:null,&quot;belowTheFold&quot;:false,&quot;topImage&quot;:true,&quot;internalRedirect&quot;:&quot;https://maggiegray.us/i/164138316?img=https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F227fd846-47e8-4679-8d72-09a880356eac_1920x1080.jpeg&quot;,&quot;isProcessing&quot;:false,&quot;align&quot;:null,&quot;offset&quot;:false}" class="sizing-normal" alt="" srcset="https://substackcdn.com/image/fetch/$s_!rrNs!,w_424,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F227fd846-47e8-4679-8d72-09a880356eac_1920x1080.jpeg 424w, https://substackcdn.com/image/fetch/$s_!rrNs!,w_848,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F227fd846-47e8-4679-8d72-09a880356eac_1920x1080.jpeg 848w, https://substackcdn.com/image/fetch/$s_!rrNs!,w_1272,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F227fd846-47e8-4679-8d72-09a880356eac_1920x1080.jpeg 1272w, https://substackcdn.com/image/fetch/$s_!rrNs!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F227fd846-47e8-4679-8d72-09a880356eac_1920x1080.jpeg 1456w" sizes="100vw" fetchpriority="high"></picture><div class="image-link-expand"><div class="pencraft pc-display-flex pc-gap-8 pc-reset"><button class="pencraft pc-reset pencraft icon-container restack-image buttonBase-GK1x3M" tabindex="0" type="button"><svg aria-hidden="true" width="20" height="20" viewBox="0 0 20 20" fill="none" stroke-width="1.5" stroke="var(--color-fg-primary)" stroke-linecap="round" stroke-linejoin="round" xmlns="http://www.w3.org/2000/svg" class="icon-noB79L"><g><path d="M2.53001 7.81595C3.49179 4.73911 6.43281 2.5 9.91173 2.5C13.1684 2.5 15.9537 4.46214 17.0852 7.23684L17.6179 8.67647M17.6179 8.67647L18.5002 4.26471M17.6179 8.67647L13.6473 6.91176M17.4995 12.1841C16.5378 15.2609 13.5967 17.5 10.1178 17.5C6.86118 17.5 4.07589 15.5379 2.94432 12.7632L2.41165 11.3235M2.41165 11.3235L1.5293 15.7353M2.41165 11.3235L6.38224 13.0882"></path></g></svg></button><button class="pencraft pc-reset pencraft icon-container view-image buttonBase-GK1x3M" tabindex="0" type="button"><svg xmlns="http://www.w3.org/2000/svg" width="20" height="20" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" class="lucide lucide-maximize2 lucide-maximize-2 icon-noB79L"><polyline points="15 3 21 3 21 9"></polyline><polyline points="9 21 3 21 3 15"></polyline><line x1="21" x2="14" y1="3" y2="10"></line><line x1="3" x2="10" y1="21" y2="14"></line></svg></button></div></div></div></a></figure></div><p>This episode was super fun to record &#8212; Brian is incredibly well versed in the nitty gritty reality of building and deploying AI to DoD customers. We had a great conversation about killer use cases for AI he&#8217;s seen in DoD and enterprise customers, the current state of AI infrastructure in DoD, policy changes he would make within DoD to accelerate AI adoption, and much more. </p><p>Episode overview:</p><ul><li><p><strong>Brian Raymond&#8217;s journey</strong> from the CIA and National Security Council to building Unstructured, an AI infrastructure startup.</p></li><li><p><strong>The &#8220;unsexy&#8221; data and infrastructure challenge</strong> behind LLMs and agents &#8212; from PDFs and XML to chunked JSON.</p></li><li><p><strong>How SOCOM, the Air Force, and the Army are leading the way</strong> in practical GenAI deployment</p></li><li><p><strong>What commercial enterprises like Nestl&#233; are doing with agents today</strong> &#8212; and what the DoD can learn from them</p></li><li><p><strong>A tactical roadmap for AI adoption in national security</strong> &#8212; from policy fixes to compute access to trust-building</p></li><li><p>And much more</p></li></ul><p>You can listen to the podcast on <a href="https://open.spotify.com/episode/3Bh2FAQ5K4aRyyLbAQBGG6?si=aZc6ZQe3Rr-r2DOcYvbkjA">Spotify</a>, <a href="https://podcasts.apple.com/us/podcast/unstructured-building-the-infrastructure-to-win-the/id1807120572?i=1000709517028">Apple</a>, <a href="https://youtu.be/i5wqpDtE8Us">YouTube</a>, the <a href="https://shieldcap.com/episodes/3-unstructured">Shield Capital website</a>, or right here on Substack.</p><p>As always, please let us know your thoughts, and please let us know if you or anyone you know is building at the intersection of national security and commercial technology. And Unstructured is hiring! Please reach out to their team if you are interested in working in the future of AI infrastructure. Tune in next month for our next episode!</p><p class="button-wrapper" data-attrs="{&quot;url&quot;:&quot;https://maggiegray.us/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe now&quot;,&quot;action&quot;:null,&quot;class&quot;:null}" data-component-name="ButtonCreateButton"><a class="button primary" href="https://maggiegray.us/subscribe?"><span>Subscribe now</span></a></p><div><hr></div><p>Here is the full episode transcript:</p><p><strong>Brian </strong>00:00</p><p>We're going to need to figure this out faster than our adversaries on how to utilize LLMs coupled with agents right in order to advance mission as fast as we possibly can.</p><p><strong>Maggie </strong>00:12</p><p>Welcome to the Mission Matters Podcast, a podcast from Shield Capital where we explore the intersection of technology startups and national security. I'm Maggie Gray,</p><p><strong>Akhil </strong>00:22</p><p>And I'm Akhil Iyer,</p><p><strong>Maggie </strong>00:23</p><p>And we are your hosts from the investment team at Shield Capital. In this podcast, we discuss the technical challenges of developing and deploying commercial technology to national security customers, as told from the founders&#8217; perspective. In this episode, we're joined by Brian Raymond, the CEO of Unstructured, a startup building the future of data tooling for generative AI transforming unstructured data into structured data that can be used by AI models. It's common wisdom that AI models are only as good as the data they're trained on and the data they have access to. However, much of the world's most valuable data is not stored online in a structured way that AI models can access. Rather, it's stored in PDFs, PowerPoint slide decks, emails, photocopies of paper, documents, satellite images and other hard to process data formats.</p><p><strong>Akhil </strong>01:25</p><p>Brian saw this phenomenon firsthand while working in government, in the Central Intelligence Agency and on the National Security Council, and then again, as a VP at Primer AI, which is a start up building natural language processing tools for the US government. Brian was inspired to build Unstructured, really, in order to accelerate the adoption of AI and a lot of the tooling needed for both the public and private sectors.</p><p>Brian, so excited, man, for you to join us here today. Really excited about what you've built already and what's yet still to come. And we're excited to just dive right in. And so I'd love to first maybe chat you came from a super sexy background, the Central Intelligence Agency and here you are digging through the dirty laundry of the AI infrastructure ecosystem. What got you excited about working on those types of really unsexy piping infra issues as you were thinking about what to do next and to build your own, your own company?</p><p><strong>Brian </strong>02:22</p><p>Thanks for having me and excited for the discussion today. It was a really, let's call it, non linear journey, and so I spent several years as a CIA analyst, did a few tours overseas, left government after a stint on the National Security Council, and after business school, ended up at a company called Primer AI, where they were doing some really interesting work with natural language processing and knowledge graphs. And so I joined the company very early on, right after they closed their Series A and had really like a front row seat to AI in action. This is in like the 2018/2019 timeframe. And at the time, natural language processing and language models more broadly, were having a bit of a renaissance after being dormant for several years. And so there's a lot of excitement about how to use these models and a lot of potential for accelerating various missions. So we were working, at the time with companies like Walmart, Goldman Sachs and others. And then we also had an In-Q-Tel work program, and so I had the privilege of helping lead a lot of the work related to that In-Q-Tel work program, where we were deploying these models, model pipelines and knowledge graphs into into classified spaces, and saw firsthand just the friction of trying to leverage these incredibly powerful models, which are tiny models, now in retrospect, in conjunction with mission relevant data. And so after four years of Primer I was looking at this problem space, and I said, look like there's this really ugly, nasty problem that no one else is really well positioned to solve at the far left hand side of the equation, which is, how do you take raw enterprise data and render it rapidly, render it in usable formats so you can use it in conjunction with these incredible models. And so that was really how Unstructured was born.</p><p><strong>Akhil </strong>04:20</p><p>That's awesome, Brian. For those who may not know, can you briefly explain what a work program is? But more importantly, as you were looking at that type of program, how unique or differentiated was their messy data infrastructure portion relative to some of the commercial companies you had looked at?</p><p><strong>Brian </strong>04:39</p><p>That's a great question. So the In-Q-Tel model is one in which they invest in dual use technology companies, primarily companies that actually have great traction in the commercial space, that are fairly early on and as part of their equity investment comes like a body of work to help more closely tailor that dual use technology to. So networks that you know, handled sensitive information to workflows that are more relevant right to the national security or defense space, until you take that base application and introduce some amount of additional work on it to just more allow it to be deployable and usable in those applications. In our case of Primer that lasted almost three years the work program, it was an extensive body of work that had an incredible outcome that led to, that led to, like, a multi year contract coming out of it. And so a lot of the manual work for that two and a half, three year work program was around taking raw XML data and then transforming that into chunk JSON. I mean, if that's not enough to put you to sleep, like, I don't know what is, but this was really a problem from hell, because each you know, each document, each kind of bit, and byte of data, it was non standard. And so anytime like, you know these, we'd have to hard code all these regex pipelines, these regular expression pipelines, to try and transform it, and then maybe a document layout might change, and then it'd break the pipelines, and then you'd have poor inference. Then you'd spend all this money on this knowledge graph, and you have to go back and redo it. It was really a lot more manual than a lot of the magic around AI would lead you to believe. And so the good news with that, though, is that like that XML to JSON, in this specific instance, everyone kind of deals with that. They deal with PDF to JSON. They deal with dozens and dozens of different file types to get it into the lingua franca for language models, LLMs, whichever may be which is generally chunked embedded JSON or markdown or HTML, but in any of it, you need to render into a canonical schema in a standardized format.</p><p><strong>Maggie </strong>06:54</p><p>Yeah, Brian, thank you so much for sharing that background on Primer. You've obviously been working in the national security space for a long time and been working at the intersection of AI and national security for a long time as well. So I'd really be curious to hear, when you started back in the government and at Primer, what was really the state of AI adoption within DoD and AI infrastructure within DoD, and how has it changed over the last decade or so to where we are today?</p><p><strong>Brian </strong>07:28</p><p>It&#8217;s a really interesting topic, because around 10 years ago, you saw natural language toolkit NLTK, a range of other models begin to emerge. But it wasn't really until 2017 when transformer models were introduced, that you saw the industry around this begin to explode, as well as the use cases that were reachable by machine learning begin to emerge. And so shortly after that, Project Maven was formed, right? And you saw significant investments around object detection, image classification models. So really around computer vision, that sort of work, there's a lot less around the language models. And one of the reasons, or a few of the reasons are because, like around the computer vision, there was an immediate need for this in Afghanistan at the time, and a lot of work going on in Syria around taking drone feeds, for example, and being able to classify rapidly classify targets in it. And it was a great application for the tech at the time, and so they were able to put money against labeling data, fine tuning models, deploying these models at scale, and then nesting those within different mission applications.</p><p>On the language side, there was intense interest. But the one of the main challenges with these models is that, if you think of it like horse blinders, they had very small token windows. And so, like our context windows. And so today we're often we see context windows, 50,000 tokens, a half million or several million tokens. And so you can put an entire book in that context window, like think ChatGPT, and ask questions of it. Back then, your thing the context window was around 15 to 20 words. And so what you were able to do with it was not really take a huge amount of data and then ask questions of it easily. Instead, what you had to do was structure that data using these models so pull out like named entities or topics, or do different classification tasks, and then index all of that and then do Boolean queries against it. That is as slow and boring as it sounded coming out of my mouth right now, but like how. A lot of potential for interesting things, right? And so the limitations on the models call it like pre 2022 relegated a lot of the natural language use cases to really interesting like proofs of concept, but that weren't necessarily scaled in the same way that these computer vision use cases scaled out of Maven and across DoD.</p><p><strong>Maggie </strong>10:24</p><p>So then, what are some of the different ways you're seeing people in DoD actually adopt AI today, and what are some of the big use cases that are popping up that are delivering real value to end users?</p><p><strong>Brian </strong>10:38</p><p>We&#8217;re about two and a half years into the LLM generation of machine learning, right? Or this, this most recent epic and ChatGPT was released in November of 2022 and then in this first half and throughout 2023 industry as a whole, as well as, like data scientists and government, started to try and understand, like, &#8220;Okay, how could we use this to engage with our data in new and interesting ways?&#8221; And so a new term has now proliferated, RAG &#8211; retrieval, augmented generation. I believe, like the first RAG deployment was done in January 2023, like two months after, after ChatGPT was released on a on a classified network, and since then, most of the use cases have been knowledge related. So really accelerated search, right as well as some light levels of automation.</p><p>Some of the things that like hindered adoption, at least from you know, 2022 through call at the end of last year were one the political climate. There was huge amounts of anxiety with among the previous administration at the highest level of the government, with adopting kind of a forward looking Gen AI strategy. Instead, there was a huge amount of effort to study it, to measure risk, to mitigate risk, rather than operationalize the usage of it. What that resulted in was a proliferation of bottoms up initiatives. And if you go on LinkedIn any day, you see lots of discussion on this, but you see NIPRGPT, CamoGPT, SOF Chat, as well as a range of other applications across the defense space that are all aimed at, like bringing your data to these models and being able to not only query it, but hopefully help summarize it, automate it, maybe draft new, you know knowledge products in the process that that really defined. I call it like 2023 and 2024 the limiting factors there was model availability, GPU availability, as well as budget and support among service chiefs, COCOM chiefs and others, which really wasn't there. So you saw just lots of 1000 sprouts kind of spring up from inner enterprising units across the landscape using open source tools as well as what limited kind of commercial tools were available.</p><p><strong>Maggie </strong>13:34</p><p>On that topic of where people are really seeing success adopting this technology in DoD, what would you say are some of the unique challenges of adopting this technology within DoD compared to just a traditional enterprise, and where are there similarities in those challenges?</p><p><strong>Brian </strong>13:55</p><p>I'd say the use cases are almost indistinguishable, from what we were talking about around like, chat your data type applications to trying to, we'll talk more about this later, deploy agents across your data in order to automate. Go from kind of Copilot to autopilot in a lot of use cases. That's similar. What's different is that DoD is great at buying, let&#8217;s call it, solutions, right? They're not great at buying infrastructure. And so if you go work with an investment bank or a large CPG company, Fortune 500 of any case.</p><p>The way that Gen AI has unfolded has been the CEO told the CIO or the CTO or the Chief Data Officer, &#8220;We got to go figure out Gen AI.&#8221; And somebody got made the Gen AI czar back in 2023 and then the Gen AI czar cast about for use cases across the organization and like big companies. Companies typically have between like 50 and 100 use cases that they identified. And then what do they do? They put resources across those and so they'll resource them with people, they'll resource them with compute with models, with data, and then they'll graduate those that have the most potential into production, and then scale them right. And so you have a CIO who's got a relationship with one of the hyperscalers from a from a cloud standpoint, they have a relationship with Anthropic, OpenAI, Google Gemini, whatever it might be, right? And they're able to make those infrastructure investments that are required to vector resources across lots of these use cases.</p><p>In contrast to that in the federal space, especially the defense space, you do not have that. You do have cloud contracts, right, with models that are riding on those, but you don't have CIOs who have directives from service chiefs to go find those use cases, provide them with compute, with models, with data, with support in terms of human capital, in order to identify which of those is going to hold the most promise against mission sets. Rather, what's happening is that they're using SBIRs. They're using $5 or $10 million contract vehicles. They're using individual like seat licenses or having individuals by tokens to utilize open source or more universal kind of like DIY do it all, kind of like platforms, in order to try and, like, work their way up. And so I'm optimistic that that might change in the future, but I think that there's, it's going to take a lot of concerted effort, because you what you don't necessarily have in the commercial space that you have here, just don't have ATOs, you might have one ATO that you have to do, like, if you don't want to work with JP Morgan, you got to get your models approved. You got to get through all the security scans. But there's just one CISO that you got to work with in the government.</p><p>You would have thought that CDAO would have solved this, or would have been able, like, have the agency to solve this through Alpha One and various initiatives that never happened. Instead, what they did was more experimentation, which is what the government's great at. There's almost no infrastructure, so to speak, that's being allocated from that, from actual DoD like the Pentagon, down, in order to enable Gen AI use cases. And so that creates a very different environment for a commercial company trying to operate with the customers compared to the private sector.</p><p><strong>Akhil </strong>17:47</p><p>Brian, this is an awesome topic. I love that we can dive into a little bit of this. Certainly, many of our companies, at Shield Capital, really, at the application layer right, are looking to do this, and they want democratized easy access to models compute infrastructure so they can focus on the application built with their customer. So two questions for you based upon what you just said. One, what's the ballpark: How many months or years is the government / DoD behind even the most highly regulated commercial space when it comes to some of this, AI, infrastructure, from a maturation standpoint?</p><p><strong>Brian </strong>18:24</p><p>I would say two to three. I would say they&#8217;re still in 2023 kind of land right now, Akhil. I'm not casting stones, but from the ability to procure and the ability to like take action &#8211; you know, there are lots of folks with a vision, a lot of folks with, like, deep technical expertise, but their ability to actually get things done, I would say that we're there at least a couple of years behind, if not further. I think that, you know it's going to take Congress, and it's going to take the current administration really focusing on this intensely if they're going to solve it, and it'll probably require legal reforms as well as policy reforms than DoD. We're already seeing some great work being done with the CIO shops around this, but it's the tip of the iceberg. It's going to require a whole lot more work in it to really move at a pace that we haven't seen previously.</p><p><strong>Akhil </strong>19:13</p><p>Yeah, thanks, Brian. Let's say if you had to take one call or spend $1 to best accelerate the AI infrastructure in the government. What would that go to?</p><p><strong>Brian </strong>19:23</p><p>It would go somewhere around like something that works really, really well Akhil in the commercial space: application or infrastructure companies like Unstructured working in tandem with hyperscalers in order to rapidly access customers. And so that can that means a few different things. That means one, network access. So for example, with Azure, AWS GCP, we're able to, like execute private offers through their marketplaces and then just deploy our containers easily into customers VPCs. Related to that, we're also able to transact using those marketplace mechanisms very effectively, flipping it around on the customer side, they can access us and other another emerging technologies, really easily. But then they can spin up large clusters and CPUs, GPUs. They have other cloud infrastructure services that are readily available. And so I think, like right now, there's a huge amount of friction and actually capitalizing on the potential of these hyperscalers for transact-ability, for network-ability, data availability, as well as all those other ancillary services that are required around this. And so you've got this, like sports car that you can't really take out of a garage in some ways. And I not really want to go around like heaping praise on hyperscalers, but in this case, they're really have reduced friction in the in the private sector, but it's had almost no impact in the public sector, despite them having marketplaces and these things, they're just not operating in any way, any in remotely the similar manner that they are in the commercial space.</p><p><strong>Akhil </strong>21:06</p><p>Yep, that totally makes sense. Brian, I know we've been a little critical here of the government space over the last couple of minutes, but obviously all of us here, you, Maggie, me, are in this business too, because the mission matters too, and we're excited by the applications. Can you share maybe a more positive story? What was one deployment on the public sector side, or maybe even a mission critical commercial, commercial side that was really exciting for you that either from a technical aspect or from an impact aspect?</p><p><strong>Brian </strong>21:34</p><p>Early on? So we were like a three month old company of three months post slide deck, and I was wandering around AUSA trying to make friends, and I bumped in to Nick Frazier from USASOC, and I was chatting about what we were doing, and he's like, I actually have an Army of contractors hard coding pipelines exactly like what your team had to do at Primer as part of your work program. And so can we do some sort of like design partnership and just start working?</p><p>And so our open source project, actually, we don't really advertise this. We don't want to have it on the website, but the fingerprints all over that are actually from us being in Slack together with USASOC AI divisions developers on real world use cases, and that open source project now has been downloaded almost 35 million times. It's used in almost every single Gen AI application in government. It's used by 85% of the Fortune 1000 and it was actually built in tandem, sitting side saddle with the folks down at Fort Bragg. And so that was, that was incredibly exciting to see, and to see, like all of the different use cases that folks have built around our open source in government, on the commercial side, we're in some really interesting spaces right now, working with a range of companies from like airlines to finance to biotech pharma.</p><p>A really interesting customer that we have is actually Nestle, who's headquartered just there in Northern Virginia, and they are making some huge investments in generative AI and in agentifying their AI stack. And so we are in a really unique position to deliver data to like their agents that are not only helping with an internal knowledge management work, but also creating new products, helping identify market opportunities and new product strategies for them. And so it's really kind of incredible for me to wake up every day and see all the different ways that, like our kind of foundational infrastructure is being used to populate a range of different use cases across these industries.</p><p><strong>Akhil </strong>23:59</p><p>That&#8217;s awesome. Totally awesome, Brian, and awesome to see where you've come, both from those early days and to now, I want to ask one question a little bit on the Nestle point before turning over to Maggie to maybe dive a little bit more into the technical aspects. And that is maybe a broader question, Nestle, how are they thinking about the return on investment with something like this?</p><p><strong>Brian </strong>24:17</p><p>I would say a common theme what's almost universal among the use cases on the on the private sector side, is that it's almost all productivity focused, right? Because you could focus on driving revenue, or you can focus on being more efficient with cost centers. And so they're doing some really interesting work around procurement and legal. They're doing some really interesting work around research and development and utilizing generative AI to generate to deliver near term returns in those area. That doesn't mean that there aren&#8217;t like revenue opportunities. We've seen companies like Writer and Typeface and others leap out to huge, huge valuations by helping accelerate marketing. We&#8217;ve got companies like Apollo and others that are using generative AI to help make sellers more more efficient. But I think that the cost centers in these companies are so large that it's not necessarily about laying people off and reducing workforce. It's more about, how can you 2x or 3x your current headcount by allowing them to be a lot more efficient? And maybe hold that OPEX constant as the as the business continues to grow.</p><p>And so, that's something that's very similar across there isn't, like, a, really a revenue side, I guess maybe tip of the sphere type stuff and in defense. But we're working with some of the testing centers, for example, that have to that as part of their work, they're responsible for putting together, like, incredibly complex deliverables, packages, to higher ups as they're testing munitions or different aircraft, whatever it might be. And so and those R&amp;D type centers, right? Those are, they're so manual, they're so paper focused, that they're really ripe for disruption with generative AI. And you see a lot of demand coming from that as well.</p><p><strong>Maggie </strong>26:21</p><p>So Brian, I wanted to turn to talk through like, what does it actually look like to build a generative AI app for a customer like the Department of Defense? You know, let's say I have an amazing RAG app. I've done all my user interviews. People love it. They desperately want it. I want to be able to chat with my documents, and maybe some of that data that I want to be able to chat with is classified. It's going to have to be deployed on classified networks. I guess, my first question on that, what does it actually take to get that data I want to chat with in a state that it can be used by this model? And how do I actually keep that data up to date as the new data is constantly being developed?</p><p><strong>Brian </strong>27:07</p><p>Yeah, that's, it's really kind of the central question right now, when there's a bunch of different approaches or strategies that you're seeing kind of play out in the space. So, you have companies like us, right where we're selling a piece of infrastructure alongside us. We're doing the normalization, the Extract, Transform, Load of that raw data, and then we're doing a baton pass to a database, typically like a graph or a vector database. And then there's a framework typically utilized to orchestrate between an LLM and that that that data that's in that external memory and that's being continuously updated in order to deliver that that capability. And so in that case, this is invest, like large investments by data teams, usually like data engineering teams as well as cloud infrastructure teams, who want to kind of own each layer of the cake they want to have. They want to own the data they want to own the data structures. They want to own the data storage right and manage that and that's incredibly important to them.</p><p>Now another delivery model is one like Ask Sage, like what Nick's done. There is, he's used our open source with some other tooling, taking Weaviate as a vector data database. And then he has done a lot of work around the frameworks for how those LLMs orchestrate with that data in that external knowledge base to deliver value like ATO in a box chat your data, whatever that might be. And so it's almost pre-packaged, and he's done a lot of that layering for you, but you have a lot of adjustability. You can choose which models you can you choose how your data is indexed. There's, there's a lot there, and it's really almost a B2C motion, right, where we're a pure business to business motion. Nick's delivering a really interesting product that's like a B2C motion.</p><p>Then you have companies like Legion, formerly known as Yurts, Primer, and a range of others that are going kind of far beyond what Nick's doing in terms of vertically integrating that stack. They may have proprietary chunking strategies, proprietary embedding models. They might be using things like graph RAG. So might be using graph databases alongside alongside vector databases. They may have optimized their retrieval models with their and re rankers with their embedding models, in order to optimize it. A corollary in the commercial space or companies like Contextual which is doing a very similar thing where they're doing a lot of the extreme kind of fine tuning of all the different parameter settings on all of this in order to deliver, like, an incredible, like a very exquisite sort of, like, user experience. But they own the whole box, right?</p><p>And so a few different models here on how to engage, and you're seeing the same thing right in the in the commercial space, where you can invest in a vertically integrated stack, and you just buy the box to teams that want to own each layer in the same way that they have, say, with the modern data stack, where they may have bought the ETL/ELT provider, like Fivetran, DBT indexed into like, say, Databricks, snowflake, BigQuery, and then use say Microsoft Power BI on top, and then they have sovereignty over each layer of the cake. And so there's a lot of parallels between kind of how this is playing out today, and then how it played out with structured data over the last five or 10 years.</p><p><strong>Maggie </strong>31:01</p><p>So once I have all my data set up, all ready to go in whatever database of choice, what models do you have access to on the high side to actually then plug into that data?</p><p><strong>Brian </strong>31:17</p><p>This is a good question. This is maybe one that you all would have some thoughts on as well. I mean, I think increasingly you're starting to see, like the two big labs have their models somewhat available on secret, like on tipper or on JWICS, right, with Anthropic and Open AI models. Now, how available those are, how much volume and quota, right? It's even a challenge for us and the commercial space to get quota to do what we're doing. And so that's though they may be available. They might just be available for experimentation. And you know, these things are incredibly GPU hungry, and so the size of the clusters that they're running on in each respective network is the hard constraint on throughput right. And then you know how many applications are trying to hit that model right? Creates real scarcity for the ability to not only experiment, but also like put these applications into production.</p><p><strong>Maggie </strong>32:17</p><p>And then what is the state of compute hardware that's available on the high side for, I guess, both storing this data and these databases as well as actually running these models.</p><p><strong>Brian </strong>32:32</p><p>It really depends. So there's been there continues to be investments in GPUs, but the there's a big but, and the but is, you have federated networks, right? And so some that may be available to the Navy or might be available to Air Force or to NSA, doesn't necessarily mean it's available for your application. That's for an Army PEO, right? And so the total number is growing, but it's incredibly federated.</p><p>But then also comes back to an earlier point they were talking about, which is, like, where's the budget for that coming from? Right? And so is there a CIO shop that's creating budget and allocating it? You know, there, I hear lots of stories about different units or wings that want to go and use it, but then they need to have a minimum commit to a hyper scaler of, say, a million dollars over 12 months for some fixed kind of set of nodes. And so that that's a real friction point, right? And the ability to adopt that doesn't necessarily exist in the commercial sector, just because GPUs are more plentiful, right? And the demands a lot more elastic, or supply is more elastic.</p><p><strong>Maggie </strong>33:52</p><p>To what extent have you started to see the adoption of actual agents doing some amount of tool use &#8211; both within Enterprise and then within the Department of Defense?</p><p><strong>Brian </strong>34:06</p><p>Enterprise: the last like six months, it's exploded. And so particularly the last 90 days it's absolutely exploded. And so we've seen barriers fall with agent experimentation. We've seen frameworks mature, and then really interesting paradigms, like MCP right begin to proliferate that will make it easier for agent to agent communications and these multi agent systems are mature.</p><p>In the defense space, we're seeing desire. We're seeing some experimentation, but it is incredibly constrained compared to what we're seeing in the in the first space, there's a lot of advertising going on, and there's a lot a lot of fostering and positioning going on, but the ability to you. To train and deploy models is mainly being done in sandboxes right now, but they're really interesting use cases, and they hold a lot of promise.</p><p><strong>Maggie </strong>35:08</p><p>What do you think will be the first couple use cases of agents, in particular, for the Department of Defense?</p><p><strong>Brian </strong>35:15</p><p>I think a lot of them are going to be extremely boring things right now, right? And so I don't think that's a bad thing at all, because there's a lot of boring bureaucracy that's required in order to enable that giant war fighting machine that is the US military and so things like what Advana was that's been focused on right, passing the audit around, workforce management, things like that. They're just perfect right.</p><p>For agents, right now, the sexier things that will probably get the wired articles are probably going to be around rapid mission planning, right. Closing the OODA loop, faster agents. There was a really interesting blog that was written back in, back in February by Nikita, the CEO of Neon that just got acquired by Databricks, and it showed the number of neon databases that were being created each day by agents versus by humans. And you saw this enormous J curve where you saw like 10s of 1000s of these databases being created by agents every day, and that that just accelerating. You see numbers of like lines of code written by with cursor every day. You see that same sort of J curve that's going to enable like if, that's if they do make these tools available and they resource them, you're going to see the pace of innovation around kind of the point into the spear, really, really accelerate. It's going to take data fusion. It's going to take the infrastructure. But it's going to be really, really exciting to see what the folks that are close to these missions are able to come up with these tools in their hands.</p><p><strong>Maggie </strong>36:53</p><p>So it's going to start with just filling out paperwork and whatnot, and then slowly move closer and closer to the battlefield.</p><p><strong>Brian </strong>37:00</p><p>Absolutely.</p><p><strong>Maggie </strong>37:02</p><p>Brian, I'm curious. You've been doing this for a long time. What does it take to build trust with the Department of Defense to get them to trust this technology? You know, particularly if we want to start deploying AI agents that have the ability to use tools that might actually change something in the world?</p><p><strong>Brian </strong>37:21</p><p>I think that, like a lot of the senior leaders, it's not that they're distrustful necessarily today, it's that what they need to be able to buy is a capability, and that the Department's not really well positioned, and the capital markets aren't really well positioned either to deliver capabilities for them. And so like, let me talk about that for a second. So with contrasting it with, like, the commercial sector we talked about earlier, they'll have some $50, $100, $500 million a year commit with a hyper scaler or multi cloud strategy. They'll allocate resources across dozens of teams. Those teams will effectively build capabilities, right? And they can experiment with them rapidly, and then they can scale those that are successful. In contrast, in the in the defense space, you have that sort of with SBIRs a little bit, and something with, like with these other various kind of funding lines, but none of them are large enough, right, in terms of, like, a critical mass of funding in order to actually demonstrate the capability. And it takes so long over the period of performance of these things to deliver it, that what it does is it incentivizes capital markets to fund like defense tech companies that will package everything up into a bespoke capability, right, that they could then go sell. I think Vannevar did a great job about this. Vannevar&#8217;s done this. Companies like Legion, others are doing this as well. And so I think that it's really around packaging up a really tight capability for them to go and fund. That's something that that fits within, like the funding paradigm in DoD, but that isn't really a natural motion in the commercial sector.</p><p><strong>Maggie </strong>39:06</p><p>Where have you seen glimmers of success within the US government in terms of AI adoption? Are there any groups or initiatives within DoD that are particularly forward leaning?</p><p><strong>Brian </strong>39:16</p><p>I think most of it these days, at least from where we sit, which is like primarily around natural language data: Army, Air Force, and Special Operations. We're not seeing as much yet from Navy, from Space Force, from the Marine Corps. Within Army, we see a lot of experimentation going on around Linchpin on C5ISR, around various initiatives there in order to data fusion, that's kind of filter on Titan.</p><p>On the Air Force side, you have so much technical talent spread across ACC, AMC, AFTC, Air Force Research Labs that what you've ended up with is like a huge amount of experimentation. And from that, they've sort of begun to develop really tight theses around where they think they're going to be able to accrue value and go out and start getting tools that they want.</p><p>And then with SOCOM, really around the teams at Fort Bragg around Army Special Operations Center and their AI division. They've been a leader from the beginning on this, at least, to partner with us. And they've, I think, been a leader across the Department of Defense. And Frazier in particular demonstrated incredible technical depth, but also that initiative that you really see and expect with from SOCOM to move quickly and to and to mature quickly and so those are really the kind of three areas that we're seeing the most pull from these days.</p><p><strong>Maggie </strong>41:00</p><p>What do you think has made those organizations successful, and what can the rest of the DoD and US government learn or take from those initiatives?</p><p><strong>Brian </strong>41:10</p><p>I think on the SOCOM side, it's you resource, you empower really hard chargers, and you set aggressive goals, right? What they had there, though, was they had compute, they had network, they had data, and they had human capital. And those are, like the four things right that we were talking about earlier that are needed to be successful in the commercial space, and General Braga and and then others, later on, really made it a priority to resource that. And so that created the set the conditions for success.</p><p>You've had that to a lesser extent with Air Force, but they've been able, like the enterprising Airmen, have been able to piece that together in really interesting ways across different parts of it.</p><p>And then on Army, you see a really a strong mission set there around AI, and really aggressive goals around that, though they have slightly different mission sets and they're buying it and working in different ways. And so I would say the combination of resources at SOCOM deep talent and Air Force, and then you know, mission on the Army side have, at least from where we're sitting, accelerated those three organizations.</p><p><strong>Akhil </strong>42:33</p><p>Hey, Brian, we all know that at some bottom up level, folks are just going to figure it out, right? Airmen, sailors, soldiers, Marines, Coast Guardsmen, obviously, Space Force too. Your critiques with regards to the scalability and the importance of a top down strategy is still sticking with me. Folks are just figuring out how to get data, compute talent right at the lower levels. And so I wanted to return to this whole idea you were talking about. And specifically, could you talk about one or two key policy changes the DoD needs to make that would better support the scalability of some of these bottom up initiatives?</p><p><strong>Brian </strong>43:10</p><p>Look, I think that there's been way too much discussion (that's my hot take) on contract vehicles over the last couple of years, and not nearly enough discussion around those factors that you just talked about. So you have these huge companies that are you know, have been intensely lobbying for reforms on acquisition. That's fine. Let's do it. Let's keep let's keep making progress there. That's not going to that's not going to be sufficient though, to take you to where you need to go.</p><p>I firmly believe that an organization like CDAO or the CDAOs, for each of these respective organizations, my preference would be centralized, because I'm selfish and I'm in the commercial sector, and I could have one person to sell to who could be responsible for the infrastructure, for the network access, right, for the compute availability, for the model availability, and getting the data into those architectures, as well that mission needs to be solved. And so if it's done at the command level, at the service level, fine, but I think that mission set for CDAO is a valid one despite execution flaws that we've seen over the last few years.</p><p><strong>Akhil </strong>44:30</p><p>Yep, that totally makes sense, Brian, and to be fair, correct me if I'm wrong, that's not necessarily selfish of you. I think what we're looking also is what is in the interest of the users and the customers trying to build applications, and what I believe is should be the case is they should be spending less time trying to connect things and more time trying to figure out what is the right application and what is the right type of usage with the either compute constraints, whether they're operating on edge or cloud or wherever that they should be focused on, unless I have that wrong.</p><p><strong>Brian </strong>45:00</p><p>Yeah, absolutely right, absolutely right. I think that, like any day that's spent trying to get a hold of data or trying to marshal compute resources is a day wasted that could have been spent on mission, right? And so that's just friction that needs to be eliminated</p><p><strong>Maggie </strong>45:16</p><p>Brian, let's say tomorrow Congress decides to appropriate $10 billion or $50 billion or something to CDAO, they call you in to give them advice on how to spend that money. How would you advise them to spend a new large budget?</p><p><strong>Brian </strong>45:36</p><p>Have more than one or two authorizing officials for ATOs &#8211; so that's number one. My advice always is to go hunt for bottlenecks, right? God bless them. But they have like, two people there that can actually like, sign ATOs. Go solve that. Okay, one, two, go make sure that there's GPU availability across all the regions and all the federated networks. That's two. Three, provide an easy way to transact. Tradewinds is not the easy way to transact. Allow marketplaces, consumption based contract vehicles make it as similar as possible to the private sector, and three go make this stuff available for almost nothing to the folks at the ground level that are closest to the mission problems, right, who are in the best possible position to drive that innovation and then scale the hell out of that as quickly as you can right?</p><p><strong>Akhil </strong>46:39</p><p>I had one follow up question on the agent piece, you mentioned some of the bottlenecks, whether it's MCP or something else. You know, there's some commanders out there that are really excited about that agent to agent future. What to you is the one or two bottlenecks you talked about wanting to drive down bottlenecks. What's the one bottleneck, maybe specific to agentic maturation in government that you think needs to happen and needs to happen and needs to happen fast, or something that the commercial space is already pretty far ahead on?</p><p><strong>Brian </strong>47:06</p><p>Look, I think MCP client servers are proliferated over the last over the last several months, and that's been great. I think that those by themselves are not enough for these multi agent systems to be successful, I think that it's really well defined and capable APIs coupled with MCPs or other emerging frameworks that enable multi agent systems. I think that that defining those protocols for how these systems are going to talk to each other, this next generation technology is really going to be the linchpin to unlocking, unlocking the efficacy of multi agent systems, and especially multi agent systems coupled with these multi step deep reasoning models.</p><p><strong>Maggie </strong>47:51</p><p>I was going to ask you know, one word you keep saying, Brian is experimentation. DoD is really good at experimentation. What does it take to actually move beyond experimentation and actually bring this technology to the end user?</p><p><strong>Brian </strong>48:08</p><p>Yeah, I think this comes back to familiar challenges, right? But if you like, let's take all the GIDE challenges, right? The Global Information Dominant Exercises that were done, you're able to find sandbox network environments, you're able to get sandbox data. You're able to have it for a finite amount of time, and you didn't have to worry about changing people's job titles or re upskilling folks that had been doing manual processes. And so if you want to actually scale these things, right? You need it to be on real networks. So you solve ATO problems. You need to have real data. You need to be able to have someone that's sufficiently invested in this that they're willing to upskill their workforce.</p><p>And so in the in the private sector, we've seen really a few phases. We saw a proliferation of proofs of concepts with Gen AI, then a consolidation of those that they were going to go scale. And then everyone thought, Okay, the next phase is actually production wrong? There's actually like this third step here in a four step act that folks didn't really anticipate, which was they needed to go and rethink all their people ops. So what are the job criteria is, what are you actually doing? What are the, what are the processes inside these organizations so that they're actually well positioned to capitalize on these tooling, otherwise you just have a cool app that sits idle and isn't effectively utilized, that requires top down cover, top down pressure, right? And top down resources, if you're going to actually make that happen. And so that's actually a really critical step here is you got to have the data, you got the network, you got to have the models. But you also like these. These are actually humans that are using this. They're using it to accomplish a task, right? And you need to think, do? Deeply at an organizational level with you know how you're actually shaping those job functions and those processes so that you can actually capitalize on that, on these tools.</p><p><strong>Maggie </strong>50:11</p><p>What are some of the most common mistakes that you've seen startups make when trying to build and deploy AI for the Department of Defense?</p><p><strong>Brian </strong>50:19</p><p>The most common mistake is to get sucked into abandoning dual use technology. And so it's really, really easy to land some initial contracts and to end up, as you know, a software vendor that has loose, if any, product market fit in the commercial space, but great product market fit within one particular part of one service. Now, there are companies that have done that and done it incredibly well, but they're, I could probably count them on one hand. Like Vannevar is the most recent, right? They've crushed. And so, like a tip of the hat to Vannevar for doing that. That is very, very difficult to replicate for most others. And so I would like the rule of thumb that I tell a lot of the other CEOs that I talked to about doing business in this is like, if you can maintain a single, unified code base for your commercial clients and your and your public sector clients, then you're then you're on the right track. Now, if you're forking it and having to Frankenstein things, then that you should really take pause and think about the scalability, like when the speed and breadth of customers in the in the public sector that you can actually go sell to, versus the good personal space, because public sector is a great place to land. It's a great place to steer a mature business. My opinion, it's an absolutely horrible space to try and scale a venture backed startup.</p><p><strong>Maggie </strong>52:02</p><p>What would you say is your most controversial hot take about AI and or AI infrastructure?</p><p><strong>Brian </strong>52:09</p><p>I'm not sure if I have hot takes here, other than I would put myself in the extreme optimist camp around agents and about where, how quickly agents are going to be useful, and so, like, while I'm optimistic about the tech, I'm also worried about what that portends in terms of competition. And I think we should utilize it to drive innovation and drive productivity increases as fast as we can. You could bet that the Chinese are going to be using that as well for offensive purposes. And so I think that this warming that we've had between DC and the Pentagon in particular, and then Silicon Valley like I hope that continues. I hope that deepens, and I hope that that accelerates, because we're going to need to figure this out faster than our adversaries on how to utilize LLMs, coupled with agents right in order to advance mission as fast as we possibly can.</p><p><strong>Akhil </strong>53:17</p><p>I love that optimism Brian and where the things are headed from an agent to agent collaboration and the AI front, I know you have some pointed critiques, but I know they come from a place where we want to make the ecosystem better and we want to advance against the global competitors. Speaking of global competitors, Brian, where are we vis a vis the PRC and others? Obviously, plenty of news around there about R1, DeepSeek, et cetera, but you're seeing it also, not just from the model stack, but from the infrastructure stack.</p><p><strong>Brian </strong>53:47</p><p>Look, I think that there was a broad consensus in 2023 and 2024 that we had a fair lead here in the US, that sanctions on GPU availability were effective, and that we were in a pretty good spot. I think that we have a very different view of that here in Q2 2025, now, and that, from a hardware standpoint, the Chinese have effectively circumvented aloneness of the sanctions and are actually building domestically or cultivating domestically, incredibly advanced GPU manufacturing capability.</p><p>Second from a software standpoint and model training standpoint, the only thing that we have over the Chinese at this point is momentum, right? It's the speed of innovation. And so I think that it's absolutely critical that we support our labs, or that we support Open AI, that we support Anthropic, Google, Meta and others, and continue to innovate as rapidly as they have. I think that that's the only real advantage that we're going to have. That's going to be potentially durable over time is speed of innovation. And I think that we're focused on the right things right now, which is going to be electricity, really, it's going to be power generation, right as well as making sure that we don't stifle innovation through excessive regulation of these of this industry.</p><p><strong>Akhil </strong>55:20</p><p>Awesome. Thanks, Brian. Brian, we're coming here to the end, and I want to focus on you and your company a little bit as we close out. Maybe the first ask, what was your biggest surprise, going back to when this was on the drawing board, napkin table, in terms of building unstructured since then and to now?</p><p><strong>Brian </strong>55:38</p><p>Yeah, I'd say one I'd like to think that I anticipated, but I didn't anticipate ChatGPT launching six months in. So here we were fall of 2022, us just groveling for GitHub stars, and then ChatGPT drops that November, and demand explodes, right? And so from a timing standpoint, it was we were really fortuitous. I'd say on the flip side of that, it was just it was moving so fast during that period of time, like every week it seemed like the technology was changing, and what hasn't really changed, the foundational sort of pieces that you need to normalize all the data, get it in a consistent format. You need to index it in a way that's discoverable by the models. And that there's a lot of art to getting these, these architectures, to work even now in 2025.</p><p><strong>Akhil </strong>56:37</p><p>Yeah, Thanks, Brian. It's been awesome to see the journey you've been on where is unstructured going from here? What are you looking to do in the next couple months? Who you're trying to bring on in terms of awesome folks? Would love to hear a little bit about where that's headed.</p><p><strong>Brian </strong>56:50</p><p>I'd say like, especially within the last quarter, quarter and a half, the market has really matured, and so we're receiving a lot of inbound now from Fortune 100, Fortune 500 companies that now are looking at their data, Gen AI data strategy, and looking to normalize. And so we have call it like a couple dozen really challenging and ambitious deployments that we're working on as we speak, that I'm really excited about. And then we're doing a similar thing within the DoD, across the DoD. And so from you know, a talent standpoint, a lot of this comes down to really phenomenal engineers, right, that understand the customers, that are incredibly capable in their respective kind of fields of expertise, and that can move at the pace that innovation is happening today, and so we're looking, you know we're gonna, we expect it to grow significantly over the back half of the this year, and are really excited for what the future pretends. Awesome.</p><p><strong>Akhil </strong>57:52</p><p>Brian, thanks so much for being with us today. Always great to get your insights and have some conversations and see you be able to do some awesome stuff again, both in the commercial space and in the government space, and we look forward to continuing to see that grow.</p>]]></content:encoded></item></channel></rss>