In the spring of 2022, a twelve-person engineering firm in northern Virginia was trying to solve a problem that most small defense companies recognize: they had strong technical capabilities, an established clearance base, and a track record of solid work — but they were perpetually subcontracting to large primes on programs where their contribution was valuable but their margin was thin and their strategic position was weak.

The firm's leadership decided to run a systematic analysis of the defense budget to identify programs where their specific expertise — autonomous systems integration and real-time data fusion — was not yet being addressed by an established incumbent. What they found shaped the next three years of the company's growth trajectory.

This is the story of how they did it, and why the approach is repeatable for firms in similar positions.

The Starting Point: Mapping Capabilities to Budget Lines

The firm began with a list of their own capabilities, described in technical terms rather than marketing language. Real-time sensor fusion. Heterogeneous network integration. Autonomous task allocation for multi-agent systems. Edge processing under bandwidth-constrained conditions. These were specific things they knew how to do.

The next step was translating those capabilities into budget vocabulary — finding the Program Elements across DoD that were funding programs which needed those capabilities. This required reading R-2A justification exhibits, not just scanning titles. A PE might be titled "Advanced Sensors Development" and appear irrelevant to an autonomy firm, until the program description reveals that 40% of the funded work involves integrating sensor outputs from multiple dissimilar systems in contested environments — which is exactly what sensor fusion does.

After three weeks of systematic reading across Army, Navy, Air Force, US Special Operations Command (SOCOM), and DARPA budget exhibits, the firm had identified approximately 35 PE numbers with meaningful overlap to their capabilities. Of those 35, they needed to prioritize the ones where the timing was right — where the program was funded at a level indicating real work was imminent, but where an incumbent was not yet entrenched.

Identifying the Gap

The timing analysis came from the funding profiles. A program that had been funded at $2–3M annually for several years, then suddenly appeared in the FY2023 President's Budget (PB2023) at $12M with a Future Years Defense Program (FYDP) showing $25M in the following year and $40M the year after, was exhibiting a classic ramp-up signature. That ramp almost always precedes a competitive contract award — the program has been in exploratory or advanced development, has demonstrated enough to earn a larger investment, and is now ready to move to the next phase through competition.

Three of the 35 PEs showed this pattern at approximately the same time. The firm focused on two of them — one in the Army's tactical network modernization portfolio and one in a SOCOM program for autonomous logistics resupply.

For each program, they then did R-3 analysis: looking at the contract history exhibits to understand who had been performing the early work. In both cases, the prior contracts were small, going to a mix of universities, Federally Funded Research and Development Centers (FFRDCs), and systems integrators who had done foundational research but were not positioned as product developers for a fielded system. The prime contractors who would normally dominate were not yet engaged at the program-element level.

The Window

What the analysis had identified was a window. The programs were real, funded, and about to grow. The incumbents were researchers, not integrators. The program offices would soon need a different kind of performer — one who could take research-stage autonomy work and build it into something deployable. The large primes would figure this out eventually, but they tend to engage serious capture resources only once a program reaches a certain funding level, and they are typically responding to signals from contracting officers rather than reading budget documents proactively.

The firm moved quickly. They identified the program managers for both programs through a combination of the budget exhibits (which often name the technical point of contact), conference speaker lists, and targeted outreach to contacts at the relevant program offices. They requested informal technical meetings, which both PMs agreed to, and used those meetings to understand the specific gaps that the upcoming competitive awards would be designed to fill.

Positioning Before the RFP

Over the next eight months, the firm did three things:

  • Submitted an unsolicited white paper to each program office describing a specific technical approach to the autonomous integration challenge, grounded in work they had done in analogous commercial and defense contexts
  • Presented at two conferences where the program offices had a significant presence
  • Quietly began discussions with two mid-tier defense firms about teaming arrangements that would give their proposal additional depth in areas where they were thin — specifically, program management experience and manufacturing readiness

None of this required access to inside information. All of it was driven by reading the budget documents, doing the R-3 contract history analysis, and investing the time to understand what specific programs needed before those needs became a formal requirement.

The Result

When the first solicitation dropped — the Army tactical network program — the firm was ready. They had a teaming arrangement in place, a technical approach that had already been informally socialized with the program office, and a clear understanding of the evaluation criteria based on white paper feedback they had received. They submitted as a prime contractor leading a team that included one of the mid-tier firms they had identified during the analysis phase.

They won. The award was $8.7 million for a 24-month base period, with options that could extend to $34 million. For a twelve-person firm, it was a transformative contract — not only in revenue but in the strategic positioning it created. As a program prime, they now had direct program office relationships, access to the government's technical data, and a seat at the table for discussions about the follow-on work.

The second program, the SOCOM resupply effort, took longer. But the intelligence was correct, the gap was real, and the firm was eventually awarded a subcontract through a prime they had cultivated during the positioning phase.

The Playbook

The approach is repeatable because the underlying data is public and the pattern it reveals is consistent. Defense programs follow a predictable funding lifecycle. Budget documents describe that lifecycle in detail. The gap between "early-stage funded research" and "fielded competitive program" is where small firms can establish positions that are genuinely hard for late-arriving primes to displace.

The investment required is time, not money or access. Three weeks of systematic budget reading produced a prioritized list of 35 PE numbers. A few months of positioning work — white papers, conference presence, teaming discussions — produced a winning proposal. The only resource that can't be bought is willingness to do the analysis before the opportunity is obvious to everyone else.