Sources Sought Notices: How to Respond and Win Contracts Before the RFP

Most small businesses lose government contracts months before the RFP is even written. They lose at the sources sought stage, a step the majority of first-time bidders do not know exists.

A sources sought notice is the contracting officer's market research call. They are deciding whether the work can be set aside for small businesses, what the statement of work should include, and which vendors are credible. The companies that respond well to sources sought get to influence those answers. The companies that ignore them get an RFP that has already been shaped around someone else's strengths.

This guide explains how to respond to sources sought notices in a way that actually moves the procurement in your direction. You will learn what these notices are, how to read the contracting officer's intent, what a strong response includes, and how to build a bid/no-bid framework so you spend your time on the right ones. We will also cover the realistic outcomes, what happens in the weeks and months after you submit.

If your firm has a small footprint of past performance and you are trying to break into a new agency or capability area, sources sought is the most asymmetric leverage point you have.

Quick Answer: How to Respond to a Sources Sought Notice

A sources sought notice is a federal market research request issued by a contracting officer before the RFP. The contracting officer is trying to determine two things: are there at least two qualified small businesses that can do the work (so the requirement can be set aside), and what should the actual statement of work say. Your response shapes both decisions.

To respond well:

Read the notice line by line and identify every task, capability, or question the contracting officer asks.
Address each item directly, with three to five concrete past performance examples (contract number, agency, period, value, and your specific role).
State your socioeconomic status, 8(a), HUBZone, WOSB, EDWOSB, SDVOSB, small business under the relevant NAICS, and your UEI.
Recommend specific edits to the requirement where you have evidence (preferred period of performance, modular scope, qualifications). This is the highest-leverage section.
Submit before the close date through the email or portal listed, even though late responses are typically accepted.
Follow up with a brief introductory email to the contracting officer.

A strong response can trigger a small business set-aside, drive language into the SOW that fits your strengths, and place your firm at the top of the contracting officer's pursuit list when the RFP drops.

What Is a Sources Sought Notice (And What It Is Not)

A sources sought notice, sometimes labeled "sources sought synopsis" or simply "market research", is a federal pre-solicitation announcement issued under the authority of FAR Part 10 (Market Research) and posted to SAM.gov Contract Opportunities. The contracting officer is asking the marketplace: who can do this work, what does it cost, and what should we put in the solicitation.

It is not:

A request for proposal (RFP) or request for quote (RFQ).
A guarantee that a contract will be awarded.
A request for a binding price quote.
A formal solicitation that you must respond to in any specific format.

It is also distinct from a request for information (RFI), although the two are often used interchangeably. An RFI usually focuses on technical questions or capability validation. A sources sought notice focuses on identifying qualified vendors, evaluating small business interest, and shaping acquisition strategy. In practice, the response approach is similar.

The key thing to remember: the contracting officer has not yet decided how to buy this work. Your response is part of how they decide.

Why Sources Sought Is the Highest-Leverage Step in Government Contracting

By the time an RFP is published, most of the consequential decisions are already made. The set-aside category is set. The evaluation criteria are written. The period of performance is fixed. The technical approach the SOW expects is implied. If you wait for the RFP, you are responding to a procurement that has been shaped by other vendors, often the incumbent, during the sources sought phase.

This is why capture management in government contracting starts at sources sought, not at the RFP. The shaping window is open here and only here. Three things that can shift in your favor during this window:

Set-aside designation. If the contracting officer sees two or more credible small businesses respond, they are required under the Rule of Two (FAR 19.502-2) to set the procurement aside for small business. If only your firm responds with credible past performance, the requirement may pivot to sole-source under 8(a) or another set-aside vehicle.
Statement of work language. Contracting officers regularly cut and paste vendor capability descriptions directly into the draft SOW. Your wording shapes what the eventual RFP asks for.
Period of performance and contract structure. If you point out that a 12-month base with four option years is more efficient than a 5-year fixed-price contract, and you have evidence, contracting officers listen.

For first-time bidders, the difference between winning and losing often comes down to whether you showed up at sources sought. The win rate for first-time bidders responding cold to a published RFP sits at roughly 3%. That number climbs sharply when the bidder participated in the pre-RFP shaping process.

How Contracting Officers Actually Use Your Response

Understanding the contracting officer's job at this stage helps you write a response they can actually use. Three things they are doing simultaneously:

1. Justifying the acquisition strategy

