Find Government Contracts Coming Up for Recompete

Overview

Here's the most underused signal in government contracting: every award has an end date, and every end date is a recompete with a predictable clock. That data is public. It's in USASpending, right now, for every contract in your NAICS.

Yet almost everyone waits for the solicitation. By then the incumbent has years of relationship, the requirements often read like their capability statement, and you're writing a proposal you were never going to win. The recompete is decided in the 12–18 months before the RFP — which is a window you can see coming, if you look.

This Hound finds contracts expiring in your space, ranks them by how displaceable the incumbent looks, finds the program and contracting leads, and opens the conversation while there's still time to change the outcome.

How to set it up

Four things to brief your Hound. This is the exact configuration behind this play.

A · Describe the opportunity

This is the brief every source is filtered against. You describe what you're looking for in plain language, add keywords to sharpen it, then set the structured criteria.

Tell Forest what you're looking for:

"I'm looking for federal contracts approaching their end date in my NAICS codes and capability area — recompetes I could realistically win. I want them 12 to 18 months out, while there's still time to build a relationship and shape requirements, not when the RFP drops. Prioritize contracts where the incumbent looks displaceable: small incumbents, poor past performance, contracts that have rolled over without competition, or agencies I already have a footprint in. Skip contracts expiring in under 6 months (too late), and vehicles I'm not eligible for."

Keywords to watch for: recompete · follow-on · contract expiration · option year · bridge contract · sole source justification · intent to extend · [your NAICS codes] · [your target agencies]

Fields to extract: contract_number · incumbent · agency · office · naics_code · award_date · period_of_performance_end · total_obligated · contract_type · set_aside_type · option_years_remaining

Match criteria:

• ✓ NAICS matches your capability

• ✓ End date 6–24 months out (the shaping window)

• ✓ Contract value within your capacity

• ✓ Incumbent appears displaceable (soft — see scoring)

• ✗ Exclude contracts expiring in under 6 months — too late to matter

• ✗ Exclude vehicles you're not eligible to hold

B · Choose the sources to monitor

This play is built almost entirely on one free federal dataset that almost nobody reads this way.

Federal award data (free — connected by default) 🟢

• USASpending.gov — usaspending.gov — The core source. Every federal award with period_of_performance_end. Filter to your NAICS, sort by end date, and you have a recompete calendar. This is the whole play.

• FPDS-NG — fpds.gov — Contract actions and modifications. Shows whether options are being exercised or a bridge contract was issued — a bridge is a tell that the agency is unprepared and the recompete is in play.

• SAM.gov — sam.gov — Watch for the sources-sought notice on your tracked contracts. That's the starting gun, and Hounds tracking a recompete should catch it the day it posts.

• Agency procurement forecasts 🔵 — bring your own link — many agencies publish planned recompetes a year out.

News & Press 🟡 default source, always on — reads the open web against your brief for incumbent performance problems, protests, program restructuring, and leadership changes at the buying office — all signals the incumbent is vulnerable.

This is a "computed event," not a published one. Nothing announces "this contract is expiring." Forest derives the event from the award's end date and counts backward. Same free data everyone has; almost nobody reads it forward.

C · Define the ICP to reach

Who to reach, in priority order. This is a long-game relationship play, not a bid response.

1. Program Manager / Technical POC — Primary — owns the requirement and shapes the recompete — PRIMARY

2. Contracting Officer — Owns the vehicle and timing. Named in the award record — source-native.

3. Small Business Specialist — Fallback; their job is to help you find a way in — FALLBACK

D · Email & LinkedIn sequence

The play the Hound runs for each match. Deliberately slow, helpful, and never about the current contract's failings. Fields drop in as variables.

Email · Day 0 Hi {{first_name}} — I saw {{agency}}'s {{capability}} work under {{contract_number}} runs through {{period_of_performance_end}}. We do {{capability}} for {{comparable_agency}} and would welcome the chance to introduce ourselves well ahead of any follow-on — no agenda, and happy to share what we've seen work on similar requirements if that's useful market research.

↓ Wait 5 days · no reply

LinkedIn · connection request · Day 5 Hi {{first_name}} — reaching out regarding {{agency}}'s {{capability}} program. Would value connecting.

↓ Wait 7 days · no reply

Email · Day 12 · follow-up Following up once — happy to send our capability statement for the file, or to be included in any market research or industry day as {{period_of_performance_end}} gets closer. Here whenever it's useful.

⏸ Any reply on either channel pauses the whole sequence — the conversation is yours.

Why this Hound works differently

Most Hounds fire on something that happened. This one fires on something that will happen, on a date already published. That means:

• Very long sequences. The Hound may touch a contact quarterly for a year. Build the sequence accordingly — this is cultivation, not conversion.

• The real trigger comes later. When the sources-sought notice posts on a contract you've been tracking, that's the moment — and you'll already know the program manager by name.

• Never sell against the incumbent. You're introducing yourself, not campaigning. Agencies talk, and the vendor who badmouths the incumbent is remembered for exactly that.