A Federal Capture Plan That Actually Works: What to Include at Each Stage
Most GovCon capture plans are too long, too generic, and too late. This guide describes a lean capture plan structure — Identified, Qualified, Pursuit, Proposal — and what intelligence you should have at each gate.
Marcus Webb
A capture plan is a living document that organizes everything you know about a pursuit — the agency, the incumbent, the requirement, your win themes, your team, and your price strategy — so that when the RFP drops, your proposal team is executing, not researching. The mistake most small contractors make is either having no plan or having a plan that is 40 pages long and updated once. Neither works.
Stage 1: Identified — opportunity on the radar
An opportunity earns 'Identified' status when you've found it in SAM.gov (or through pipeline tracking) and confirmed that the NAICS, set-aside type, dollar range, and agency mission are a plausible fit. At this stage you need three things: a preliminary Pwin estimate, a decision on whether to invest capture resources, and a watch date for the next pre-solicitation activity.
- Sources needed: SAM.gov notice, USASpending.gov award history, prior-year solicitation if available
- Key questions: Is there an incumbent? What is the expiration date of the current contract? Is this a re-compete or new work?
- Minimum capture record: opportunity name, NAICS, estimated value, agency, estimated solicitation date, assigned capture lead
Stage 2: Qualified — worth pursuing
You move an opportunity to 'Qualified' after a formal Go/No-Go discussion — even a 20-minute team call counts. At this stage you should know: your preliminary technical approach, whether you need a teammate (and who), the incumbent's contract number and performance indicators, and the budget authority at the agency. Pwin should be estimated at this point — not computed, but gut-checked by the capture lead against known factors.
Stage 3: Pursuit — active capture work
Pursuit means you've committed time and money. The capture lead is actively working the account — responding to RFIs, attending industry days, requesting briefings, building or confirming the team. Your win theme should be written and reviewed. Competitive intelligence on likely competitors should be in the capture file. Price-to-win analysis should be underway if this is a Best Value procurement.
- Win theme brief: 1–2 pages describing your discriminators, the agency's key priorities, and how your approach addresses them
- Competitive analysis: who is likely bidding, what are their strengths and known weaknesses
- Team structure: prime/sub split confirmed, teaming agreement in draft
- Draft outline: section structure for technical volume, at minimum
Stage 4: Proposal — solicitation is out
The RFP has dropped. At this point your capture plan converts into a proposal plan. The capture manager hands off intelligence — win themes, competitive insights, team structure, price strategy — to the proposal manager. The capture plan does not close; it becomes the reference document for the proposal team's color reviews.
The gate review: making Go/No-Go decisions
Gate reviews should happen at the transition between every stage. The key question at each gate is whether your Pwin justifies the investment you are about to make. A 5% Pwin opportunity is not worth a $50,000 bid and proposal investment. Use objective criteria: technical fit, competitive strength, agency relationship, incumbency, price-to-win alignment. Document the decision — both to protect the BD team and to learn from the outcome.
Frequently Asked Questions
How long should a capture plan be?
A working capture plan should fit in a short brief or structured template — not a 40-page word document. The capture lead needs to be able to share the key points in a 15-minute pipeline review. Two to five pages plus a competitive intelligence appendix is a practical target for most pursuits.
What is Pwin and how do I calculate it?
Pwin (Probability of Win) is a 0–100% estimate of your likelihood of winning a specific pursuit. It accounts for factors including: your technical fit score, incumbency advantage (yours or a competitor's), agency relationship depth, competitive field strength, price competitiveness, and past performance relevance. Most capture tools assign weighted scores to each factor. GovPillar computes a base Pwin from your company profile and the solicitation data — use it as a starting point, then adjust for factors you know that the algorithm doesn't.
What is the difference between capture and proposal?
Capture is everything that happens before the RFP drops — building relationships, gathering intelligence, shaping requirements, and developing win themes. Proposal is everything after the RFP drops — writing, reviewing, pricing, and submitting. They are sequential, not parallel. Good capture makes proposal writing faster and more confident; poor capture makes even excellent writing a longshot.
Put this into practice
GovPillar helps you apply everything in this guide — AI-scored opportunities, RFP shredding, capture pipeline, and more. Free to start.