Sources Sought Is Your Unfair Advantage. Here's How to Use It.

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 (also called “Request for Information” or RFI) is the government's way of asking: “Before we write a solicitation, who's out there capable of doing this?”

The agency uses responses to answer three practical questions:

1. Is there enough capable small business to set this aside? If at least 2 qualified small businesses respond, the Rule of Two requires them to set it aside for small business (or further — 8(a), HUBZone, SDVOSB).
2. What's technically feasible? The agency shapes the eventual RFP around what respondents say is achievable, cost-effective, and realistic.
3. Who has the capacity?Program offices make mental lists of who they'll invite to the pre-solicitation conference, who they'll flag for teaming conversations, and who they expect to compete hard.

Why 80% of winners respond

Three reasons the correlation is so strong:

1. You shape the RFP

Your response influences the requirements document. If you have a unique capability — say, a specific certification or a geographic presence — and you describe it clearly in your response, that capability often shows up as a mandatory requirement in the eventual RFP. Your competitors are now out before the game starts.

2. The program office already knows you

By the time the RFP drops, a contracting officer who remembers your Sources Sought response has a mental shortlist. You're not a cold entry in a pile of 40 proposals — you're “oh yeah, those folks from February.”

3. You can force a set-aside

If you're a qualified small business (SDVOSB, 8(a), HUBZone), responding makes the Rule of Two math work in your favor. Two qualified responses = the agency mustset it aside. One response = they can go full-and-open. You're literally controlling competitive structure by submitting.

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)

3-4 paragraphs: who you are, what you understand the requirement to be, why you're relevant, and your high-level recommendation. Most contracting officers read this page and skim the rest.

3. Capability response (2-4 pages)

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

• Direct answer — can you do it, yes/no
• Supporting evidence — past performance citation, cert, staff credential
• Relevant detail— what's specific about your approach

4. Past performance (1-2 pages)

3-5 contracts with agency, dollar value, period, your role, and outcome. Mirror the requirement — don't list unrelated commercial work.

5. Recommendations (0.5 page)

This section is underused. Give the agency specific, professional recommendations about 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 maintain a Sources Sought response template for every industry our clients operate in. Here's the high-level structure, ready to reuse:

Never copy-paste prior responses verbatim. Contracting officers spot boilerplate immediately. Start with your template, rewrite the executive summary and recommendations for the specific notice.

After you submit

Submission is the start, not the end. The 30 days after a Sources Sought response are where most of the capture value is created:

• 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

The bottom line

Sources Sought is the single highest-leverage capture move a small veteran-owned firm can make. The responses take 4-8 hours. The upside is 6 months of relationship equity with a program office that's about to write an RFP. Nothing else in capture has that ratio.

Respond to 2-3 per month. Keep the template tight. Build a routine around it. Twelve months in, you'll be on the mental shortlists of half a dozen program offices — and that's where real pipeline comes from.