Federal acquisition regulation requires the contracting officer to conduct market research and document their findings (FAR 10.001). Your response goes into that documentation. If they end up choosing full and open competition over a small business set-aside, they need a defensible record showing they tried to find small business sources. Your detailed, qualified response either supports or undermines that record.

2. Drafting the statement of work

Most SOWs are written collaboratively between a program office (which knows what the agency needs) and the contracting officer (who knows how to buy it). Vendor responses to sources sought become reference material. Specific language about deliverables, methodology, and deliverable timelines often appears verbatim in the final SOW. This is the most underused leverage point in federal capture.

3. Building the pursuit list

When the RFP drops, the contracting officer already knows which vendors responded to the sources sought, who has the strongest past performance, and who is likely to bid. Vendors who did not respond start the RFP race two laps behind.

Your response should make all three of these jobs easier. A clear, organized, task-by-task response is the kind of document a contracting officer can pull straight into their market research summary. A vague capability statement attached to a generic email is not.

What a Strong Sources Sought Response Includes

There is no single mandated format. The notice itself usually lists what the contracting officer wants. Your job is to give them everything they asked for, in the order they asked, with no padding. A typical response is three to seven pages, long enough to be substantive, short enough that a contracting officer can read it during a single pass.

A strong response includes the following sections:

Cover information

Company legal name, UEI, CAGE code
Point of contact (name, title, email, phone)
NAICS code(s) you bid under
Socioeconomic status (small business size standard, 8(a), HUBZone, WOSB/EDWOSB, SDVOSB, etc.)
Whether you intend to bid as a prime, subcontractor, or both

Tailored capability statement

This is not the generic capability statement you upload to vendor portals. Tailor it to the specific scope of this notice. If the notice asks about IT modernization for a federal civilian agency, do not lead with your DoD logistics history.

Task-by-task response

Break out each task or requirement listed in the notice. For each one, write two or three sentences explaining how your firm has done that work, plus a specific past performance example.

Past performance examples

Three to five recent (last three to five years), relevant past performance entries. For each one include:

Contract or task order number
Agency or commercial customer
Period of performance
Total dollar value
Your specific role (prime, sub, percentage of work)
A two-sentence description of what you delivered

If you are a first-time federal bidder, commercial past performance counts, describe scope, scale, and outcome. See our guide on breaking into government contracting without past performance for how to position yourself.

Recommendations on the requirement

This section is optional in most notices but it is where the highest-leverage shaping happens. Recommend specific changes to the period of performance, contract structure, evaluation factors, or scope, always anchored in evidence from your past performance. For example: "On similar enterprise help desk transitions, a 90-day phase-in period reduced ticket resolution lapse by 38%. We recommend a 90-day phase-in be included in the SOW."

Pricing approach (only when asked)

If the notice asks for rough order of magnitude (ROM) pricing or labor categories, provide them. Be conservative, this is not a binding bid, but contracting officers do remember unrealistic numbers. If the notice does not ask for pricing, do not volunteer it.

The Mistake That Kills 80% of Responses

The single most common failure mode is sending a generic capability statement attached to a brief email. Contracting officers receive dozens of these per notice. They are functionally invisible.

Compare two responses to the same notice for federal data center migration services:

Generic (the kind that gets ignored):

"ABC Tech is a small business with 15 years of IT modernization experience. We hold an active GSA Schedule and are 8(a) certified. Our past performance includes work for DoD, DHS, and the Department of Education. Please find our capability statement attached."

Tailored (the kind that gets the SOW edited):

"ABC Tech specifically performs Tier-2 federal data center consolidations under [agency program] specifications, which is the closest analog to the work described in your notice. Of the seven tasks you listed, we have direct past performance on tasks 1, 2, 4, and 6. On Task 4 (legacy application discovery), our work for [Agency] under contract [number] inventoried 1,247 applications across 14 sites in 90 days, identifying $4.2M in annual licensing redundancy. We recommend the SOW require automated discovery rather than manual surveys, given the scale you describe. We are 8(a), HUBZone, and SBA-certified small under NAICS 541512."

The second version is roughly the same length. It does five things the generic version does not: it maps to the notice's specific tasks, it cites a contract number and quantified outcome, it recommends a specific SOW change, it stacks socioeconomic certifications relevant to set-aside decisions, and it gives the contracting officer something to copy into their market research memo.

This is what shaping looks like in practice.

How to Find Sources Sought Notices

Sources sought notices are published in three places:

SAM.gov Contract Opportunities

