Defense Market Playbook, Part 1: Reading the Defense Buyer — Programs, Budgets, Decision-Makers

The defense market does not reward generic enterprise selling. The buyer is a programme office, not a procurement department; the budget is legislated, not allocated by a CFO; the decision is a committee outcome, not a signature. Most commercial vendors lose their first three defense pursuits because they read the buyer wrong — they pitch to the wrong stakeholder, qualify the wrong budget, and discover the kill-switch only after submitting a proposal. This four-part series is the business-side walkthrough paired with our Defense Market pillar. Part 1 teaches you how to read the buyer before you write a single page of capture material.

The architectural framing is in The Complete Guide to Defense Procurement. For the European budget context referenced below, see EU Defense Tech and the EDTIB and JADC2 for European Vendors. The product-side counterpart to this playbook is the cybersecurity stack series and the C2 build series — read those once you have a live opportunity, not before.

How to Read a Defense Program Budget

Defense budgets are public documents written in a private dialect. Reading them well is the single highest-leverage skill in defense business development. A vendor that reads budgets accurately knows, eighteen months before the RFP drops, which programs have real money, which programs are political theatre, and which programs are about to be cancelled. A vendor that reads budgets poorly chases white papers for two years and books no revenue.

The three budget instruments worth knowing:

• US Program Budget (PB). The President's Budget submission to Congress, published every February. The PB documents are organized by appropriation (RDT&E, Procurement, O&M) and by line item (P-1, R-1, O-1). Each line item has a five-year funding profile. A "live" line is one with funding rising in the out-years and a named Program Element (PE) you can trace to a programme office. A "dying" line shows flat or declining out-year funding and is often cancelled in the next budget cycle.
• NATO Defence Planning Process (NDPP). NATO's four-year capability-targeting cycle. Member nations agree Capability Targets; those targets cascade into national budget submissions. The published NDPP outputs are political documents — the operational signal is which Capability Targets a nation has accepted and which it has flagged as "with reservations". The latter rarely produces near-term procurement.
• EU EDF and ASAP allocations. The European Defence Fund publishes annual work programmes; ASAP (Act in Support of Ammunition Production) and EDIRPA top up specific gaps. EDF money is grant-style co-funding, not direct procurement — a winning EDF project does not automatically become a national contract. Read the work programme call topics as signals about national pull, not as buy orders.

The discipline: never pursue a programme without a traceable funding line. If you cannot point to the appropriation, the PE, the fiscal year, and the dollar amount, you are pursuing aspiration. Aspiration is fine for white papers; it is not fine for capture investment.

The Stakeholder Map

A defense purchase is the output of a committee. The committee is informal, distributed, and rarely meets in the same room — but every member can stop the deal. Mapping the committee before the pursuit starts is non-optional.

The five roles every defense pursuit has, under different national job titles:

• Program Manager (PM). Owns the programme's cost, schedule, and performance. The PM wants the capability delivered, on time, without political risk. The PM is the buyer in the sense that matters — without PM sponsorship, nothing moves.
• Contracting Officer (KO). Owns the legal instrument. In the US, only a warranted KO can obligate funds. The KO is procedurally neutral and protects the procurement record; in practice, an unhappy KO can slow a deal by months through clarifying questions and amended timelines.
• End-User / Operator. The unit or operator who will use the capability. Their voice — sometimes routed through user juries, sometimes through requirements documents — determines whether the delivered product is accepted in the field. Vendors who never speak to operators ship products operators reject.
• Requirements Officer (J5/J8 equivalents). The staff officer who writes and defends the capability requirement. Influencing the requirement before it is published is the highest-leverage activity in defense capture — done within the legal and ethical lines covered later in this article.
• Test & Evaluation (T&E) lead. The technical authority who certifies that a delivered product meets the requirement. T&E can silently kill a deal post-award by stretching the test schedule. Bring T&E into the conversation early and you will find the test plan is built around your strengths, not your weaknesses.

