BidClarity Resources How to Win a Government Contract Before the RFP Is Posted — BidClarity
Procurement Intelligence

How to Win a Government Contract Before the RFP Is Posted

📅 May 2026 ⏱ 18 min read ✍ BidClarity Intelligence Team

Most small businesses find a government contract opportunity the same way: they log into SAM.gov or CanadaBuys, search for open solicitations, and start reading. That is the most expensive moment to start. By the time an RFP is posted, the incumbent has typically had 12 to 24 months of relationship-building, capability alignment, and technical influence on requirements — advantages that are almost impossible to overcome in a 30-day bid window.

The data is stark. Analysis of 4,200 federal recompete awards from FY2023–FY2025 (Fed-Spend Research, February 2026) shows challenger win rates of 38% on recompetes where pre-RFP engagement was documented vs 12% on cold bids against the same incumbents. The difference is not proposal quality. It is timing.

This guide covers everything: how to find contracts expiring in the next 18 months using USASpending.gov exact field names, the six signals that tell you an incumbent is vulnerable, a milestone-by-milestone positioning calendar, and the Canadian equivalent process on BuyAndSell.gc.ca.

In this guide
  1. The number nobody talks about: 38% vs 12% win rate
  2. What a recompete is — and why it is different from a cold bid
  3. How to find expiring contracts on USASpending.gov
  4. The 6 incumbent vulnerability signals
  5. The 18-month positioning calendar
  6. Sources Sought: the most underused move in SMB govcon
  7. Canadian recompetes: the BuyAndSell.gc.ca equivalent approach
  8. How BidClarity automates all of this

The Number Nobody Talks About: 38% vs 12%

The govcon industry talks constantly about how to write proposals. Very little attention goes to when — which is where the real competitive advantage lives.

The 38% challenger win rate cited above comes from federal procurement records cross-referenced against agency market research logs. The methodology: identify recompete awards where at least one losing offeror had documented pre-solicitation contact with the agency (capability briefings, Sources Sought responses, industry day attendance), then compare win rates to challengers with no pre-solicitation record. The 38%-vs-12% gap held across civilian agencies (GSA, HHS, DOE) and defence (Army, Navy, Air Force) in FY2024 data.

The mechanism is not mysterious. Pre-RFP engagement allows challengers to:

None of this is possible if you find the opportunity on the day the RFP drops. It requires a systematic pipeline of expiring contracts monitored months in advance.

What a Recompete Is — and Why It Is Different from a Cold Bid

A recompete is the rebidding of a contract that is approaching its end date. Under FAR Part 17, most federal contracts cannot exceed a five-year total period of performance (base plus four option years) without a new competitive solicitation. When a contract expires, the agency must recompete it — unless they exercise an extension, award a bridge contract, or convert to an open-ended contract vehicle (IDIQ).

The key distinction from a cold bid is that recompetes have a known history: the current contractor, their performance record, their pricing, and often their staffing approach are all traceable through FPDS-NG (Federal Procurement Data System — Next Generation) and USASpending.gov. This intelligence is public and freely accessible. Cold bids against a net-new requirement have no such baseline.

Factor Recompete Net-New (Cold Bid)
Challenger win rate 38% (pre-positioned) / 18% (cold) 12% average
Positioning time available 12–24 months before expiry 0 — requirement is new
RFP complexity Predictable — mirrors prior contract structure High variance — requirements unclear
Incumbent advantage Significant but measurable and often eroding None — no incumbent
Price intelligence available Yes — prior award visible in FPDS, number_of_actions shows modifications Government estimate only (if disclosed)
Recommended approach 18-month positioning, Sources Sought response, capability briefing to COR ~9 months out RFI response, industry day attendance, teaming with established contractor

How to Find Expiring Contracts on USASpending.gov

USASpending.gov is the public interface for federal spending data. Every contract award, modification, and extension is recorded here. The Advanced Search function lets you filter by expiry date range, NAICS code, and agency — building a pipeline of every contract in your space that expires in the next 12–24 months.

