Defense Innovation Unit
Work With Us / Acquisition Process
Explains DIU's Commercial Solutions Opening, prototype Other Transactions, evaluation, and transition pathways.
How proven capability actually crosses from a working prototype into a program of record, funded production, and sustainment — and why so many technologies die in the gap.
A successful prototype is not a capability. Between a proven demonstrator and a warfighter holding a fielded system there is a gauntlet of statutes, contract vehicles, budget lines, program offices, primes, testing regimes, and manufacturing steps. Most technologies die there.
That gauntlet exists for good reasons — cost, quality, security, sustainability, industrial base — but it moves on a rhythm that adversaries and battlefield adaptation do not respect. The result is what people in the defense-innovation community call the Valley of Death: the gap where promising prototypes lose the money, the champion, or the pathway they need to survive.
A U.S. defense reader — whether program office, prime, or investor — should care because the same operational lessons that produced Ukraine's rapid drone and electronic warfare adaptation are being absorbed by adversary defense industrial bases in real time. If a mature allied capability is stranded on the wrong side of the transition gauntlet, it is not an inert asset; it is capability that adversaries can copy, counter, or acquire before U.S. and allied forces can field it. Transition discipline is a national-security question, not an administrative one.
Jump to: Deep Dive · What This Means for Helicon · Sources · Videos
This section explains the actual mechanisms — statutes, program offices, contract vehicles, primes, readiness levels, and low-rate production — that either move a capability forward or leave it in the Valley of Death. Terms in bold are defined in the Field Guide Glossary.
The Department of Defense does not have one acquisition process. Since 2020 the Adaptive Acquisition Framework has organized six official pathways, each tuned to a different kind of capability and urgency:
A capability's transition path depends on which pathway it enters. A drone-defeat system may enter through MTA rapid fielding; an autonomy stack may enter through the software pathway; an urgent counter-UAS capability may enter through UCA. Choosing the wrong pathway wastes years.
The Small Business Innovation Research (SBIR) and Small Business Technology Transfer (STTR) programs are how most defense-technology small businesses first enter the DoD. Both programs operate in phases:
Phase III is misunderstood. It is not a separate funding round from the SBIR program office — it is an authority that any federal agency or prime contractor can use to place production work with a company that has already competed at Phase I or II. Companies that miss this are leaving the most valuable part of the SBIR program unused.
Codified at 10 U.S.C. § 4022, an Other Transaction Authority lets DoD components enter prototype agreements outside the Federal Acquisition Regulation, and — critically — award a follow-on production contract to a successful prototype without re-competition. OTAs are the mechanism behind most rapid commercial-technology adoption at DIU, AFWERX, and the service innovation offices.
Two prerequisites matter: the prototype must actually be successful under the terms of the agreement, and a service partner must be lined up to fund the production. An OTA is not a grant; it is a milestone-based contract with a defined exit ramp into production.
Several DoD organizations exist specifically to move commercial and small-business technology into fielded use faster than the traditional acquisition system:
Below the innovation-office level sits the actual buying organization: the Program Executive Office (PEO). A PEO owns a portfolio of programs — for example, PEO Ground Combat Systems, PEO Aviation, PEO Missiles and Space — and its program managers are the people who ultimately place capability on a warfighter's belt or platform.
Primes matter because most capability is delivered into a fielded system through a prime integrator. A capability that cannot be integrated into a prime's platform, or that lacks a champion inside a prime's business development team, has a much harder path to production. Transition-ready capabilities enter with prime relationships already established.
The DoD uses two readiness scales to describe how mature a technology is:
A capability with a strong TRL and a weak MRL will fail at production. That is a Helicon-specific concern: allied battlefield-proven capability may be at TRL 8 or 9, but if the manufacturing pathway is not trusted or scalable, the capability cannot cross into U.S. and allied production. TRL and MRL must advance together.
Before full-rate production, most major systems enter Low-Rate Initial Production: a limited manufacturing run that demonstrates production capacity, validates the manufacturing process, generates units for operational test and evaluation, and de-risks the leap to full-rate production. LRIP is where MRL problems surface as real cost, schedule, and yield issues.
The Valley of Death is the gap between a successful prototype and funded production at scale. In the defense context, it is not primarily about product-market fit — a demonstrated prototype has, by definition, shown promise. It is about the alignment of four things that rarely arrive together on the timescale that matters:
When any one of these is missing, promising capability dies. Companies exhaust their capital during the year-and-a-half or longer wait between prototype success and production award. Founders leave. Investors move on. The technology is either shelved, sold abroad, or absorbed into an adversary's ecosystem. This is a national-security problem, not a commercial one.
Helicon Defense exists because the transition gauntlet is not fair to allied technologies that arrive fully validated on a battlefield but need protected sequencing, trusted manufacturing, and disciplined integration into U.S. acquisition to be fielded here. The problem is not that the acquisition system is broken — the problem is that a functioning acquisition system, applied to allied and battlefield-proven capability, requires a discipline that does not exist in most originator relationships.
Helicon Defense supplies that discipline. We identify serious allied capability, protect the originator, translate the operational case into U.S. mission and acquisition terms, structure demonstrations and evaluation, stand up trusted manufacturing partnerships, and plan for sustainment from day one. That is why the operating model is a five-stage transition — Qualify, Protect, Translate, Demonstrate, Produce & Sustain — and not a set of introductions.
Every claim on the front page of this site — that Helicon transforms battlefield-proven allied technology into trusted U.S. capability — is downstream of the acquisition-transition system explained above. That is why this chapter matters more than most.
Three implications shape how Helicon operates:
This is the operating premise of the company. The five-stage model on the homepage is not a slogan. It is the shape of the actual work that lets a mature allied capability arrive on the correct side of the Valley of Death.
Sources are grouped by type so a defense reader can go directly to the official material without wading through commentary. Every URL was verified live at last review.
Defense Innovation Unit
Explains DIU's Commercial Solutions Opening, prototype Other Transactions, evaluation, and transition pathways.
Defense Acquisition University
The official framework for major capability, middle-tier, urgent capability, software, services, and business-system pathways.
U.S. Small Business Administration
The federal starting point for SBIR and STTR phases, participating agencies, opportunities, and commercialization resources.
U.S. Small Business Administration
Practical courses on program basics, agency requirements, proposals, Phase III, data rights, ITAR, and prime partnering.
U.S. House Office of the Law Revision Counsel
Statutory basis for prototype Other Transactions and qualifying follow-on production.
U.S. Government Accountability Office
Examines flexible authorities and financing mechanisms intended to move promising R&D toward use.
AFWERX (Department of the Air Force)
Air Force explanation of the Phase III sole-source authority and how it is used to transition small-business capability into Air Force and Space Force programs.
Department of the Navy — Office of Small Business Programs
Practical reference for program managers on using Phase III authority to place production and follow-on work with SBIR/STTR small businesses.
Curated video from official DoD channels and recognized public policy voices. Each clip runs in the page — nothing you click sends you off the site unless you choose to open on YouTube.
A practical official overview of DIU proposal and pitch expectations — the CSO process in plain terms.
Former Under Secretary of Defense for Policy Michèle Flournoy explains, plainly, why successful prototypes fail to scale — and what must change in the budget process for them to succeed.
Practical walkthrough of how the SBIR Phase III sole-source authority is used to bridge from small pilots into multi-million dollar production contracts.
Helicon Defense works with U.S. and allied defense partners, Ukrainian and allied innovators, and trusted manufacturing organizations. If the transition gauntlet is what stands between a technology and a warfighter, that is the problem we are built for.