The notice most firms scroll past
Somewhere on a SAM.gov results page, between a presolicitation and an award notice, sits a Sources Sought notice with a five-page limit and a ten-business-day window. No money attached, no contract at the end of it, and a paragraph at the bottom saying this is not a request for proposals. Most firms skip it. Many of those same firms complain nine months later that the requirement was written around the incumbent, the NAICS code was wrong, and three separate jobs got bundled into one award nobody their size could carry. All three were decided during the market research phase, using the responses that came in.
Federal buyers are not hiding this. The contracting officer publishing a Sources Sought notice has a real problem: the FAR obliges them to know their market before they write the solicitation, and their picture of who can do the work is often two acquisition cycles out of date. When two capable small businesses answer with specifics, the acquisition strategy changes. When nobody answers, the file records that nobody answered, and the strategy that follows is the one the agency already had.
What a Sources Sought notice actually is
FAR Part 10 makes market research a requirement, not a courtesy. FAR 10.001 directs agencies to conduct market research appropriate to the circumstances before soliciting offers for any acquisition above the simplified acquisition threshold, which FAR 2.101 sets at $250,000. FAR 10.002(b)(1) spells out the question that research has to answer: whether sources capable of satisfying the agency's requirements exist, and what commercial practice looks like in that market. A Sources Sought notice is the public instrument for asking.
The Request for Information is the companion tool, governed by FAR 15.201(e). An RFI may be used when the government does not presently intend to award a contract but wants price, delivery, other market information, or capabilities information for planning purposes. The same paragraph carries the line firms misread most often: responses to these notices are not offers and cannot be accepted by the government to form a binding contract. There is no required format. When an agency issues something that looks like a solicitation purely for planning, it uses the provision at FAR 52.215-3.
Publicity is why these notices are findable at all. FAR 5.101 and FAR 5.201 require proposed contract actions expected to exceed $25,000 to be publicized on the governmentwide point of entry, and SAM.gov Contract Opportunities is that point of entry. Sources Sought and Special Notice are distinct notice types there, filterable and subscribable. FAR 5.203(a) then requires the presolicitation notice to publish at least 15 days before the solicitation issues, so the gap between "we are thinking about this" and "here is the RFP" is visible in advance.
| Notice type | What the agency is doing | What your response can still change | Typical window |
|---|---|---|---|
| Sources Sought | Testing whether capable sources exist, and in which size and socioeconomic categories | The set-aside decision, the NAICS code, whether the buy is split or consolidated | 5–15 business days |
| RFI (FAR 15.201(e)) | Collecting technical, price, delivery and capability information for planning | Technical approach assumptions, cost realism, contract type, CLIN structure | 10–20 business days |
| Draft RFP / draft PWS | Validating a requirement that is already written down | Specific clauses, evaluation factors, page limits, period of performance | 7–14 days |
| Industry day | Briefing the requirement and taking questions in the room | Teaming relationships, and the questions that get answered in writing afterward | Registration 1–3 weeks out |
| Presolicitation | Announcing an acquisition whose strategy is already set | Very little on strategy; mostly your own teaming and pricing posture | 15 days minimum before solicitation |
The Rule of Two, and why your response is an input to it
The highest-value thing a market research response does is feed the set-aside decision. FAR 19.502-2(b) states the test plainly: an acquisition above the simplified acquisition threshold shall be set aside for small business when the contracting officer has a reasonable expectation that offers will be obtained from at least two responsible small business concerns, and that award will be made at fair market prices. Below that threshold and above the $10,000 micro-purchase threshold, FAR 19.502-2(a) reserves the acquisition for small business automatically unless the contracting officer determines no reasonable expectation of two offers exists.
Read it with a bidder's eye. The trigger is two. Not a market study, not a consultant's report: two responsible small firms that look capable on paper. The reasonable expectation comes from the market research file, which is built from the responses that came in. A notice that draws six substantive small business replies produces a set-aside almost every time. One that draws two brochures and a large-business capability statement produces a full and open competition, and the file will say why.
Two responsible small businesses at fair market prices
FAR 19.502-2(b) is the whole test. The contracting officer needs a documented, reasonable expectation of two capable small offerors. Every response that demonstrates capability against the draft scope moves that count. Every response that does not demonstrate anything gets summarized as "no capability information provided" and counts for nothing.
The arithmetic tiers downward. A HUBZone, SDVOSB, WOSB or 8(a) set-aside requires the contracting officer to expect two capable firms inside that category, under FAR subparts 19.13, 19.14, 19.15 and 19.8. Where only one surfaces, sole-source authority may apply instead: FAR 19.805-1(a)(2) requires competitive 8(a) procedures once the anticipated award exceeds $4.5 million for services or $7 million for manufacturing, and FAR 19.1306 and 19.1406 follow the same pattern. A clean status statement under the listed NAICS puts your firm in whichever lane the agency picks.
The mandatory version of this logic is settled law in one place. In Kingdomware Technologies, Inc. v. United States, 579 U.S. 162 (2016), the Supreme Court held that the Department of Veterans Affairs must apply its Rule of Two before buying goods or services, including orders placed through the Federal Supply Schedule. VA's statute is stronger than the general FAR rule, but the mechanism is the same everywhere: the decision runs on documented evidence of capable small firms, and the evidence is what firms submitted.
What a market research response can still move
Editorial weighting from public acquisition regulation and practitioner reading — illustrative, not a measured statistic.
Everything else the response quietly decides
The NAICS code. One six-digit code sets the size standard for the whole competition. Under 13 CFR 121.201, NAICS 541512 (Computer Systems Design Services) carries a $34.0 million receipts standard, while 541715 (Research and Development in the Physical, Engineering, and Life Sciences) carries an employee-based standard of 1,000 employees. Those codes describe overlapping work and produce different fields of eligible bidders. Once the solicitation issues, a NAICS appeal to SBA's Office of Hearings and Appeals must be filed within 10 calendar days under 13 CFR 121.1103. A sentence submitted before that clock starts is a much cheaper fix than an appeal.
Consolidation and bundling. FAR 7.107 governs what happens when an agency merges requirements that were previously separate contracts. Consolidation above the thresholds in FAR 7.107-2 requires a written determination that it is necessary and justified, and substantial bundling triggers further analysis under FAR 7.107-4. Contracting officers would rather not write those determinations. A response saying "these three task areas were separately awarded through FY24, small firms perform each of them today, and splitting them into lots preserves competition" gives the acquisition team a reason not to bundle and a record to cite.
Qualification language. A draft PWS demanding five years of experience on one named legacy system has, in effect, named the incumbent. The fix a small firm can propose is a functional equivalent: five years integrating comparable systems of the same class, or demonstrated performance against the same interface standard. Contracting officers accept that substitution more often than firms expect, because unduly restrictive requirements are protest exposure they would rather not carry.
Whether the work is executable at all. Ask, in writing, what government-furnished data and environments will be provided, what the CUI designation is, whether an existing authorization to operate covers the environment, and what the data rights position will be on anything delivered. On software, DFARS 252.227-7014 and its noncommercial-technical-data sibling 252.227-7013 decide who can reuse what. Each of those is easier to raise now than in a Q&A window with a page limit and competitors reading your questions.
What an effective response contains
Length is not the variable. A four-page response mapped directly to the draft scope beats a fifteen-page corporate brochure every time, because the contracting officer is building a market research report and needs quotable evidence. Give them material they can paste.
- An administrative block on page one with legal name, UEI, CAGE, address, POC name, email and phone, and the notice number you are answering.
- An explicit size and status statement under the NAICS code the notice lists, in one sentence, with the socioeconomic categories you hold. This is the line that gets tallied.
- A task-by-task mapping table against the draft PWS, SOO or statement of need, with one row per numbered task.
- Relevant work described in specifics: scope, approximate size, period, whether performed as prime or subcontractor, and the technical result.
- A numbered answer to every question the notice asked, in the notice's own order and numbering.
- Recommendations on requirement structure: NAICS, set-aside, lot structure, period of performance, contract type, evaluation approach.
- Any risk you can see in the draft, stated in neutral language, with a proposed alternative rather than an objection.
- Vehicles you can be reached on, so the agency knows a fast ordering path exists if one is needed.
The mapping table does most of the work
The element that separates a serious response from a filed-and-forgotten one is a three-column table: the draft task on the left, what your firm does to satisfy it in the middle, the evidence on the right. One row per task, two to four sentences each, no marketing language. The contracting officer, the program technical lead and often an SBA procurement center representative under FAR 19.402 decide, per task area, whether capable small sources exist. Force them to infer the mapping and they will not. Build it, and your firm appears in their summary as capable across tasks 1 through 6, language that propagates into the acquisition plan.
The evidence column is where firms earn credibility or lose it. Name the technical particulars: data volumes, standards, the security boundary, the integration surfaces, the measured outcome. "Experienced in data engineering" is worth nothing. "Built an ingest and reconciliation pipeline handling roughly 40 million records per month across six source systems, with row-level lineage retained for audit" tells a technical evaluator what class of firm is writing.
Answer the questions they asked, in their order
Most notices end with a numbered list. Are the requirements clear as drafted? Is the period of performance realistic? What is your recommended NAICS? Would you bid as prime or subcontractor? What percentage would you self-perform? Do you hold a facility clearance? Those questions are the outline of the market research report the contracting officer must document under FAR 10.002(e), and answers get lifted almost verbatim. Answering seven of eight and skipping the awkward one leaves a hole in the record where your firm's name should be.
The self-performance question deserves care. FAR 52.219-14 sets limitations on subcontracting for set-aside work: for services, at least 50 percent of the amount paid must go to the concern's own employees or to similarly situated entity subcontractors. An answer implying you would sub out 80 percent tells the agency a set-aside will not function. Say what you would genuinely self-perform, and name the areas where you would bring on specialists.
What a weak response looks like
Contracting officers describe the same failure patterns across agencies. None of them are about writing quality.
- The unmodified capability statement. A two-page PDF built for a matchmaking event, attached with no reference to the draft scope. It reads as "we did not read this."
- No size declaration under the listed NAICS, which means the response cannot be counted toward the Rule of Two at all, no matter how capable the firm is.
- Capability asserted, never demonstrated. "We can support all task areas" with nothing behind it. The market research summary will say capability was claimed but not substantiated.
- Format and channel violations: past the page limit, wrong subject line, wrong file type, sent to the wrong mailbox, or submitted after the deadline. Automatic exclusion, no appeal.
- Everything marked proprietary, including the parts that are plainly not. A wholly restricted response is one the contracting officer cannot quote or summarize, which limits its usefulness in the file.
- Answering only the easy questions and leaving the self-performance, clearance or transition questions blank, which reads as a firm that has not thought about executing.
One more, subtler than the rest: the response that argues. State the risk, propose the alternative, keep the tone of a colleague who has done the work. The people reading it are the people you will work with if this goes well.
Markings, and the file the contracting officer has to write
Mark what is genuinely proprietary and nothing else. A response whose every page carries a restrictive legend cannot be excerpted into the market research documentation FAR 10.002(e) requires, so your firm's capability never makes it into the record. Keep the mapping table, the size declaration and the recommendations releasable, and restrict only technical detail that is genuinely your own.
Know what happens to the file after you submit. Market research results feed the acquisition plan, the small business coordination record on DD Form 2579 for DoD actions, and any set-aside determination. SBA procurement center representatives review acquisitions under FAR 19.402 and can recommend a set-aside the agency did not plan. Your response is the raw material that recommendation gets built from.
Market research to award — the working timeline
The spread is real and worth planning around. Some notices convert inside 90 days. Others sit for a year, or die when the requirement is funded differently. Treat the response as an option bought cheaply, not as a forecast.
Tracking them without losing a day a week
Finding these notices is a solved problem if you build the pipeline once. SAM.gov Contract Opportunities supports saved searches with email notification, filtered by notice type, NAICS, set-aside type, agency and place of performance. Set separate saved searches for Sources Sought and Special Notice under each NAICS you compete in, and keep the geographic filter off; market research is usually national even when performance is not.
Past a handful of searches, use the API. SAM.gov exposes a Contract Opportunities search endpoint taking a date range, NAICS list and notice type, returning structured JSON with the response deadline and the point of contact. An API key comes from a SAM.gov account. A scheduled job pulling that endpoint each morning, deduplicating against what has been seen and scoring the rest against your codes, replaces the hour a day manual browsing costs. Our engineers build this pipeline for clients who want the pursuit list assembled before they open a laptop.
Three other sources belong alongside it. Agency procurement forecasts, published by small business offices under the Small Business Act's forecasting requirement, name upcoming requirements before any notice posts. FPDS and USAspending give the incumbent, the value and the ultimate completion date on expiring contracts, which is how you predict a Sources Sought months before it appears. GSA eBuy carries RFIs restricted to schedule holders that never reach the public feed.
Then set a cadence and hold it: a weekly ninety-minute pass over the queue, three to five responses a month, and a sheet recording each notice, the recommendations made, and what the eventual solicitation looked like. That last column teaches. After a year you can see which agencies move on market research input and which publish notices as a formality.
What it costs, and what it returns
A strong response takes four to eight hours: two reading the draft scope and the incumbent contract data, two to four building the mapping table and the evidence, one on the questions and recommendations. Call it a day of senior time, unbilled.
You buy four things with it. A vote in the set-aside decision, which is the difference between competing against four small firms and competing against a large integrator with a hundred-person capture team. Standing with the contracting officer and the program technical lead before the blackout, when conversation is still welcome. Months of lead time on a requirement competitors first see when the RFP drops. And an early read on whether the work is worth pursuing at all.
Bottom line
Sources Sought and RFI responses are the lowest-cost, highest-return documents in federal business development. They shape the set-aside under FAR 19.502-2, the NAICS code and size standard, whether requirements get consolidated under FAR 7.107, and how restrictive the qualification language ends up. Write them the way a contracting officer needs to read them: administrative facts up front, a size declaration that can be counted, a task-by-task map with real technical evidence, numbered answers to every question asked. Skip the brochure. Send four pages that are hard to ignore.
Frequently asked questions
They overlap heavily. A Sources Sought notice identifies capable sources and their size and socioeconomic status, which feeds the set-aside decision. An RFI under FAR 15.201(e) casts wider, asking for price, delivery, technical approach and commercial practice information. Some agencies title the same document either way. Read the questions at the bottom to see which it really is.
No. FAR 15.201(e) states that responses are not offers and cannot be accepted by the government to form a binding contract, and FAR 52.215-3 says the same when a planning-purposes solicitation issues. You are not committing to bid, to price, or to an approach, and you are not reimbursed for the effort.
Under FAR 19.502-2(b), an acquisition above the $250,000 simplified acquisition threshold must be set aside for small business when the contracting officer reasonably expects offers from at least two responsible small business concerns and award at fair market prices. Below that threshold and above the $10,000 micro-purchase threshold, FAR 19.502-2(a) reserves it for small business unless the contracting officer determines otherwise. Market research responses are the primary evidence.
Before the solicitation issues, yes, by recommending a different code and explaining why it better describes the principal purpose of the work. After issuance, the route is a NAICS appeal to SBA's Office of Hearings and Appeals, which under 13 CFR 121.1103 must be filed within 10 calendar days. The market research phase is the cheaper and less adversarial place to raise it.
Yes, and say so. Notices routinely ask whether you would bid as prime or sub. A capable subcontractor response still tells the agency how deep the small business market runs, and primes use these notices to build teams. Be direct about which task areas you would carry.