Restructure Your Capture Strategy for DoD Portfolio Acquisition

The Department of Defense's shift to Portfolio Acquisition Executives, outcome-based requirements, and OTA-first buying demands a fundamentally different capture strategy from every contractor in the federal market. If your BD cadence is still organized around recompete cycles with rotating contracting officers and specification-based SOWs, you are building pipeline on a foundation that DoD is actively demolishing.

The 2024-2025 Acquisition Transformation Strategy isn't a memo that will gather dust. It consolidates decision authority under PAEs, assigns contracting officers to portfolios for four or more years, and directs program offices to prefer Other Transaction Authority vehicles over traditional FAR Part 15 competitions. The old model, where you built a relationship with a CO for 18 months before they rotated to a different program, is being replaced by something that rewards sustained performance and punishes short-term BD sprints.

This article walks through exactly what these changes mean for your capture process, your past performance library, your proposal structure, and your quarterly BD plan. If you restructure now, you gain a 12 to 18 month advantage over competitors still running the old playbook.

What PAEs Actually Change About Who Decides and How Long They Stay

A Portfolio Acquisition Executive is not just a renamed program executive officer. PAEs hold consolidated decision authority across multiple program lines within a capability portfolio. Instead of six separate program offices each managing their own acquisitions with different contracting officers, a PAE oversees the portfolio and ensures acquisition decisions align with mission outcomes across the entire capability set.

The practical effect on contractors is immediate. COs assigned to a PAE's portfolio carry minimum four-year tenures. This eliminates the rotation pattern that defined DoD contracting for the last two decades. Under the old model, a CO would cycle into a program, manage one or two recompete actions, then rotate out. You could survive a mediocre performance period because the next CO wouldn't have firsthand memory of it.

That safety net is gone. A CO with a four-year assignment will remember that your team missed three CDRLs in Q2 of year one. They will also remember that your competitor's team delivered an unsolicited capability brief that solved a real operational gap. Relationship depth compounds over multi-year tenures, and the contractor who invests early captures disproportionate trust.

The bottom line: your BD team can no longer treat CO relationships as disposable assets that reset every procurement cycle.

Reframing Past Performance: Mission Outcomes Over Deliverables

DoD's move toward outcome-based requirements doesn't just change how solicitations are written. It changes how evaluators read your past performance volume. A CPARS narrative that says "delivered 47 servers on schedule and under budget" tells an evaluator you can manage logistics. It says nothing about whether you solved a mission problem.

Under outcome-based evaluation, the same performance needs to read like this: "Reduced INDOPACOM sensor-to-shooter latency by 38% across 3 combatant commands by deploying 47 edge-compute nodes integrated with existing C2 infrastructure." Same contract. Same deliverables. Entirely different evaluation impact.

The framework for rewriting past performance is straightforward but requires effort. For each citation, identify three elements: (1) the operational problem the contract addressed, (2) the measurable change in mission capability your work produced, and (3) the scope of military impact (number of users, combatant commands, or operational theaters affected).

If your original SOW was specification-based and never mentioned mission outcomes, you still have the data. Pull it from program reviews, CDRLs, user feedback, and quarterly performance reports. Interview your program managers and task leads. The mission impact existed even if the contract didn't measure it explicitly. Your job is to reconstruct and document it.

For teams managing large past performance libraries, a structured content reuse system makes the difference between rewriting five citations in a week and spending three months tracking down retired PMs for outcome data.

OTA-First Buying: How Traditional Contractors Get In the Door

Other Transaction Authority agreements (10 U.S.C. 4021-4022) bypass FAR Part 15 entirely. No formal RFP. No sealed bidding. No mandatory LPTA evaluation. DoD's transformation strategy explicitly directs acquisition professionals to prefer OTAs for prototype and follow-on production when the authority applies.

For traditional contractors who have spent decades building FAR-based proposal machines, this feels like the ground shifting under their feet. But the entry path is more accessible than most BD leaders assume.

