Field Guide · Defense Acquisition

Defense Acquisition Transition 101

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.

Executive Summary

A 3-minute read on how U.S. defense capability actually gets fielded.

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.

Why a U.S. defense reader should care

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.

Deep Dive

The transition system, mechanism by mechanism.

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 Adaptive Acquisition Framework (AAF)

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:

  • Major Capability Acquisition (MCA) — the traditional pathway for large weapon systems and platforms.
  • Middle Tier of Acquisition (MTA) — for rapid prototyping and rapid fielding of capability inside five years, with tailored oversight.
  • Urgent Capability Acquisition (UCA) — for capability needed in months to address an urgent operational need.
  • Software Acquisition — for continuous software delivery, treating software as an evolving product rather than a fixed deliverable.
  • Services Acquisition — for the acquisition of services rather than end items.
  • Defense Business Systems — for enterprise IT and business-process systems.

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.

SBIR, STTR, and the Phase III authority

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 I — feasibility study, typically 6 months, small award.
  • Phase II — prototype development, typically two years, larger award.
  • Phase III — commercialization and transition, with a critical statutory advantage: Phase III contracts can be awarded sole-source, without further competition, so long as the work derives from Phase I or Phase II. This authority is the intended bridge across the Valley of Death.

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.

Other Transactions (OTAs)

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.

The rapid-innovation program offices: DIU, AFWERX, and the service equivalents

Several DoD organizations exist specifically to move commercial and small-business technology into fielded use faster than the traditional acquisition system:

  • Defense Innovation Unit (DIU) — the Secretary of Defense's principal commercial-technology bridge. Uses the Commercial Solutions Opening (CSO) process to award prototype OTAs in 60–90 days, with a defined transition to production.
  • AFWERX — the Department of the Air Force's innovation arm, focused on small-business SBIR/STTR flow into Air Force and Space Force use.
  • NavalX and NAVSEA innovation programs — the Navy's counterparts, engaging with both small business and mid-tier companies for undersea, surface, and aviation systems.
  • SOFWERX and USSOCOM's acquisition authority — Special Operations Command has broad, fast acquisition authority for capability that supports the SOF enterprise.

Program Executive Offices and prime contractors

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.

Readiness levels: TRL and MRL

The DoD uses two readiness scales to describe how mature a technology is:

  • Technology Readiness Level (TRL) 1–9 — from basic research (1) to operationally proven in an actual mission environment (9).
  • Manufacturing Readiness Level (MRL) 1–10 — from basic manufacturing implications identified (1) to full-rate production capability with proven cost, yield, and supply chain (10).

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.

Low-Rate Initial Production (LRIP)

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

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:

  1. A service partner with budget authority to place a production contract.
  2. A budget line item — because the DoD budgets on a two-year forward cycle, capability successfully demonstrated today may need funding that was not planned for two fiscal years ago.
  3. A trusted manufacturing base that can build the capability at the required rate, cost, and quality.
  4. A sustainment plan — spares, training, upgrades, and lifecycle support — because a fielded system without sustainment is a briefing chart.

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.

Why Helicon Defense exists

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.

Helicon Perspective

Why the transition system is the whole game.

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:

  1. A capability that cannot be manufactured, sourced, and sustained is a demonstration, not a fielded capability. This is why we invest in the manufacturing-readiness side of the transition — trusted partners, quality systems, supply-chain integrity — from the moment we begin qualifying a technology, not at the end.
  2. Speed without discipline creates its own Valley of Death. Rushed prototypes without evaluation partners, budget lines, and sustainment planning may look faster in the near term, but they die in the same gap for the same reasons. Helicon's discipline is the compression of the gauntlet through preparation, not the skipping of it.
  3. Adversaries know the transition system too. Russia, China, and Iran are studying not only what wins on the battlefield but how quickly the U.S. and its allies can turn that knowledge into fielded capability. If Helicon's model is slower than the adversary's absorption cycle, the transition problem becomes a strategic problem.

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

Primary and authoritative sources for this chapter.

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.

Official (DoD, service programs, statutes)

Official Guide

Defense Innovation Unit

Work With Us / Acquisition Process

Explains DIU's Commercial Solutions Opening, prototype Other Transactions, evaluation, and transition pathways.

Official Framework

Defense Acquisition University

Adaptive Acquisition Framework

The official framework for major capability, middle-tier, urgent capability, software, services, and business-system pathways.

Official Program

U.S. Small Business Administration

SBIR/STTR — America's Seed Fund

The federal starting point for SBIR and STTR phases, participating agencies, opportunities, and commercialization resources.

Course Hub

U.S. Small Business Administration

SBIR/STTR Online Tutorials

Practical courses on program basics, agency requirements, proposals, Phase III, data rights, ITAR, and prime partnering.

Primary Law

U.S. House Office of the Law Revision Counsel

10 U.S.C. § 4022 — Prototype Projects

Statutory basis for prototype Other Transactions and qualifying follow-on production.

Government Report

U.S. Government Accountability Office

DOD R&D Financial Flexibilities

Examines flexible authorities and financing mechanisms intended to move promising R&D toward use.

Additional official pathways

Official Program

AFWERX (Department of the Air Force)

SBIR/STTR Phase III

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.

Official Program

Department of the Navy — Office of Small Business Programs

SBIR/STTR Phase III Quick Reference

Practical reference for program managers on using Phase III authority to place production and follow-on work with SBIR/STTR small businesses.

Videos

Watch key voices in defense acquisition transition.

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.

Defense Innovation Unit · Official

How to Pitch the Defense Innovation Unit

A practical official overview of DIU proposal and pitch expectations — the CSO process in plain terms.

Institute for Security and Technology · Public Policy

Addressing the "Valley of Death": Defense Technology Innovation & The Pentagon Acquisition Landscape

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.

SBIR industry panel · Educational

From R&D to Phase III: Navigating the New SBIR Landscape

Practical walkthrough of how the SBIR Phase III sole-source authority is used to bridge from small pilots into multi-million dollar production contracts.

Have a technology, a program, or a partnership question?

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.