The BD-to-Capture Lifecycle: How Defense Contractors Win Before RFP Drop

Here's the uncomfortable truth about winning defense contracts: the proposal is not where you win. It's where you document why you already should. Strong capture teams in GovCon (government contracting) put much of their time and money into what happens before the solicitation drops: understanding the customer's real problem, shaping requirements to favor their approach, and disqualifying competitors before source selection begins.

This is the BD-to-capture lifecycle, and mastering it is what separates teams that win regularly from teams that mostly write losing proposals.

This article is a companion to our pillar guide: Breaking Into GovCon: The Complete Guide for Defense Contractors.

The Five Stages of the BD-to-Capture Lifecycle

A quick caveat: the timelines and percentages in this post are common industry rules of thumb, not data or requirements. They vary a lot by company, customer, and contract size, so treat them as starting points.

Stage	Typical Timeline Before Award	Key Activities	Go/No-Go Criteria
1. Identify	24–36+ months	Market scanning on SAM.gov, GovWin, Bloomberg Government; agency budget analysis; expiring contract research; FOIA requests; industry day attendance	Is this in our target market? Does it align with our capabilities and strategic plan? Is the opportunity large enough to justify pipeline entry?
2. Qualify	18–24 months	Customer engagement; pWin (probability of win) assessment; competitor analysis; go/no-go gate review with leadership; initial teaming conversations	Do we have a realistic shot (pWin > 25%)? Can we meet minimum qualifications? Do we have customer access? Is the customer's budget confirmed?
3. Shape	6–18 months	Active customer engagement; RFI (Request for Information) responses; solution development; teaming agreements; influencing the Statement of Work (SOW); competitive intelligence; Black Hat reviews	Are we shaping requirements to our strengths? Is our pWin improving? Have we confirmed our team and solution? Do we have a credible win strategy?
4. Propose	30–90 days (RFP period)	Proposal kickoff; compliance matrix; storyboarding; color reviews (Pink, Red, Gold); pricing/cost volume; past performance write-ups; final submission	Are we compliant with Section L? Does every section map to Section M evaluation factors? Is our price competitive? Have we passed Red Team review?
5. Close	Post-submission (30–180 days)	Oral presentations (if required); Evaluation Notices (ENs) / discussions; Final Proposal Revisions (FPR); award; debriefs	Are we responding to ENs with evidence, not arguments? Did we win? If not, what did the debrief tell us about our next pursuit?

Stage 1: Identify. Building a Pipeline That Matters

Business development (BD) begins with pipeline management. A pipeline is simply a list of future contract opportunities you're tracking, with probability weights, expected award dates, and estimated contract values. The pipeline tells you where your revenue is coming from and where you need to invest.

A common rule of thumb is to keep a pipeline worth 3–5x your annual new-award target. For example (hypothetical): if you need $10M in new contract awards this year, you'd want $30M–$50M of qualified opportunities in your funnel at various stages. Why so much? Because nobody wins every bid, and some opportunities slip, get cancelled, or change shape before the RFP drops.

Where do you find opportunities? The primary sources:

• SAM.gov: The government's official solicitation portal. Set up saved searches by NAICS code, agency, and keyword. Monitor it daily.
• USASpending.gov: Track existing contract awards to understand who buys what, from whom, for how much, and when contracts expire.
• GovWin IQ (from Deltek) / Bloomberg Government: Commercial tools that aggregate early-stage pipeline data, including opportunities that aren't on SAM.gov yet because they're still in planning stages.
• Industry days and pre-solicitation notices: When agencies post RFIs (Requests for Information) or hold industry days, they're telling you they're planning a procurement. Get there early.

Stage 2: Qualify. The Go/No-Go Gate

Not every opportunity in your pipeline deserves a full capture effort. The qualify stage is where you make the disciplined decision: do we invest real resources here, or do we pass?

The pWin framework gives you a structured way to answer that question. pWin (probability of win) is a scored assessment of your competitive position on a specific opportunity. Key inputs include:

• Customer fit: How well does our solution solve their actual problem?
• Customer relationship: Do they know us? Have they seen us perform?
• Competitive position: Who else is likely to bid? Are we better positioned than the incumbent (the company currently holding the contract)?
• Past performance relevance: Do we have contracts of similar scope, scale, and complexity?
• Teaming strength: Do we have the right partners for capability gaps?
• Price competitiveness: Can we deliver at a competitive price while maintaining margin?

For example (hypothetical): a simple quadrant model might cap pWin like this:

• Current customer + current offering = pWin ceiling of ~95%
• Current customer + new offering = pWin ceiling of ~75%
• New customer + current offering = pWin ceiling of ~50%
• New customer + new offering = pWin ceiling of ~25%

These aren't guaranteed outcomes. They're probability ceilings based on strategic fit. Your actual pWin is shaped downward by competitive factors, customer relationships, and whether you've done the capture work.

The go/no-go gate is a formal decision point: a meeting where BD leadership, capture, and executive leadership review the pWin assessment and decide whether to fund full capture. If pWin is below your threshold (a number leadership sets in advance, for example 35–40%), you either pass on the opportunity or continue light monitoring until new information changes the picture.

Stage 3: Shape. Where the Work Actually Happens

The shape stage is the heart of capture management, and it's where the best contractors separate from the pack. Shaping means actively influencing the acquisition before the RFP is written.

How do you shape an opportunity?

