Sources Sought Is Your Unfair Advantage

If you're only looking at RFPs, you're 6 months late to every competition. Sources Sought notices — the RFIs that agencies post before they write an RFP — are where the real shaping happens. Firms that respond to Sources Sought win the resulting contract 80% of the time (industry estimates vary from 60-85%, but the pattern is consistent).

Most veteran-owned small businesses skip Sources Sought because the response “doesn't pay.” That's exactly backwards. Here's how to use them correctly.

What Sources Sought actually is

A Sources Sought notice (sometimes posted as an RFI — Request for Information) is the government asking, in writing: “Before we write the solicitation, who's out there who could actually do this?”

The agency uses the responses to figure out three things:

1. Can we set this aside for small business? If at least two qualified small businesses respond, the Rule of Two kicks in and the agency has to set it aside (small business, or further — 8(a), HUBZone, SDVOSB).
2. What's actually realistic?The eventual RFP gets shaped by what respondents say is achievable. If everyone says “six-month delivery is too tight,” the agency hears that.
3. Who's on the shortlist? Program offices build mental notes — who to invite to the pre-solicitation conference, who to introduce to teaming partners, who they expect to bring a real proposal.

Why the 80% number isn't an accident

Three reasons the correlation is that strong:

1. You shape the RFP

Your response goes into the requirements draft. If you have a unique capability — a specific certification, a regional presence, a piece of equipment most don't own — and you describe it clearly, it often surfaces as a mandatory requirement in the final RFP. Half your competitors are out before the bid window opens.

2. The program office already knows your name

When the RFP drops, the contracting officer reads forty proposals. Yours is “oh yeah, those folks from February.” Everyone else is a cold entry. That's a small thing on paper and a huge thing in practice.

3. You can force a set-aside

If you're a qualified small business (SDVOSB, 8(a), HUBZone), your response makes the Rule of Two math work. Two qualified responses and the agency has toset it aside. One response and they can go full-and-open. By submitting, you're shaping the competitive structure of the contract before it exists.

The 6-month pre-RFP timeline

A realistic capture timeline when you spot a Sources Sought you want to pursue:

• Day 1: Spot the notice. Decide bid / no-bid in 48 hours.
• Day 3-5: Draft your response (4-8 pages).
• Day 7-14: Email the contracting officer with a question or brief intro.
• Day 15-21: Request a capabilities briefing (30-min call).
• Day 30-60: Build teaming relationships with other respondents.
• Day 60-90: Follow up; watch for pre-solicitation notices.
• Day 120-180: RFP drops. You've done 4+ months of capture. Competitors are starting.

The response structure

A standard Sources Sought response is 4-8 pages and follows this structure:

1. Cover page

Your logo, company name, UEI, CAGE, cert stack (SDVOSB/HUBZone/8(a)/WOSB), and the notice number. Make it easy to file.

2. Executive summary (1 page)

Three or four paragraphs. Who you are, what you read the requirement to be, why you're relevant, and one high-level recommendation. Most contracting officers read this page and skim the rest. Spend time here.

3. Capability response (2-4 pages)

Answer every question in the notice, in order, using the same numbering. For each:

• Direct answer — yes or no, no hedging
• Supporting evidence — a past performance citation, a cert, a named staff credential
• What's specific about your approach — one or two lines

4. Past performance (1-2 pages)

Three to five contracts. Agency, dollar value, period of performance, your role, outcome. Mirror the requirement — don't pad with unrelated commercial work, the evaluator will notice.

5. Recommendations (0.5 page)

Most small firms skip this. Don't. Give the agency specific, professional suggestions on how to structure the eventual RFP:

• “We recommend Sources Sought set aside for SDVOSB given the qualified pool.”
• “Consider splitting into 2 lots by geography to increase competition.”
• “Minimum technical requirements should include CMMC Level 2 given the data sensitivity.”

6. Point of contact

Named person. Direct phone. Direct email. Available for follow-up.

Templates & examples

We keep a Sources Sought response template for every industry our clients work in. High-level structure, ready to drop into your Word doc:

Don't copy-paste old responses verbatim. Contracting officers spot boilerplate in about ten seconds. Start from your template, then rewrite the executive summary and recommendations against the specific notice. Sixty extra minutes here is worth more than the rest of the response combined.

What happens after you submit

Submission is the start of the work, not the end. The thirty days after you send a Sources Sought response are where most of the capture value gets built:

• Email the contracting officer a brief thank-you + offer to answer follow-up questions
• Request a 30-min capability briefing call (most COs will say yes if you ask)
• Attend the pre-solicitation conference if one is announced
• Monitor FBO / SAM.gov daily for the pre-solicitation or RFP notice
• Build teaming relationships with other respondents in the same NAICS
• Update your capture plan with intel from the briefing + response

So what does this actually look like as a habit?

Four to eight hours per response. You get six months of relationship equity with a program office that's about to write an RFP. We don't know another capture move with that ratio.

Two or three responses a month. Keep the template tight, swap in the specifics each time. A year in, you're on the mental shortlists of half a dozen program offices. That's where pipeline actually comes from.