Founders Who Finish

Build the Participation Profile the Rewired Buy-Side Reads

Back to Field Notes
May 16, 2026 Founders Who Finish

Rocket Lab partnered with RTX on May 15 to bid as a subcontractor for Space-Based Interceptor work inside the $3.2 billion Golden Dome architecture. AeroVironment took a $43 million PANTHER award on May 12 to instrument the SkyRange hypersonic test fleet. The Pentagon’s FY27 budget request proposes to fund the Defense Autonomous Warfare Group at roughly $54.6 billion against a current-year base of $226 million. Two new DARPA RFIs released in early May tell the autonomy and robotics supplier base what the FY27 and FY28 program-office buy is going to require at the architectural level. Four signals across four days, all pointing at the same thing. The defense-hardware buy-side is being rewired in public, and the participation profile founders building defense or dual-use hardware platforms have to design against has been spelled out inside the disclosures. Founders who finish in this environment do not wait for the formal RFP to read the operating profile the rewired buy is going to require. They design the architecture, the partnership stack, the predecessor-program references, and the operating cadence against the participation profile the buy-side has now disclosed, across the years that precede the bid window where the participation profile is no longer engineerable.

If You Are Building a Company in This Environment

The default first-time defense or dual-use hardware founder treats the formal RFP as the moment the program-office conversation begins. The build-phase logic is that the technical capability is the thing the bid will be priced against, that the operating team will run the bid process when the program office releases the formal solicitation, and that the prime relationships and the predecessor-program references can be assembled inside the bid-process window. The four signals this week reframe the logic. Rocket Lab did not partner with RTX in the bid window. The partnership lands at the start of the Golden Dome SBI bid cycle because Rocket Lab spent years engineering the predecessor PWSA prime position, the Electron launch cadence, and the Neutron development profile that make the company a credentialed-capability supplier RTX has to bring into the bid set. AeroVironment did not bid PANTHER cold against the SkyRange test program. The PANTHER architecture, the GrandSKY operating footprint, the prior SkyRange relationship work, and the sustainment-curriculum partnership with Bismarck State College were in motion across the years that preceded the May 12 award. The DAWG budget construction and the DARPA RFIs are giving the supplier base the operating profile the FY27 and FY28 program-office conversations will read, and the architectural and operating-cadence work that produces a platform aligned to that operating profile has to be in motion now because the program-office buildout will start running the supplier conversation inside the next two to four quarters.

Founders who finish defense or dual-use hardware platforms run the participation-profile question from the opposite end of the timeline. They identify the program-office conversation the business is being designed to land in, define the operating profile the program office and the prime side will read candidate suppliers against, and engineer the architectural, partnership, regulatory or pathway-clearance, and operating-cadence work that produces the profile across the years that precede the formal bid window. They run the prime-side relationship cadence with the primes who will assemble the subcontractor stack through the build phase before the bid window opens. They cultivate the predecessor-program references that the prime side and the program office actually read at the bid. They resource the participation-profile work as a Day-1 capital line equivalent in scale to the visible product-engineering work that produces the next visible milestone. The compensation arrives at the formal bid window, when the prime side and the program office read the business against the operating profile the rewired buy-side is now writing checks against, and the participation profile slots the business into the bid set that the founders running the prior-generation profile cannot enter.

The version of the participation-profile decision that breaks first-time defense and dual-use hardware founders is the one that begins after the technical milestones are in hand and the operating team initiates the bid process. The founder discovers in those conversations that the prime side will not bring a capability supplier into the bid set without a credentialed predecessor-program track record the founder has not been engineering, that the program office reads the operating profile against the rewired buy-side framing the founder has not been architecting against, and that the operating-cadence history the founders ran through the build phase does not match the operating cadence the program-office and prime-side conversation now requires. The cost shows up at the bid window, when the participation profile the engineering team produced through the build years does not slot into the bid set the rewired buy-side is now writing against, and the operating cadence in the months before the bid cannot move the profile into the read the rewired buy-side requires.

