The Four Words That Win DoW Deals
Most startups walk into the Pentagon with a solution nobody asked for. Peter Belk has watched it happen for decades, and he has a fix.
Until a few weeks before this conversation, Belk was the Principal Deputy Assistant Secretary of War for Readiness, and for a longer stretch, the Acting Assistant Secretary. Before that he was Deputy Director of Operations at U.S. Northern Command, Deputy Director for Strategy, Policy, Plans, and Concepts at U.S. Special Operations Command, and Director for Weapons of Mass Destruction and Terrorism Threats at the National Security Council. In short, he has spent a career inside the rooms where DoW decisions actually get made, and he has worked with Israeli defense startups along the way. When he talks about how the building thinks, it’s worth listening.
Readiness isn’t the PT test. Most people assume readiness means whether a service member passed their fitness or medical check. At the enterprise level, covering 3.1 million service members and a trillion-dollar budget, it’s something else entirely. Belk describes his old role as being “the chief risk and impact officer for the Secretary of War.” The department frames its choices across three axes: employment (where to put people and resources), development (what to buy or man, train, and equip), and design (what the force should look like as a whole). For founders, the lesson is that your product isn’t evaluated in isolation. It’s weighed against a moving picture of risk across time, space, and intersecting budgets.
Readiness is now predictive, and that’s your opening. The concept has shifted from static (“Can I do X, Y, or Z today?”) to dynamic. Belk points to DoD Instruction 3000.18, which defines what the department now calls strategic readiness, and credits work by Dr. Benjamin Hull that built on Richard Betts’s seminal “Military Readiness.” Crucially, the department is now using AI and machine learning for “predictive analytics” to model the future impact of today’s decisions. If your technology helps the department see around corners, you’re speaking its current language.
Understanding, performance, relevance, adoption. This is Belk’s core framework, and it applies from seed stage to mature business. He walks through the first two:
1. Understanding.
“Do you know the problem that your thing is seeking to resolve for the Department of War?” In military terms, this is the planning phase, and Belk calls it one of the most important. The failure mode is universal: “a lot of companies will jump in with what they think is a solution, but may or may not have varying degrees of understanding about what the problem is.” His advice is blunt: invest the time, aggressively, before you pitch. Yes, you want to sell quickly. Do the work anyway.
2. Performance.
“It’s great to understand the problem. It’s great to talk about the solution, but if the solution doesn’t work” and work flawlessly against that problem, the conversation ends. Understanding gets you in the door. Performance keeps you there.
For Israeli founders, the trap is the same one every startup falls into. You arrive with a capability you’re proud of and assume the need is obvious. Belk’s message is that the burden is on you to prove you understand the problem the way the department does, and that your tech performs against it without excuses.
The bottom line: Interest in your solution is not the same as understanding the problem. Start with the problem, prove flawless performance, and you’ve cleared the first two of four gates the DoW actually cares about.
Contact us to learn more, discuss go-to-market, or find U.S. partners.
