Industry verticals
Warm Introductions in Defense and Aerospace Business Development
Defense and aerospace business development is structurally relationship-driven: program offices are shaped before RFPs are issued, prime contractor teaming agreements are assembled through existing networks, and cleared-community trust operates on different terms than civilian B2B. Four mechanics specific to defense BD: the prime contractor teaming introduction, the cleared-network referral, the program office access pathway, and Congressional staff relationships.
Defense and aerospace procurement is formally governed by competitive acquisition rules: the Federal Acquisition Regulation (FAR), the Defense Federal Acquisition Regulation Supplement (DFARS), and the statutory requirements that govern how the Department of Defense awards contracts. These rules create open competition at the solicitation stage. But the decisions that determine who can compete effectively are made long before a formal solicitation is issued: which companies are known to program offices, which have been included in prime contractor teaming agreements, which have established the cleared-community credibility that gives their technical claims weight.
CSIS defense acquisition research consistently documents that the pre-acquisition phase is where program requirements are shaped, where sub-tier relationships are established, and where the informal evaluation of potential contractors happens. Companies that arrive for the first time in a final RFP are competing after the most consequential conversations have already taken place. Warm introductions are the mechanism for accessing this pre-solicitation landscape.
Granovetter’s analysis of hierarchical organisational brokerage applies directly here: program offices, prime contractors, and Congressional staffers occupy different positions in a hierarchical network where information flows through established relationships rather than open channels. The bridge connector who can translate credibility across these layers, from the commercial technology company to the program office and from the international supplier to the US teaming partner, is where the introduction value is created.
Four defense BD introduction mechanics
The prime contractor teaming introduction
Non-traditional defense suppliers and startups rarely win prime contracts directly. Most program work flows through teaming agreements in which a prime contractor (Lockheed Martin, Northrop Grumman, Raytheon Technologies, Boeing, L3Harris) assembles a coalition of sub-tier specialists to cover the full capability requirement of a bid. The gatekeeping function sits with the prime’s business development and capture teams, but program office Program Managers (PMs) often identify specific capability gaps and suggest sub-tier partners to the primes they work with. A warm introduction from an existing program participant who already holds program office credibility is the mechanism that opens the teaming conversation. Cold outreach to a prime’s BD inbox rarely converts: the prime’s capture managers maintain a stable of known and qualified subs and add new partners when a gap emerges that their existing network cannot fill. The introduction from a trusted PM or existing sub-tier contractor signals that the new company has already passed an informal technical and reliability filter.
The cleared-network referral
Security clearances create a structurally distinct professional community in defense. TS/SCI-cleared professionals often know each other across contractor and government roles through shared SCIF environments, prior service, or classified program participation. Recommending someone into a cleared environment carries implicit endorsement of trustworthiness alongside professional competence: the introducer’s own clearance-holder reputation is partially on the line. Former government officials who have transitioned into industry (retired flag officers, Senior Executive Service civilians, former Program Executive Officers) are the highest-value connectors in this mechanism. They hold active cleared-network credibility built from years of government service and simultaneously have the commercial authority to make introductions in both directions: into the government program office they came from, and into the contractor community they now work within. Defense Acquisition University (DAU) research on acquisition workforce transitions documents the structural role of former government officials in technology transfer and program introductions across the defense industrial base.
The program office access pathway
Direct access to Program Managers, Program Executive Officers (PEOs), and contracting officers is the objective of defense business development. The formal access channels, from industry days to Requests for Information (RFIs) and Sources Sought notices, are open to all respondents, but companies that arrive for the first time at a final RFP are typically too late to shape requirements or be seriously considered for sole-source or small-business set-aside provisions. Pre-acquisition engagement, guided by warm introductions from existing program participants, allows companies to interact with a program office before the procurement is formally structured. The Defense Innovation Unit (DIU) and service innovation organizations like AFWERX and NavalX create semi-formal introduction channels for non-traditional suppliers, but CSIS defense acquisition research consistently shows that the most successful non-traditional entrants combine formal innovation pathways with informal program office introductions from their existing defense network. A company known to a PM before the RFP drops has already provided the evidence of reliability and capability that a cold RFP response cannot convey.
Congressional and staff relationships
Defense appropriations and program authorization are shaped significantly by Congressional relationships, particularly through the Senate and House Armed Services Committees, the defense appropriations subcommittees, and the state congressional delegations representing defense-heavy districts in Virginia, California, Texas, Maryland, and Connecticut. Congressional directed spending (earmarks and program line-item additions) often follows from constituent relationships. A defense technology company introducing itself to a member’s Armed Services Committee staff through a state technology council, a defense-focused university partner, or an economic development office is using a legitimate relationship pathway to establish program awareness with a stakeholder who has budget authority. GAO analysis of small business innovation contracting documents the outsized role of congressional advocacy in SBIR program continuations and SBIR-to-production transitions, where champions in the relevant acquisition program office and on the oversight committees determine whether an awarded SBIR reaches procurement scale. The introduction to the congressional staff member is not a procurement influence channel but a visibility mechanism that allows program awareness conversations to happen with the appropriators who fund programs.
The defense trust environment
The cleared-community trust model
Defense contracting operates within a trust architecture that differs fundamentally from civilian B2B. Institutional affiliation is the primary credibility signal, not individual reputation or commercial track record: branch of service, career program office, clearance level, contractor lineage. A company’s portfolio of prior program experience is read as evidence of reliability in a procurement environment where contract performance data is systemically tracked in CPARS (Contractor Performance Assessment Reporting System) and Past Performance Information Retrieval System records. The introduction from a cleared colleague carries a dual endorsement: professional competence and the character reliability that the introducer has implicitly vouched for by recommending someone into their cleared professional community. This makes cleared-network introductions qualitatively different from civilian referrals: the stakes for the introducer are higher, which means the threshold for making the introduction is correspondingly higher, and a successful introduction carries proportionally more weight.
Small business programs and the SBIR pathway
The US defense acquisition system has significant structural provisions for small businesses that create distinct access pathways outside the prime contractor ecosystem: the Small Business Innovation Research (SBIR) and Small Business Technology Transfer (STTR) programs, 8(a) set-asides, HUBZone provisions, and service-disabled veteran-owned small business preferences. GAO reporting on SBIR utilization shows that Phase II-to-Phase III transitions (from R&D contract to production procurement) are the highest-value moment in the SBIR pipeline, and that these transitions most reliably happen when a company has developed a program office champion within the relevant acquisition command who advocates for the technology during the procurement planning phase. The warm introduction to the program office evaluator who administered a SBIR solicitation, or to the senior official who championed a technology during a Phase II review, is the mechanism that converts an innovation program award into a production contract. Defense-focused innovation organizations (AFWERX, DIU, SOFWERX, NavalX) function as structured introduction pathways into these program office relationships for non-traditional suppliers.
International market entry and FOCI considerations
International defense firms seeking access to US defense programs face structural barriers that have no civilian equivalent. Foreign Ownership, Control, or Influence (FOCI) review requirements, ITAR (International Traffic in Arms Regulations) registration obligations, and classified program access restrictions mean that a foreign company’s technology typically cannot participate directly in US classified procurement without a FOCI mitigation structure: a Special Security Agreement, a Voting Trust, or a proxy arrangement that places US citizens in operational control. The introduction path for international firms consequently runs through finding a US-based teaming partner who holds the relevant program relationships and clearance infrastructure, then structuring a joint venture or prime-sub relationship that allows the technology to participate on a cleared program under US governance. Defense industry associations such as the Aerospace Industries Association (AIA) and the National Defense Industrial Association (NDIA), together with allied-nation defense attaché offices in Washington, serve as the introduction brokers in this mechanism, connecting foreign companies with US partners who can structure compliant teaming arrangements.
What to include in a defense introduction brief
A defense introduction is most effective when the connector can relay specific, verifiable information to the program office or prime contractor they are bridging to. The brief prepared for the connector should cover four elements.
Technical capability and program fit
The introduction brief should specify which capability gap the technology addresses and, where possible, which specific program or program office is the relevant target. Defense BD introductions work best when the connector can describe a concrete fit rather than a general capability: "addresses the EW survivability gap in Program X" is more useful to a PM than "electronic warfare technology." If the company has responded to an RFI or attended an industry day for the relevant program, this should be noted, as it establishes that the company has done the baseline program familiarity work.
Clearance and compliance status
The brief should state the company’s clearance status (facility clearance level, personnel clearance levels), ITAR registration status, any existing government contracts and the awarding agencies, and if relevant, the FOCI mitigation structure in place. For cleared-network introductions, this information is the minimum technical threshold: a connector introducing a company that lacks the clearance infrastructure for the relevant program is creating friction, not value. Including compliance status upfront signals that the company understands the requirements of the environment it is entering.
Prior program office engagement
Existing touchpoints with the relevant program office should be included because they signal prior engagement with the formal acquisition process: RFI responses, industry day participation, SBIR awards, OTA (Other Transaction Authority) engagements, or CRADA (Cooperative Research and Development Agreement) relationships with a national laboratory. Program offices receive significant inbound interest from companies seeking access; a company that has already done the pre-acquisition work is distinguishable from a company that is seeking an introduction as a shortcut to the first formal engagement.
Specific and bounded ask
Defense BD introductions should specify whether the company is seeking a teaming conversation with a prime’s capture team, a pre-solicitation meeting with a contracting officer, or an introduction to a program office for a capability briefing. A PM’s time is highly constrained; an introduction request that arrives without a clear agenda places the work of structuring the meeting on the program office. The more specifically the ask is bounded ("a 30-minute capability briefing before the formal RFI response window for [program]"), the easier the introduction is to act on and the more likely it is to succeed.
FAQ
Defense BD warm introduction FAQs
Why do warm introductions matter in defense when procurement is governed by formal competition rules?
Defense procurement rules ensure competitive access to formal solicitations, but most program opportunities are substantially shaped before the RFP is issued. Companies that are known to a program office through prior work, industry day participation, or contractor introductions can engage during the pre-acquisition phase when requirements are still being defined. Companies appearing for the first time in a final RFP are competing after the most important conversations have already happened. Warm introductions are the mechanism for accessing pre-solicitation program office engagement: they do not bypass the formal competition but position a company to participate in the informal requirements-shaping process that precedes it.
What role do prime contractors play in introducing smaller defense companies to program offices?
Prime contractors build teaming agreements with sub-tier specialists for every major program bid. Their business development teams maintain networks of qualified subs and add new partners when a capability gap emerges. A warm introduction from an existing program participant to a prime’s capture team is the fastest path to program participation for a smaller company: the prime can verify technical credibility against a specific program requirement and, if there is a fit, make the introduction to the relevant program office at the right moment in the acquisition timeline. Primes are effective connectors because they have authentic program office relationships built on past performance, which gives their sub-tier endorsements weight with acquisition officials.
How do DIU and AFWERX work as introduction pathways for defense startups?
The Defense Innovation Unit (DIU), AFWERX, SOFWERX, and NavalX create semi-formal channels for non-traditional suppliers to engage with program offices. Their solicitation processes are designed to lower the acquisition barrier for commercial technology companies unfamiliar with defense procurement. Even within these channels, companies with prior introductions to the relevant program office evaluators, whether through portfolio company referrals from defense-focused investors, prior SBIR awards with the same office, or introductions from other DIU portfolio companies, are better positioned to shape their proposals around the program’s specific operational needs. The innovation organizations function as structured introduction brokers, but warm connections within their networks accelerate the process.
What makes an introduction to a Congressional defense staff member valuable in BD?
Congressional staff on Armed Services Committees and defense appropriations subcommittees have significant influence over program funding levels, SBIR program authorization, and directed spending provisions. An introduction from a state technology council, a defense-focused university partner, or a constituent business organization to the relevant staff member creates a program awareness channel with an appropriations stakeholder. This is not a procurement influence mechanism (contracting officers make award decisions independently), but program visibility with the Congressional staff who oversee funding for the relevant acquisition account can support SBIR-to-production transitions and program continuation advocacy when budget decisions are being made.
How should an international defense company approach the US market without direct program access?
Most international defense firms cannot participate directly in US classified programs without a FOCI mitigation structure in place. The standard entry path is to identify a US-based prime or sub-tier contractor who holds the relevant program relationships and clearance infrastructure, then build a teaming or joint venture structure that places the foreign firm’s technology under US operational control for the purposes of the program. Defense industry associations (AIA, NDIA), allied-nation defense attaché offices in Washington, and defense-specialized law firms with FOCI mitigation experience are the introduction brokers for this pathway. The goal of initial BD introductions is to find a US teaming partner before pursuing program office access. The partner’s existing relationships are the access mechanism.
Build the defense relationships that open program offices
LetsBridge connects businesses and networkers to make high-value introductions happen, including in the defense and aerospace sector.