They arrived in the same shape every week. Company name in the subject line. A first paragraph about the year the firm was founded. A deck attached, large enough to bounce off the mail server. Nothing anyone could act on that morning.
The deletion was never rudeness. The government said so in its own writing. The 2012 OFPP Myth-Busting 2 memo, written for vendors, says contracting officers and program managers “are often inundated with general marketing material that doesn’t reach the right people at the right time.”
You already have the list. Our advisors covered how to build it out of public award data. This is what you send those offices.
Four people, and only one of them opens the mail
The contracting officer holds the warrant. Nobody else obligates the government, nobody else signs. Before a requirement reaches that desk, they’re the least useful person to write to.
The contract specialist works the file under that warrant. GS-1102 series, no separate FAR definition. They draft the synopsis, build the market research record, and usually open the mail addressed to the contracting officer.
The agency small business specialist sits in a statutory office. 15 U.S.C. 644(k) puts an Office of Small and Disadvantaged Business Utilization in every agency with procurement authority, and FAR 19.201(c) carries it into the regulation. The clock is in FAR 19.201(d)(1), and it points the opposite way from the one everybody assumes: “The contracting activity shall coordinate with the small business specialist … no later than 30 days before the issuance of a solicitation.” So the specialist sees the requirement before the public does.
The program official owns the need and the money. They can tell you whether a problem is real. They can’t change the acquisition strategy alone.
Write the specialist first, though not for the reason usually given. The FAR assigns industry outreach to them nowhere. The basis is agency practice: Interior tells vendors in writing to introduce themselves to its specialists by email, and calls them “your direct contact for information regarding present and future solicitations.”
What they are actually measured on
The agency gets graded in public, on dollars. 15 U.S.C. 644(g)(1)(A) sets the floors: 23 percent of prime dollars to small business, 5 percent each to service-disabled veteran-owned, small disadvantaged and women-owned firms, 3 percent to HUBZone. SBA’s FY2025 scorecard, released June 25, 2026, put small business at nearly 28 percent of prime dollars, about $179 billion, and graded the government A.
Two of those floors get repeated wrong. SDVOSB is 5 percent, not 3, since section 863 of the FY2024 National Defense Authorization Act. Small disadvantaged is 5 percent, not 15, since Executive Order 14091 was revoked January 20, 2025.
When the seat is empty
What our advisors are seeing: small business offices were cut hard through 2025, and in some departments the job now sits with one person. Your fallbacks are the contact point every synopsis has to name under FAR 5.207, and the SBA procurement center representative under FAR 19.402, who can recommend a set-aside and appeal a refusal.
Why your message dies in the queue
What usually gets blamed is not a constraint. The Procurement Integrity Act at 41 U.S.C. 2102 prohibits knowingly disclosing or obtaining contractor bid or proposal information and source selection information before award, both defined at FAR 3.104-1. It’s a rule about two kinds of paper, not a gag order on conversation.
The first real constraint is that fairness is personal legal exposure. 5 CFR 2635.101(b)(8) requires federal employees to act impartially and give no preferential treatment, and (b)(14) to avoid even the appearance. FAR 1.102-2(c)(3) sets the standard: prospective contractors “shall be treated fairly and impartially but need not be treated the same.” The 2011 Myth-Busting memo says officials “can generally meet one-on-one with potential offerors as long as no vendor receives preferential treatment.” It puts the conflict-of-interest line at drafting specifications under contract; marketing efforts “in themselves, do not raise OCI concerns.”
The second catches people who mean well. 5 CFR 2635.204(a) caps unsolicited gifts at $20 per source per occasion and $50 a year from one person. Coffee, lunch, a branded jacket. Offering it asks a stranger to take on a compliance problem for your benefit.
The third is that your pitch has nothing to attach to. Calling it an unsolicited proposal makes it worse: FAR 15.603(c) disqualifies “an advance proposal for a known agency requirement that can be acquired by competitive methods,” so a pitch aimed at a known recompete fails on its face and still has to be logged and disposed of.
The window that decides everything else
FAR 15.201(a) is the sentence to know: exchanges among all interested parties, “from the earliest identification of a requirement through receipt of proposals, are encouraged.” FAR 15.201(c) lists nine techniques, and item four is one-on-one meetings with potential offerors.
Check the number before you quote it at anyone. Most large buying offices run Part 15 under a class deviation from the Revolutionary FAR Overhaul, where early exchanges sit at 15.101 and the nine-technique list is gone from the regulation, though the practice is not. Parts 15 and 19 were not in the first four proposed rules published June 23, 2026, so none of it is settled.
Your opening sits inside a sequence. The contracting activity brings the requirement to the specialist no later than 30 days before the solicitation issues. A synopsis publishes in SAM.gov Contract Opportunities for actions over $25,000, under FAR 5.101(a). And 15 U.S.C. 637(a)(12)(C) makes agencies above $50,000,000 in reported contract actions publish a forecast naming the fiscal-year quarter each procurement request is expected. All of it before the notice you were waiting for.
Once the solicitation posts you don’t go silent. You get routed. FAR 15.201(f) makes the contracting officer “the focal point of any exchange with potential offerors,” and anything given to one offeror has to reach the public “no later than the next general release of information.”
Nor is there a FAR deadline for questions on a request for proposals. FAR 52.214-6 comes closest, and it governs sealed bidding under FAR Part 14: a bidder wanting an explanation “must request it in writing soon enough to allow a reply to reach all prospective bidders before the submission of their bids.” A sufficiency standard, not a date. FAR 52.215-1, used in competitive negotiated acquisitions, says nothing about questions at all. In an RFP the deadline is a Section L term. Ask anyway, in writing, early; Myth-Busting 2 notes contracting officers “generally prefer questions via e-mail.”
The anatomy of an email that gets answered
The subject line
Two that get triaged out:
- “Introduction: [Company Name], Certified SDVOSB”
- “Request for Meeting to Discuss Our Services”
Two that get opened:
- “Notice ID [ID], NAICS 561730, question on size standard”
- “FY27 Q2 forecast line [item], grounds maintenance, one question”
The subject names the office’s artifact, not your company. It’s often the only thing read, and someone scanning for their own workload stops on a notice ID and skips a company name.
The first sentence
It has to establish relevance to their requirement. Not your founding date, not your certification, not your service lines. Myth-Busting 2 makes the point about meetings, and it travels: time gets spent “sharing commonly available information, which is not helpful to either party.”
Relevance means naming the artifact the way the office names it. Under FAR 5.207 a synopsis carries a proposed solicitation number, a contact point or contracting officer, a closing response date, and a set-aside status. The notice ID at the top of the page is a SAM.gov system field, not a FAR element, and it’s the one a specialist searches on. Award records add the recipient UEI and a period of performance current end date; pull those from SAM.gov contract award data, since FPDS public functionality moved there and ezSearch was decommissioned February 24, 2026. Viewing results needs a free account.
The ask that costs one line to answer
“Can we schedule 30 minutes to introduce our capabilities” asks a stranger to open a calendar, invent an agenda, and justify the time.
These are answerable. Is 561730 still the intended code here, or is the office looking at 561210. Is a sources sought notice planned before the solicitation, and roughly which quarter. May I send a one-page capability statement for the market research file.
Each one maps to something the office already knows or has to decide. A yes, a no, or a forwarded link closes it.
The attachment and the signature block
One PDF, named so it survives being dragged into a folder. No FAR provision requires a one-page capability statement, a PDF, a file name, or a size limit; that is practice, not law. Follow the practice anyway. What goes on the page is a separate discipline.
The signature block does more work than the body. Legal name exactly as registered in SAM. UEI and CAGE. NAICS codes with your size status under each. Certifications named with the certifying body, SBA 8(a), SBA HUBZone, SBA VetCert SDVOSB. SBA’s baseline is a Unique Entity Identifier, an active SAM registration, and matching NAICS codes. Never a DUNS number.
Those fields get retyped into the market research memo and into SBA Small Business Search, formerly DSBS, which took over from the Dynamic Small Business Search in July 2025, where the capability narrative, keywords and past performance don’t flow from SAM. You enter them yourself.
“I never deleted an email because the company was small. I deleted them because there was nothing in the message I could put into a file. Give me a legal name, a code, a size status and one comparable job, and I could type it into the market research memo that afternoon. The rest was reading I did not get paid to do.”
The rewrite that did the work
The version our advisors received constantly, sent to a contracting officer named on a solicitation closing in nine days.
Subject: Introduction: [Company], a certified SDVOSB
Dear Mr. [Name],
I hope this email finds you well. [Company] was founded in 2011 by a disabled veteran and provides IT, staffing, logistics and facilities support nationwide.
We have worked with your agency before and would welcome the chance to introduce our capabilities. Could we schedule 30 minutes at your convenience? Our presentation is attached, and I can add you to our monthly newsletter. Happy to buy you a coffee sometime.
Attachment: [Company]_Capabilities_2026_FINAL_v3.pptx
Same firm, same week, writing to the small business specialist about a requirement that does not exist yet.
Subject: [PIID] follow-on, NAICS 561730 question before the synopsis
Ms. [Name],
[Office] holds grounds maintenance at [installation] under PIID [number]. The period of performance current end date in SAM.gov is [date], and [Agency]’s forecast shows a follow-on in FY[YY] Q[n].
We self-perform the same scope as prime at two other federal campuses in [state]: [contract number], [agency], and [contract number], [agency].
One question. Is 561730 still the intended code for the follow-on, or is the office looking at 561210, facilities support services? That decides whether we bid as prime or find a partner, and I’d rather ask before Section L is written.
A one-page capability statement is attached for the market research file.
[Name], President [Legal name as registered in SAM] UEI [xxx] | CAGE [xxx] Small under NAICS 561730, 561210, 561720 SBA VetCert SDVOSB | SAM registration active
Attachment: [Company]_CapabilityStatement_561730_202606.pdf
The recipient change did the most work. The first message forced a contracting officer on a live solicitation to treat it as an inquiry under FAR 15.201(f), so any substantive answer had to reach every other offeror. The second landed in the market research window FAR 15.201(a) encourages.
The rest follows. The subject names a contract number instead of the sender. The certification moved to the signature, where a qualifier belongs. And the deck became one named PDF that drops into the contract file described at FAR 4.803(a), carrying the line a specialist retypes into the market research memo.
After you press send
No federal source prescribes a follow-up cadence, so treat this as our recommendation. One follow-up, two weeks out, carrying something the first message did not. What you’re offering is market research input; a repeated request offers none.
The strongest second touch is a response to a sources sought notice from that same office, a channel they opened rather than one you created.
Nothing obligates anyone to answer you. Myth-Busting 4 asks each CFO Act agency to name a public industry liaison who will “promote timely responses to general vendor requests where appropriate.” That is aspiration, not duty. Silence means you were triaged. Stop at two.
When a meeting does come, plan for a short slot. No rule sets the length, but agencies run these as prearranged one-on-one appointments, and in our advisors’ experience the block runs closer to fifteen minutes than an hour, with the capability statement uploaded before it starts.
Bring the person who does the work. Myth-Busting 2: “it’s far more valuable for you to bring subject matter experts to the meeting rather than focusing on the sales pitch.” Then ask the question that gets the most useful answer: which part of the current requirement gives this office the most trouble.
Sources sought lands in a real file
A sources sought notice is the survey a buying office runs before it writes a solicitation. The FAR calls that family requests for information. Under FAR 15.201(e) they’re used when the government “does not presently intend to award a contract” but wants market information for planning, responses are not offers, and “[t]here is no required format.”
You’ll read that a tailored response forces a contracting officer to consider you. It doesn’t, and the accurate version is stronger. FAR 10.002(e) makes the agency document its market research, and FAR 4.803(a) puts the set-aside decision in the contract file “including the type and extent of market research conducted.” Your response joins a reviewable record, and GAO weighs it when a set-aside is protested.
The set-aside is a judgment, not a headcount. Between the $15,000 micro-purchase threshold and the $350,000 simplified acquisition threshold, FAR 19.502-2(a) sets the work aside unless the contracting officer finds no reasonable expectation of two or more competitive small business offers. Above that, FAR 19.502-2(b) turns on a reasonable expectation of two responsible small firms at fair market prices. Both figures moved on October 1, 2025. Two responses compel nothing.
A brochure answers none of that. A responsive reply takes the numbered questions in order, using the same numbers, and gives UEI and CAGE, size status under the stated NAICS, two or three comparable efforts with contract number and agency, and any concern with the draft scope. Stay on the list: the rewritten Part 10 text at 10.001(d) tells agencies not to ask for more than the minimum information necessary, which is why the list is short.
The mistakes that look like effort
Mass mailing feels like coverage, and it’s the one failure the government condemned in its own words. Agency contracting professionals “do not find mass emails helpful,” says Myth-Busting 2, and it is “much more effective to target your e-mails to them on specific capabilities or projects.”
Writing the contracting officer first on a live solicitation feels like going straight to the decision-maker. It moves you into FAR 15.201(f), where any substantive answer must reach every competitor. You did not open a conversation. You generated an amendment.
Asking for a set-aside puts a request in the file that the reader has no power to grant. Name-dropping is worse: “we have worked with your agency,” against a subcontract two tiers down at another component, takes one lookup to disprove.
Then the quiet one, which no rewriting fixes. Writing an office that has never bought what you sell. If you didn’t check what it buys and how its buyers search, the email was never the problem.
What to do this week
Then set the follow-up date and leave it alone. Watch that office’s sources sought notices and answer the first one that fits.
When our bench runs outreach, the deliverable is never a mailing list. It’s one email per office, each carrying a number that office recognizes. Same idea behind ask the buyer: the questions worth sending are the ones a former contracting officer would have answered.
Nobody over there is waiting to hear who you are. They’re waiting to find out whether you are one of the two responsible small firms they have to write down before Friday.