• Engage the program office: Meet with the Program Manager (PM), the Contracting Officer (CO), and the Contracting Officer's Representative (COR). Learn their priorities. Understand what's been frustrating them about the current contract. Position your approach as the solution.
• Respond to RFIs: RFIs are not proposals, but they're invitations to shape requirements. Well-written RFI responses influence the SOW (Statement of Work) and the evaluation criteria that end up in Section M.
• Conduct a Black Hat review: A Black Hat review is an internal analysis where your team takes the competitor's perspective and asks: how would Competitor X approach this? What are their strengths? What story would they tell? This reveals your vulnerabilities before the RFP and informs how you structure your win strategy.
• Solidify your team: Execute teaming agreements (TAs) early. Your team structure (who's on your team and in what roles) becomes part of your technical proposal. If you're locking in teammates after the RFP drops, you're already behind.

Stage 4: Propose. Converting Capture into a Winning Document

If you've done Stages 1–3 correctly, the proposal is not a blind exercise. It's a documentation of the win strategy you've already developed. The proposal manager's job is to translate that strategy into a compliant, compelling document that evaluators can score.

The color review process is the quality assurance framework for proposals:

• Blue Team: Validates the overall proposal strategy, structure, and win themes before writing begins. Think of it as the blueprint review.
• Black Hat (pre-proposal): Competitor analysis: understanding how each likely competitor will position themselves, so you can counter it in your narrative.
• Pink Team: Reviews early storyboards or first drafts. Catches structural problems, compliance gaps, and weak win themes before the team invests in polishing prose.
• Red Team: The most critical review: a near-final draft evaluated from the evaluator's perspective. Red Team reviewers apply Section M factors to score what they read, surfacing gaps, inconsistencies, and missed discriminators before submission.
• Gold Team: Final executive review and approval before submission. Verifies that all Red Team feedback is addressed, that pricing is aligned with technical, and that leadership signs off.

For the full breakdown of how evaluators score proposals and how to write discriminating strengths, see: Section L vs. Section M: The RFP Anatomy Every Defense Contractor Must Master.

Stage 5: Close. The Period Most Teams Get Wrong

After submission, the government evaluates proposals and may open a period of discussions: a formal exchange where they send you Evaluation Notices (ENs) identifying weaknesses or requesting clarifications. This is not an attack; it's an opportunity.

Common mistakes in the close stage:

• Arguing instead of responding: An EN about a weakness means an evaluator couldn't find evidence of your capability. Don't tell them they missed it. Provide clearer, stronger evidence.
• Missing the Final Proposal Revision (FPR): The FPR is your last chance to update pricing, strengthen weak areas, and incorporate new information. Teams that treat it as a formality often lose to teams that treat it as a second proposal.
• Skipping the debrief: Whether you win or lose, request a debrief. Win debriefs tell you what to protect in future proposals. Loss debriefs tell you exactly what evaluators found missing, which is invaluable competitive intelligence for the next pursuit.

Teaming Strategy: Building the Right Team

In GovCon, teaming (forming a partnership between two or more companies to pursue a contract together) is standard practice, especially on larger programs. A well-structured team:

• Fills capability gaps your company doesn't have
• Adds past performance relevant to the specific requirement
• Brings key personnel with specific certifications or clearances required
• Satisfies small business subcontracting requirements if you're a large prime

Team early and team intentionally. The companies you team with signal something to evaluators: their reputations, their past performance, and their roles become part of your overall offer. A weak subcontractor doesn't hide in a proposal; they create risk that evaluators will note.

For small businesses in particular, teaming with large primes through mentor-protégé programs is a proven path to build past performance and market credibility. See: How to Win as a Small Business in Federal Contracting.

Frequently Asked Questions

What's the difference between business development and capture management?

Business development (BD) is the broad, always-on activity of building market presence, identifying opportunities, and maintaining customer relationships across your entire pipeline. Capture management is the focused, opportunity-specific effort to position your company to win a particular contract. It typically begins 12–18 months before proposal drop and concludes at submission. BD is the funnel; capture is the close.

How do I calculate pWin for a specific opportunity?

pWin is a weighted scoring of multiple factors: customer fit, relationship strength, competitive position, past performance relevance, team strength, and pricing competitiveness. A common approach is a scoring template where each factor is rated 1–5 and weighted by importance. The resulting score is converted to a probability percentage. The key is calibration over time: track your predicted pWin against your actual win rate and adjust your weighting accordingly.

How long before an RFP should I start capture activities?

Ideally, 12–18 months for a mid-size opportunity and 24–36 months for a large program. If you're starting capture after the RFP draft drops, you're late. The shaping window has closed. For new entrants, this timeline feels impossibly early, but even 6–9 months of advance positioning is dramatically better than starting at RFP release.

What does a Black Hat review actually produce?

A Black Hat review produces a competitor assessment document that identifies: how each likely competitor will position themselves, their strengths relative to your approach, their weaknesses you can exploit, likely teaming arrangements they'll pursue, and price points they might target. This directly informs your win strategy. You write a proposal that defeats the competition, not just one that describes your own capabilities.

Should a small business with limited BD staff run a formal color review process?

Yes, but scale it to your resources. Even a two-person proposal team should run a "Red Team" review using an outside perspective, whether that's a consultant, a teaming partner, or a colleague not involved in writing. The purpose is to simulate the evaluator's view. A 30-minute review by someone reading your draft cold often catches more gaps than three more hours of self-editing by the people who wrote it.