What the Four Signals Tell You About the Participation Profile the Buy-Side Now Reads

The four signals this week describe what the participation profile looks like inside the rewired defense-hardware buy across the prime-subcontractor architecture, the test-infrastructure procurement lane, the categorical autonomy capital line, and the architectural framing the program-office conversation will read. The Rocket Lab and RTX disclosure shows that the prime-subcontractor architecture rewards a credentialed predecessor-program reference, a capability the prime cannot organically supply, and an operating cadence that plugs into the prime’s bid schedule. The AeroVironment PANTHER award shows that the test-infrastructure procurement lane rewards a sensor, telemetry, instrumentation, or calibration capability mapped against a specific test program already inside the budget, plus a sustainment-tail strategy that extends the revenue beyond the initial integration award. The DAWG budget construction shows that the autonomy buy has been moved into a categorical capital line whose program-office cadence will start reading candidate suppliers inside the next two to four quarters, with the funding split between base and reconciliation favoring suppliers who have invested in the fast-cycle operating cadence the reconciliation pool will require. The DARPA RFIs show that the architectural framing the FY27 and FY28 autonomy buy will read against is edge compute for untethered autonomous operation and peer-to-peer multi-agent coordination, rather than the centralized command-and-control architectures the prior-generation autonomy framing required.

The architectural work that separates the platforms that finish from the platforms that stall in this environment is the participation-profile decision the founder makes years before the formal bid window opens. The platforms that finish are designed against a specific program-office and prime-side conversation from initial product architecture, with the technical mechanism, the regulatory or pathway-clearance work, the partnership and predecessor-program references, the operating-cadence history, and the operating-team profile aligned to the participation profile the rewired buy-side is now writing checks against. The platforms that stall are designed against a generic technical or category opportunity the engineering team is most confident in, and the participation-profile question gets answered at the formal bid window rather than during the build phase. The business that arrives at the formal bid window with a participation profile engineered through the build years gets priced into the bid set the rewired buy-side is now writing against. The business that arrives at the bid window with a participation profile that was not engineered gets priced at the standalone-capability multiple regardless of the engineering quality of the underlying platform.

What Participation-Profile Discipline Looks Like at Operating Scale

The companies that win on the participation-profile question in defense and dual-use hardware do specific architectural work that is easy to defer and expensive to skip. They identify the program-office conversation the business is being designed to land in before the product architecture freezes, with senior corporate-development, regulatory, and operating-cadence operators who have run comparable platforms through the program-office and prime-side conversation and understand how the rewired buy-side reads candidate suppliers. They map the operating profile each prospective prime and program office reads, identify the specific capability gap inside the operating profile the business is being engineered to fill, and design the technical, regulatory, partnership, and operating-cadence architecture against the participation profile the rewired buy-side is now writing. They run the predecessor-program work that produces the credentialed reference the prime side and the program office actually read at the bid window. They review the participation-profile architecture quarterly against the operating cadence and update the architecture when a comparable defense or dual-use hardware business changes the participation profile the rewired buy-side is now writing, when a regulatory or operating decision reshapes the operating profile the program-office conversation requires, or when a strategic partnership or deployment relationship opens a profile dimension the architectural work has to design against.

At the operating level, the discipline shows up as a structured participation-profile review that runs alongside the engineering, regulatory, and commercial cadence with the same operating intensity. The review covers the program-office and prime-side conversation the business is being designed to land in, the operating profile the prospective primes and program offices read candidate suppliers against, the operating cadence the business has to run with prospective primes and program offices through the build phase, the architectural and partnership work the build phase has to produce to satisfy the participation profile, and the specific operating metrics the rewired buy-side is now using to read candidate suppliers. The four signals this week show what it looks like when the discipline produces the operating profile the rewired buy-side is now writing checks against, and the founder operating plan that finishes well in defense or dual-use hardware in 2026 runs the participation-profile work with the same operating discipline the four examples just demonstrated.

The Five Questions for the Participation-Profile Decision

