A sources sought notice or a request for information is market research. The government is asking who can do the work, how the work should be bought, and whether its draft requirement makes sense. The answers feed the acquisition strategy: the scope, the contract type, the vehicle, and whether the work is set aside for small business. Once the solicitation is released, most of those decisions are fixed. The response to the notice is the last cheap chance to shape them.
Most responses waste it. A company attaches its capability statement, adds a paragraph of marketing, and moves on. The contracting officer learns that the company exists and nothing else.
What a useful response does
- Answers every question asked, in the order asked, with the notice's own numbering. Reviewers read responses side by side; make yours easy to score.
- States size and socioeconomic status plainly, on the first page. If enough capable small businesses respond, the work can be set aside. Your response is part of that count.
- Shows comparable work: similar scope, size, and complexity, described in a sentence or two each. Comparable means comparable. A stretch weakens the whole response.
- Recommends. Suggest the NAICS code that fits, the contract type that matches the risk, and a vehicle the customer already uses. Point out where the draft scope is unclear or where two requirements pull against each other.
- Respects the limits. Page counts, file formats, and due dates are read as a test of whether you follow instructions.
What to leave out
- Pricing, unless the notice asks for it. A rough estimate offered unasked can anchor the government's estimate in a way you will regret.
- Proprietary solution detail. The response may be shared more widely than you expect. Describe the approach, not the secret.
- Promises you cannot keep. Anything you write here can be read back to you at proposal time.
Ask the questions that shape the requirement
A notice that invites questions is an invitation to steer. Ask about the incumbent's scope, the expected period of performance, how performance will be measured, and which outcomes matter most. Good questions show the customer that you understand the mission. They also expose assumptions in the draft that every bidder would otherwise have to price as risk.
Then treat it as capture
A response is not a finish line. It is the start of a capture file. Log the notice, the response, the questions you asked, and the people you met at any industry day. Watch for the draft solicitation and compare it with what you recommended. If the final scope moved toward your response, you have learned something about how this customer listens. If it moved away, you have learned something too. Either way, the bid or no-bid decision at the next gate review is better informed.
Layered Intel runs sources sought and RFI responses as part of capture: finding the notices worth answering, drafting responses that answer the questions and shape the buy, and carrying what you learn into the pursuit.