Apr 2, 2025 · 52m · a16z

Can the Military Move at Startup Speed? How the Army and Navy Are Rebuilding

Alex Miller · 23m spoken Justin Fanelli · 21m spoken Layla Sturdy · 3m spoken Leila Hay · 1s spoken
0:00 / 0:00
▶ Watch on YouTube →

gold bands on the timeline = statements, start to end. Hover to read, click to jump. CC turns on captions

In this episode of the a16z American Dynamism podcast, host Layla Sturdy interviews U.S. Army CTO Alex Miller and U.S. Navy CTO Justin Fanelli on reforming defense acquisition, breaking down legacy bureaucracy, and rapidly integrating commercial technologies to maintain military technological overmatch.

How this conversation actually went

Every chapter scored 0–10 on four independent dynamics. Hover any point for the reasoning behind the score. How this is scored →

The host as informed peer 3.6 Guest teaching 4.4 Guest disagreement 0.8 The host pushing back 0.2
05100:0015:0030:0045:000:38–3:45 · The host as informed peer 2/10 Disclaimer and Title Sequence Layla asks standard introductory questions about background and roles. The guests explain how DoD CTO roles function relative to private sector positions.3:45–8:07 · The host as informed peer 4/10 Startup Pathways and Demystifying DoD Bureaucracy Layla demonstrates knowledge by citing her co-authored article on selling into the DoD and mentioning organizations like DIU, AFWERX, and SBIR/STTR pathways. Alex explains the historical origin of federal acquisition bureaucracy.8:07–11:02 · The host as informed peer 5/10 Program Executive Offices and Crossing the Valley of Death Layla accurately expands the APFIT acronym on the fly, earning praise from Justin. Justin explains how PEOs operate and how Navy is shifting to portfolio management.11:02–15:44 · The host as informed peer 2/10 Reforming Requirements and Streamlining Acquisition Alex forcefully criticizes internal DoD bureaucracy, calling PEOs and complex requirements workarounds to a broken system. The host listens as the guests discuss counter-UAS requirements.15:44–20:24 · The host as informed peer 4/10 Scaling Real-World Field Wins and Horizontal Integration Layla synthesizes the conflict between rapid software/AI development cycles and rigid multi-year defense procurement timelines. Justin shares real-world field examples such as adapting Navy electronic warfare kit for Army Humvees.20:24–27:32 · The host as informed peer 5/10 Defining Overmatch and the Modular Lego-Block Architecture Layla reframes the guest's overmatch concept into venture capital logic, comparing defense capability switching costs to VC requirements for 100x outcome thresholds. Alex details legacy software architecture issues in Army mission command.27:32–37:53 · The host as informed peer 4/10 Shared Services, Historical Budget Origins, and Risk Culture Layla summarizes horizontal integration across 75 PEOs. Alex provides a detailed history lesson on how the 1968 Minuteman III budget allocation created today's line-item budgeting constraints.37:53–43:38 · The host as informed peer 4/10 Realigning Risk Calculus and Startup Success Models Layla highlights the cultural gap between venture capital risk-seeking and Pentagon risk-aversion. Alex explains how defense acquisition measures risk as prevention of waste/fraud/abuse rather than lost time.43:38–47:47 · The host as informed peer 2/10 Look Ahead: Next-Gen C2, Drone Defense, and Autonomy Consortiums Layla prompts the guests for future outlooks. Alex outlines concrete Army initiatives including next-gen command and control, Project Flytrap drone defense, and autonomy consortiums.0:38–3:45 · Guest teaching 3/10 Disclaimer and Title Sequence Layla asks standard introductory questions about background and roles. The guests explain how DoD CTO roles function relative to private sector positions.3:45–8:07 · Guest teaching 4/10 Startup Pathways and Demystifying DoD Bureaucracy Layla demonstrates knowledge by citing her co-authored article on selling into the DoD and mentioning organizations like DIU, AFWERX, and SBIR/STTR pathways. Alex explains the historical origin of federal acquisition bureaucracy.8:07–11:02 · Guest teaching 4/10 Program Executive Offices and Crossing the Valley of Death Layla accurately expands the APFIT acronym on the fly, earning praise from Justin. Justin explains how PEOs operate and how Navy is shifting to portfolio management.11:02–15:44 · Guest teaching 5/10 Reforming Requirements and Streamlining Acquisition Alex forcefully criticizes internal DoD bureaucracy, calling PEOs and complex requirements workarounds to a broken system. The host listens as the guests discuss counter-UAS requirements.15:44–20:24 · Guest teaching 4/10 Scaling Real-World Field Wins and Horizontal Integration Layla synthesizes the conflict between rapid software/AI development cycles and rigid multi-year defense procurement timelines. Justin shares real-world field examples such as adapting Navy electronic warfare kit for Army Humvees.20:24–27:32 · Guest teaching 4/10 Defining Overmatch and the Modular Lego-Block Architecture Layla reframes the guest's overmatch concept into venture capital logic, comparing defense capability switching costs to VC requirements for 100x outcome thresholds. Alex details legacy software architecture issues in Army mission command.27:32–37:53 · Guest teaching 6/10 Shared Services, Historical Budget Origins, and Risk Culture Layla summarizes horizontal integration across 75 PEOs. Alex provides a detailed history lesson on how the 1968 Minuteman III budget allocation created today's line-item budgeting constraints.37:53–43:38 · Guest teaching 5/10 Realigning Risk Calculus and Startup Success Models Layla highlights the cultural gap between venture capital risk-seeking and Pentagon risk-aversion. Alex explains how defense acquisition measures risk as prevention of waste/fraud/abuse rather than lost time.43:38–47:47 · Guest teaching 5/10 Look Ahead: Next-Gen C2, Drone Defense, and Autonomy Consortiums Layla prompts the guests for future outlooks. Alex outlines concrete Army initiatives including next-gen command and control, Project Flytrap drone defense, and autonomy consortiums.0:38–3:45 · Guest disagreement 0/10 Disclaimer and Title Sequence Layla asks standard introductory questions about background and roles. The guests explain how DoD CTO roles function relative to private sector positions.3:45–8:07 · Guest disagreement 1/10 Startup Pathways and Demystifying DoD Bureaucracy Layla demonstrates knowledge by citing her co-authored article on selling into the DoD and mentioning organizations like DIU, AFWERX, and SBIR/STTR pathways. Alex explains the historical origin of federal acquisition bureaucracy.8:07–11:02 · Guest disagreement 0/10 Program Executive Offices and Crossing the Valley of Death Layla accurately expands the APFIT acronym on the fly, earning praise from Justin. Justin explains how PEOs operate and how Navy is shifting to portfolio management.11:02–15:44 · Guest disagreement 2/10 Reforming Requirements and Streamlining Acquisition Alex forcefully criticizes internal DoD bureaucracy, calling PEOs and complex requirements workarounds to a broken system. The host listens as the guests discuss counter-UAS requirements.15:44–20:24 · Guest disagreement 1/10 Scaling Real-World Field Wins and Horizontal Integration Layla synthesizes the conflict between rapid software/AI development cycles and rigid multi-year defense procurement timelines. Justin shares real-world field examples such as adapting Navy electronic warfare kit for Army Humvees.20:24–27:32 · Guest disagreement 1/10 Defining Overmatch and the Modular Lego-Block Architecture Layla reframes the guest's overmatch concept into venture capital logic, comparing defense capability switching costs to VC requirements for 100x outcome thresholds. Alex details legacy software architecture issues in Army mission command.27:32–37:53 · Guest disagreement 1/10 Shared Services, Historical Budget Origins, and Risk Culture Layla summarizes horizontal integration across 75 PEOs. Alex provides a detailed history lesson on how the 1968 Minuteman III budget allocation created today's line-item budgeting constraints.37:53–43:38 · Guest disagreement 1/10 Realigning Risk Calculus and Startup Success Models Layla highlights the cultural gap between venture capital risk-seeking and Pentagon risk-aversion. Alex explains how defense acquisition measures risk as prevention of waste/fraud/abuse rather than lost time.43:38–47:47 · Guest disagreement 0/10 Look Ahead: Next-Gen C2, Drone Defense, and Autonomy Consortiums Layla prompts the guests for future outlooks. Alex outlines concrete Army initiatives including next-gen command and control, Project Flytrap drone defense, and autonomy consortiums.0:38–3:45 · The host pushing back 0/10 Disclaimer and Title Sequence Layla asks standard introductory questions about background and roles. The guests explain how DoD CTO roles function relative to private sector positions.3:45–8:07 · The host pushing back 0/10 Startup Pathways and Demystifying DoD Bureaucracy Layla demonstrates knowledge by citing her co-authored article on selling into the DoD and mentioning organizations like DIU, AFWERX, and SBIR/STTR pathways. Alex explains the historical origin of federal acquisition bureaucracy.8:07–11:02 · The host pushing back 0/10 Program Executive Offices and Crossing the Valley of Death Layla accurately expands the APFIT acronym on the fly, earning praise from Justin. Justin explains how PEOs operate and how Navy is shifting to portfolio management.11:02–15:44 · The host pushing back 0/10 Reforming Requirements and Streamlining Acquisition Alex forcefully criticizes internal DoD bureaucracy, calling PEOs and complex requirements workarounds to a broken system. The host listens as the guests discuss counter-UAS requirements.15:44–20:24 · The host pushing back 0/10 Scaling Real-World Field Wins and Horizontal Integration Layla synthesizes the conflict between rapid software/AI development cycles and rigid multi-year defense procurement timelines. Justin shares real-world field examples such as adapting Navy electronic warfare kit for Army Humvees.20:24–27:32 · The host pushing back 1/10 Defining Overmatch and the Modular Lego-Block Architecture Layla reframes the guest's overmatch concept into venture capital logic, comparing defense capability switching costs to VC requirements for 100x outcome thresholds. Alex details legacy software architecture issues in Army mission command.27:32–37:53 · The host pushing back 0/10 Shared Services, Historical Budget Origins, and Risk Culture Layla summarizes horizontal integration across 75 PEOs. Alex provides a detailed history lesson on how the 1968 Minuteman III budget allocation created today's line-item budgeting constraints.37:53–43:38 · The host pushing back 1/10 Realigning Risk Calculus and Startup Success Models Layla highlights the cultural gap between venture capital risk-seeking and Pentagon risk-aversion. Alex explains how defense acquisition measures risk as prevention of waste/fraud/abuse rather than lost time.43:38–47:47 · The host pushing back 0/10 Look Ahead: Next-Gen C2, Drone Defense, and Autonomy Consortiums Layla prompts the guests for future outlooks. Alex outlines concrete Army initiatives including next-gen command and control, Project Flytrap drone defense, and autonomy consortiums.