Here is the exact workflow:

1
Navigate to USASpending.gov Advanced Search (~2 min)

Go to usaspending.gov/search. Select "Contracts" as the award type. All filters described below are in the left-side panel.

2
Set the period_of_performance_current_end_date range (~3 min)

In the "Time Period" filter, set the award date range to the contract's Current End Date, not the action date. Filter: today's date through 18 months from now. This field — period_of_performance_current_end_date — is distinct from the potential end date. Current end date reflects the last exercised option. Potential end date includes unexercised options; those contracts are not yet recompeting.

3
Filter by naics_code (~2 min)

Add your business category codes (NAICS — North American Industry Classification System) in the "NAICS Code" filter. Use the 6-digit code, not the 2- or 4-digit sector. A 6-digit NAICS code (e.g., 541512 for Computer Systems Design Services) will return contracts where the agency used that exact classification at award time.

4
Export and sort by recipient_name to identify repeat incumbents (~5 min)

Download the results as CSV. Sort by recipient_name to identify which contractors hold multiple expiring contracts in your NAICS. A contractor with 3+ expiring contracts in the same NAICS in the same agency is likely overextended — a vulnerability signal discussed in Section 4.

5
Check number_of_actions for modification frequency (~10 min per target)

In the contract detail view, number_of_actions shows how many modifications the contract has received. A base award with 15+ modifications in 36 months is a significant red flag — it signals scope creep, performance disputes, or pricing pressure. Compare against similar contracts in FPDS. Normal modification frequency for a services contract is 3–5 actions per year (option exercises, admin changes). Anything above 10/year warrants investigation.

6
Look up the PIID in FPDS-NG for full modification history (~10 min per target)

The contract's PIID (Procurement Instrument Identifier, e.g., GS-35F-0026T) is your key to the full Federal Procurement Data System record. Go to fpds.gov, search by PIID, and pull all modifications. Look for deobligations (negative-value modifications), which indicate the agency clawed back funds — a clear performance flag.

⚠ Do not confuse Current End Date with Potential End Date

period_of_performance_current_end_date and period_of_performance_potential_end_date are different fields. The potential end date includes all unexercised option periods — a contract with a current end date of June 2026 and a potential end date of June 2029 still has three option years remaining and is unlikely to recompete in 2026. Only track contracts where current end date = potential end date, or where the current end date falls within your monitoring window and the agency has historically not exercised all options.

The 6 Incumbent Vulnerability Signals

Not every expiring contract is worth pursuing. The incumbents who are genuinely vulnerable share identifiable patterns in their public record. These six signals, when present in combination, indicate an incumbent whose position can be challenged:

Signal 1 — High Modification Frequency

What to look for: More than 8 modifications per year of contract life in FPDS, excluding routine option exercises. What it means: Scope disputes, delivery failures, or pricing pressure. Agencies modify contracts heavily when the original scope was poorly defined or when they are managing performance issues without wanting to formally cure the contractor.

Signal 2 — Bridge Contract Issuance

What to look for: A short-term extension (3–6 months) issued after the current end date without a recompete. Bridge contracts are issued as J&A (Justification and Approval) sole-source actions, visible in SAM.gov Contract Opportunities under "Award Notices." What it means: The agency needed more time — either because procurement slipped, or because they were dissatisfied with available alternatives. Bridge contracts are almost always followed by a competitive recompete within 12 months.

Signal 3 — Set-Aside Certification Continuity Risk

What to look for: The incumbent won as a small business set-aside (8(a), HUBZone, WOSB, SDVOSB) but the contract is now in its final base year. What it means: After five years, the incumbent may have graduated from the SBA program that enabled the set-aside. The agency may need to recompete under the same set-aside but the incumbent is no longer eligible — creating an open lane for qualified challengers.

Signal 4 — Deobligations (Negative Modifications)

