How to respond to a Sources Sought notice (and why most small businesses do it wrong)

A Sources Sought (SS) is the contracting officer's market research before they issue a real solicitation. Often the most consequential single document in the federal-contracting calendar for a small business. Most SS responses are 1-page brochures. The ones that actually shape the eventual solicitation look very different.

What a Sources Sought is for

The contracting officer is trying to answer three questions:

1. Is there a competitive small business pool? If yes, they can set it aside. If no, they have to go full-and-open.
2. What's the realistic price band? Helps them set the budget and the contract type (FFP vs T&M).
3. What scope is realistic? Helps them write the SOW. If 8 vendors say "you'll need to drop requirement X," X usually disappears from the solicitation.

Your SS response should answer all three. Most don't.

The structure that works

Section 1: Company identification (10% of doc)

• UEI, CAGE, NAICS, primary set-aside category
• 2-sentence company description
• POC for the response

Section 2: Direct affirmation of capability (30%)

• "Apache-3 has performed work substantially similar to the proposed scope. Specifically..."
• Cite past performance with $ value, period, agency or commercial customer
• Cite NAICS history (years registered under the cited NAICS)
• Cite past delivery in the proposed geography

Section 3: Recommendations to the agency (40% — THIS IS THE KEY SECTION)

This is where most small business responses fail. The CO is asking for your expert opinion on what would help them get a better acquisition outcome. Tell them.

Examples:

• "Recommend splitting this into two CLINs: the AI literacy work and the documentation cleanup work have very different talent profiles."
• "The proposed 6-month POP is tight for a 1200-person training rollout. Recommend 9 months with two-month surge."
• "Per FAR 19.5, this should qualify as a small business set-aside given the NAICS 611420 size standard."

Be specific. Be useful. Be the small business they remember when they write the SOW.

Section 4: Set-aside qualification + interest (10%)

• "Apache-3 is a SDVOSB and VOSB under VetCert. We are interested in performing as prime under [proposed set-aside]."
• "Apache-3 will provide more than the FAR 52.219-14 minimum percentage with our own employees."

Section 5: Pricing-band signal (10%)

• "Based on past performance and current market rates, we estimate the price band at $X-$Y for the proposed scope."
• One sentence. Don't quote. They explicitly cannot use SS for price discovery — but a range helps them budget.

Common mistakes

1. Capability brochure with no recommendations. Says "we can do this," does not help the CO write the SOW.
2. Over-claiming. "We are the leading provider..." Skip. CO sees through it.
3. No mention of set-aside category. CO has to guess.
4. Submitting after the deadline. They will not read it.
5. No follow-up. Email the CO 1 week after submitting a thank-you note that adds one piece of value (a recent published article, a similar engagement summary). Stay in their inbox.

What Apache-3 does

We've built our auto-apply pipeline (private platform) to handle SS responses at scale. Every response includes Section 3 recommendations specific to the notice. It works because we treat the SS as a 4-page consultative deliverable, not a 1-page capability statement.

If you want our help responding to a specific SS, see Sources Sought response support.