Winning vendors engage agencies before the RFP by getting known to the program office while the requirement is still forming: responding to requests for information and sources sought notices, showing up at industry days, briefing the operating department that owns the problem, and bringing a peer agency that already made the same purchase. They find those agencies by watching the public record that precedes a solicitation, which is filed budget requests, board and committee agendas, capital improvement plans, and contract expirations. Then they stop. Once the solicitation posts, contact is restricted to the designated procurement officer, and stray outreach can disqualify a bid.
That last sentence is the whole reason the first one matters.
Pre-RFP engagement is not lobbying and it is not writing the specification. It is being known to the program office while the requirement is still forming, so that the eventual solicitation does not quietly exclude you and the buyer's list of references includes you. The window closes, legally, the day the solicitation posts.
How do winning government contractors engage agencies before an RFP is released?
Start with the fact that the buyer wants this. It is easy to read early engagement as something vendors do to agencies. Read the acquisition literature and it looks more like something agencies keep asking vendors to do.
The Government Accountability Office put it plainly in its review of federal acquisition practice: "engagement with vendors well before the 30 day solicitation period is key to ensuring vendors have adequate time to review draft requests." The government's own oversight body treats the pre-solicitation conversation as part of a healthy process, not an end run around it. State and local procurement follows the same logic with different paperwork.
Now look at the other side of the ledger. Deltek's 2026 Clarity survey of 917 government contractors found that 83% miss opportunities because they discover them too late. Not on price, not on past performance. They arrived after the requirement was written.
There is also broader evidence, from outside government, about how much first contact is worth. 6sense surveyed roughly 4,766 B2B buyers for its 2025 Buyer Experience Report and found that the vendor a buying group contacts first wins the deal about 80% of the time, and that 94% of buying groups have already ranked a shortlist before speaking with any seller. Two honest caveats. That research is B2B-wide, not SLED-measured, and public procurement runs under competition rules that private purchasing does not. Treat it as directional evidence about how buyers form preferences, not as a number about government contracts.
Put the three together and the shape of the problem is clear. Buyers form a view early, they are formally encouraged to talk to vendors early, and most contractors show up late anyway.
What does the buy side actually want before the RFP?
We asked. One of the more useful conversations we have had this year was with a chief procurement officer of a major city, three decades in the role. Six things from that conversation and others like it influenced how we think about pre-RFP work.
The program manager drives what gets bought, not the procurement officer. Procurement runs the process and enforces the rules. The need originates in the operating department: the public works director, the CIO, the transit chief. His own advice to vendors was to brief him early anyway, so that he could point them toward the right internal sponsor. The mistake he sees is sequencing, vendors working procurement first and the program office later, or the reverse. Engage both at the same cadence. They answer different questions and neither one can substitute for the other.
Agencies are often quietly unhappy with the system they have and do not know how to switch. This is the most underused fact in public-sector selling. The dissatisfaction is real and rarely voiced in public. What unlocks it is not a feature comparison. It is a credible migration path, meaning a concrete answer to what happens to the data, the integrations, and the staff who know the old system, plus a peer agency that already made the same switch and survived it.
Peer comparables are the strongest trust signal a vendor has, because procurement's real risk is a protest. The procurement officer is not primarily worried about overspending. He is worried about an award that gets challenged, delayed, and rerun. A comparable agency of similar size and structure that already bought what you sell is evidence that the requirement is standard rather than tailored, and a standard requirement is a defensible one. Bring the peer reference to the early meeting, not to the proposal.
Watch the sole-source threshold before the meeting, not after. Vendors who grow an account past a dollar threshold can inadvertently trigger the open competition they were trying to avoid, converting a quiet renewal into a public RFP. Know the agency's thresholds and its available cooperative purchasing vehicles before you walk in. Sometimes triggering the competition is the right trade. It should be a decision rather than a surprise.
The realistic goal is a seat at the table, not authorship of the specification. A sales lead in a heavily commoditized category put it to us this way: nobody hands you the pen, and you should not want it. The achievable outcome is being present enough that the drafter knows your category exists and does not write a clause that rules you out by accident. That is a much lower bar than shaping the spec, and it is worth far more than it sounds.
When the solicitation posts, the relationship window closes. Most jurisdictions impose a cone of silence: contact is restricted to the designated procurement officer, and outreach to the program office or an elected official can disqualify a bidder outright. This is not a soft norm. Treat the posting date as a hard stop on the relationship track and a hard start on the compliance track.
How do the best SLED sales teams learn about opportunities before the RFP is published?
They read the paperwork that precedes the solicitation. Almost none of it is hidden.
Budget requests, filed 9 to 11 months ahead. Before a dollar is spent, someone has to ask for it in writing. Georgia's Office of Planning and Budget, to take one representative state, has agencies file their requests in early September for a fiscal year that begins the following July, roughly ten months later (budget process). The filed request is the first hard evidence that an agency intends to buy something.
Board and committee agendas, posted 72 or more hours ahead. California's Brown Act requires that agendas for regular meetings of local legislative bodies be posted at least 72 hours in advance, with a brief description of every item. Most states have an equivalent open meetings law. Contract awards, project authorizations, and study approvals surface here before they surface anywhere else.
Capital improvement plans, covering 5 to 25 years. The Government Finance Officers Association describes capital planning documents that lay out projects over horizons of five to twenty-five years. These are directional rather than committed, but they tell you which agency intends to replace which system, and roughly when.
Contract expirations. An expiring contract is a scheduled decision. It is the single most reliable predictor of a future solicitation, and the date is usually a matter of public record.
Compare that runway to the one you get after the fact. Across the public RFPs in Settle's corpus, the median response window is 22 days and the median deadline for written questions falls 12 days in. A team that first learns about an opportunity when it posts has about a week and a half to decide whether to bid and to understand the requirement well enough to ask an intelligent question. The budget filing that produced that RFP was public ten months earlier. Our SLED budget calendar walks the full cycle month by month.
How can my sales team better identify upcoming public sector opportunities before formal bid announcements?
Six practices, in rough order of effort.
- Monitor budget adoption in your territory. Track the filing date and the adoption date for every state and entity type you sell into. Read the line items in your category. A funded line is an opportunity with a name attached.
- Read board and committee agendas. Agenda packets carry staff reports, and staff reports explain the reasoning behind a purchase in a way no solicitation ever will.
- Respond to every relevant RFI and sources sought notice. These are the sanctioned channel for pre-solicitation input, and agencies use the responses to write requirements. Declining to answer is declining an invitation.
- Attend industry days and pre-solicitation conferences. They exist to let buyers and sellers talk before the cone of silence descends. Attendance is also a matter of record, which occasionally matters later.
- Brief the program office early, and procurement on the same cadence. Explain the category, not the product. Ask what constraints the department is working under. Ask who else internally owns a piece of the problem.
- Bring a peer reference and know the thresholds. A comparable agency that already bought is your strongest asset in the room. The purchasing thresholds and cooperative vehicles determine what is even possible. Learn both before the meeting.
Every item on that list is a next step attached to a signal. None of them is a mass email.
Where is the line between shaping and steering?
The defensible version of pre-RFP engagement is transparency-based. You make your category, your capabilities, and your constraints visible to a buyer who is trying to write a sound requirement, through channels the agency itself opened. Responding to an RFI is sanctioned. Attending an industry day is sanctioned. Briefing a program office during market research is normal practice.
The indefensible version is influence peddling. Ghost-writing a specification that later appears verbatim in the solicitation can create an organizational conflict of interest that disqualifies the vendor, taints the award, or both. Requirements engineered so that only one firm can satisfy them are what protest attorneys look for first. We wrote a longer piece on where that line falls, and on how often what looks wired is really just benchmarked against the incumbent, in Was That RFP Wired?.
The practical test is simple. If the conversation would embarrass the agency if it appeared in a public records request, it was the wrong conversation.
Where Settle fits
None of the signals above are secret. That is the problem. The hard part is watching the budgets, agendas, and contract expirations of roughly 90,000 state and local entities at once, each on its own fiscal calendar and its own document format.
That is the part Settle works on. A Settle team member works directly with your team to turn that public record into verified signals, each with a recommended next action, built around the workflows your team already runs. The goal is not another feed to check. It is that the budget filing which predicts next summer's solicitation reaches the person who can act on it while the requirement is still forming.
If you want the underlying mechanics first, start with pre-RFP signals.
Frequently asked questions
Is it legal to talk to an agency before the RFP is released?
Generally yes, and it is often encouraged. Market research, requests for information, sources sought notices, and industry days exist specifically so buyers and sellers can talk before a solicitation is drafted, and GAO has described early vendor engagement as key to a workable acquisition timeline. The rules tighten sharply once the solicitation posts, when most jurisdictions restrict contact to the designated procurement officer. Check the specific agency's policy, because blackout rules vary by state and by entity.
Should I contact procurement or the program office first?
Both, at the same cadence. The program manager in the operating department drives what gets bought and defines the need. Procurement runs the process, controls the thresholds, and can tell you which vehicle a purchase is likely to run through. A chief procurement officer we spoke with asks vendors to brief him early precisely so he can route them to the right internal sponsor. Treating the two as sequential steps costs you time and usually leaves one of them uninformed.
How far in advance can we realistically see a SLED opportunity?
Nine to eleven months is a reliable horizon, because that is when agency budget requests get filed and the intent to purchase first appears in writing. Capital improvement plans extend the view further, since GFOA describes plans covering five to twenty-five years, but those are directional rather than committed.
What if the RFP has already posted and we have no relationship?
Bid it if the fit is genuinely strong, and treat that bid as a bid rather than as a strategy. Read the evaluation method first, submit questions before the question deadline, and accept that you are competing on response quality against vendors who have understood the requirement for months. Then use the posting as a map. Whoever issued that solicitation runs the same cycle again, and you now know when their next budget request gets filed.