Every day, federal contracting officers post notices on SAM.gov that aren't solicitations, aren't RFPs, and don't ask for a price. They're called Sources Sought notices — and most small contractors scroll past them because they don't see a bid to submit.
That's a mistake. A Sources Sought notice is the contracting officer telling the market: we're planning to buy something, and we want to know who can do it. Responding to a Sources Sought notice is the earliest point in the procurement process where you can put your name in front of the person who will eventually award the contract.
The contractors who respond to Sources Sought notices aren't bidding on a contract. They're doing something more valuable: getting on the CO's radar before the competition even opens.
What a Sources Sought notice actually is
A Sources Sought is a market research tool. Before an agency can decide how to structure a procurement — whether to set it aside for small businesses, which NAICS code to use, what the scope should look like — the contracting officer needs to understand what's available in the market.
The notice typically describes the planned work in general terms and asks interested businesses to respond with information about their qualifications: what they've done, what licenses they hold, what size they are, and whether they'd be interested in competing when the formal solicitation comes out.
This information directly shapes the procurement:
- If fewer than two qualified small businesses respond, the agency may decide it can't set the contract aside for small businesses
- If multiple HUBZone firms respond, the agency may issue a HUBZone set-aside
- If responses reveal specific technical expertise or equipment requirements, those may be written into the SOW
Sources Sought vs. RFI vs. Pre-solicitation: the differences
SAM.gov uses several similar notice types that serve related purposes. It's worth knowing the difference:
| Notice Type | Purpose | Should You Respond? |
|---|---|---|
| Sources Sought | Market research — finding qualified vendors before a formal procurement | Yes, always if you're qualified |
| RFI (Request for Information) | Gathering technical or market information; similar to Sources Sought | Yes — same logic applies |
| Pre-solicitation Notice | Advance notice that a solicitation is coming; may invite early feedback | Yes — watch for the follow-on RFP |
| Solicitation / RFP / IFB | Formal competitive bidding document requiring a priced proposal | Yes — this is the actual bid |
Sources Sought and RFI responses are not evaluated competitively. There's no winner. They're informational — which is exactly why most contractors skip them. But that low-stakes nature is also why responding is so valuable: you're making an impression with no risk of losing.
How to find Sources Sought notices on SAM.gov
On SAM.gov, go to "Contract Opportunities" and use the search filters:
- Notice Type: Select "Sources Sought" and "Request for Information"
- NAICS Code: Enter your primary code (e.g., 238210 for electrical, 238220 for HVAC/plumbing)
- Place of Performance: Filter by state or region to focus on local opportunities
- Posted Date: Set a recent window (last 30 days) to see active notices
Save this search. SAM.gov allows you to create saved searches that send email alerts when new notices matching your criteria are posted. Set this up and you'll be notified the same day a relevant Sources Sought goes live — giving you maximum response time.
Why responding is worth your time
A Sources Sought response takes 30–60 minutes to write. In exchange, you get:
- Name recognition with the contracting officer — They may receive 3 responses or 30. Either way, yours is one of the files they're looking at when they structure the procurement.
- Early intelligence on the work — The notice description tells you what the agency is planning to buy. You can start thinking about pricing, subcontracting, and approach before the solicitation is released.
- Influence on how the procurement is structured — Your response contributes to the CO's market research. If you're the only HUBZone-certified electrical contractor who responds, you've made the case for a HUBZone set-aside.
- A chance to ask questions — Sources Sought notices often invite questions. Asking a smart, specific question about the scope demonstrates competence and gives the CO a reason to remember you.
How to write a one-page capability response
The most effective Sources Sought responses are short, specific, and structured. One page is enough. Contracting officers are reading dozens of these — don't make them work to find your information.
Here's the structure that works:
Section 1: Company information (3–4 lines)
Your legal business name, SAM.gov UEI, CAGE code, primary NAICS code, business size (small business / SDVOSB / HUBZone / WOSB as applicable), bonding capacity, and point of contact with email and phone.
Section 2: Relevant experience (3–5 bullet points)
List 3–5 past projects that are directly relevant to the scope described in the Sources Sought. For each project, include: a brief scope description (2–3 sentences), dollar value, agency or client name, completion date, and point of contact if the job was federally funded. Specificity matters — "we've done similar work" is useless; "$175,000 electrical panel replacement at [installation] in 2024" is not.
Section 3: Technical capability (1–2 short paragraphs)
Briefly describe your relevant equipment, certifications, licenses, and workforce capacity for this type of work. If the notice mentions specific technical requirements (a particular system, a specific NEC version, security clearance requirements), address them directly. Don't write a general company bio.
Section 4: Interest statement (2–3 sentences)
State clearly that you are interested in competing for this work when the formal solicitation is released. Include your geographic service area and note any relevant certifications (small business set-aside eligibility, HUBZone, SDVOSB, etc.) that are relevant to how the procurement might be structured.
After you respond: following up
Most Sources Sought notices include the contracting officer's contact information. After you submit your response, you can follow up with a brief email — not to push for a contract, but to confirm your response was received and to express that you're available to discuss the scope if helpful.
Keep this email to 3–4 sentences. The goal is to be remembered as organized, responsive, and easy to work with — not to sell yourself. Contracting officers have heard every pitch. A clean, professional follow-up stands out more than an aggressive one.
Tracking your Sources Sought pipeline
Treating Sources Sought notices as a pipeline — not as individual one-off responses — is how you build consistent federal contract flow over time. For any Sources Sought you respond to, track:
- Date posted and response due date
- Agency and contracting officer name
- Estimated award date (if listed) or expected solicitation timeline
- Whether a formal solicitation was eventually posted
- Whether you bid, and whether you won or lost
Over 6–12 months, this data tells you which agencies are consistently posting work in your trade, what the typical lead time is between Sources Sought and solicitation, and where your responses are converting into bid opportunities.
Ready to turn a Sources Sought into a winning bid?
Pick a live federal job near you. Watch the full bid get drafted on the spot.
Build a Custom Bid Draft in 5 Minutes →The bottom line
Sources Sought notices are the least competitive, highest-leverage touchpoint in the federal procurement process. Responding costs you an hour. Ignoring them costs you the relationship that leads to the award.
The contractors consistently winning set-aside work aren't just good at bidding. They're showing up earlier than everyone else — at the Sources Sought stage, before the competition opens, when the contracting officer is still deciding how to structure the deal.
Most contractors wait for the RFP. Get there first.