The official source. Filter the Contract Opportunities search by Notice Type = "Sources Sought" or "Special Notice." Save searches by NAICS code and set up email alerts. This is free and authoritative.

Agency procurement forecasts

Most cabinet agencies publish annual procurement forecasts that signal upcoming sources sought activity months in advance. Examples include the DHS, GSA, and VA forecasts. These are the highest-value early-warning signal in federal capture.

APEX Accelerator network

The SBA-funded APEX Accelerator network (formerly PTAC) provides free counseling and bid match services in every state. Many APEX offices forward relevant sources sought notices to registered small businesses. If you have not registered with your state APEX office, do that this week.

For a broader walkthrough of how to find federal opportunities at all stages, see our guide on how to find government contracts.

A Bid/No-Bid Framework for Sources Sought

Sources sought responses are cheap compared to RFP responses, but they are not free. A serious response takes four to eight hours of focused work. Build a quick scoring framework so you spend that time on the right notices.

For each notice, score on five dimensions (1-5 each, max 25 points):

A score of 18 or higher is a clear yes. 14-17 is a maybe; respond if you have bandwidth or want to build a relationship with the contracting officer. Below 14, decline and spend the time elsewhere.

This framework will save you from the most expensive failure mode in government contracting: spending capture hours on requirements you were never going to win.

What Happens After You Respond (Realistic Outcomes)

Three to twelve weeks after you submit, one of four things will happen.

Outcome 1: The RFP drops with a set-aside that favors you. The most common positive outcome. The contracting officer found enough qualified small business respondents to invoke the Rule of Two and set the procurement aside. Your name was on that list. You now have a much better shot at the RFP.

Outcome 2: The SOW reflects your input. When the RFP drops, you read the SOW and find phrasing, scope, or evaluation factors that match the recommendations in your sources sought response. This is the highest-value outcome because the eventual RFP is now structured around your strengths.

Outcome 3: A sole-source award or directed buy. Less common but real. If only one credible small business responded under a set-aside-eligible NAICS, the procurement may proceed as a sole-source award under 8(a), HUBZone, or another vehicle. This is the most asymmetric outcome in federal contracting.

Outcome 4: Silence. No RFP drops, or the RFP drops as full-and-open competition without a set-aside. This happens about a third of the time. Add the contracting officer to your CRM, follow the agency's procurement forecast, and look for the next opportunity. Sources sought activity is a signal that the agency is buying in this space; a no this quarter is not a no forever.

In all four cases, the contracting officer now knows your firm exists. That awareness compounds across multiple sources sought responses to the same agency.

From Sources Sought to RFP Win

The capture loop closes when the RFP drops. By then, you should already have:

A draft technical approach mapped to the SOW (because you helped shape the SOW)
Past performance write-ups updated and CPARS-validated
Teaming partners identified for any capabilities you cannot self-perform
A pricing approach informed by your ROM submission

This is the difference between treating an RFP response as a sprint and treating it as the final stage of a months-long capture process. Firms that build a sources-sought-first capture rhythm see proposal win rates climb from the industry-average 3% to 15-25% over time, the same range as experienced small businesses with dedicated proposal operations.

For the actual RFP-response mechanics once the solicitation drops, see our complete guide to winning government proposal writing strategies.

When to DIY vs Partner With Specialists

You can respond to sources sought notices yourself. The format is permissive, the rules are documented, and the upside is real. If you have one or two people on your team with the time, the writing skill, and the federal contracting context to do the work, this is one of the highest-leverage activities they can spend hours on.

You may want a partner if:

You are evaluating ten or more sources sought per quarter and cannot triage them in-house.
You are entering a new agency or capability area where you do not yet have past performance to anchor the response.
You want to convert sources sought participation into a structured pipeline with bid/no-bid scoring, capture plans, and proposal handoff.
You have already identified specific small business certifications but have not yet figured out how to translate them into early-stage shaping wins.

Specialists like SLED.AI work alongside small businesses to build a sources-sought-first capture rhythm and carry the work through to RFP submission. The decision is not "DIY or pay someone else to do it." It is whether you have the bandwidth and judgment in-house, or whether the math favors a partner who has run this loop hundreds of times. Either path is valid. The path that loses is ignoring sources sought entirely.

The companies winning their first government contract in 2026 are not the ones who write better RFP responses. They are the ones who showed up before the RFP existed.

Sources Sought Notices: How to Respond and Win Contracts Before the RFP