By Raees Rasool
Pre-RFP positioning is the work you do before the solicitation exists: where federal requirements surface, what FAR 15.201 allows, and where the line sits. Pre-RFP positioning is the research and relationship work that happens before a solicitation exists. This guide covers where federal requirements surface, what FAR 15.201 permits, and where shaping a requirement turns into a conflict of interest. Pre-RFP positioning is everything a company does before the solicitation exists. It means finding the requirement while it is still a budget line, meeting the people who own it, and shaping your own offer around what they actually need. Do that work and the RFP lands as a document you already understand. Skip it and you get thirty days to learn a program the agency spent two years building. Most losses trace back to this gap. The winner did not write faster. The winner started earlier. This guide covers where federal requirements surface first, which conversations the FAR encourages, and where legitimate influence turns into a disqualifying conflict. What Pre-RFP Positioning Means Pre-RFP positioning is not marketing. It is a research and relationship discipline with four outputs. First, you learn the requirement in the buyer's own words. Second, you learn the acquisition history: who holds the work now, what the ceiling is, and when the option years run out. Third, you give the program office enough information to write a requirement your firm can meet. Fourth, you decide early whether to bid, so your team never burns a month on a pursuit you cannot win. None of that happens after the RFP posts. By then the requirement is frozen, the contracting officer has stopped taking calls, and every competitor sees the same document you do. Where Requirements Become Public Federal requirements surface in a predictable order. Learn the order and you buy yourself months. Agency procurement forecasts come first. The agency recurring procurement forecast directory (https://www.acquisition.gov/procurement-forecasts) on Acquisition.gov links to forecast pages for more than twenty departments. Forecasts list anticipated actions, estimated dollar ranges, likely set-aside status and target quarters. They are planning documents, so they move. They still tell you a year in advance that a program exists. Forecast quality varies widely between agencies. Some publish quarterly spreadsheets with point-of-contact names. Others post a stale PDF and leave it. Treat a thin forecast as a reason to call the agency small business office, not as evidence that nothing is coming. Budget justifications come next. Agency congressional budget justifications name programs, appropriations and out-year amounts. A program with money in the FY 2028 request will need a contract vehicle before FY 2028 starts. Then come the notices on SAM.gov. Sources sought notices, requests for information, presolic
Pre-RFP positioning is the research and relationship work that happens before a solicitation exists. This guide covers where federal requirements surface, what FAR 15.201 permits, and where shaping a requirement turns into a conflict of interest.
Pre-RFP positioning is everything a company does before the solicitation exists. It means finding the requirement while it is still a budget line, meeting the people who own it, and shaping your own offer around what they actually need. Do that work and the RFP lands as a document you already understand. Skip it and you get thirty days to learn a program the agency spent two years building. Most losses trace back to this gap. The winner did not write faster. The winner started earlier. This guide covers where federal requirements surface first, which conversations the FAR encourages, and where legitimate influence turns into a disqualifying conflict. What Pre-RFP Positioning Means Pre-RFP positioning is not marketing. It is a research and relationship discipline with four outputs. First, you learn the requirement in the buyer's own words. Second, you learn the acquisition history: who holds the work now, what the ceiling is, and when the option years run out. Third, you give the program office enough information to write a requirement your firm can meet. Fourth, you decide early whether to bid, so your team never burns a month on a pursuit you cannot win. None of that happens after the RFP posts. By then the requirement is frozen, the contracting officer has stopped taking calls, and every competitor sees the same document you do. Where Requirements Become Public Federal requirements surface in a predictable order. Learn the order and you buy yourself months. Agency procurement forecasts come first. The agency recurring procurement forecast directory (https://www.acquisition.gov/procurement-forecasts) on Acquisition.gov links to forecast pages for more than twenty departments. Forecasts list anticipated actions, estimated dollar ranges, likely set-aside status and target quarters. They are planning documents, so they move. They still tell you a year in advance that a program exists. Forecast quality varies widely between agencies. Some publish quarterly spreadsheets with point-of-contact names. Others post a stale PDF and leave it. Treat a thin forecast as a reason to call the agency small business office, not as evidence that nothing is coming. Budget justifications come next. Agency congressional budget justifications name programs, appropriations and out-year amounts. A program with money in the FY 2028 request will need a contract vehicle before FY 2028 starts. Then come the notices on SAM.gov. Sources sought notices, requests for information, presolic