Defense Market Playbook, Part 2: RFP/RFI Mechanics — From Sources Sought to Submission

Part 1 mapped the buyer. Part 2 maps the machine the buyer runs to acquire. The defense solicitation lifecycle is structured, regulated, and unforgiving of vendors who improvise. Vendors who read the machine correctly compete on substance; vendors who do not get filtered out before evaluators read a single technical sentence. Part 2 walks through the lifecycle, the documents, and the disciplines that turn a qualified opportunity into a submitted, scoring proposal.

The pillar-level framing is in The Complete Guide to Defense Procurement; the deeper RFP-to-contract mechanics in Defense Procurement: From RFP to Contract.

The Solicitation Lifecycle

The defense solicitation flows through eight predictable stages: Sources Sought, Request for Information (RFI), Draft RFP, Final RFP, Q&A period, Submission, Source Selection, and Award. Each stage has a different purpose, a different audience, and a different optimal vendor behaviour. Treating them as interchangeable wastes effort and signals inexperience to the contracting officer.

Sources Sought is market research. The buyer is testing whether a competitive pool exists, whether small-business set-asides are viable, and whether the requirement as drafted is procurable. Responses are short, capability-focused, and explicitly non-binding. Vendors who skip Sources Sought give up the earliest opportunity to shape the requirement language.

RFI is deeper market research. The buyer asks specific questions about technical feasibility, pricing ranges, schedule realism, and risk. RFI responses inform whether the programme proceeds, how it is structured, and what evaluation criteria the final RFP will use. RFI is also where vendors educate the buyer on what good looks like.

Draft RFP is the buyer's first attempt at a procurable document. It is circulated for industry comment. Vendors who comment substantively — pointing out ambiguous requirements, infeasible schedules, evaluation criteria that bias toward one solution — shape the final RFP. Vendors who stay silent inherit whatever the draft becomes.

Final RFP is the procurement instrument. Section L tells vendors what to submit. Section M tells evaluators how to score. The Statement of Work (SOW) or Performance Work Statement (PWS) defines the scope. The contract data requirements list (CDRL) defines the deliverables. The clauses define the legal terms.

Q&A period is structured clarification. Vendors submit written questions; the contracting officer publishes answers to all bidders simultaneously. Questions reveal what vendors do not understand, so phrase them carefully — competitors read every answer.

Submission is the proposal lodged through the designated portal by the designated deadline in the designated format. Late, mis-formatted, or non-compliant submissions are rejected without evaluation. The contracting officer has no discretion here.

Source Selection is the evaluation phase. The Source Selection Evaluation Board (SSEB) scores proposals against Section M. The Source Selection Authority (SSA) makes the award decision based on the SSEB's findings and the source selection plan. Discussions, BAFO rounds, and clarifications may occur.

Award is the contract action. The winning vendor is notified; debriefs are offered to unsuccessful vendors; protest windows open.

The regulatory framework differs by jurisdiction. US Federal Acquisition Regulation (FAR) Part 15 governs negotiated procurements; FAR Part 12 handles commercial items; FAR Part 13 handles simplified acquisitions. EU directive 2014/24/EU sets the open, restricted, competitive-dialogue, and innovation-partnership procedures used by EU member-state defense buyers. National variants — Germany's VgV, Poland's PZP, France's Code de la commande publique — add member-state-specific rules. NATO procurement (NSPA, NCIA) follows its own Bi-SC procurement directives. The lifecycle stages are recognisable across all of them; the document names and timelines vary.

Small and medium vendors win at the front end of the lifecycle (Sources Sought, RFI, Draft RFP comments) by shaping the requirement, and lose at the back end (submission, evaluation) when they treat the proposal as a writing exercise rather than a compliance and scoring exercise.

Reading Section L (Instructions) and Section M (Evaluation Criteria)

Two sections of the RFP matter more than the rest combined. Section L tells you what to submit, in what order, in what format, at what length. Section M tells you how the evaluators will score it. The pairing is the entire game.

Section L is procedural. It specifies volumes (Technical, Management, Past Performance, Cost), page limits per volume, font sizes, margin widths, graphics rules, file formats, submission medium, and the order in which information must appear. Violating Section L produces compliance findings; serious violations get the proposal rejected before substantive evaluation.