The primary on-ramp is consortium membership. Organizations like NSTXL (National Security Technology Accelerator), SOSSEC (System of Systems Consortium), and the Space Enterprise Consortium serve as intermediaries. DoD posts requirements to the consortium. Members respond with brief solution proposals (typically 10 to 20 pages, not 500-page FAR Part 15 volumes). The consortium manages evaluation and award.

If your company has never executed a prototype agreement, you can still qualify. Most consortia require only a capability statement, a technology focus area alignment, and annual membership fees ranging from $2,500 to $25,000. You do not need prior OTA experience. You need a relevant technical capability and the willingness to respond to consortium-posted opportunities in compressed timelines (often 30 days or less).

The critical strategic point: a prototype OTA win creates a legal pathway to production awards without competition. This means the contractor who captures the prototype position owns the follow-on. Waiting for a traditional recompete on a program that started as an OTA prototype is waiting for a competition that may never happen.

Modular Open Systems: Why Proprietary Lock-In Now Kills Your Score

The Modular Open Systems Approach (MOSA) mandate under 10 U.S.C. 4401 requires DoD programs to design systems with open interfaces, widely supported standards, and modular architectures. This isn't aspirational guidance. It is law, and evaluators are trained to score against it.

Here is what happens when you ignore MOSA: a mid-tier defense contractor held a $200M sustainment contract for an ISR processing system. When the recompete dropped, the solicitation included MOSA evaluation criteria weighted at 15% of the technical score. The incumbent's architecture used proprietary data formats and unpublished interface specifications. Their proposal could not credibly demonstrate MOSA compliance. They lost the recompete to a competitor who offered an architecture built on published APIs and government-owned interface control documents.

To audit your current solutions, map each major system against these compliance attributes:

• Published interface specifications: Are your APIs documented in government-accessible ICDs?
• Widely supported standards: Do your data formats use open standards (JSON, XML, NATO STANAG) or proprietary encodings?
• Modular decomposition: Can the government replace your component with a competitor's without re-engineering adjacent modules?
• Government data rights: Does the government hold sufficient technical data rights to enable future competition at the module level?
• Conformance verification: Can you demonstrate compliance through testing, not just assertion?

If your current solutions fail two or more of these attributes, you need a MOSA remediation plan before your next pursuit. Creating compliance artifacts that demonstrate open architecture conformance is now as critical as traditional Section L/M compliance.

Rebuilding Your BD Cadence for Tenured CO Relationships

The old BD model was episodic. You surged engagement 12 months before a recompete, built relationships during the pre-solicitation phase, then retreated after award until the next cycle. With four-year CO tenures, this burst pattern is not just inefficient; it is visible and transparent to the CO. They know who shows up only when money is on the line.

The new cadence requires continuous value delivery. Specific activities that compound over multi-year CO relationships:

• Quarterly capability briefings aligned to the PAE's portfolio priorities, not your company's product catalog
• White papers addressing specific operational gaps the CO's programs face, submitted unsolicited and unclassified
• Industry day attendance with prepared follow-through: not just showing up, but delivering a written response to the CO's stated challenges within 10 business days
• Prototype demonstrations using internal R&D funding to prove concepts before the government spends money

Track CO relationship depth as an actual capture metric. Contact frequency alone is meaningless. Score each relationship on a five-point scale: (1) CO knows your company name, (2) CO can describe your relevant capabilities, (3) CO has seen a demonstration of your work, (4) CO has referenced your capability in internal planning documents, (5) CO has provided informal feedback on your technical approach. If your top three pursuits are all at level 1 or 2, your capture position is weaker than you think.

Restructuring Proposals for Outcome-Based Evaluation Criteria

Outcome-based Section M criteria change what evaluators are looking for. Instead of "does this proposal comply with every SOW paragraph," the question becomes "will this contractor actually solve the mission problem." That shifts the evaluation from compliance checking to solution credibility.

