US Federal · Procurement Strategy
A Sources Sought notice is the federal government's formal market research step under FAR Part 10 — the regulatory anchor that requires agencies to conduct market research before issuing a solicitation above the simplified acquisition threshold. The notice itself is short, often posted on SAM.gov for as little as 14 business days, and easy to scroll past. The agency is asking industry one question: do enough capable suppliers exist for this requirement to be set aside for small business, or should it be full and open?
The way contractors answer that question — collectively, through Sources Sought responses — determines whether the eventual RFP is set aside for 8(a) firms, for HUBZone, for SDVOSB, for Total Small Business, or run as full-and-open competition against large primes. By law, the Contracting Officer must set aside the procurement if there is reasonable expectation that at least two responsible small business sources will submit competitive offers. No response from small businesses = no evidence of capability = no set-aside.
This guide covers the regulatory mechanics under FAR 10, the section-by-section response template, weak-versus-strong response excerpts, and the seven fatal mistakes that contractors repeatedly make and that contracting officers consistently flag as the reason a procurement could not be set aside.
Per FAR 10.001(a), agencies must conduct market research appropriate to the circumstances before:
The Sources Sought Notice (sometimes called Sources Sought Announcement, or SSA) is one of the most common market-research instruments. FAR 10.002 sets out the procedures — Contracting Officers may use industry days, RFIs, capability statements, prior procurement files, and direct industry outreach. A Sources Sought response is your formal contribution to the agency's market research record. It becomes part of the procurement file and informs decisions made before any RFP is written.
Sources Sought differs from a Request for Information (RFI) in one specific way:
Posting minimums: 14 business days for Sources Sought, 21 business days for an RFI (some agencies post longer; the floors are minimums). Response windows are typically 10–30 calendar days but vary widely.
The reason Sources Sought is the highest-leverage moment in federal capture has nothing to do with the response itself. It has to do with what your response causes the agency to do next.
Three downstream decisions are made on the basis of Sources Sought responses:
None of this is true at RFP release. By the time the RFP drops, the requirement is locked, the NAICS is selected, the vehicle is chosen, and the set-aside (or lack thereof) is determined. The Sources Sought window is where those decisions are still moveable — and the response is the lever.
Most effective Sources Sought responses run 5–10 pages plus a capability-statement attachment. Quality matters more than length — focus on directly answering what the agency asked for. The proven structure has five sections:
Legal business name, doing-business-as, Unique Entity Identifier (UEI), Commercial and Government Entity (CAGE) code, SAM.gov registration status (active / expiration date), business size against the notice's stated NAICS, and applicable set-aside designations (8(a), HUBZone, WOSB, EDWOSB, SDVOSB, VOSB).
2 to 4 directly analogous federal contracts. Each reference contains: agency name, contract number (PIID), period of performance, total contract value, scope of work in 2–3 sentences, and your role (prime or sub). Where possible, include the CPARS rating you received and the technical representative's name. Make the relevance to the Sources Sought requirement explicit — "this prior contract used the same data-migration approach the notice describes."
Specific technical responses to the agency's stated requirement. Not "we provide IT services" — "we have deployed FedRAMP Moderate boundary architectures on three federal contracts using the specific configuration the notice describes." Cite the notice's own language wherever possible. If the notice mentions "transition plan," describe your transition plan. If it mentions "data migration," name the systems you have migrated.
If you plan to prime: state that explicitly and identify any subcontractors by name with their roles. If you plan to sub: name the prime relationships you have. This tells the agency the market can support competition and influences whether they set aside, and at what tier. Subcontracting arrangements without names ("we will partner with established firms") are read as having no real teaming yet.
Explicit confirmation that your team can be available for a contract awarded on the agency's anticipated timeline. Then a single named point of contact: name, title, direct phone, work email. Agencies route follow-up questions back to your firm based on this contact — anything generic ("info@") goes to the bottom of the contracting officer's list.
The difference between a Sources Sought response that gets cited in the procurement record and one that gets archived without effect is rarely length. It is specificity. The same response section, written weak and strong:
| Section | Weak (won't move requirements) | Strong (moves requirements) |
|---|---|---|
| Past Performance | "We have supported numerous federal agencies including DOD, DHS, and HHS over the past decade. Our customers consistently rate us highly on contractor performance evaluations and we maintain strong relationships across the federal landscape." | "Prior performance — (1) NIH NCATS, contract HHS-2023-N-0892, $4.2M, FY2023–FY2025, cloud migration for 11 research-data systems within FedRAMP Moderate boundary. CPARS Very Good across five factors FY2024. (2) DoD DLA, BPA order N00604-22-F-3210, $1.8M, FY2022–FY2023, Section 508 remediation across 47 user-facing systems. CPARS Exceptional on Quality." |
| Technical Capability | "Our team has extensive experience with cloud migration projects, modern DevOps practices, and federal compliance frameworks. We are committed to delivering on schedule and within budget." | "For the migration approach described in §3 of the notice, we have executed three comparable migrations using AWS GovCloud landing zones with FedRAMP Moderate ATO inheritance. Average migration duration for similar 8–12 system workloads was 14 months. Our reference architecture aligns with the NIST SP 800-53 Rev. 5 control set referenced in the notice's draft SOW." |
| Teaming | "We partner with leading industry firms to deliver comprehensive solutions to federal agencies. Our network of subject-matter experts allows us to scale to any requirement size." | "For this requirement we plan to prime, with two named subcontractors: Acme Cybersecurity (FedRAMP Moderate assessor, holds active 3PAO certification) for the security-assessment work share (~25% of effort), and Beta Data Services (prior NIH NCATS subcontract; cleared engineers for data-migration work share ~15%). 100% of management and program-control work is performed by our team." |
| Availability | "We are available to support this requirement and look forward to the opportunity to discuss our capabilities further." | "Confirmed availability for a contract with anticipated award date Q4 FY2026 (per notice). Three named key personnel (Program Manager, Technical Lead, Security Architect) are uncommitted in that window. Two are 8140-qualified and one holds active Secret clearance, in alignment with the notice's draft personnel requirements." |
Every strong example does the same three things: (a) references the specific notice's language, (b) names specific past contracts with PIIDs and dollar values, (c) includes specific certifications, clearances, or capability evidence rather than capability claims. The weak version makes claims about capability; the strong version provides evidence and lets the Contracting Officer draw the conclusion.
Contracting officers read hundreds of Sources Sought responses across a year. They consistently report the same seven mistakes that cause responses to be discounted in the market research record:
| # | Mistake | What it actually does | Remediation |
|---|---|---|---|
| 1 | Submitting a generic capability statement unchanged | Signals you did not read the notice; response counted as non-responsive | Customize 60–80% of content to the notice; the agency's stated keywords must appear |
| 2 | Failing to reference the agency's stated NAICS code in Section 1 | Implicit signal you may not qualify; uncertainty resolves against you | Explicit statement: "Our firm is a small business under NAICS 541512 with [size-standard] of [revenue range]" |
| 3 | Past performance without contract numbers, dollar values, periods | Agency cannot verify the reference; treats it as anecdotal | Each reference must include PIID, value, period, agency, scope (2–3 sentences) |
| 4 | Vague teaming statements ("we partner with leading firms") | Agency reads as having no real teaming yet; cannot count toward the Rule of Two | Name specific teaming partners with their work share and federal credentials |
| 5 | Treating the response as a sales pitch | Marketing language signals lack of seriousness; CO discounts the entire response | Factual capability assertions backed by evidence; let conclusions emerge from facts |
| 6 | Missing the response deadline entirely | Response not in the market-research record; CO has no basis to set aside on your behalf | Calendar alert at notice issuance; full draft within 5 days; submit within first half of window |
| 7 | Submitting late in the response window | Late submissions reviewed less carefully; sometimes not entered into record at all | Submit in the first half of the response window; the CO often drafts the market research memo by mid-window |
The influence curve is steep. Once the market research memo is drafted (typically 30–60 days after the Sources Sought close), the set-aside decision and most requirement language are locked. Subsequent draft-RFP feedback can shift specific clauses but cannot reopen the set-aside designation or the underlying NAICS selection. Industry days held after the draft RFP are useful for clarification but not for reshaping the procurement strategy.
If a Sources Sought response is what unlocks a small-business set-aside that would not otherwise have existed, the SMB win economics for the resulting contract are dramatically better — the competitor pool is narrower, large-prime competition is excluded, and price competition runs only against other small businesses. The same RFP, set aside vs full-and-open, has a 3–5× win-probability differential for SMBs. The Sources Sought response is the lowest-cost, highest-leverage moment in the entire procurement cycle.
The 14-day Sources Sought response window is where this guide's framework operationalizes — but discovering the notice on day 1 of that 14-day window is itself the hardest part. SAM.gov's native alert system surfaces notices with significant lag and no capability-matching. By the time a manually-tracked alert arrives, the response window is often half-spent.
BidClarity's Sources Sought Agent is purpose-built for this gap. The agent operates inside the Agent Layer alongside the Funding Agent and Knowledge Base retrieval — surfacing pre-solicitation signals 90–180 days before the formal RFP drops, and Sources Sought notices the moment they post. The agent scores each notice against your declared capability profile, flags small-business set-aside potential, identifies the agency's likely NAICS preference, and surfaces your prior teaming history with relevant primes from your Knowledge Base. The output is not "here's a notice" — it is "here's a notice, here's your fit score, here's the past-performance reference you should cite, and here's the contracting officer who has favored your competitor on three prior recompetes."
Combined with BidClarity's Intelligence layer match scoring (which assigns HIGH / WATCH / SKIP bands to each opportunity) and Tier 3 Tech Intel extraction (which parses solicitation language for specific technology and compliance requirements), the Sources Sought response moves from a 14-day scramble to a 60-day capture cycle that begins the moment the notice posts. No other SMB-priced platform runs proactive pre-RFP intelligence across federal and SLED procurement at this depth.
Manually scanning SAM.gov for Sources Sought notices in your NAICS produces 30–80 notices per week for an active SMB capture program — and the response windows are short. BidClarity surfaces Sources Sought notices alongside open solicitations, tagged with the agency's stated NAICS, anticipated set-aside designation, and response deadline. The compliance calendar tracks each notice's window from issuance through close, so you respond inside the first half of the window every time.
AI-powered match scoring weights Sources Sought notices the same way it weights open RFPs — by capability fit, NAICS match, and past-performance relevance — so the highest-leverage notices surface before the lower-fit ones.
Sources Sought tracking and procurement-cycle calendar are included in the Intelligence plan ($349/mo or $279/mo billed annually).
Start My 14-Day Trial →For the broader pre-RFP positioning playbook that runs alongside Sources Sought responses, see how to win a government contract before the RFP is posted. The Sources Sought response is the formal entry into the market research record; the pre-RFP positioning calendar is the relationship and capability work that makes the response credible. For the proposal mechanics that follow once the RFP drops, see how to read a federal RFP. The CPARS portfolio referenced in Section 2 of your response — and the past-performance evidence that gives it weight — is built per the CPARS ratings guide.
A Sources Sought response takes 4–8 hours to draft once the template is built. The downstream effect — set-aside designation, requirement shaping, NAICS selection — can multiply your win probability on the resulting contract by 3–5×. Of every hour spent in federal capture, the Sources Sought response hour is the highest-return one. Treat it accordingly.