A spreadsheet works for a GovCon pipeline until you have more than one person touching it, more than a couple dozen live pursuits, or a recompete you cannot afford to miss. Past that point, move to a CRM, but only one configured around the federal acquisition lifecycle: notice types, vehicles, NAICS and set-asides, capture gates, teaming, and recompete dates.
I spent 18 years in federal acquisition as a Contracting Specialist and Contracting Officer at GSA, IRS, DoD, DOI, HHS, FTC, and Energy, hold FAC-C Level III and a Harvard Master of Liberal Arts, and have supported 70+ GSA contract awards. From both sides of the desk, the tool matters less than the discipline it enforces, and agencies can see that discipline in everything you send.
When does a GovCon firm outgrow a spreadsheet pipeline?
You have outgrown the spreadsheet when the pipeline lives in someone's head instead of the file. The usual triggers are a second BD or capture person, more than one contract vehicle to track, a missed response deadline, or leadership asking for a pipeline number nobody can produce without a day of reconciliation.
- Version drift: two people keep their own copy and the "real" pipeline depends on who you ask.
- Missed dates: an RFI response window or a question deadline slipped because no one owned the reminder.
- No history: you cannot reconstruct who talked to which program office, when, and what they said.
- No gate record: bid/no-bid decisions happen in hallways, so you cannot learn from the ones you lost.
- Recompete blindness: incumbent contracts in your lane expire and you find out when the solicitation drops.
If none of those describe your shop, keep the spreadsheet and tighten its columns. A well-structured sheet beats a badly configured CRM.
What does a GovCon pipeline track that a commercial CRM does not?
Commercial CRMs are built around a buyer, a deal value, and a close date. A federal pipeline is built around an acquisition: who is buying, through which vehicle, under which NAICS and set-aside, at what stage of the public acquisition lifecycle, and when the incumbent's period of performance ends. Out of the box, most CRMs track none of that.
| Field | Commercial CRM default | What a GovCon pipeline needs |
|---|---|---|
| Stage | Lead, qualified, proposal, closed | Forecast, sources sought, RFI, draft RFP, RFP/RFQ, submitted, award, protest window |
| Customer | Company and contact | Department, bureau, contracting office, program office, CO/CS of record |
| Vehicle | Not tracked | Open market, GSA MAS SIN, GWAC, IDIQ, BPA, and whether you hold it or need a teammate who does |
| Classification | Industry tag | NAICS code and size standard, Product Service Code (PSC), set-aside type |
| Timing | Expected close date | Forecast award quarter, solicitation release, response due date, incumbent period of performance end |
| Competition | Optional notes | Incumbent, contract number, prior award value, likely bidders |
| Partners | Not tracked | Teaming partners, role (prime/sub/JV), NDA and teaming agreement status |
| Past performance | Not tracked | Which of your references map to this scope, and their CPARS status |
Every one of those fields can live in a spreadsheet. The difference is whether the system enforces them and alerts you before dates hit.
How should pipeline stages map to the federal acquisition lifecycle?
Tie every stage to a public, verifiable government action instead of a sales feeling. A forecast entry, a sources sought notice, an RFI, a draft RFP, and a final solicitation each tell you something specific about where the agency is, and each one triggers a defined BD or capture task on your side.
- Forecast: the requirement appears on an agency procurement forecast. Start customer research and check the incumbent.
- Sources sought / market research: the agency is testing the market under FAR 10.002. Your capability response can influence the set-aside decision.
- RFI: under FAR 15.201(e), RFIs gather planning information when the government does not yet intend to award. Answer what is asked.
- Draft RFP: listed in FAR 15.201(c) as an early-exchange technique. Submit questions on ambiguous evaluation criteria now, not later.
- Synopsis and RFP/RFQ: FAR 5.203 generally requires the notice at least 15 days before issuance and at least 30 days for responses above the simplified acquisition threshold, currently $350,000 under FAR 2.101. MAS orders through eBuy run on their own timelines.
- Award and debrief: log the result and debrief notes.
What do Contracting Officers see from the other side when your pipeline is weak?
From the CO seat, pipeline discipline shows up in timing and fit. Disciplined firms respond to sources sought notices with capability statements mapped to the actual requirement, ask sharp questions on draft RFPs, and show up teamed correctly on day one. Undisciplined firms appear for the first time at the final RFP with a generic package.
When I was a Contracting Specialist working market research, I could usually tell which companies were tracking our office and which ones had set a keyword alert the morning before. The tracking firms referenced our forecast, knew the incumbent's vehicle, and answered the set-aside question we actually asked. As a Contracting Officer, those sources sought responses were what I relied on when documenting the rule of two under FAR 19.502-2. If you were not in that response file, you had no voice in whether the work was set aside for you.
Where should GovCon pipeline data come from?
Your pipeline should be fed from primary government sources: SAM.gov for notices and award data, USAspending.gov for obligations and period of performance dates, agency procurement forecasts for what is coming, and CPARS for your own performance record.
| Source | What you pull into the pipeline |
|---|---|
| SAM.gov Contract Opportunities | Sources sought, special notices, presolicitations, solicitations, amendments, award notices |
| SAM.gov contract award data | Incumbent, contract number, NAICS, PSC, vehicle, and action history (formerly FPDS.gov) |
| USAspending.gov | Obligations by agency and recipient, period of performance end date and potential end date |
| Acquisition.gov procurement forecasts | Links to agency forecasts, including GSA's forecast of contracting opportunities |
| CPARS | Your evaluations, which future source selection teams will read |
One change to note: GSA decommissioned FPDS.gov ezSearch on February 24, 2026. Contract award search now lives in SAM.gov, and the legacy ATOM feed is being replaced by the SAM.gov Contract Awards API on open.gsa.gov. If your spreadsheet or CRM still pulls from the old FPDS feed, fix that integration.
How do you track recompetes from USAspending and SAM.gov award data?
Pull every active award in your NAICS and PSC codes at your target agencies, record the incumbent and the potential end date including options, and work backward. A recompete usually needs capture effort 18 to 24 months before that date, which is long before any notice appears on SAM.gov.
- Search award data in SAM.gov and USAspending by agency, NAICS, and PSC.
- Record contract number, incumbent, vehicle, set-aside, current end date, and potential end date.
- Flag anything ending within 24 months as a recompete record in the pipeline.
- Check the agency forecast for the follow-on and note any change in set-aside or vehicle.
- Assign an owner and the first capture gate date.
That lead time is a working practice, not a regulation.
What capture gates and teaming data belong in the pipeline?
Record every gate decision with a date, a decision maker, and the reasons. Gates turn a list of opportunities into a managed portfolio, and teaming fields keep partner commitments from falling through the cracks between BD, capture, and contracts.
- Gate 1, qualify: fit with NAICS, vehicle access, past performance, and set-aside eligibility.
- Gate 2, pursue: customer contact plan, competitor read, and teaming gaps identified.
- Gate 3, bid/no-bid: decided on the draft or final solicitation, with price-to-win and staffing confirmed.
- Gate 4, submit: final review, compliance check, and approval to price.
- Teaming: partner name, role, workshare, NDA date, and teaming agreement status. FAR 9.601 defines a contractor team arrangement as either a partnership or JV acting as prime, or a prime with agreed subcontractors.
- Past performance: CPARS ratings on each reference. Under FAR 42.1503, you have up to 14 calendar days to comment on an evaluation, so log notification dates.
For who owns each gate, see capture vs. BD vs. proposal manager roles.
Spreadsheet or CRM: which one fits your firm?
Use a spreadsheet if one person owns BD and you track a few dozen pursuits. Move to a CRM once multiple people touch the pipeline, you hold or chase several vehicles, or leadership needs weighted pipeline reporting. Either way, the fields matter more than the software.
| Your situation | Recommended tool | Why |
|---|---|---|
| Solo founder, first contract vehicle, under ~25 pursuits | Structured spreadsheet | Low cost, fast to change, enough for one owner |
| First BD hire, shared pipeline | Spreadsheet with strict ownership, or a light CRM | Version control becomes the main risk |
| BD, capture, and proposal staff working together | CRM configured with federal fields | Gate history, task alerts, shared contact records |
| Several vehicles, teaming on most pursuits | CRM with partner and vehicle objects | Spreadsheets break on many-to-many relationships |
| Need reporting tied to finance or ERP | CRM integrated with back office | Pipeline forecast feeds hiring and cash planning |
Deciding on that first hire? Read when to hire your first business development person and hiring across capture, BD, and proposal roles.
What should you do now?
- Add stage, vehicle, NAICS, PSC, set-aside, incumbent, and potential end date columns to your current pipeline this week.
- Redefine every stage around a public government action: forecast, sources sought, RFI, draft RFP, solicitation, award.
- Rebuild your recompete list from SAM.gov award data and USAspending, and replace any FPDS.gov feed.
- Write down your gate criteria and record every bid/no-bid decision with the reason.
- Move to a CRM only when you can configure those federal fields; do not buy one and track commercial stages.
If you want help building a federal pipeline that matches how agencies actually buy, see how Blackfyre supports federal sales and business development. I bring the Contracting Officer view to your pipeline, capture gates, and agency targeting.
Frequently Asked Questions
Is a spreadsheet good enough for a small GovCon business pipeline?
Yes, if one person owns it and you track a manageable number of pursuits. Add federal-specific columns such as vehicle, NAICS, PSC, set-aside, incumbent, and potential end date. Move to a CRM when multiple people edit it or deadlines start slipping.
What fields should a government contractor CRM include?
At minimum: acquisition stage, agency and contracting office, contract vehicle, NAICS and size standard, PSC, set-aside type, incumbent, period of performance end dates, teaming partners, gate decisions, and past performance references. Commercial CRMs usually need custom fields for most of these.
Where do I find recompete dates for federal contracts?
Use contract award data in SAM.gov and award records on USAspending.gov, which show period of performance end dates and potential end dates. Pair that with agency procurement forecasts linked from Acquisition.gov to see whether a follow-on is planned.
Is FPDS.gov still available for contract award data?
No. GSA decommissioned FPDS.gov ezSearch on February 24, 2026, and contract award data now lives in SAM.gov. Programmatic users should move to the SAM.gov Contract Awards API on open.gsa.gov.
Why should I respond to sources sought notices if there is no solicitation yet?
Sources sought responses feed the agency market research the Contracting Officer uses to decide on set-asides under FAR 19.502-2. If you are not in that response file, you have no influence on how the work is structured.
How far ahead should I start capture on a recompete?
A common working practice is 18 to 24 months before the incumbent contract potential end date. Larger or more complex follow-ons often need more lead time, because the requirement and set-aside decisions are shaped well before any notice posts.
Should CPARS ratings be tracked in a BD pipeline?
Yes. Past performance evaluations are entered in CPARS under FAR 42.1502 and can support future award decisions. Track which references map to each pursuit and log notification dates, since FAR 42.1503 gives you up to 14 calendar days to comment.