Your proposal structure must reflect this. Lead with the operational concept and mission thread. Show the evaluator how your solution fits into the warfighter's workflow from alert to action. Then demonstrate technical approach. Then map compliance.

This does not mean your compliance matrix becomes irrelevant. It means the compliance matrix shifts from the primary organizing principle of your proposal to a secondary validation artifact. Evaluators still verify compliance, but they evaluate the proposal on mission impact first.

Here is a concrete restructuring example. A traditional proposal volume for a C4ISR integration contract might organize sections as:

1. SOW paragraph 3.1.1 compliance response
2. SOW paragraph 3.1.2 compliance response
3. Technical approach summary
4. Management approach

An outcome-based restructuring of the same proposal:

1. Mission thread: how our solution reduces the kill chain timeline from 47 minutes to 12 minutes
2. Operational concept of employment across INDOPACOM theater
3. Technical approach with architecture decisions mapped to mission outcomes
4. Compliance traceability matrix (appendix, demonstrating full SOW coverage)

The evaluator reads the same information. But the first structure makes them hunt for the "so what." The second structure answers it in the first three pages.

Frequently Asked Questions

Do PAE changes apply to all DoD acquisitions?

Not yet. PAE authority is rolling out by portfolio, with initial implementation focused on major capability areas like command and control, ISR, and electronic warfare. But the CO tenure mandates and outcome-based evaluation trends apply broadly across DoD, and the direction is clear for all services.

Can small businesses compete under OTA vehicles?

Yes. Most OTA consortia actively recruit small businesses, and many DoD OTA solicitations include small business evaluation preferences. The compressed proposal format (10 to 20 pages) actually reduces the barrier for small firms that lack large proposal staffs.

How do I rewrite past performance if my CO won't update CPARS?

You cannot change the CPARS narrative itself without CO cooperation. But your proposal's past performance volume is where you control the story. Use the past performance citation to provide context, explain mission impact, and connect deliverables to operational outcomes. Evaluators read both CPARS and your narrative.

Does MOSA compliance matter for services contracts?

Increasingly, yes. Even services-heavy contracts for software development, systems engineering, and IT modernization now include MOSA criteria when the work product involves system interfaces or data architectures.

Your 90-Day Capture Strategy Migration Plan

Weeks 1-2: Pipeline Audit. Classify every active pursuit in your pipeline as traditional FAR, OTA-eligible, or hybrid. For each OTA-eligible pursuit, identify the relevant consortium and determine your membership status. If more than 40% of your pipeline is OTA-eligible and you have zero consortium memberships, you have an urgent gap.

Weeks 3-4: Past Performance Rewrite. Take your top five past performance citations and rewrite them in outcome-based format. For each citation, identify the operational problem, the measurable mission impact, and the scope of warfighter benefit. If you cannot find outcome data, schedule interviews with former PMs and task leads.

Weeks 5-8: Consortium Entry. Join at least one relevant OTA consortium. Submit your capability statement. Assign a BD lead to monitor consortium-posted opportunities weekly. Set an internal SLA: any relevant consortium posting gets a go/no-go decision within 72 hours.

Weeks 9-12: PAE Engagement. Identify the PAE-assigned COs for your top two to three active pursuits. Prepare outcome-focused capability packages (not generic company overviews) and request briefing opportunities. Track each CO relationship on the five-point depth scale described above.

The metric to track starting this week: percentage of active pursuits with outcome-based past performance narratives versus deliverable-based narratives. If that number is below 50% by day 90, your capture strategy hasn't actually migrated.

The contract you won last year under the old rules is not the contract you will win next year. DoD is not waiting for you to catch up. The contractors who restructure their capture cadence, rewrite their past performance, join OTA consortia, and build tenured CO relationships in the next 90 days will own the competitive positions that define the next decade of defense spending. The ones who wait for the old FAR Part 15 RFP to drop will be waiting for a solicitation that increasingly will never come.