Section M is substantive. It lists evaluation factors (typically Technical Approach, Management Approach, Past Performance, Cost/Price), the sub-factors under each, the relative weighting, and the adjectival rating scale (Outstanding, Good, Acceptable, Marginal, Unacceptable, or numeric equivalents). It also specifies the source-selection methodology — best value tradeoff, lowest-price technically acceptable (LPTA), or a hybrid.

The discipline that wins is traceability: every paragraph of the proposal traces to a specific Section M factor or sub-factor, and every Section M criterion is addressed somewhere in the proposal. Most losing proposals fail here. They are well-written, technically credible, and partially non-responsive — they answer questions the evaluators did not ask while missing questions the evaluators did ask. The compliance matrix that maps Section L requirements and Section M criteria to specific proposal paragraphs is the single highest-leverage proposal artefact.

Evaluators score against Section M. They do not score against vendor brilliance, vendor history, or vendor preference. Proposals that respect this constraint compete; proposals that ignore it self-eliminate.

The Capture Plan

Proposal writing is the visible part of winning. Capture is the invisible part. Capture management is the structured pre-RFP discipline that decides whether the proposal has any chance before drafting starts.

The capture plan covers seven things. Customer intimacy — who in the buying organisation cares about this, what they believe is true, what they fear, what they prefer. Competitive analysis — who else is bidding, what their likely solution is, what their weaknesses are. Win themes — three to five sentences that the proposal will reinforce throughout, each tied to a Section M factor and a buyer concern. Ghosting — the discipline of highlighting competitors' weaknesses without naming them, by emphasising attributes the buyer values that competitors lack. Value proposition — the quantified statement of what the buyer gets that they would not get from anyone else. Pricing-to-win analysis — the target price range that wins the tradeoff, derived from competitive analysis and buyer budget. Teaming strategy — who fills capability gaps, who provides past performance, who improves the political optics.

Capture-as-code means the capture plan is a versioned document reviewed and updated at gate reviews. Pursue / no-pursue, bid / no-bid, and pricing-to-win decisions are explicit, recorded, and reviewed against competitive intelligence at every gate. Organisations that run capture as code win at materially higher rates than organisations that run it as folklore.

Teaming and Sub-Contracting

Few defense vendors bid alone. Teaming agreements allocate work shares, capability responsibilities, and exclusivity. The choices are consequential.

Prime vs sub. Leading the prime carries the contract risk, the customer relationship, and the past-performance credit. Subcontracting reduces risk and capital requirements but limits past-performance build-up and customer access. New entrants typically sub first to build past performance, then prime later.

Exclusivity clauses. Teaming agreements often include exclusivity — the sub commits to bid only with this prime on this opportunity. Exclusivity is leverage; over-committing exclusivity across multiple potential primes is reputationally damaging. Read the clauses before signing.

Capability gap fill. The teaming strategy maps Section L and Section M requirements to vendor capabilities; gaps are filled by adding teammates. Adding a teammate purely for past performance, with no real role, is increasingly visible to evaluators and increasingly counterproductive.

When to lead, when to sub. Lead when the requirement is in your sweet spot, you have customer access, and you can carry the cost-share or financing burden. Sub when the requirement is adjacent to your sweet spot, the prime has the customer relationship, and you need the past performance record. The deeper criteria are in Becoming a NATO Subcontractor.

Past Performance Storytelling

Past performance is the evaluation factor where new entrants struggle and incumbents coast. The buyer is asking: have you done something like this before, for someone like us, recently enough that it matters, well enough that the customer would hire you again?

In the US, the Contractor Performance Assessment Reporting System (CPARS) is the federal record. Each completed contract generates a CPARS rating — Exceptional, Very Good, Satisfactory, Marginal, Unsatisfactory — across quality, schedule, cost control, management, and small-business participation. CPARS records are visible to other contracting officers and carry significant weight. National equivalents exist: the UK's Supplier Relationship Management framework, EU member-state contractor-performance registries, NATO's NSPA contractor database.

