The DARPA-to-Program-of-Record Gap Nobody Budgets For

DARPA hands you a check. Maybe it's a $2M SBIR Phase II, maybe it's a larger direct contract under one of the major program offices. Your technology works in a controlled environment. Demos have gone well. The program manager is enthusiastic. You start thinking about scale.

Photo by cottonbro studio on Pexels.

Then reality hits.

DARPA's job is to fund high-risk, high-reward science. Its mandate is explicitly not to transition technology into programs of record. That transition is somebody else's problem. In practice, it usually becomes the startup's problem, and founders consistently underestimate what solving it actually costs.

The gap between a successful DARPA prototype and a funded Program of Record (PoR) is where defense startups go to die quietly. No failed demo, no public embarrassment. Just a slow erosion of runway while the startup waits for a transition partner who never quite commits.

What the Gap Actually Looks Like

DARPA typically funds technology to roughly Technology Readiness Level (TRL) 5 or 6. You have a working prototype in a relevant environment. That sounds close to deployment. It isn't.

Moving from TRL 6 to TRL 9 (full operational capability) requires a military service to own the program, budget for it through the PPBE process, write a requirements document around it, run an acquisition program, and survive the annual budget cycle. Each of those steps takes time measured in years, not quarters.

Here's how that transition typically sequences:

graph TD
    A[DARPA Contract / TRL 5-6] --> B(Service Transition Partner)
    B --> C{PPBE Budget Inclusion}
    C --> D[Program of Record Established]
    D --> E(RFP / Competition)
    E --> F[Contract Award]
    F --> G((Revenue))

Every arrow in that diagram is a potential multi-year stall. The PPBE process alone runs on two-year cycles. If your technology misses the budget window, you wait. If the service's priorities shift, you wait. If the program manager rotates out, you often start the relationship-building over from scratch.

Founders typically model this as an 18-month process. The realistic median is closer to four to six years from DARPA graduation to first PoR revenue.

Why Investors Keep Getting Caught Flat-Footed

Venture investors who come from commercial software backgrounds see DARPA validation as the equivalent of product-market fit. It isn't. DARPA validation means the technology is real. It says almost nothing about whether any military service has budgeted, prioritized, or internally championed adoption.

The distinction matters enormously for how you model capital requirements.

A commercial SaaS company at product-market fit can grow into revenue within 12 to 18 months of a Series A. A defense tech company at TRL 6 with DARPA validation often needs three to five years of bridge capital before the first meaningful PoR revenue lands. During that window, the company has to pay engineers, maintain security clearances, respond to government requests for information, survive audits, and keep a team together with no clear revenue horizon.

That burn profile breaks most standard venture return models. It also breaks most founder psychologies, which is underappreciated.

The Transition Funding Problem

There is a formal mechanism designed to help here: the DoD's rapid prototyping and transition authorities, including Middle Tier Acquisition (MTA) and various service-level transition funds. These exist precisely because Congress recognized the DARPA-to-PoR gap decades ago.

The problem is that transition funding is consistently underappropriated relative to demand. Program offices compete for it. Politics within service branches affect who gets prioritized. A startup without a well-connected internal champion inside the relevant service often gets nothing.

DIU can help accelerate early commercial-to-military transitions, but its authorities are better suited to fielding existing commercial technology than to bridging the TRL 6-to-9 chasm on novel defense-specific hardware.

What Good Investors Do Differently

The defense tech investors who consistently back winners do a few things that separate them from the pack.

First, they map the internal service champion before the investment closes. Not the program manager. The senior acquisition executive who will still be in the building in three years. People rotate; institutional commitment has to run deeper than one relationship.

Second, they size the round for the gap, not for the milestone. If TRL 9 and first PoR revenue is five years out, the company needs capital structured for that timeline. Tranched investments with milestone gates calibrated to commercial timelines are a trap. Defense timelines don't bend to investor pressure.

Third, they diversify the customer base intentionally. A startup with one DARPA contract and one interested service program is one budget cut away from zero. The more transition conversations running in parallel, the better the odds that at least one survives the next PPBE cycle.

DARPA funding is genuinely valuable. It validates technology, provides non-dilutive capital, and opens doors inside the Pentagon that would otherwise stay shut for years. What it doesn't do is carry a company to revenue. The founders and investors who understand that distinction before they take the first check will be the ones still standing when the PoR finally lands.