How to Write a Sources Sought Response That Gets You Noticed
A sources sought notice is not junk mail — it is a contracting officer asking whether your company can do the work before they finalize the acquisition strategy. Here is how to respond in a way that shapes the solicitation in your favor.
Priya Nair
A sources sought notice is market research. The contracting officer (CO) is deciding whether to set a contract aside for small businesses, whether to bundle requirements, and which NAICS code to assign — all based on what comes back. Most small businesses ignore them. The ones who respond well end up influencing the final solicitation language, and sometimes the CO writes their specific capabilities directly into Section L.
What a sources sought response is actually used for
COs are required by FAR 10.001 to conduct market research before every acquisition above the simplified acquisition threshold ($250,000). The sources sought notice is one of the primary instruments. Responses directly inform three decisions that are very hard to change later.
- Set-aside determination: if two or more capable small businesses respond, the CO can set it aside (the "Rule of Two")
- NAICS code selection: if respondents flag the proposed code as wrong, COs often update it — changing your size eligibility
- Period of performance and scope: responses that identify execution risks can result in scope reduction or phased awards
- Bundling decisions: if responses show multiple small businesses can perform each component, bundling becomes harder to justify
- Acquisition strategy type: IDIQ vs. single award vs. multi-award BPA choices are all influenced by market research
- Evaluation criteria: capable respondents with unique approaches sometimes see their differentiators reflected in Section M
What the CO actually reads in your response
Most COs spend two to five minutes on each response. They are looking for three things: whether you are a real company that can do this work, whether you are the right size, and whether your experience is genuinely relevant. Everything else is noise.
- Company name, CAGE code, UEI, SAM.gov registration status — confirmed active
- Business size and socioeconomic certifications (8(a), SDVOSB, HUBZone, WOSB) with certification status
- Relevant experience: at least two to three prior contracts of similar scope, with dollar values and agency names
- Technical capability: a specific description of how you would approach the work — not a generic capability statement
- Teaming intent: if you plan to prime with a subcontractor, say so and identify the teammate
- Questions or concerns about the scope, period of performance, or NAICS code assignment
The five-part structure that works
Sources sought responses do not have a mandated format unless the notice specifies one. When they do not, use this structure. It hits everything the CO needs and stays readable in under three minutes.
- 1. Company profile: name, address, CAGE/UEI, SAM.gov status, NAICS codes, business size, certifications
- 2. Relevant experience: two to three contracts — agency, contract number, dollar value, brief description, period of performance
- 3. Technical approach: two to three paragraphs describing specifically how you would solve the problem
- 4. Teaming: confirm whether you are pursuing as prime, sub, or in a team — and name the team if known
- 5. Comments on the requirement: scope questions, NAICS concerns, period of performance issues
The detail level that separates a useful response from a generic one
Generic capability statements do not help COs make decisions. Specific responses — ones that reference the actual requirement, name past contracts at the same agency or in the same mission space, and flag real technical or contractual issues — are what get read twice and sometimes forwarded to the program office.
- Reference the specific notice: use the SAM.gov notice number and quote the relevant scope language
- Name the agency you are speaking to: "We supported DHS CBP on a similar requirement under contract #HSBP..." lands differently than "we support federal agencies"
- Include a dollar value on every past performance reference — this tells the CO whether your experience is scaled appropriately
- Flag NAICS mismatches explicitly: "The proposed NAICS 541519 covers general IT support; the scope described aligns more closely with 541512 (Computer Systems Design)" is useful
- Ask a real question: COs appreciate questions that show you read the requirement carefully — it also gets you a one-on-one exchange in some cases
- Stay under four pages: longer responses are not more persuasive; they are skipped or skimmed
How early to engage — and when not to
Sources sought are often posted 60–120 days before a solicitation drops. But if you have been doing good capture work, you may have been in contact with the program office for six months before the notice appears. Responding to sources sought without any prior engagement is a cold start. It still works — but it is less effective than responding after you have already had a capability briefing.
- Pre-notice: monitor agency procurement forecasts and submit unsolicited capability statements 90–180 days out
- At notice: submit a strong response within the first half of the response window — late responses carry no weight
- Post-response: if the CO responds with questions, answer quickly and completely
- Do not respond to everything: if you cannot name at least two prior contracts with relevant scope, your response weakens the pool rather than strengthening it
- Do not respond to recompetes you are not tracking: incumbents know the requirements; a cold response from a new vendor rarely changes the outcome
One mistake that gets responses discarded
Attaching a marketing PDF instead of answering the question. COs post specific questions in sources sought notices — "describe your experience with X", "confirm your business size under NAICS Y". Companies that attach a generic brochure instead of directly answering those questions get set aside immediately. Read the notice. Answer the questions in the order they were asked.
- Write your response as a structured document that answers each question in the notice — numbered, if the notice uses numbers
- Do not attach PDFs unless the notice asks for them — the response itself should be self-contained
- Sign the response with a named point of contact, direct phone number, and email — anonymous submissions raise flags
- Submit before the deadline: sources sought responses submitted after the closing date are not read
Frequently Asked Questions
Is responding to a sources sought required?
No. Responding is voluntary. But if you are tracking an opportunity and want to influence the acquisition strategy, responding is the only formal channel you have at this stage.
Does responding to a sources sought help you win the contract?
Not directly — responding does not give you a scoring advantage in the proposal. But it can result in NAICS corrections, set-aside decisions, or scope clarifications that improve your competitive position before the solicitation even drops.
Can I respond to a sources sought if I do not have exactly the right past performance?
Yes, but be honest. Flag that your experience is adjacent, explain why it is relevant, and propose a teaming arrangement that covers the gap. COs use responses to understand the market — partial capability is better than silence, as long as you are accurate.
How long should a sources sought response be?
Two to four pages is standard. One page is acceptable if the notice is narrow. More than five pages is too long unless the notice specifically asks for detailed information.
Put this into practice
GovPillar helps you apply everything in this guide — AI-scored opportunities, RFP shredding, capture pipeline, and more. Free to start.