speaking balance: gold is the host, purple is the guest (3 minute bins)

0:00 · the host 0% · guest 100%0:00 · the host 0% · guest 100%3:00 · the host 0% · guest 100%3:00 · the host 0% · guest 100%6:00 · the host 0% · guest 100%6:00 · the host 0% · guest 100%9:00 · the host 0% · guest 100%9:00 · the host 0% · guest 100%12:00 · the host 0% · guest 100%12:00 · the host 0% · guest 100%15:00 · the host 0% · guest 100%15:00 · the host 0% · guest 100%18:00 · the host 0% · guest 100%18:00 · the host 0% · guest 100%21:00 · the host 0% · guest 100%21:00 · the host 0% · guest 100%24:00 · the host 0% · guest 100%24:00 · the host 0% · guest 100%27:00 · the host 0% · guest 100%27:00 · the host 0% · guest 100%30:00 · the host 0% · guest 100%30:00 · the host 0% · guest 100%33:00 · the host 0% · guest 100%33:00 · the host 0% · guest 100%36:00 · the host 0% · guest 100%36:00 · the host 0% · guest 100%39:00 · the host 0% · guest 100%39:00 · the host 0% · guest 100%42:00 · the host 0% · guest 100%42:00 · the host 0% · guest 100%45:00 · the host 0% · guest 100%45:00 · the host 0% · guest 100%48:00 · the host 0% · guest 100%48:00 · the host 0% · guest 100%51:00 · the host 0% · guest 100%51:00 · the host 0% · guest 100%
Sharpest disagreement ▶ 11:03 Alex attacks PEO bureaucracy

