A vendor held a seat on a Texas school district's multiple-award contract for two consecutive three-year terms. Six years of eligibility. In that time, the district sent zero inquiries and placed zero orders.
The contract was not defective. The vendor was not disqualified, delisted, or quietly blacklisted. The award did exactly what an award does, which turned out to be almost nothing. Writing about it in a government contracting forum, the vendor reached for a practitioner's metaphor that names the whole problem: the award is essentially a hunting license, and if you do not know when the buyer is actually hunting, it sits on the shelf.
That is the failure mode. A contract vehicle (a pre-established contract, co-op award, or approved list that makes you legally purchasable) is permission to transact. It is not demand, not a relationship, and not a reason for anyone to pick up the phone. Vehicles answer the question can we buy from you. Nothing about winning a vehicle answers the question that actually produces revenue: should we buy something today, and from whom. Necessary, and in this case worth nothing on its own.
Why does being on the approved vendor list produce no orders?
Because the award is a procurement artifact, not a sales event.
When an agency executes a multiple-award contract, it has finished a compliance task. It has established a lawful path for future purchases from a pool of qualified suppliers. Nothing has been budgeted, nothing has been scheduled, and no end user inside the agency has been told that a new option exists. The vendor experiences the award as a milestone. The buyer experiences it as paperwork filed.
Then the structure of the award works against you. Multiple-award means you are one of several pre-approved suppliers, sometimes one of dozens. Being pre-approved for everyone is functionally identical to being preferred by no one. The vehicle removes an obstacle from a purchase somebody else has already decided to make.
There is a mirror-image version of the same misunderstanding, and it is just as expensive. A solo reseller described being locked out of a state's business entirely because the master contract list had not reopened since 2012: no new vendors, no rebid, no path in. One vendor waits for the list to pay off. The other waits for the list to open. Both are treating the vehicle as the mechanism that produces revenue, and both are standing still.
The practitioner from the first story eventually changed something specific: instead of watching vendor portals, the team started reading board meeting minutes. That is the entire shift in one sentence. A portal tells you what has already been decided. A board packet tells you what is being decided.
How big is the cooperative channel really?
Large enough that holding a vehicle is table stakes, not an advantage.
Sourcewell reported more than $11 billion in cooperative contract sales in fiscal year 2023-24, up roughly 40 percent year over year, across about 800 contracts serving more than 40,000 agencies (audited annual report). NASPO ValuePoint manages more than $21 billion in annual spend, and in NASPO's 2022 Survey of State Procurement Practices, roughly 98 percent of responding states reported purchasing through it.
Read those numbers together and the strategic picture inverts. Cooperative purchasing is not the alternative channel that clever vendors discover. It is the default channel, at enormous scale, and your competitors are on the same paper you are.
It is also narrower than most vendors assume. Piggybacking on someone else's award is a legally constrained act, not a creative one. NIGP's position paper on cooperative procurement is explicit that a piggyback purchase cannot differ in specification, quality, or price from the original award (position paper). Washington State offers a clean worked example of how this gets enforced, with a four-part interlocal test a purchase must satisfy before it is valid.
So the vehicle gives you less room than the sales pitch implies. You cannot negotiate your way into a deal on a cooperative contract. You can only be selected for the thing that was already awarded, which puts all of the leverage upstream, in the period before anyone writes a specification.
What actually triggers an order?
Not the vehicle. Something happens inside the agency, and the vehicle is merely how the resulting purchase gets executed.
The triggers are mundane and observable: a budget line appears in a proposed fiscal year. A board votes to fund a program. A bond measure passes. A grant is awarded with a spend deadline attached. A CIO or superintendent retires and a successor arrives with a mandate. An incumbent contract reaches its final renewal. An implementation fails loudly enough to reach a council agenda.
A veteran procurement chief from a large city described the demand side of this to us plainly: agencies are frequently unhappy with an incumbent in private, and simply do not know how to switch. What unlocks the change is not a better feature list. It is a credible migration path and a peer agency that already made the move and survived it. And the vendors who get the chance to offer that are, almost without exception, the ones already in the room when the conversation starts.
Being in the room is a timing problem, not an access problem. Across Settle's corpus of 33,096 public RFP listings posted between August 2024 and July 2026, 53 percent already include a named procurement contact with an email address. Contact information was never the scarce resource. Knowing which of those people has a reason to talk this month is.
The cost of getting that wrong is measurable. In Deltek's 2026 Clarity study of 917 government contractors, 83 percent reported missing opportunities because they discovered them too late. And late arrives quickly: Settle's analysis of 29,591 public RFP listings put the median response window at 22 days from posting to close. Discovery on day 15 is not a discovery. It is a rushed submission against someone who has been working the account for a quarter.
| What the vehicle gets you | What a signal gets you | |
|---|---|---|
| Question answered | Can this agency legally buy from us? | Should we call this agency today? |
| Timing | Static, valid for a multi-year term | Dated, tied to a meeting, vote, budget, or expiration |
| Competitive position | Identical to every other awarded vendor | Ahead of anyone who is not watching |
| What it enables | A transaction someone else already decided on | Shaping the requirement before it is written |
| Effort profile | Front-loaded, then dormant | Continuous, and compounding |
| Failure mode | Sits on the shelf for six years | Surfaces, then nobody owns it |
Note the last row, because that is where most attempts at fixing this quietly break.
How do winning teams time it?
They treat routing as part of the system, not as an afterthought.
The first thing we hear from teams starting this work is rarely a request for more pipeline. A head of sales came to us after her team lost an RFP that one of her own people had actually seen. The information existed inside the company. It never reached the group. What she wanted was not volume. She described it as a security blanket: confidence that nothing important could pass through the team unnoticed.
That is a routing problem, and it has a specific fix. An alert with no named owner is an alert nobody acts on. The systems that work map territory ownership up front and route each signal to the individual responsible for that account, not to a shared inbox, not to a channel, and not to a weekly digest that everyone skims and no one owns.
The problem gets worse as teams get bigger. At enterprise scale, an opportunity may pass among SDRs, inside AEs, field AEs, and channel partners before anyone with authority touches it. One rep on PTO can silently consume half of a two-week window while the signal sits in a queue. The strongest teams we work with set an explicit budget for this: never lose more than 24 to 48 hours to internal routing. It is an unglamorous rule, and it recovers more days than any improvement in discovery speed.
Practically, four categories are worth instrumenting for the agencies you already hold a contract with:
- Board and council agendas and minutes, where funding decisions become visible before they become solicitations.
- Proposed and adopted budget documents, where next year's purchases are named a year early.
- Expiration and renewal dates on contracts you already hold, and on the incumbents you would like to displace.
- Leadership changes in the departments that buy what you sell.
None of that is exotic. All of it is public. The reason it does not happen is that it is nobody's job, it arrives in no consistent format, and it does not fit the way the team already works. Which is exactly why it fails as a side project and succeeds as a system.
Where Settle fits
Vehicles answer "can we transact?" Signals answer "should we call today?"
Settle works with public-sector sales teams to build that second system. A Settle team member works directly with your team, learns how you already run discovery and pipeline, pieces together the sources you are already monitoring, and builds signal routing into the workflows you actually use, with a named owner and a clear next step attached to every signal, so nothing surfaces into a void. That person stays with your team after the sale, until the system is producing revenue rather than notifications.
The contract vehicle stays exactly where it belongs: as the mechanism you use once someone has a reason to buy. The work worth doing is making sure you know when that reason appears.
Related reading: Pre-RFP signals: how to find opportunities before they are posted and the best SLED sales intelligence platforms.
Frequently Asked Questions
Are contract vehicles and cooperative awards worth pursuing at all?
Yes, they are necessary. Without a vehicle, a purchase that an agency wants to make may not be legally executable, and you will lose deals you had already won on the merits. The mistake is treating the award as the objective rather than the prerequisite. Budget the effort accordingly: qualifying for the vehicle is a compliance project with a finish line, while knowing when a buyer is ready is ongoing work with no finish line and considerably more revenue attached.
If we already hold the vehicle, where should we start?
Start with the agencies that can already buy from you. Build a list of every entity eligible to purchase under your existing awards, then instrument the four categories above for the largest ones: agendas and minutes, budget documents, contract expirations, and leadership changes. You are not prospecting from zero. You are adding timing to relationships that are already legally live, which is the fastest available path from a dormant award to a real conversation.
How is this different from a bid board or an RFP alert?
A bid board tells you what has already been posted, which means the requirements are written, the evaluation criteria are set, and someone has usually been shaping the specification for months. Signals sit earlier: the budget line, the board vote, the expiring contract, the new department head. The practical difference is what you can still influence. Once the solicitation is public, you are competing on the response. Before it is public, you are competing on the relationship, and that is the part the hunting license was never going to win for you.