The kill-switch role varies by programme. In a US ACAT II programme, the PM dominates. In a European cooperative programme, the requirements officer dominates because the requirement is a treaty-level document. In a Ukrainian rapid-acquisition programme, the operator dominates because the war shortens the decision cycle. Learn which role holds the switch before you allocate capture budget.

Country-Specific Buying Structures

The org chart of the buyer is the map of the pursuit. The five most-relevant defense buyers for European-aligned vendors, with the structures that determine where contracts actually originate:

• United States — PEO / PM structure. Acquisition runs through Program Executive Offices, each containing multiple Program Management offices. PEO Soldier, PEO C3T, PEO IEW&S inside the Army; analogous structures in the other services. The PM owns the programme; the PEO owns the portfolio; the Component Acquisition Executive owns service-level priorities. Selling to the US means selling to a specific PM, not to "the Army".
• France — DGA (Direction Générale de l'Armement). Centralised acquisition agency under the Ministry of the Armed Forces. DGA combines requirements, acquisition, and test under one roof — a structural advantage for coherent capability development and a structural disadvantage for vendors used to lobbying separate offices. Programme directors inside DGA are the equivalent of US PMs.
• Germany — BAAINBw (Bundesamt für Ausrüstung, Informationstechnik und Nutzung der Bundeswehr). The Federal Office for Bundeswehr Equipment, IT and In-Service Support. BAAINBw handles acquisition and through-life sustainment for the Bundeswehr. The procurement process is famously thorough; vendors expect long timelines and documented compliance with German constitutional law (Article 87a constraints on military procurement).
• United Kingdom — DE&S (Defence Equipment & Support). Bristol-headquartered acquisition agency for the UK MoD. Delivery Teams inside DE&S are the equivalent of US PMs. The UK Front Line Commands (Army, Navy, Air, Strategic Command) own the requirement; DE&S owns the delivery. The split matters — DE&S cannot change a requirement, only deliver against it.
• Ukraine — DOT / AT-AT and the Brave1 stack. The Defence Procurement Agency (DPA) and the State Operator of the Rear / armament directorates (AT-AT) run procurement; Brave1 surfaces innovation pull from operators. Decision cycles compress dramatically under combat pressure. Operator feedback feeds requirement changes within weeks. See the Brave1 ecosystem guide for the live picture.
• Poland — AU (Agencja Uzbrojenia). The Armament Agency, established to consolidate Polish military procurement. AU centralises what was previously distributed across the Inspectorate of Armed Forces Support and the Armament Inspectorate. Polish procurement post-2022 has been the fastest-moving in NATO; AU's project teams are the entry point.

Spotting a Live Opportunity

Most pre-RFP signals are noise. The skill is separating real-budget signals from fishing expeditions.

Sources Sought notices. A Sources Sought is the procurement office asking the market whether qualified suppliers exist. A real Sources Sought references a specific programme element, names the contracting office, and includes a narrow capability description. A fishing Sources Sought is broad, generic, and references no programme. Real Sources Sought tend to be followed by an RFI within 60–120 days.

Requests for Information (RFI). An RFI is the office asking detailed technical questions. A real RFI follows a real Sources Sought, asks for solution architecture, pricing ROM, and past performance, and gives respondents 30–45 days. A fishing RFI is unfocused and gives respondents 90+ days because no one is waiting for the answers.

Industry Days. An Industry Day with the PM in the room and a published draft requirement is high-signal. An Industry Day with only the procurement office in the room and no draft requirement is theatre.

Whitepaper requests with no budget reference. These exist to feed staff studies. They produce no contracts. Respond if the work is cheap and the relationship value is real; do not invest capture budget against them.

The calibration heuristic: tie every signal back to a budget line. If the Sources Sought maps to a funded PE, it is real. If it does not, it is a future bet at best.

Capture Discipline — Bid/No-Bid Scoring

Disciplined defense vendors run a written bid/no-bid scoring rubric before committing capture investment. The rubric prevents emotional pursuits — the kind that consume engineering hours, distract leadership, and lose on day-one factors that were knowable up front.

A defense-grade rubric scores six factors on a 1–5 scale:

• Programme fit. Is the funding real, in the right fiscal year, in the right appropriation? Is the procurement strategy compatible with your business model (sole-source, full-and-open, IDIQ task order, OTA)?
• Capability fit. Does your existing product meet 70%+ of stated requirements? Below 60%, you are not bidding — you are funding R&D at your own expense in the hope of award.
• Competitive position. Who are the incumbents and likely competitors? Do you have a discriminator — past performance, technology, price, schedule — that survives evaluation?
• Past performance. Do you have a relevant past performance reference at the right contract size, complexity, and classification level? Without it, your evaluation score is capped regardless of technical merit.
• Capacity. Can you actually execute if you win? Capture-and-fail-to-deliver is the worst possible defense outcome — it damages past performance for every future bid.
• Strategic value. Does the win open a market, a customer, or a capability area? A low-margin win in a strategic account beats a high-margin win in a one-off.

A typical threshold: average score above 3.5 with no factor below 2 — pursue. Average 2.5–3.5 — pursue selectively with a capped capture budget. Below 2.5 — no-bid and document the reasoning so the same opportunity is not re-litigated three months later.

Relationship Capital — Without Crossing Lines

Defense relationships compound over years. They also operate under tight legal constraints once a solicitation is in the air. Effective vendors invest heavily in pre-RFP engagement and disengage cleanly when the rules change.

Pre-solicitation engagement (lawful and expected). Industry Days, programme briefings to contractor associations, conference panels, capability demonstrations, draft-RFP comment periods, technical exchanges hosted by the requirements office. All of this is on the record and encouraged. Show up, listen first, contribute substance.

Post-solicitation engagement (constrained). Once the RFP is issued, contact with the Contracting Officer (and only the KO) is permitted through the formal Q&A channel. Direct contact with the PM, the requirements office, or operators is generally prohibited and can result in disqualification. In the US this is governed by FAR Part 3 (Improper Business Practices) and FAR Part 15 (negotiated acquisitions). In the EU, equivalent provisions are in the Defence and Security Procurement Directive (2009/81/EC) and national implementing regulations.

The clean-disengagement discipline. The moment a solicitation drops, capture leads brief every customer-facing employee on the new rules. Calendar invites are cancelled. Conference small-talk is constrained. The cost of an inadvertent FAR Part 3 violation is the deal plus reputational damage that follows the company for years.

From Listening to Influencing Requirements

The most underused legitimate influence vector in defense capture is the Sources Sought response. Procurement offices write Sources Sought to learn from industry; substantive responses shape what becomes the requirement.

What a high-leverage Sources Sought response does:

• Validates the programme office's mental model on the points where you agree, with named technical references. Validation builds the office's confidence in their own draft.
• Challenges specific assumptions where industry knows the office has a gap — typically integration complexity, sustainment cost, classification handling, or schedule realism. Challenge with evidence, not opinion.
• Introduces evaluation criteria that favour proven approaches over speculative ones. Sections L (instructions to offerors) and M (evaluation factors) of the eventual RFP are partly built from Sources Sought inputs. Influence them before they are written.
• Surfaces qualified-supplier diversity. Procurement offices nervous about a thin market often relax restrictive clauses once Sources Sought responses show real competition exists. If you want a clause relaxed, demonstrate that relaxing it produces more bidders, not fewer.

White papers and RFI responses are the same instrument at higher fidelity. A 6–10-page white paper, submitted unsolicited but on-topic, lands on the PM's desk and shapes the next iteration of the requirement. It is the defense business analogue of a well-targeted technical disclosure — modest investment, asymmetric upside, fully within the rules.

What's Next

Part 1 has built the buyer-reading foundation. You can now triage a programme budget, identify which committee role holds the kill-switch, name the right acquisition agency, separate real signals from fishing, and influence a draft requirement without crossing legal lines. The next step is mechanical: turning that read into a winning proposal.

Part 2 walks through RFP and RFI mechanics — from Sources Sought response to colour-team reviews to compliant submission. The practical operating model that converts a well-read opportunity into an executed contract.