Alex forcefully rejects standard defense procurement structures, calling PEOs workarounds to a fundamentally broken system and declaring his intention to blow them up.

Hardest push from the host ▶ 23:48 Layla reframes overmatch using VC metrics

Layla pushes back on standard defense terminology by reframing overmatch and switching costs directly into venture capital investment math and 100x return expectations.

Biggest teaching moment ▶ 32:46 Alex explains 1968 budget origin

Alex educates the host on the exact historical origin of rigid defense line-item budgeting, tracing it back to the 1968 Minuteman III program.

The host holds their own ▶ 10:29 Layla expands APFIT acronym

Layla instantly demonstrates acquisition knowledge by accurately expanding the APFIT acronym in real time, earning direct validation from guest Justin Fanelli.

the scores for every segment, with the reasoning behind each
ChapterTopicThe host as informed peerGuest teachingGuest disagreementThe host pushing backWhy
Disclaimer and Title Sequence 2300 Layla asks standard introductory questions about background and roles. The guests explain how DoD CTO roles function relative to private sector positions.
Startup Pathways and Demystifying DoD Bureaucracy 4410 Layla demonstrates knowledge by citing her co-authored article on selling into the DoD and mentioning organizations like DIU, AFWERX, and SBIR/STTR pathways. Alex explains the historical origin of federal acquisition bureaucracy.
Program Executive Offices and Crossing the Valley of Death 5400 Layla accurately expands the APFIT acronym on the fly, earning praise from Justin. Justin explains how PEOs operate and how Navy is shifting to portfolio management.
Reforming Requirements and Streamlining Acquisition 2520 Alex forcefully criticizes internal DoD bureaucracy, calling PEOs and complex requirements workarounds to a broken system. The host listens as the guests discuss counter-UAS requirements.
Scaling Real-World Field Wins and Horizontal Integration 4410 Layla synthesizes the conflict between rapid software/AI development cycles and rigid multi-year defense procurement timelines. Justin shares real-world field examples such as adapting Navy electronic warfare kit for Army Humvees.
Defining Overmatch and the Modular Lego-Block Architecture 5411 Layla reframes the guest's overmatch concept into venture capital logic, comparing defense capability switching costs to VC requirements for 100x outcome thresholds. Alex details legacy software architecture issues in Army mission command.
Shared Services, Historical Budget Origins, and Risk Culture 4610 Layla summarizes horizontal integration across 75 PEOs. Alex provides a detailed history lesson on how the 1968 Minuteman III budget allocation created today's line-item budgeting constraints.
Realigning Risk Calculus and Startup Success Models 4511 Layla highlights the cultural gap between venture capital risk-seeking and Pentagon risk-aversion. Alex explains how defense acquisition measures risk as prevention of waste/fraud/abuse rather than lost time.
Look Ahead: Next-Gen C2, Drone Defense, and Autonomy Consortiums 2500 Layla prompts the guests for future outlooks. Alex outlines concrete Army initiatives including next-gen command and control, Project Flytrap drone defense, and autonomy consortiums.

