Five roles, and only one signature
Most first contact with a federal agency fails for a structural reason rather than a persuasive one. It reaches someone who wants the technology and cannot buy it, someone who can buy it and has no idea what it does, or a shared mailbox nobody owns. The people inside a buying office hold different authorities, and the regulations treat each differently depending on where the calendar sits. Sorting that out is the cheapest capture work available.
The five roles are the contracting officer, the program manager, the contracting officer's representative, the technical point of contact, and the small-business specialist. A sixth person sits outside the agency and is often the most useful: the Small Business Administration's procurement center representative assigned to that buying activity. Each is findable in public records, and each answers a different question.
The contracting officer holds the warrant
Under FAR 1.602-1, contracting officers have the authority to enter into, administer, and terminate contracts. That authority arrives on a certificate of appointment, the SF 1402, which states the dollar limit of the warrant. A CO with a $10M ceiling cannot sign your $25M deal, and enthusiasm from the program office does not change it.
The practical consequence shows up in FAR 1.602-3, which deals with unauthorized commitments. If a government employee without warrant authority tells your team to start work, the government is not obligated, the invoice is not payable, and cleaning it up requires a formal ratification. Firms have absorbed six-figure losses this way. When direction arrives that changes price, scope, delivery, or terms, the correct response is to ask the CO to put it in a modification.
The program manager owns the problem and the money
The program manager, or the program office more generally, holds the requirement and the funding line. This is the person losing sleep over a data backlog, a sustainment forecast that keeps missing, or an accreditation package stuck in review. They write or approve the statement of work, and they decide whether a capability is worth buying before the contracting shop ever sees a package.
Program offices are more reachable than most firms assume, because the regulation encourages it. FAR 15.201(a) states that exchanges of information among all interested parties, from the earliest identification of a requirement through receipt of proposals, are encouraged. FAR 15.201(c) lists the mechanisms by name: industry days, market research, one-on-one meetings, presolicitation notices, draft solicitations, requests for information, and site visits. This is not a loophole. It is the government asking to be educated before it writes a requirement it will regret.
FAR Part 10 makes that education mandatory on the government's side: agencies must conduct market research before soliciting offers above the simplified acquisition threshold, currently $250,000 under FAR 2.101. That is where a small firm's technical input has real weight, because the set-aside decision, the NAICS code, the period of performance, and the evaluation factors are all still soft.
Where a first contact actually gets read
Editorial weighting from public guidance and practitioner reading — illustrative, not a measured statistic.
The COR runs the work and cannot change it
Once a contract exists, the contracting officer's representative is the person your engineers talk to every week. FAR 1.602-2(d) requires the CO to designate the COR in writing, and the same paragraph draws the fence: a COR has no authority to make commitments or changes affecting price, quality, quantity, delivery, or other terms and conditions. In DoD, COR certification requirements come from DoDI 5000.72.
Before award the COR is rarely the right first contact, because the role often does not exist yet. After award it is the most important working relationship you have, and the one that shapes whether a follow-on is competed. Treat the COR's technical judgment as the real customer, and copy the CO on every scope conversation.
The technical point of contact, and the pre-release window
In SBIR and STTR, the technical point of contact named in the announcement is the government engineer or scientist who wrote the subject area, usually because a program they support has a gap. That person is the highest-value contact in the federal market for a technology firm, and the window to talk to them directly is narrow.
DoD SBIR/STTR announcements run a pre-release period ahead of the open period, typically two to four weeks. During pre-release you may contact the named technical point of contact directly and ask what the gap actually looks like. When the announcement opens, that door closes: questions move to the public Q&A system on the DoD SBIR/STTR Innovation Portal, where question and answer are visible to every competitor. The rule exists so no offeror gets private information.
Civilian agencies run the same idea on different clocks. NIH program officers are listed in the omnibus solicitation and expect to be asked whether an idea fits their institute. NSF requires a Project Pitch before a full proposal, a structured version of the same conversation. Under 15 U.S.C. § 638(r)(4), agencies are directed to issue Phase III awards, including sole-source awards, to the firm that developed the technology, which is why the technical relationship built during a Phase I is worth more than the Phase I itself.
The small-business specialist is paid to help you
Section 15(k) of the Small Business Act, 15 U.S.C. § 644(k), requires each federal agency with procurement authority to maintain an Office of Small and Disadvantaged Business Utilization. In DoD, the equivalent is the Office of Small Business Programs, with a small-business professional at each buying activity. Their job description is to get small firms into the agency's contracts, and most of them answer fast.
A specialist can tell you which upcoming actions are candidates for a set-aside, which prime holds the incumbent work, who the cognizant contracting officer is, and whether the agency runs vendor outreach sessions. Several agencies, DHS among them, run scheduled one-on-one sessions with a program or contracting representative. Those slots are free and undersubscribed.
Outside the agency, SBA procurement center representatives, established under 15 U.S.C. § 644(l), sit at major buying activities and can formally challenge a contracting officer's decision not to set an action aside for small business. APEX Accelerators, the DoD-funded network formerly known as PTACs, provide free counseling and often know the local buying office personally.
| Role | What they control | Best time to contact | What to send |
|---|---|---|---|
| Contracting officer | Signature authority, solicitation terms, all official contact once a competition is live | Before release; in writing during the Q&A window | Short written questions; capability statement with UEI and CAGE |
| Program manager | The requirement, the funding line, the statement of work | Market research and sources-sought stage, 3 to 24 months out | One-page technical note tied to their named program |
| COR | Day-to-day technical direction; no scope authority | After award only | Performance data, nothing contractual |
| Technical point of contact | The technical gap behind an SBIR or STTR subject area | Pre-release window only; public Q&A after opening | Two or three precise technical questions |
| Small-business specialist | Set-aside advocacy, introductions, forecast detail | Any time, including during an open competition | Capability statement plus a specific NAICS and target office |
| SBA PCR | Independent review of set-aside decisions | Before a solicitation is finalized | Evidence that two or more small firms can perform the work |
How to find these people without knowing anyone
Every one of these names is in a public record. Under FAR 5.101, proposed contract actions expected to exceed $25,000 must be published on SAM.gov, and every notice carries a named point of contact with an email address. Sources-sought and presolicitation notices frequently name both the contracting specialist and the technical lead, a pairing you will not find anywhere else.
USAspending.gov and FPDS give you the awarding office, the incumbent, the ceiling, and the recompete date. Agency procurement forecasts, published under the requirement created by the Business Opportunity Development Reform Act of 1988, list planned actions with estimated values, NAICS codes, set-aside intent, and a named small-business contact.
For defense work, congressional budget justification books identify program elements and the offices that execute them by name. Conference agendas do the rest: program managers speak publicly at NDIA, AFCEA, and SAME events, and the agenda is the org chart.
- SAM.gov notices: named contracting POC on every synopsis, sources sought, and special notice.
- Agency forecasts: planned actions with NAICS, set-aside intent, and a named contact.
- USAspending and FPDS: awarding office, incumbent, ceiling, and recompete timing.
- OSDBU directories: every agency publishes its small-business office and outreach calendar.
- GAO and IG reports: program offices by name, with their problems described in detail.
The calendar decides what is allowed
Timing governs everything here. The same email that is welcome in March is a compliance problem in June, and the dividing line is the release of the solicitation.
Contact windows across an acquisition
FAR 15.201(f) is the passage to memorize. General information about agency mission needs and future requirements may be disclosed at any time. After release of the solicitation, the contracting officer must be the focal point of any exchange with potential offerors, and information necessary for preparing proposals that goes to one offeror must be made public. Agencies apply that by routing questions through the CO and publishing every answer as an amendment.
Calling the program manager after the solicitation drops rarely gets anyone in trouble. It gets a polite redirect, and it marks your firm as a team that does not know the rules.
Three ways to disqualify yourself
Procurement integrity. The Procurement Integrity Act, 41 U.S.C. §§ 2101 through 2107, implemented at FAR 3.104, prohibits obtaining another firm's bid or proposal information or the government's source-selection information before award. If someone offers it, decline in writing. It also governs employment discussions: an official participating personally and substantially in a procurement above the simplified acquisition threshold who is contacted about a job must report it and disqualify themselves. Never raise employment with anyone touching a live competition.
Gifts. Under 5 C.F.R. § 2635.204, the standard exception for gifts to federal employees is $20 per source per occasion and $50 aggregate per year. Coffee is fine. Lunch often is not, and putting a contracting officer in the position of refusing is a poor introduction.
Organizational conflict of interest. FAR subpart 9.5, and specifically FAR 9.505-2, provides that a firm preparing specifications or work statements may be excluded from competing on the resulting contract. Shaping a requirement is legal; drafting the government's specification can cost you the bid. Give them the technical facts and the trade space, and let them write it.
What the first email actually says
The first email is short, specific, and asks for one small thing. Under 150 words, plain formatting, one attachment. Our engineers write these the way they write a status note to a customer.
Subject line. Name the thing. "Capability response to Sources Sought [notice number], document extraction and validation" beats "Introduction from Precision Federal" every time.
First sentence. Why you are writing, anchored to something they published: a notice number, a forecast line, a program element, a panel they spoke on.
Second and third sentences. One concrete statement of relevant capability with a number in it: what system, what data volume, what accreditation boundary, what result. If the strongest thing you can say is that you are experienced and innovative, do not send the email yet.
The ask. One question, answerable in a sentence. "Is the FY27 recompete still planned as a full and open action, or is a small-business set-aside under consideration?" is a real question. "Do you have any opportunities?" is not.
The facts block. UEI, CAGE, primary NAICS, socioeconomic status, SAM status, and any vehicles. Four lines at the bottom. A contracting officer checks these before replying, and having them in view saves a round trip.
The attachment. One page, under 1 MB, a capability statement. Never a proposal, never a deck.
What we do differently
Our team treats agency contact as an engineering problem with a schedule attached. We track forecast entries and recompete dates for the offices that buy the work we do, we answer sources-sought notices in writing with the detail that helps the government write a better requirement, and we build the relationship in the window where it is both allowed and useful. That discipline is visible to evaluators.
The uncomfortable part is that it rewards patience. The contact that wins an award in 2027 usually happens in 2026, before the requirement has a number. Firms that appear only when a solicitation posts are competing against firms the program office already understands.
Common questions on the contact rules
Can we talk to a contracting officer before a solicitation exists?
Yes. FAR 15.201 encourages exchanges from the earliest identification of a requirement. Before release, both the contracting officer and the program office are available, and many agencies want the conversation because FAR Part 10 market research is a requirement they must satisfy.
Does helping shape a requirement disqualify us from bidding it?
Providing technical information and describing the trade space does not. Preparing the specification or statement of work can, under FAR 9.505-2. The safe boundary is that the government writes its own requirement document. If an agency asks you to draft language, ask the contracting officer to address the conflict question in writing first.
Is a conference conversation during an open competition a problem?
General discussion of mission needs is allowed at any time under FAR 15.201(f). Discussion of the live solicitation is not, and the government participant will end that conversation. If a program office person raises the competition, redirect them to the written Q&A process.
Frequently asked questions
It depends on where the acquisition sits. Twelve to twenty-four months out, the program office. Inside a live competition, the contracting officer, in writing. At any point, the agency small-business specialist, whose job is to route small firms to the right office.
No. FAR 15.201(f) makes the contracting officer the focal point for all exchanges after release. Anything specific enough to help you write a proposal must be published to every offeror, so the mechanism is the written question window and the amendment that answers it.
Start with SAM.gov, where every notice above $25,000 carries a named point of contact under FAR 5.101. Cross-check the awarding office and incumbent on USAspending or FPDS, then confirm through the agency small-business office.
A specific subject line, one sentence referencing something they published, two sentences of relevant capability with real numbers, one small answerable ask, and a four-line block with UEI, CAGE, NAICS, and SAM status. One attachment, one page, under 1 MB.
Request it in writing within three days of receiving notice of exclusion or notice of award, under FAR 15.505 and 15.506. In DoD, DFARS 215.506-70 lets an offeror submit written follow-up questions within two business days of the debriefing, with a response within five business days, and the debriefing is not closed until then.
Bottom line
The rules governing agency contact are public, short, and mostly permissive. FAR 15.201 invites the conversation. FAR Part 10 obligates the government to do market research. Section 15(k) of the Small Business Act staffs an office whose job is to bring firms like yours in. What the rules restrict is timing, and the restriction bites exactly when most firms first think to call. Do the work early, put questions in writing once the competition opens, and the person who reads your proposal will already know who you are.