How to Respond to a Sources Sought Notice and Shape the RFP

A sources sought notice is the one document in the federal pipeline where the government is actually asking for your opinion. Respond well and you can influence whether the eventual solicitation is set aside for small business, how the work is scoped, and whether the requirements quietly favor you or a competitor. Skip it and you show up to an RFP that someone else helped write.

This playbook covers what a contracting officer does with your response, exactly what to put in it, and how to shape the requirement without being obvious about it.

What a Sources Sought Notice Actually Is

A sources sought notice (sometimes posted as an RFI, though they are not identical) is market research. Before an agency can issue a solicitation, the contracting officer needs to answer two questions:

1. Are there enough capable vendors to compete this?
2. Are there enough capable small business vendors to set it aside?

Your response is evidence in that file. Under the Rule of Two, if the contracting officer finds two or more responsible small businesses likely to submit fair offers, the requirement generally gets set aside for small business. If capable responses come in from firms holding SDVOSB, WOSB, HUBZone, or 8(a) status, the set-aside can get even narrower.

That is the entire strategic point: your response can shrink your future competition before the RFP exists. If you are unsure how sources sought differs from the other pre-solicitation documents you see on SAM.gov, our breakdown of RFP vs RFQ vs RFI covers the distinctions.

What the Contracting Officer Does With Your Response

Nobody scores a sources sought response. There is no evaluation board and no award. But real decisions get made from it:

One more thing happens that vendors underestimate: the contracting officer and program office learn your name. When the RFP drops months later and your company appears in the offer list, you are a known quantity instead of a stranger.

Step 1: Decide Fast Whether It Is Worth Responding

A good sources sought response takes a few hours, not a few weeks. Even so, do not respond to everything. Run a quick version of the same discipline you would use on a full bid. Our post on go/no-go bid decision scoring works here too, just with lower thresholds since the investment is smaller.

Respond when:

• The work matches your core capabilities, not your aspirational ones
• You could plausibly bid the eventual solicitation as a prime or a well positioned sub
• Your size or socioeconomic status could tip a set-aside decision

Skip when the requirement is clearly wired for an incumbent with unique certifications you will never hold, or when the scope is so far from your experience that your response would weaken the government's case for a set-aside you want.

Timing matters. Sources sought notices often have short response windows, sometimes two weeks or less, so you need to see them the day they post. A daily scan of SAM.gov, whether you do it manually or let a service like RFPhound do it for you, is what makes this play possible at all.

Step 2: Answer Exactly What Was Asked

Read the notice twice. Most sources sought notices ask for specific items: company data, capability narrative, answers to numbered questions, page limits. Mirror their structure. If they ask five numbered questions, your response has five numbered answers in the same order.

A standard response includes:

1. Cover page or header block. Company name, address, UEI, CAGE code, point of contact, business size under the stated NAICS, and every socioeconomic certification you hold. Put certifications up front. This block alone can influence the set-aside decision.
2. Capability statement. Two to four paragraphs mapping your capabilities directly to the scope described in the notice. Use their language. If the notice says "enterprise service desk support," write "enterprise service desk support," not "IT helpdesk solutions."
3. Relevant experience. Two or three short project summaries: customer, scope, size, and outcome. These do not need to be federal. State, local, and commercial work counts as market research evidence. If your history is thin, the techniques in our guide to writing past performance with little experience apply here in miniature: lean on personnel experience, subcontract work, and closely analogous projects.
4. Direct answers to their questions. Numbered, concise, complete.
5. Comments and questions on the requirement. This is where shaping happens. More below.

Keep the whole thing to roughly three to five pages unless the notice says otherwise. Contracting officers read stacks of these. Short and specific beats long and generic every time.

Step 3: Shape the Requirement (Carefully)

Shaping is not lobbying and it is not gaming. It is giving the government honest feedback that happens to align with your strengths. Three techniques:

Suggest scope clarifications that favor your model

If you deliver work with a small senior team and you suspect the agency will demand large staffing levels out of habit, say so: "Based on similar engagements, we recommend the PWS define outcomes and service levels rather than fixed staffing counts, which allows offerors to propose efficient team structures." Framed as good acquisition practice, it also happens to remove a barrier for you.

Flag requirements that would exclude capable small businesses

If a draft requirement demands a certification, facility clearance, or contract vehicle that few small firms hold, point it out and propose an alternative, such as achieving the certification within a defined period after award. Contracting officers who want a defensible set-aside often welcome this.

Ask questions whose answers help you and hurt the incumbent

Questions like "Will incumbent staffing data be provided in the solicitation?" or "Will the government provide the current system architecture documentation?" level the playing field. If the answers show up in the RFP, every challenger benefits.

An illustrative example, not a real notice: imagine an agency posts a sources sought for facilities maintenance across a regional campus and the draft scope bundles janitorial, grounds, and elevator maintenance into one requirement. A small facilities firm that does everything except elevators might respond: "We recommend the government consider a separate line item or subcontracting approach for elevator maintenance, a specialized trade typically delivered by OEM certified providers, to maximize small business participation in the core requirement." That single sentence, if adopted, could change who can prime the job.

Step 4: Follow Up and Track to Solicitation

After you submit:

• Send a brief confirmation email to the listed contact and ask to be notified of updates. Polite, one paragraph, no sales pitch.
• Watch the notice on SAM.gov for amendments, draft solicitations, or industry day announcements. Attend the industry day if one is held.
• Log the expected solicitation timeframe in your pipeline and check monthly. Many sources sought notices turn into RFPs one to six months later, and some never do. That is normal.

Build this into a repeatable rhythm. If you work in a crowded category like IT and software or professional services, sources sought responses are one of the few moves that differentiate you before price and past performance ever get compared. The same logic applies geographically: firms chasing work in agency dense states like Virginia will see sources sought notices weekly and should treat them as a standing pipeline stage, not a novelty.

Quick Checklist Before You Hit Send

• Business size and all certifications stated on page one
• Response mirrors the notice's structure and answers every question
• Capability language matches the notice's terminology
• Two or three relevant experience summaries with outcomes
• At least one constructive comment or question that shapes scope
• Within page limits, submitted before the deadline, to the correct email
• Logged in your pipeline with a reminder to watch for the solicitation

Most of your competitors ignore sources sought notices entirely. That is exactly why responding to them works.