Small vendors and new entrants build a past-performance narrative through three moves. First, commercial-adjacent references — contracts that demonstrate the same capability for non-defense buyers, framed in defense-relevant terms. Second, subcontracting credit — primes can attest to sub performance in a way that becomes admissible past performance for the sub. Third, individual-level performance — key personnel with documented prior defense experience can supplement organisational past performance, especially for smaller contracts.

The discipline is to write past performance entries the same way the evaluator will read them: scope, scale, complexity, recency, relevance to this RFP, and customer-confirmable outcomes. Vague past-performance writeups score poorly even when the underlying work was excellent.

Proposal Structure that Wins

Compliant proposals follow Section L. Winning proposals follow Section L and tell a coherent story.

Executive Summary discipline. Two to four pages that state the win themes, the value proposition, and the highest-confidence Section M responses. Evaluators read the Executive Summary first and use it to calibrate expectations for the rest. A weak Executive Summary depresses scoring across the entire proposal.

Technical Approach traceability. Every Section M technical sub-factor gets a labelled section. Each section opens with a Section M citation, states the approach, evidences feasibility, identifies risks, and proposes mitigations. Graphics that summarise the approach earn evaluator time; walls of text lose it.

Management Approach. Programme governance, key personnel, schedule realism, risk management, quality management, subcontract management. The management volume is where many proposals reveal that the team has never actually run a programme of this size.

Key personnel commitments. Named individuals, signed letters of commitment, evidence that they will actually be available at award. Substituting key personnel post-award without buyer concurrence is one of the fastest paths to a poor CPARS rating.

Color-team review. Pink team reviews the storyboard and outline before drafting. Red team reviews the first complete draft against Section M as if scoring. Gold team reviews the final draft for executive-quality polish and price reasonableness. Each review catches different defects; organisations that skip reviews submit proposals that the buyer's evaluators will themselves red-team in scoring.

The Submission Window

The final 72 hours of a proposal cycle are where preventable disasters happen. The disciplines that prevent them are mundane and high-leverage.

Final pricing review. The cost volume is reconciled against the technical and management volumes — labour categories, labour hours, materials, travel, ODCs, indirect rates, fee. Pricing that does not reconcile to the technical approach signals either a flawed estimate or a flawed approach; evaluators flag both.

BAFO discipline. If the buyer opens discussions and requests Best and Final Offer, the BAFO is a new pricing event with its own rules. Treat it as a structured re-pricing — not a panicked discount — and document the rationale for the change. BAFO discipline is also covered in Part 3 of this series on Pricing, Cost Accounting, and DCAA-Equivalent Compliance.

Mandatory clauses. Defense RFPs incorporate clauses by reference — DFARS, FAR, NATO AQAP, ITAR, export-control, cybersecurity (CMMC, AQAP 2110, ISO 27001). Compliance with mandatory clauses is binary; a non-acceptance of any mandatory clause is non-responsive. The relevant clauses for European programmes are detailed in NATO AQAP 2110 for Software Vendors and, for ITAR posture, in ITAR-Free Defence Software.

Electronic submission platforms. US: SAM.gov for opportunity discovery, PIEE / Procurement Integrated Enterprise Environment and contract-specific portals for submission. EU: TED (Tenders Electronic Daily) for publication; member-state e-procurement portals for submission (Germany's e-Vergabe, Poland's miniPortal/Platforma e-Zamówień, France's PLACE). NATO: NSPA's eProcurement portal. Each platform has its own account-provisioning lead time, upload size limits, and submission-confirmation mechanism. Account provisioning that should take an hour can take two weeks on first attempt — never leave it to the final day.

What's Next

Part 2 has built the submission machine. Solicitation-lifecycle awareness, Section L/M traceability, capture discipline, teaming strategy, past-performance storytelling, proposal structure, and submission-window mechanics. A proposal built on these foundations is competitive on substance — which means the next discipline matters: pricing it correctly.

Part 3 covers pricing, cost accounting, and DCAA-equivalent compliance — how defense buyers expect prices to be built, the indirect-rate structures that survive audit, and the cost-accounting disciplines that distinguish auditable vendors from the rest.