What to look for: In FPDS, any modification with a negative obligated amount (money returned to the agency). What it means: The agency clawed back funds because work was not performed, deliverables were rejected, or the contractor could not staff the requirement. Even a single deobligation on a fixed-price contract is significant — it represents a formal, documented performance failure.

Signal 5 — Incumbent Acquiring Competing Contracts

What to look for: Using recipient_name in USASpending, search for new awards to the incumbent across all agencies in the 12 months before their contract expires. What it means: If the incumbent has just won 2–3 large contracts elsewhere, their available capacity for your target contract is diminished. Proposal evaluators know this — and so should you when positioning your team's dedicated capacity as a differentiator.

Signal 6 — COR Turnover

What to look for: The Contracting Officer's Representative (COR) named in the original contract is no longer with the agency. Check LinkedIn or the agency's staff directory. What it means: The incumbent's primary relationship inside the agency has departed. Their technical performance history lives with a new COR who has no personal investment in the current contractor — the playing field flattens significantly.

Score each target before investing

Assign 1 point per signal present (0–6 scale). A target scoring 4+ is worth a full positioning campaign. A target scoring 1–2 is worth monitoring but not deep investment. A target scoring 0 — strong incumbent, no signals, option years remaining — should be deprioritized in favour of higher-score targets. Time spent on low-vulnerability recompetes rarely pays off against a firmly entrenched incumbent.

The 18-Month Positioning Calendar

Once you have identified a high-vulnerability target with 18+ months until recompete, the following calendar tells you exactly what to do and when. All timings assume the contract expires Month 0 and the RFP drops approximately Month −3 to −6 before that expiry.

Month −18
Intelligence gathering and bid/no-bid decision (~1 week)

Pull the full FPDS record using the PIID. Score the target using the 6-signal framework above. Identify the agency's primary point of contact (CO and COR) from the contract record. Research the agency's strategic plan and budget submissions (agency budget justifications are public, posted annually to OMB). Decide definitively whether to pursue — uncommitted pursuit wastes relationship capital.

Month −15
Teaming decisions and capability gap analysis (~2 weeks)

Compare your capability profile against the existing contract's SOW (attached to the original SAM.gov solicitation, still accessible). Identify every capability gap. For each gap: decide whether to hire, partner, or subcontract. Begin teaming conversations — do not sign teaming agreements yet, but establish non-binding relationships with firms that fill your gaps. If the contract requires a security clearance facility, start the facility clearance process now — it takes 6–12 months.

Month −12
Capability briefing to the COR (~20 min meeting, 2 weeks to schedule)

Request a 20-minute capability briefing with the COR (not the CO — the CO is the contracting professional, the COR is the technical decision-maker who will write the PWS). Frame the meeting as market research input, not a sales call. Bring one page: your company's NAICS, relevant past performance with dollar values and agency names, and one specific capability that solves a problem the current contract has visibly struggled with. Do not mention the expiring contract by name in the meeting request — request it as a general capability discussion.

Month −9
Sources Sought response (see Section 6) (~3 days)

If the agency issues a Sources Sought notice (RFI), respond. Even if they do not, consider whether an unsolicited capability statement is appropriate. Sources Sought responses are tracked by contracting officers and directly inform whether a procurement is set aside, full-and-open, or structured around a specific capability. Your response shapes the RFP before it is written.

Month −6
Draft proposal outline and price build (~2 weeks)

Using the existing contract's SOW as a baseline, build your proposal outline. Develop your pricing model using FPDS data on the current contract's ceiling value, number_of_actions, and any option exercise values. The incumbent's actual pricing is often visible in FPDS for firm-fixed-price contracts — use it as your competitive benchmark. The goal at Month −6 is a draft price ± 10% of final. You will tighten it when the RFP drops but you should not be building your model from scratch at that point.

Month −3 to 0
RFP drops — proposal execution (~15–30 days, per solicitation deadline)

With 15 months of preparation, RFP release is not a scramble — it is a documentation exercise. Your technical approach is already developed, your teaming agreements are signed, your past performance references are pre-briefed, and your price is built. The proposal window (typically 30 days for a complex services contract) is used to tailor and comply, not to start from zero. Challengers who start here for the first time are 15 months behind you.

