Recompetes are where small govcon teams have the highest shot at winning federal work, but only if you find them early enough to matter. Twelve to eighteen months out, the incumbent is beatable. By the time the RFP drops, they’re usually not. This post walks through how to build that early-warning routine without a dedicated capture staff.
TL;DR
- Recompetes make up an estimated 60 to 70 percent of federal contract value, making them the highest-probability target for lean BD teams.
- Find recompetes 12 to 18 months early by querying USAspending.gov for period-of-performance end dates in your NAICS code, then cross-referencing FPDS.
- Bridge contracts, declining CPARS ratings, and protest history are the three signals that tell you whether an incumbent is actually beatable.
- A black hat review run 4 to 8 months before the RFP lets you model the incumbent’s pricing, past performance, and teaming before you can no longer act on what you learn.
- Sweetspot’s Federal Market Intelligence automates the USAspending and FPDS research, flags recompetes 12 to 18 months out, and keeps capture knowledge indexed so staff turnover doesn’t reset a pursuit.
What Capture Management Is and What a Capture Manager Does
Capture management is the structured, pre-RFP work that happens before a solicitation ever hits SAM.gov. You research a specific opportunity, size up the competition, build relationships with the contracting agency, and position your company as the obvious choice while there is still time to shape the outcome.
The capture manager owns that whole pre-RFP cycle. They pick which pursuits are worth the investment, gather intelligence on the incumbent and likely bidders, and set the win strategy the proposal team will later execute.
That last distinction matters. The capture manager works the opportunity before the RFP drops. The proposal manager runs the response after it does.
Why Recompetes Are the Highest-Probability Target in Federal Contracting
Small teams cannot chase everything. That is the whole case for recompetes.
A recompete is a contract already being performed by someone, coming up for its next award cycle. The scope is defined, the budget is proven, and the agency has a track record you can read. Compared to a net-new open competition, the field is far more knowable.
The dollars back this up. Recompetes account for an estimated 60 to 70 percent of annual federal contract obligation by value, and challenger win rates run higher than on net-new competitions.
For a lean BD shop, that is where limited hours earn the most return.
How to Find Federal Recompetes 12-18 Months Before the RFP Drops
Start with the contract end dates. Every active federal contract lists a period of performance, and that expiration date is your clock.
Work the public record in order:
- Query USAspending.gov for awards in your NAICS code and target agency with a period of performance ending 12 to 18 months out. Those are your recompete candidates.
- Cross-reference each in FPDS for full award history: incumbent, contract value, contract line item numbers, mods, and how long the work has run.
- Check agency OSDBU and procurement forecast pages for the planned re-solicitation.
None of this is inside information. It is all disclosed by law and free to pull.
The window is the point. A capture that starts when the draft RFP posts is nearly impossible to win against an entrenched incumbent. Twelve to eighteen months gives you time to actually move the agency’s requirements.
Early Warning Signals in Recompete Capture: Bridge Contracts, CPARS Ratings, and Incumbent Vulnerability
Finding the recompete is step one. Deciding whether the incumbent is beatable is step two, and that is where most small teams overcommit.
Three signals tell you where to concentrate:
- Bridge contracts. When an agency issues a short sole-source extension instead of a clean re-award, the recompete is usually coming and the timeline slipped. That is an opening.
- CPARS ratings. Mediocre or declining past-performance marks weaken the piece of the evaluation the incumbent should own.
- Modification and protest history. A trail of scope changes, cost growth, or prior protests points to an agency that is not fully satisfied.
Score all three before you spend a dollar of capture time. CPARS data in particular is freely accessible and one of the clearest incumbent-vulnerability signals in the public record. For teams competing on vehicles like OASIS Small Business, these signals are especially worth tracking given the competitive field.
What a Black Hat Review Is in Government Contracting
A black hat review is a formal competitive analysis run during capture, rooted in Shipley capture methodology and distinct from a broad agency announcement pursuit where competitive dynamics differ. Your pursuit team plays the incumbent or a rival bidder and maps out how that competitor will likely position, price, staff, and win the contract. The goal: see the bid through the enemy’s eyes before the solicitation drops.
Do not confuse it with two adjacent exercises:
| Review Type | When to Run | What It Tests | Primary Output |
|---|---|---|---|
| Black hat | 4 to 8 months before RFP | How the incumbent or rival will price, staff, and position their bid | Win strategy changes, teaming decisions, price posture |
| White hat | 4 to 8 months before RFP | Your own team’s strengths, gaps, and vulnerabilities | Discriminators to sharpen; weaknesses to close before proposal |
| Color teams (pink, red, gold) | After RFP drops | Your draft proposal: compliance, quality, and win themes | Proposal revisions; compliance fixes |
Run months before the RFP, it produces intelligence you can act on: win strategy changes, teaming decisions, and price position while there is still room to adjust.
When to Run a Black Hat Review and When to Skip It
Timing is the first question. Industry guidance points to 4 to 8 months before the final RFP for complex federal captures, and there is Goldilocks logic behind that range. Run it too early and there is not enough competitive intelligence to model a rival credibly, so you are guessing. Run it too late and there is no runway left to act on what you learn.
For a small team, two thresholds decide it:
- Is the opportunity material enough to warrant the prep time a good exercise demands?
- Do you know the likely competitors well enough firsthand to make the simulation evidence-based instead of speculative?
If both answers are no, skip it and put those hours where they pay off.
How to Run a Lean Black Hat Review Without a Dedicated Capture Staff
A lean black hat does not need a facilitator or an outside consultant. It needs three people for two hours: your BD lead, one subject matter expert who has actually worked the agency or NAICS (whether that is a defense shop or a team pursuing State Department contracts), and whoever owns pricing.
Prep the pre-read first. Pull the incumbent’s award history and pricing patterns from FPDS, plus any public CPARS summaries. Send it out a day ahead so nobody walks in cold.
The session answers four questions:
- How will the incumbent price, and where is their cost baseline?
- What past-performance narrative will they lead with?
- What teaming moves are they likely to make?
- Which weaknesses will they try to ghost past the evaluators?
Leave with a short action list, not a report nobody reads.
Translating Black Hat Findings into a Pre-RFP Win Strategy
A black hat is worthless until it changes what you do. Take the four answers from the session and turn each into a decision before the RFP posts.
- Teaming: if the competitor covers a capability you cannot, add a sub who closes that gap now, not during the proposal scramble.
- Pricing: set your rate posture against the incumbent’s likely cost baseline, so you are not guessing at price-to-win under deadline.
- Ghosting: seed the competitor’s known weaknesses into agency conversations and shape the requirements, then carry that framing into the eventual narrative.
- Discriminators: sharpen the two or three claims only you can make, and back each with past performance.
Then flip the lens. Run a white hat on your own bid using the same rigor, because the gaps you just found in the incumbent are the ones a rival is finding in you.
Protecting Institutional Knowledge When Proposal Staff Turns Over
On a small team, the person running a recompete is often the only one who knows the agency’s hot buttons, who they met at the last industry day, and why the incumbent is beatable. When they leave, the pursuit resets to zero.
Codify as you go, not at the end:
- Keep a living capture plan per opportunity, not per person.
- Write a short call report after every agency meeting: who, what was said, what changed.
- Index past proposals, bios, and pricing so any teammate can pull them, the kind of workflow that helped Crayon reach first drafts faster.
- Store everything around the opportunity, so a departure loses a colleague, not the pursuit.
Your biggest BD risk is usually your own turnover.
How Sweetspot’s Capture Management Platform Helps Small Teams Win Recompetes Earlier
Every manual step from the earlier sections, the USAspending queries, the FPDS cross-referencing, the hunt for contract end dates, is work Sweetspot’s Federal Market Intelligence does for you. It links SAM.gov solicitations to FPDS award records and USAspending history automatically, surfacing who won last time, what they were paid, and how long the contract ran. It also flags recompetes 12 to 18 months early by tracking period-of-performance end dates.
That linked award and modification record is the raw material a credible black hat needs, ready before your session starts.
The Organization Library solves the turnover problem. Past proposals, capability statements, and bios sit indexed in one place, so capture intelligence stays with the team when a person walks.
More than 500 govcon teams use Sweetspot to pursue 6x more RFP value. See Sweetspot in action to walk through the recompete workflow.