Agency Procurement Forecasts for Software Companies, Explained
By Philip Luca — Founder of GovExpress; prior domain experience at Bloomberg Government and GovWin IQ.
By the time a solicitation posts on SAM.gov, the buyer has usually spent months defining the requirement, setting a budget and picking an acquisition strategy. A software company that first hears about a buy on the day it posts is often weeks away from a response it can write well.
Procurement forecasts are one of the few public places where agencies say what they expect to buy before they buy it. This guide explains what a forecast is, where to find one, how to read it and what it does not commit the government to.
What a procurement forecast is
A procurement forecast is an agency’s published list of contracting opportunities it expects to pursue, usually for the current and next fiscal year. Agencies publish them so businesses, and small businesses in particular, can plan ahead. Most agencies run their forecast through the Office of Small and Disadvantaged Business Utilization (OSDBU) or an equivalent small business office.
A forecast isn’t a solicitation. Nothing on it asks for a proposal, and an entry can change or disappear without notice. It’s an early signal of intent, and that is where its value lies.
Where to find them
There isn’t one site that covers every agency, so plan on checking a few places:
| Source | What it covers |
|---|---|
| GSA Acquisition Gateway forecast tool | A shared forecast that many civilian agencies post to, searchable by agency, NAICS code and anticipated award date |
| Agency OSDBU pages | Agencies that keep their own forecast, often as a spreadsheet or a dedicated system, such as the Department of Homeland Security’s acquisition planning forecast |
| Department of War component small business offices | DoW components publish their own forecasts and long-range acquisition plans rather than a single department-wide list |
| Industry days and small business events | Program offices often walk through upcoming buys in more detail than the published forecast |
Start with the agencies that already buy what you sell. Searching a forecast by your NAICS codes narrows a long list quickly.
How to read a forecast entry
Fields vary by agency, but most entries carry some version of these:
- Requirement title and description. Often short. Read it as a pointer to a program, not a full statement of work.
- NAICS code. The code the agency expects to use, which also sets the size standard if the buy is set aside.
- Estimated value. Usually a range, not a figure. Treat it as an order of magnitude.
- Anticipated set-aside. Whether the agency expects to restrict competition to a small business category. See small business set-asides.
- Contract type and vehicle. A new standalone contract, a task order on an existing IDIQ or an order on a schedule. If the buy is planned on a vehicle you don’t hold, you need a partner who does, or a different target.
- Anticipated solicitation and award dates. Usually given as a fiscal quarter. Dates slip often.
- Incumbent and point of contact. Some agencies list the current contractor and a contracting or small business contact. The contact is your invitation to start a conversation.
What a forecast does not promise
Every forecast carries some form of the same caveat, and it’s worth taking seriously:
- It isn’t binding. The agency can cancel, delay, combine or re-scope a requirement, and budgets change with each appropriation.
- Values are estimates. An estimated range is the agency’s planning number, not a contract value and not a signal of what any company will receive.
- It’s incomplete. Many buys, especially small ones and orders under existing vehicles, never appear on a forecast.
- Timing follows the federal fiscal year. A requirement listed for one quarter often moves to the next, and a large share of buying still lands at the end of the fiscal year.
Use a forecast to decide where to spend attention, not to predict outcomes.
Turning a forecast into a plan
A forecast entry is most useful twelve to eighteen months before award, when the requirement is still being shaped. A practical sequence for a software company:
- Shortlist entries that match your product and your eligibility: NAICS code, set-aside status and the vehicle the agency plans to use.
- Watch for the next public notice. A forecast entry is often followed by a sources sought notice or request for information. Answering one is your chance to shape the requirement. See sources sought and RFIs.
- Contact the listed point of contact with a short, specific note about how your product fits the requirement, plus a capability statement.
- Line up partners early if the buy is planned on a vehicle you don’t hold. See teaming and subcontracting.
- Settle your readiness items before the solicitation posts, since registration, accessibility documentation and security attestations take longer than a response window allows.
Where it fits in your federal readiness
A forecast tells you what is coming. Whether you can respond when it arrives depends on the work you’ve already done, from your SAM.gov registration to the security and compliance questions every buyer asks. See how to find federal contract opportunities for the other places buys first appear.
To see where your company stands across the categories federal buyers check, score your company’s federal readiness.
Related reading
- How to Sell Software to the Federal Government: The Complete 2026 Guide for ISVs
- Sources Sought and RFIs for Software Companies: Why Answering Early Shapes the Contract
- The Federal Fiscal Year for Software Companies: Budgets, CRs and Q4
- NAICS Codes for Software Companies: How to Choose, and What They Decide
The CMMC brief
What the Phase 2 suspension changed and what it did not — the obligations that still bind, the assessment path a contract puts you on, the scoping decision that drives the cost, and the sequence that fits inside a pipeline. Sourced from the primary record.