The Vendor Landscape

How Many Offers Do Federal IT Recompetes Really Get? What the Award Data Shows

FedSpend

Key Takeaways
  • Dollar value does not predict how many bidders show up
  • CDC's $25.9M recompete attracted five competing firms
  • DHS and DOJ awards each drew only one offer
  • Incumbency, scope, and vendor pool size drive competitive intensity
  • Check prior offer count before committing any capture budget

A capture manager at a 60-person IT shop pulls up a recompete notice for a $14M help desk contract with about ten business days to decide whether to spend five figures on a proposal. The agency name is familiar. The dollar figure looks winnable. Nothing in the notice says whether she’s walking into a two-horse race or a field already decided by an incumbent nobody’s dislodging. That’s the gap federal tail spend analysis is supposed to close.

The Real Question Before You Chase a Recompete

The question that matters isn’t “is this winnable” — it’s “how many other firms are already circling this notice.” Contract value tells a capture manager almost nothing about that. Offer count does. Three recent federal IT recompetes make the point, running the gamut from a crowded field to a field of exactly one.

RecompeteAgencyAward ValueOffers Received
NCCDPHP IT and Public Health ServicesCDC$25.9M5
ITOMSSDHS$13.2M1
AWS GovCloudDOJ$10.3M1

Notice what that table does not show: a straight line from dollars to bidders. If size drove competition, the three awards would stack in order. They don’t. That’s exactly the kind of signal a usaspending.gov pull surfaces only if someone goes looking before the RFP drops, not after the award posts.

When Five Bidders Show Up: The CDC Recompete

A five-offer field on a $25.9M public health IT recompete signals a contestable program, not a locked one. According to federal spending data, the CDC’s NCCDPHP IT and Public Health Services recompete drew five competing offers before CyberData Technologies won the $25.9M award. Five serious bidders on that value means the requirement was legible enough, and the incumbent weak enough, that outside firms judged the pursuit worth the capture spend.

That’s the profile worth chasing. A crowded field means price and technical approach actually move the needle, because no single firm starts with a decisive structural edge. It’s also where a sharp competitive battlecard built from spend data pays for itself — differentiating against four credible competitors means knowing exactly what the incumbent delivered and where it fell short.

When Only One Bidder Shows Up: DHS and DOJ

A single-offer award means the field never materialized — the more common story in federal IT than most capture decks admit. DHS’s ITOMSS recompete ($13.2M) and DOJ’s AWS GovCloud award ($10.3M) each closed with one offer received. Neither drew a second bidder, not because the dollar value was too small to matter, but because something about the requirement kept competitors out.

Three mechanisms explain that outcome:

  • Incumbency grip — a contractor with years of accumulated systems knowledge and cleared staff already in seats
  • Specialized technical scope — cloud authorization requirements or security clearances that shrink the qualified-vendor pool before anyone bids
  • Narrow qualified-vendor pools — certifications or past-performance thresholds that functionally pre-select the winner

The caveat is worth stating plainly: these are two awards from a snapshot of a broader recompete dataset, not a comprehensive statistical sample, and a single-offer outcome reflects that program’s specific conditions rather than a government-wide rule. What it still is, though, is a legitimate pre-bid red flag — a question to ask before committing budget, not discover after a loss.

Explore federal IT spending patterns free

Start a FedSpend trial to discover growth opportunities in $675B+ of federal IT awards.

Start trial

Why Dollar Value Doesn’t Predict Competitive Intensity

Dollar value is a weak predictor of how many firms show up, and the three awards above prove it directly. The largest-value award in the set drew the most bidders; the two smallest-value awards each drew the fewest possible number. If size drove competition, that pattern would run backward.

What actually drives it is closer to what agency spending intelligence is built to surface: how narrowly the agency scoped the requirement, how entrenched the incumbent’s past performance is, and how specialized the PSC/NAICS footprint is against the available vendor base. A broadly scoped IT support contract invites generalist firms. A cloud authorization or security-heavy requirement filters down to a handful of qualified shops before the solicitation even posts.

FactorPushes Field WiderPushes Field Narrower
Incumbent tenureShort tenure, recent performance issuesLong tenure, clean CPARS record
Technical scopeGeneralist IT supportSpecialized cloud/security authorization
Qualified-vendor poolBroad NAICS, low clearance barNarrow PSC niche, high clearance bar
Program visibilityWell-known, widely tracked programLow-visibility, rarely covered recompete

None of this is exotic theory. Researchers at GovDash have tracked the same underlying dynamic: incumbents still win most recompetes, but challengers who start capture well before the RFP posts take a meaningful share of the rest. The table above sorts which bucket a given target falls into before anyone spends a dime.

What This Means for Your Bid/No-Bid Checklist

Treat offer-count history as a pre-bid input, not a post-award curiosity. Before committing capture dollars to a rebid, run through this sequence:

  1. Pull the prior award’s offer count and date signed, not just its obligated value
  2. Check how long the current incumbent has held the work and whether past performance looks clean
  3. Map the PSC and NAICS codes against how many vendors in the market actually qualify
  4. Weigh program visibility — a well-covered flagship program draws capture attention a quiet tail-spend recompete never will
  5. Decide whether the field looks like the CDC pattern or the DHS/DOJ pattern before writing a single proposal page

This is squarely the territory where small BD teams without a dedicated capture department either win efficiently or burn a quarter chasing a locked incumbent. The data to make the call already sits in the award record; most teams pull it after they’ve lost, not before.

Building Recompete Timing Into the Pipeline, Not the Post-Mortem

The recompetes that move the needle for a mid-size vendor rarely make trade-press headlines. They’re the $10M-to-$30M range sitting in agency tail spend, where the only evidence of how a bid will go is the last award’s offer count, incumbent tenure, and timing window. Recompete Radar was built to surface exactly that before a solicitation drops, not after a competitor locked in a year-long capture head start. Treat competitive intensity as a number you check, not a feeling you guess at.

The Number That Should Change Your Capture Budget

Every capture team checks contract value, agency, and period of performance before chasing a rebid. Almost none check how many firms showed up last time — the cheapest diligence available before a bid/no-bid call. A $25.9M program drawing five competitors and a $10.3M program drawing one aren’t different sizes of the same opportunity; they’re different markets wearing the same label. Vendors treating dollar value as a proxy for competitive intensity will keep losing capture budget to recompetes that were never actually in play.

Frequently Asked Questions

What does a five-bidder federal IT recompete signal about the incumbent's position?
It signals the incumbent is weak enough and the requirement legible enough that outside firms judged the pursuit worth capture spend — meaning technical differentiation and pricing actually determine the winner rather than structural incumbency advantage.
What three mechanisms most often produce a single-offer outcome on a recompete?
Incumbency grip with cleared staff already in seats, specialized cloud or security scope that shrinks the qualified-vendor pool, and certifications or past-performance thresholds that functionally pre-select the winner before solicitation.
Which factors push a federal recompete's bidder field wider rather than narrower?
Short incumbent tenure, recent performance issues, generalist IT support scope, broad NAICS codes with low clearance bars, and strong program visibility all tend to attract more competing offers.
What specific steps should a capture team run before committing to a recompete?
Pull the prior award's offer count and signed date, check incumbent tenure and CPARS record, map PSC/NAICS codes against the qualified vendor base, weigh program visibility, then decide whether the competitive pattern fits the CDC example or the DHS/DOJ example.
Get content like this in your inbox
Tips from our team — once a week, no spam, unsubscribe anytime.

Tagged: Award Data · Competitive Intelligence · Recompete Signals

About the Author

FedSpend