How to Respond to a Sources Sought Notice and Shape the RFP Before It Drops

The Decision Happens Before the Solicitation Posts

A contracting officer drafting a new requirement faces a practical problem: she does not always know what the market can deliver, at what price, or under what contract vehicle. The sources sought notice is her research tool. Your response is your opportunity to answer those questions on your terms, before the statement of work is locked, before the evaluation factors are weighted, and before a large business positions itself as the obvious choice.

Most small businesses treat sources sought responses as a box to check: name, CAGE code, NAICS code, a paragraph of boilerplate capability. That approach wastes the only pre-solicitation touchpoint the Federal Acquisition Regulation actually invites you to use.

What a Contracting Officer Is Actually Trying to Determine

FAR 10.002(b)(2) lists the market research methods agencies may use, and sources sought notices are one of the most common. When an agency posts one on SAM.gov, the contracting officer is typically trying to answer at least one of the following questions:

• Is there adequate competition among small businesses to justify a set-aside under FAR 19.502-2?
• Does the market include firms with relevant experience, or will the requirement need to be structured to attract capable offerors?
• What contract type, period of performance, or vehicle (IDIQ, BPA, standalone) fits the work?
• Are there NAICS code ambiguities that need to be resolved before the solicitation is drafted?

Each of those questions is a door. A well-constructed response walks through it.

Structure Your Response Around the CO's Decision Points

A sources sought response has no required format unless the notice specifies one. That flexibility is an advantage. Organize your response to address the CO's actual research questions rather than to summarize your company history.

1. Confirm Capability With Specificity

Generic capability statements do not move the needle. Instead, describe the specific technical approach or service delivery model you would bring to this requirement. If the notice describes a need for network operations center support at a civilian agency, do not write that your firm provides IT services. Write that your team operates a 24x7 NOC under SLA structures consistent with NIST SP 800-137 continuous monitoring requirements, with current past performance on contracts of comparable scope.

Reference real contract vehicles, real agency customers (where not restricted), and real performance outcomes. A contracting officer reading twenty responses will remember the one that sounded like it had already done the work.

2. Address the Set-Aside Question Directly

If the notice asks whether small businesses can perform the full requirement, answer directly. If you can, say so and explain why: your firm's size under the stated NAICS code, your teaming arrangements if the work requires a larger footprint, and any relevant certifications or clearances your key personnel hold.

If you believe the NAICS code is misaligned with the actual work, say that too. Propose an alternative NAICS code and cite the SBA size standard table. Contracting officers appreciate substantive market feedback, and a NAICS correction at the sources sought stage is far easier than a size protest after award.

3. Propose Scope or Structure Adjustments

This is where most small businesses leave value on the table. The sources sought stage is the correct moment to suggest that the requirement be broken into lots that small businesses can compete on independently, or that a particular performance standard is inconsistent with commercial practice and will artificially limit competition.

Frame these suggestions as market information, not complaints. Language like "based on our experience performing similar work under contract number XXXXXXX, a performance period of 12 months with two option years would allow offerors to price labor categories more accurately and reduce proposal risk" is useful to a CO. It is also language that may appear, lightly paraphrased, in the final RFP.

4. Surface Evaluation Factor Considerations

You cannot dictate evaluation factors, but you can plant seeds. If your firm's differentiator is a proprietary methodology, a cleared workforce, or a specific tool set, describe it in a way that makes it sound like a market standard. A CO who reads that three of five respondents emphasize transition planning and knowledge transfer may decide those belong in Section M.

The Follow-Up: One-on-One Market Research Meetings

Many agencies will schedule individual meetings with respondents after a sources sought closes. Request one explicitly in your response. A brief sentence at the end, offering to provide additional technical information or answer questions at the CO's convenience, signals engagement without overstepping.

In that meeting, listen more than you talk. Ask what aspects of the requirement the agency found most difficult to define. Ask whether the agency has a preferred contract type. Ask whether there are incumbent performance issues driving the new procurement. The answers will tell you more about how to win than any RFP section will.

What to Avoid

Several common mistakes reduce the impact of a sources sought response:

• Boilerplate capability statements copied from your SAM.gov registration. The CO has already seen your registration.
• Overselling past performance that does not match the scope. If your largest relevant contract was a fraction of the anticipated award value, acknowledge it and explain how your teaming arrangement addresses scale.
• Ignoring the specific questions in the notice. If the notice asks for a rough order of magnitude price range, provide one. Silence on a direct question reads as inability to answer.
• Submitting after the response date. Unlike a formal solicitation, there is no late-submission rule that requires the agency to consider your response. The closing date in the notice is the practical cutoff.

Connecting Sources Sought to Your Capture Process

A sources sought response should not be drafted in isolation. It belongs inside a broader capture plan that tracks the requirement from market research through award. That means logging the notice in your pipeline tool the day it posts, assigning a capture lead, and scheduling a debrief after the RFP drops to compare the final solicitation language against your response. Where your language appears in the RFP, you have evidence of influence. Where it does not, you have a gap to address in your proposal strategy.

Organizing past performance records, identifying which prior contracts map to the anticipated NAICS and scope, and flagging gaps in your capability coverage are all tasks that benefit from structured preparation well before the solicitation posts. Reach out to the IT Custom Solution team if you want to talk through how to build that preparation into your capture workflow.

A Note on Timing and Frequency

Sources sought notices sometimes precede an RFP by six months or more. Others appear two weeks before the solicitation. The response window is typically ten to thirty days. That means a capture team monitoring SAM.gov daily will have more time to craft a substantive response than one that discovers the notice a week after it posts. Set keyword alerts on SAM.gov for your target NAICS codes and agency offices. The notice is public information; the advantage goes to whoever acts on it first.

The Short Version

A sources sought response is market research from the agency's perspective and competitive positioning from yours. Answer the CO's actual questions: can small businesses perform this, what does the market look like, and how should the requirement be structured. Propose scope adjustments as market data, not advocacy. Request a follow-up meeting. Then use what you learn to write a sharper proposal when the RFP posts. The firms that shape the solicitation rarely have to fight as hard to win it.