Statements from this episode (31)

Opinion
Army CTO: 60 Years of Tech Rules Implemented by Risk Minimalists
“Most companies don't have 60 years of policy and rules that were written generally by enthusiasts and visionaries, but implemented by minimalists. And what I mean by that is risk minimalists.”
Alex Miller Apr 2, 2025 ▶ 1:44
Assertion Supported
Fanelli: U.S. government created CTO roles 30 years after private sector
“The CTO position within government came 30 years after it did private sector, right? And even later than that, after defense.”
Justin Fanelli Apr 2, 2025 ▶ 2:41
Assertion Not checkable as stated
Miller: DoD operates under legacy Cold War procurement rules
“In the sixties and seventies coming out of the cold war and all the way up to the nineties, we had all these different things, the Packard commission for how you think about buying things, the Klinger Cohen for how you do information technology, Goldwater Nich…”
Alex Miller Apr 2, 2025 ▶ 4:59
Assertion Not checkable as stated
Fanelli: Record Number of Companies Seeking National Security Contracts
“We have more companies than we've ever seen before who want to work on national security.”
Justin Fanelli Apr 2, 2025 ▶ 6:30
What-if
Fanelli: Slow DoD onboarding turns away breakthrough commercial innovators
“That translation piece has been very expensive, And so product market fit is slow, and at times we turn away people who or companies that would have brought in breakthroughs”
Justin Fanelli Apr 2, 2025 ▶ 7:13
Prediction Not checkable as stated
Navy CTO: DoD will shift more PEOs to portfolio models
“And so we've shifted PEO digital, and I believe that we'll shift even more of those program executive offices across DoD to that.”
Justin Fanelli Apr 2, 2025 ▶ 9:26
Opinion
Navy CTO: SBIR Defense Grants Are Just a Door Prize
“We have Small Business Innovative Research, but that's more of a door prize. You need to get to that operations and maintenance long tail funding.”
Justin Fanelli Apr 2, 2025 ▶ 10:21
Assertion Supported
Miller: Program Executive Offices are not mandated by federal law
“PEOs are not actually in statute anywhere. They don't exist in law. We made them up because the rule is that the sec def gets to determine what that looks like.”
Alex Miller Apr 2, 2025 ▶ 11:13
Insight
Miller: Programs of record create perverse incentives to slow innovation
“As soon as you've got that long-term budget, there's a perverse incentive to just to maintain and create inertia.”
Alex Miller Apr 2, 2025 ▶ 13:40
Assertion Not checkable as stated
Navy CTO: Navy Compressed 18-Month Acquisition Process Into Three Months
“We fast tracked an 18 month process in three months with a couple pages between C and S's capability needs statements and top level requirements.”
Justin Fanelli Apr 2, 2025 ▶ 14:23
Assertion Not publicly verifiable
Navy CTO: Navy Adapted Electronic Warfare Gear for Army in Three Months
“We had an electronic warfare solution, and we heard that the army was going to go out and do a request for proposal on something that was really similar The same long requirements document that we had. We said can you just paint this brown and throw it on a Hu…”
Justin Fanelli Apr 2, 2025 ▶ 16:52
Opinion
Miller: Army can adapt kit faster than Navy and Air Force
“The Army is the service that can do that because you can move around the edges of some of your ships. The Air Force can move around the edges of some of the aircraft. The capital assets, those are fixed. What I have the luxury in the Army is, like, we can modi…”
Alex Miller Apr 2, 2025 ▶ 18:13
Insight
Fanelli: Military advantage comes from rapid adaptation, not just tech quality
“It's not about who necessarily just has the best tech, it's how they're adapting. To that tech and using that as advantage.”
Justin Fanelli Apr 2, 2025 ▶ 19:43
Assertion Supported
Fanelli: Navy is consolidating 1,000 identity solutions into Naval Identity Service
“And so we have a thousand different identity management solutions. So we've said Naval Identity Service is the enterprise System. That service is what's moving forward.”
Justin Fanelli Apr 2, 2025 ▶ 20:41
Assertion Open · timeframe Apr 2028
Army CTO: Mission Command Enterprise Had 17 Redundant Mapping Programs
“We had 17 programs of record in this mission command enterprise, and each one did sort of similar things in the fact that each one of them had a map. Humans like pixels. We're really good at seeing pixels. They make us happy. So we looked at maps. Well, each o…”
Alex Miller Apr 2, 2025 ▶ 21:51
Opinion
Army CTO: DoD Does Not Build the Best Maps or Data Platforms
“We, the Department of Defense, are certainly not in twenty-twenty-five who is building the best maps, we're not building the best data platforms, we're not building the best API gateways, so let's not pretend it, let's just get all those pieces together and co…”
Alex Miller Apr 2, 2025 ▶ 23:12
Insight
Miller: Forcing contractors to build full tech stacks produces inferior defense software
“And that is a failure that we, as the Department of Defense, and really in anybody who's done federal acquisition, Sort of falls into the trap of where if you came up and you won a program, I expect you to deliver every part of that top to bottom, even the stu…”
Alex Miller Apr 2, 2025 ▶ 24:31
Insight
Army CTO: Military Modernization Bottlenecks Are Cultural, Not Technological
“This is not a technology problem. This is a culture and a process problem that we can apply technology to.”
Alex Miller Apr 2, 2025 ▶ 29:13
Insight
Navy CTO: Defense Startup CEOs Must Embed With Users Before Hiring Sales
“If you are a startup CEO, don't hire salespeople before you understand the ecosystem. Move to San Diego or get close, like, spend nine months near The group that you are trying to positively enable and empower to do their job 10 or a hundred times better than …”
Justin Fanelli Apr 2, 2025 ▶ 30:06
Assertion Supported
Miller: U.S. Army Receives 21% of Defense Budget with <50% Flexibility
“Now, today, the Army is only 21% of the defense budget. We are everywhere. We, the Army, are everywhere. And again, this is gonna sound a little parochial, but we're on the border. We're the Global Response Force. We're the Immediate Response Force. We're the …”
Alex Miller Apr 2, 2025 ▶ 33:49
Assertion Supported
Fanelli: Defense Innovation Unit Accounts for Under 1% of Defense Budget
“When we still talk about DIU is, like, less than one percent of the budget.”
Justin Fanelli Apr 2, 2025 ▶ 36:55
Assertion Partly supported
Fanelli: In-Q-Tel leverages $25 of private capital per federal dollar
“In-Q-Tel's ratio is 25 outside dollars for every federal dollar spent”
Justin Fanelli Apr 2, 2025 ▶ 38:13
Insight
Fanelli: Hedging against all risk fights inflation, not disruptive tech
“If your goal is to hedge against anything happening, then you're fighting against inflation as opposed to against disruptive technology.”
Justin Fanelli Apr 2, 2025 ▶ 40:00
Disclosure
Fanelli: Navy deployed mobile network startup CAPE in Guam pilot
“We put CAPE, our mobile virtual network operator company startup in Guam, and then we needed them. So like, hey, the pilot was ready for actual use.”
Justin Fanelli Apr 2, 2025 ▶ 43:01
Prediction Not checkable as stated
Fanelli: DoD Will Move Non-Traditional Tech to Production Within 12 Months
“So I'm excited about the best chance I've ever seen in the next six to 12 months to get capability that wasn't under government contract into full scale production.”
Justin Fanelli Apr 2, 2025 ▶ 44:25
Prediction Held up
Miller: Army Moving Next-Gen C2 Consortium to Program Phase This Year
“This year we are going to put the consortium for the Army's next generation command and control into its program phase.”
Alex Miller Apr 2, 2025 ▶ 44:41
Prediction Held up
Miller: Army Will Field Next-Gen C2 to a Division This Year
“So we're gonna take that next generation command and control into, you know, get that on contract and start moving forward and get that fielded to one of our divisions this year.”
Alex Miller Apr 2, 2025 ▶ 45:41
Prediction Open · timeframe Apr 2028
Miller: U.S. Army Will Form a Consortium for Vehicle Autonomy
“We are going to Put together a consortium for autonomy.”
Alex Miller Apr 2, 2025 ▶ 46:49
Insight
Miller: Military Autonomy Requires Shared Toolchains, Not Single Prime Contractors
“It's not one company, it's not Miller Corp that's gonna solve autonomy. It's how do we get the right tool chain in place from SIM all the way through VNV? And then how do we get the right actions and the right libraries? And how do we get ourselves off of this…”
Alex Miller Apr 2, 2025 ▶ 47:11
Insight
Army CTO: Defense Startups Must Not Rely Solely on DoD for Revenue
“Stop trying to use the Department of Defense as your only means of revenue. And I mean that because if you get complacent with the Department of Defense, then you are no longer actually on the quest that you were on. And it's just not, it's not good. We want t…”
Alex Miller Apr 2, 2025 ▶ 48:45
Assertion Not publicly verifiable
Fanelli: Department of Navy obtained 12 policy exceptions via data
“We've gotten 12 exceptions to policy because we brought data and said this is hurting us, and so these sub-optimizations that we've always had we can do better than that, and we will.”
Justin Fanelli Apr 2, 2025 ▶ 50:18
Made with StarZero

Turn any episode into a week of clips.

This entire site, over 1,000 episodes transcribed, diarized, checked and made playable, runs on the StarZero media pipeline. Drop in your own episode and the podcast clipper finds the moments worth sharing, cuts them, captions them, and reframes them for every feed.