The five-question framework in Founders Who Finish reframes what a credible participation-profile strategy actually requires the team to deliver in a defense and dual-use hardware environment where the buy-side has been rewired, the categories have been resized, and the operating profile the program-office and prime-side conversations now read is specific enough to reverse-engineer from the disclosures.

Question 1

What are you actually finishing?

If the answer is a demonstrated technical capability without a defined participation profile against the program-office and prime-side conversation the business will face, you are finishing a deliverable the bid will price at the standalone-capability multiple. The participation profile that slots the business into the bid set the rewired buy-side is now writing against is the actual completion state. Founders who finish identify the program-office conversation from initial product architecture and design the technical, regulatory, partnership, and predecessor-program work against the operating profile the rewired buy-side is now reading. The Rocket Lab and RTX, AeroVironment, DAWG, and DARPA RFI signals this week describe what that participation profile looks like across the four major lanes of the defense-hardware buy.

Question 2

Who decides you are done?

The prime decides whether you are in the subcontractor stack, the program office decides whether your operating profile reads against the buy-side framing, and the regulatory or pathway gatekeeper decides on the clearance profile. The three decisions read the business against the operating profile, the partnership cadence, and the regulatory pathway the architectural work has produced. All three get harder when the participation-profile question was deferred. Founders who finish design the business to produce the read the prime side, the program office, and the regulatory pathway actually generate against the participation profile the rewired buy-side now reads.

Question 3

What does your evidence actually prove?

The evidence base has to satisfy the regulatory or pathway-clearance work the platform is being built to anchor and the participation-profile evaluation the program-office and prime-side conversation now runs. Rocket Lab’s evidence base was the PWSA prime track record plus the Electron and Neutron launch cadence. AeroVironment’s evidence base was the PANTHER technical capability plus the prior SkyRange operating relationship plus the GrandSKY operating footprint. The DAWG and DARPA framing tells the autonomy supplier base what evidence base the FY27 and FY28 program-office buy is going to require. Founders who finish design the evidence base against the participation profile the rewired buy-side is now reading, with the regulatory or pathway data, the predecessor-program proof, the technical architecture, and the operating-cadence history mapped backwards from the participation profile the program office and the prime side read at the bid window.

Question 4

What does your path to contract, deployment, or program-of-record actually look like?

In defense and dual-use hardware, the contract, deployment, or program-of-record pathway interacts with the participation profile to produce the unit economics the program-office and prime-side conversation actually prices. A defense-hardware platform with a clean technical capability but an unclear pathway into a program-of-record runs into the unit-economics question at the bid window, when the prime side and the program office price the business against the program-revenue trajectory the pathway can support. A test-infrastructure platform with a clean technical capability but an unclear sustainment-tail strategy runs the same exposure inside the test-program procurement lane. Founders who finish design the contract, deployment, or program-of-record architecture alongside the regulatory and technical architecture, with the pathway, the sustainment-tail profile, and the per-program unit economics already characterized through the build phase.

Question 5

What does the finish line look like to the prime side, the program office, or a strategic acquirer?

Primes, program offices, and strategic acquirers of defense and dual-use hardware platforms in 2026 are pricing businesses whose technical, regulatory, partnership, and operating-cadence architecture is engineered against the participation profile the rewired buy-side is now reading. The Rocket Lab and RTX Golden Dome partnership, the AeroVironment PANTHER award, the DAWG budget construction, and the DARPA RFIs this week are the cleanest current public examples of how the rewired buy-side concentrates participation behind a specific operating profile across the prime-subcontractor architecture, the test-infrastructure procurement lane, the categorical autonomy capital line, and the architectural framing the program-office conversation will read. Founders who finish position the business to land inside the participation-profile category that the rewired buy-side is now writing against, and the architectural and partnership discipline that produces the positioning has to be embedded from initial product architecture.

Founders Who Finish

The guide for founders building in regulated and capital-intensive markets

The five-question framework for building defense, medical device, climate, industrial robotics, and other hard-tech companies that finish what they start, in the regulatory, capital, and operating environment as it actually exists.

Get the Book