The Pentagon's $1.7B Strategic Capabilities Office Just Mapped Its Three Portfolios and Eight Focus Areas. The Standing BAA Runs Until 2029 — Here's How Small Businesses and Research Teams Should Read the Map.

The Strategic Capabilities Office sits in an unusual place within the Pentagon. It is not a research agency in the DARPA sense — DARPA invests in transformational technology that may take a decade to mature, organized around individual program managers with five-year tenures who build their portfolios around specific high-risk hypotheses. SCO is a rapid-prototyping organization with a three-to-five-year time horizon, organized around bringing existing technology to operational use in unconventional configurations. It is not a service-laboratory program either — service labs (the Army Research Laboratory, the Naval Research Laboratory, the Air Force Research Laboratory) own deep-discipline research portfolios anchored in long-running mission areas. SCO sits inside the Office of the Under Secretary of Defense for Research and Engineering, draws on the service laboratories and DARPA for technology inputs, and exists specifically to push those inputs into operational use at speed.

On May 11, SCO Director Jay Dryer publicly described the office's structure in a way that the office had not previously offered. The disclosure matters because SCO has historically been one of the more opaque defense innovation organizations — its project portfolio is not openly published, the budget structure is buried inside the OUSD(R&E) appropriation, and the engagement model has been concentrated on a small set of preferred industry partners. Dryer's public framing is a signal that the office is opening its aperture to broader industry and research engagement, and the standing SCO Broad Agency Announcement that accepts white papers through August 31, 2029 is the formal mechanism through which that engagement happens.

Three Portfolios — and What Each One Actually Funds

Dryer described SCO as organized around three portfolios. The framing is important because it determines how white papers are routed, which program manager evaluates a submission, and what evaluation criteria apply.

The long-range fires portfolio covers offensive and defensive kinetic systems. Dryer described it informally — "generally, if it explodes, it is probably in this portfolio" — but the operational content is precise. SCO programs in long-range fires have included the Hypervelocity Gun Weapon System (HGWS), which adapted Navy electromagnetic railgun-derived projectiles to existing artillery tubes; Hurt Locker, a containerized missile launcher concept that allows missile systems to be deployed from logistics ships, contested forward bases, and unconventional firing platforms; and a series of long-range precision fires programs that bridge the gap between service-developed munitions and operational use cases the services have not prioritized. The portfolio's evaluation lens is whether a proposed capability extends range, increases lethality, or enables fires from platforms that do not currently fire — not whether the underlying weapon technology is novel.

The autonomy and AI portfolio is the portfolio that has grown most aggressively since 2022. SCO's autonomy programs have included Ghost Fleet, the unmanned surface vessel concept that demonstrated long-endurance autonomous operation in contested maritime environments, and a series of collaborative autonomy programs that pair manned platforms with unmanned wingmen, decoys, and sensor nodes. Dryer was explicit that the portfolio includes "the human decision-making side to it, the command-and-control aspects that come along" — which means proposals that address only the algorithmic or platform-autonomy side without addressing the operator interface, the C2 integration, or the doctrine implications are likely to be redirected to DARPA or to service-lab programs. SCO's autonomy work is specifically about operational integration of autonomy with existing forces, not autonomy as a standalone research domain.

The special and enabling capabilities portfolio is the smallest of the three and the most heterogeneous. It includes cyber, electronic warfare, space, and special operations forces support. Dryer described it as the portfolio that addresses capabilities that "do not fit cleanly inside one of the other two portfolios" and that frequently support combatant command or special operations command requirements directly. The Pele nuclear power plant program — a small modular reactor designed for forward-base deployment to reduce the logistics burden of fossil-fuel resupply — sits inside this portfolio, as do a series of less publicly disclosed cyber and space programs.

The Eight Focus Areas

Across those three portfolios, Dryer described eight focus areas: precision fires and lethal effects; contested and contesting logistics; novel employment and collaborative systems; deception and surprise; advanced kill webs; countering adversary or "red" kill chains; extended reach and survivability; and cost-effective air defense. The focus areas cut across the portfolio structure — a contested-logistics program might sit primarily in the long-range fires portfolio (if it concerns delivery of fires under contested conditions) or in the special and enabling capabilities portfolio (if it concerns special operations forces sustainment in denied environments).

Two of the focus areas are particularly worth dwelling on for grantseekers and white-paper writers.

Cost-effective air defense is the focus area that connects to the broader Pentagon problem of expensive interceptors against low-cost adversary threats. The Patriot and SM-6 interceptors that defended Saudi infrastructure and Ukrainian airspace cost between $1 million and $4 million per shot; the drones and cruise missiles they intercepted often cost a small fraction of that. The economic mismatch is not sustainable in a peer-conflict scenario, and SCO has been investing in directed-energy, low-cost-effector, and net-and-tether concepts that reverse the cost ratio. White papers in this area need to demonstrate a credible path to per-engagement cost below $50,000 against the relevant threat class — not just a novel intercept concept that happens to be cheaper than Patriot.

