Capture Before the RFP Drops: Shaping a Requirement You Can Win

A contracting officer at a civilian agency issues a Sources Sought notice for a five-year IT modernization effort. Forty-three vendors respond. Thirty-eight of them are seeing the requirement for the first time. The other five have been in the building for months, attending industry days, responding to RFIs, and briefing the program office on technical approaches. When the RFP drops ninety days later, those five companies recognize their own language in Section C. The other thirty-eight are writing to a requirement they did not help shape.

That gap, between vendors who shaped the requirement and vendors who are reacting to it, is where most federal competitions are decided. Pre-RFP capture is not a nice-to-have activity. It is the work that determines whether your proposal is a genuine contender or a compliant also-ran.

Why Shaping Matters More Than Writing

Federal acquisition is structured to be competitive, but it is not structured to be neutral. The FAR allows program offices to conduct market research (FAR Part 10), issue RFIs, hold one-on-one meetings with industry, and accept unsolicited proposals (FAR Subpart 15.6). None of that is improper. All of it creates asymmetric information between vendors who engage early and vendors who wait for the solicitation.

When a program manager writes a Statement of Work, they draw on what they know. If what they know includes your past performance, your technical methodology, and your team's specific credentials, those elements tend to appear in the requirement. Not because of any impropriety, but because the PM is solving a real problem and they reach for solutions they have already seen demonstrated.

Shaping a requirement means becoming the reference architecture in the program manager's head before the PWS is drafted.

The Capture Timeline: Working Backward from RFP Release

For a competitive acquisition above the simplified acquisition threshold, a realistic pre-RFP capture timeline looks like this:

• 12 to 18 months out: Identify the opportunity in USASpending, FPDS, or agency budget justifications (CBJ documents). Confirm the incumbent, contract vehicle, and period of performance end date.
• 9 to 12 months out: Submit an RFI response if one exists, or request a capability briefing with the program office. Attend any pre-solicitation industry days. File a FOIA request for the incumbent's contract if you need scope details.
• 6 to 9 months out: Develop a technical white paper or solution brief tailored to the agency's stated pain points. Deliver it in a follow-up meeting. Identify subcontractors or teammates who fill gaps in your past performance or clearance posture.
• 3 to 6 months out: Respond to any draft PWS or draft RFP with substantive comments. Comment on evaluation criteria, period of performance structure, and NAICS code selection if any of those affect your competitive position.
• 30 to 60 days out: Finalize teaming agreements. Lock your price-to-win analysis. Confirm your win themes map to the evaluation factors as written.

Most small businesses enter this process at the thirty-day mark. That is not capture. That is proposal writing under pressure.

What a Capability Briefing Actually Accomplishes

A capability briefing is not a sales call. Program managers and CORs are not buying anything in that meeting. What they are doing is building a mental model of the vendor landscape. Your job is to leave them with three things: a clear picture of what you have done (past performance with quantified outcomes), a credible technical approach to their specific problem, and a reason to believe you are lower risk than the incumbent or the large business prime.

Prepare a leave-behind that is five pages or fewer. Lead with relevant contract numbers and CPARS-level outcomes, not company history. If you supported a similar agency and reduced ticket resolution time by 34 percent, say that. If your team holds the specific clearances the program requires, list them. If you have a GSA MAS contract under the relevant SIN, note it, because it signals you have already cleared a procurement vehicle the CO may use.

Do not pitch. Diagnose. Ask the program manager what is not working with the current contract. Ask what the follow-on effort needs to accomplish that the current one does not. The answers will tell you exactly what to write in your proposal six months later.

Influencing the Evaluation Criteria

Section M is where competitions are won or lost, and Section M is written by humans who have opinions about what good performance looks like. If you have had substantive conversations with the program office, you have a chance to influence those opinions before they become evaluation factors.

Common leverage points include:

• Technical approach weighting: If your differentiator is methodology and the draft RFP weights price highest, submit a comment arguing that technical approach should carry more weight given the complexity of the requirement. Cite comparable acquisitions where the agency used a best-value tradeoff.
• Past performance recency and relevance: If the draft requires ten years of experience and your most relevant contract is four years old, comment that recency within the last five years better predicts performance on a modern technology effort.
• Contract vehicle restrictions: If the agency is considering restricting competition to a specific IDIQ vehicle you are not on, submit comments during the draft RFP period or engage your SBA Procurement Center Representative (PCR) if the set-aside structure disadvantages small businesses.
• NAICS code selection: The NAICS code determines size standards. If the assigned code does not match the principal purpose of the work, you have standing to request a change. The SBA's NAICS Appeal process exists for exactly this reason.

None of this is gaming the system. It is participating in the acquisition process the way the FAR intends. Agencies are required to consider industry comments on draft solicitations. Most agencies receive very few substantive ones.

Teaming as a Shaping Tool

Your teammates are part of your competitive position before the RFP drops, not just after. If the incumbent is a large business and the follow-on is likely to be set aside for small businesses, the large business will be looking for a small business prime to team with. Being that prime, rather than a sub, requires you to have the relationships and the past performance to lead.

Conversely, if you are missing past performance in a specific domain, a teaming agreement with a firm that has relevant CPARS citations can close that gap. Structure teaming agreements to be specific: define work share percentages, key personnel commitments, and which partner's past performance will be cited for which evaluation factor. A teaming agreement that says "we will collaborate on the proposal" is not a teaming agreement. It is a letter of intent with no operational value.

Tracking the Intelligence You Gather

Pre-RFP capture generates a lot of information: meeting notes, RFI responses, incumbent contract data, budget line items, org charts, and program office priorities. That intelligence is only useful if it is organized and accessible when you sit down to write. Build a capture file for every opportunity above your bid threshold. At minimum it should contain the opportunity source, key contacts, incumbent data, your competitive assessment, and your current go/no-go recommendation.

If you are managing multiple pursuits, our services page describes how IT Custom Solution LLC supports small business capture teams with structured opportunity tracking and proposal development workflows through Winrove, available at winrove.com starting at $49/mo.

The Takeaway

The RFP is a lagging indicator. By the time it posts on SAM.gov, the competitive landscape is mostly set. Vendors who engaged the program office, submitted RFI responses, commented on draft solicitations, and built relationships with the CO and COR have a structural advantage that no amount of proposal writing skill can fully overcome. Start your capture work when the opportunity appears in the budget, not when the solicitation appears on SAM. The companies winning competitive federal contracts are not better writers. They are earlier movers.

If you want to talk through your capture approach on a specific pursuit, reach out for a brief consult. No commitment required.