Sources Sought: The Most Underused Move in SMB Govcon

A Sources Sought notice (also called an RFI — Request for Information) is the agency's formal market research step before issuing an RFP. Responding to a Sources Sought is not just an intelligence-gathering opportunity for you — it is an opportunity to influence what the agency asks for.

Understanding how to read the resulting federal RFP is downstream of this step — but Sources Sought is where requirements are still malleable. The typical Sources Sought response window is 10–15 days. Here is what a strong response contains:

⚠ Do not submit a Sources Sought response that reads like a brochure

Generic capability statements ("We are a woman-owned IT services company with experience in federal contracting") are ignored. Contracting officers read hundreds of Sources Sought responses. The ones that get read twice — and that influence RFP language — are the ones that demonstrate specific, relevant capability against the exact problem described in the notice. Write to the requirement, not to your company profile.

Canadian Recompetes: The BuyAndSell.gc.ca Equivalent Approach

Canada's procurement recompete landscape is governed by Public Services and Procurement Canada (PSPC) and posted on CanadaBuys (the replacement for BuyAndSell.gc.ca, fully migrated as of 2024). The equivalent of USASpending.gov for contract history is the Proactive Disclosure database at open.canada.ca.

The Canadian process follows a parallel logic to the US approach, with these key differences:

The same vulnerability signals apply in the Canadian context — modification frequency (visible in proactive disclosure as multiple contract amendments), bridge contract issuance (awarded as Advance Contract Award Notices, or ACANs, on CanadaBuys), and set-aside program transitions (Aboriginal procurement strategy, women-owned business initiatives). For international procurement strategies that extend beyond North America, see the international government contracts guide.

How BidClarity Automates All of This

BidClarity Intelligence: Pre-RFP Monitoring Included in Command Plan

The research described in this guide — scanning USASpending.gov for contracts expiring in your NAICS, identifying incumbent vulnerability signals, tracking Canadian proactive disclosure for recompetes — takes 4–6 hours per week when done manually. BidClarity's Command plan automates the entire pipeline: 37+ procurement portals monitored daily, AI-scored against your capability profile, with recompete contracts flagged separately from net-new opportunities and delivered to your inbox on your schedule.

Recompete intelligence is available in the Command plan ($699/mo or $559/mo billed annually). Scout and Intelligence plans cover open solicitations only.

Start My 14-Day Trial — Command Plan →

Specifically, BidClarity's Command plan monitors the following recompete-relevant sources daily:

Each identified recompete opportunity includes a Vulnerability Score (the 6-signal framework described in Section 4, calculated automatically), a Positioning Window (how many months remain before the likely RFP drop date), and a 5-Step Action Plan calibrated to your positioning timeline.

For a detailed comparison of how BidClarity scores opportunities against your profile, including how NAICS code matching, CCC eligibility, and bank fundability flags are calculated, see the tender intelligence guide.

The cost of a missed recompete window

A single federal services contract in the $2M–$5M range, won through pre-RFP positioning rather than cold bidding, represents 3–5 years of predictable revenue and the past performance references needed to pursue larger contracts. The opportunity cost of discovering a recompete at RFP release — after the positioning window has closed — is measured in years of pipeline, not individual bids. Early intelligence is not a nice-to-have. It is the strategy.

FIND → WIN → DELIVER → WIN AGAIN

Pre-RFP positioning wins the contract. Delivering it well wins the recompete after that. Every contract you execute becomes past performance that feeds your next positioning cycle — but only if that performance is documented. BidClarity Fulfill auto-drafts your CPARS narrative (your official government performance report card) at closeout, tracks every deliverable deadline, and stores your past performance in a searchable knowledge base that surfaces automatically when you're writing your next proposal. The 38% challenger win rate comes from doing both halves well. BidClarity runs the full loop.

Found this useful? Share it. Discuss in r/govcon →