Advanced kill webs is the focus area that addresses the C4ISR-to-fires architecture. Traditional kill chains are linear: sensor detects, processor identifies, decision authority approves, shooter engages. A kill web is a non-linear architecture where any sensor can cue any shooter, any platform can serve as a C2 node, and the path from detection to engagement is optimized in real time based on availability and survivability. The proposal lens here is integration rather than novel technology — SCO is looking for white papers that connect existing sensor, C2, and effector systems in ways that produce demonstrable improvements in engagement timeline, sensor-to-shooter latency, or resilience to node failure.

The Engagement Model Is Different from DARPA

The most consequential observation Dryer offered is that SCO seeks industry partners "who can work with others, that can be part of that team" rather than single vendors capable of solving everything independently. This is a meaningful contrast with DARPA, where the program manager often selects a single prime contractor or a small consortium and the program structure is built around that prime's technical approach. SCO's preferred model is a team-of-teams approach where multiple companies and labs contribute components, and the office takes the integration risk.

The practical implications for small businesses and university research teams are significant. A small business with a strong sensor algorithm, a specific autonomy subsystem, or a specialized component is more competitive at SCO than the same company would be at DARPA, because SCO is explicitly looking for the components that integrate into a larger architecture rather than for a prime contractor capable of delivering the full architecture. The corresponding cost is that SCO white papers need to be written with awareness of the larger architecture the component will plug into, including the other component providers and the integration entity. White papers that propose a standalone capability without addressing the integration question will be evaluated less favorably than white papers that explicitly position the proposed work inside an SCO program structure.

The standing BAA also operates differently from DARPA's office-wide BAAs. White papers are accepted continuously through August 31, 2029, with technical evaluations performed on a rolling basis. Submissions that receive favorable initial evaluations are invited to submit full proposals, and the office reserves the right to fund work directly off the white paper without a follow-on full proposal step. The implication is that the white paper itself is the first competitive instrument — a strong white paper that maps cleanly onto one of the eight focus areas can result in funded engagement faster than a DARPA full proposal cycle would.

How SCO Spends $1.7 Billion

Dryer's disclosure that SCO is executing a $1.7 billion FY 2026 budget puts the office in a specific spending category. By comparison, DARPA's FY 2026 budget is approximately $4.4 billion, and a major service-laboratory's annual basic and applied research budget is in the $1–3 billion range. SCO is therefore a peer institution in dollar terms to a major service laboratory, but with a different organizational mission and a different obligation profile. SCO does not maintain large standing research staffs; the budget is heavily concentrated in contracted prototyping work, with a smaller share going to internal staff, government-furnished equipment, and operational testing in conjunction with the combatant commands and the services.

The $1.7 billion is distributed across the three portfolios, but the distribution is not publicly disclosed in detail. Based on the program portfolio that has been publicly discussed — Ghost Fleet and related autonomy programs, HGWS and related long-range fires programs, Pele and related special and enabling capabilities programs — a reasonable working estimate is that long-range fires and autonomy and AI each consume roughly 40 percent of the budget, with special and enabling capabilities consuming the remainder. The autonomy and AI portfolio is growing fastest and may reach parity with long-range fires within the next two budget cycles as autonomy programs move from prototyping into production.

For grantseekers, the budget structure means individual SCO contracts are typically in the $1 million to $50 million range for prototyping work, with larger awards reserved for production-readiness or operational-testing programs. White papers should be sized accordingly — a $200,000 proposal is too small for SCO's normal engagement model and will likely be redirected to SBIR or to a service-lab program; a $200 million proposal is too large for the prototyping stage and will likely be sent back for restructuring.

What to Do With This Map

Three concrete moves follow from Dryer's public framing of SCO. First, the eight focus areas function as topic categories for the standing BAA — any white paper submitted should explicitly identify which focus area it addresses, and the technical approach should be written with awareness of the other programs already in that focus area. SCO program managers will route white papers based on focus area alignment, and a misaligned submission can sit in queue for months before being returned. Second, the team-of-teams engagement model means small businesses and research teams should be building relationships with the integration entities that SCO works with — major defense primes, specialized integration firms, and the federally funded research and development centers (FFRDCs) that frequently serve as SCO technical advisors — rather than treating SCO as a direct customer relationship. The integration entities have visibility into which components SCO is sourcing, and they are the path to component-level work inside SCO programs. Third, the standing BAA's open submission window through August 31, 2029 means there is no submission deadline pressure — which has the unintuitive effect of making submission quality more important, not less. White papers compete continuously against other white papers in the same focus area, and a marginal submission has a longer time window in which to be displaced by a stronger one.

For companies that have historically engaged the Pentagon innovation ecosystem through SBIR, DARPA, or service-lab programs, SCO is a different door into the same building. The technologies SCO funds frequently start in those other programs — DARPA-developed autonomy concepts moving into SCO prototyping, SBIR-developed components being integrated into SCO architectures — and SCO white papers should reference that upstream pedigree explicitly. Tools like Granted can map a company's technical capabilities and prior federal engagement against the eight SCO focus areas, surface the integration partners and FFRDCs already engaged with each focus area, and identify the gaps in current SCO program portfolios where a credible new entrant has the strongest competitive position before the white paper goes in.