What a cooperative award is actually worth
A cooperative contract is a competitively awarded contract that public entities other than the awarding one are permitted to use without running their own solicitation. One evaluation, one negotiation, one published price list, and then a standing population of buyers who can issue a purchase order in a week instead of six months. The Census Bureau counts roughly 90,000 local government units in the United States, on top of fifty states and their agencies, and the national cooperatives count their participating members in the tens of thousands. That is the whole point of the instrument. It converts a single win into a channel.
The catch is that a channel only pays if you can deliver into it. A firm that wins a statewide IT contract covering data platforms, analytics, and machine learning services has bought the right to sell that work in dozens of jurisdictions at once. It has not bought the engineers. Cooperative contracts are frequently won by firms with strong capture teams and thin delivery benches, and the gap between the awarded scope and the staffed scope is where most cooperative revenue quietly dies. Orders get declined. Scopes get narrowed to whatever the incumbent bench already does. The vehicle renews with a fraction of the sales it was capable of carrying.
The fix is boring and effective. Two firms share the vehicle. One holds the contract, keeps the customer relationship, and carries the privity. The other supplies the engineering depth for the scopes the holder cannot staff. Done properly this is invisible to the buyer in the ways that should be invisible and fully documented in the ways that must be documented. Done sloppily it produces an order that a jurisdiction's counsel cancels, or an audit finding, or a cooperative that pulls the contract. The difference is almost entirely paperwork discipline.
Piggyback readiness — what decides whether an order clears review
Editorial weighting drawn from public procurement codes and cooperative program rules — illustrative, not a measured statistic.
Two different doors, routinely confused
The first door is federal. Under 40 U.S.C. § 502(c), state, local, and tribal governments may buy information technology from GSA Multiple Award Schedule contracts through the Cooperative Purchasing program, an authority created by the E-Government Act of 2002 and later extended to cover security and law enforcement products and services. A separate authority at 40 U.S.C. § 502(d) supports Disaster Purchasing, which lets non-federal entities buy from Schedule contracts in advance of or in recovery from a declared major disaster. Neither authority opens the whole Schedule. Eligibility runs at the Special Item Number level, and GSA eLibrary flags which SINs are open to cooperative purchasing and which are federal-only. Read the flags before you promise a county anything.
The second door is state and local, and it is much larger. The lead-agency model dominates. One entity runs a full public solicitation with language stating that other public entities may use the resulting contract, and other jurisdictions then adopt it. NASPO ValuePoint is the mature version at state scale: a lead state competes a master agreement, and other states join by executing a participating addendum that layers their own terms on top. Sourcewell, a Minnesota service cooperative, competes contracts used nationally by governments, schools, and nonprofits. OMNIA Partners, E&I for higher education, TIPS out of a Texas education service center, and BuyBoard for Texas school districts run the same play with different membership bases. Statewide programs such as the Texas Department of Information Resources cooperative contracts sit in between, competing IT contracts that local entities across the state may use.
The third form is the plain piggyback. A city adopts a neighboring county's competitively awarded contract by resolution because the county's solicitation contained an "other public agencies may purchase from this award" clause. Most states enable this through an interlocal cooperation statute. It is the least formal path and the one most likely to be challenged, because the adopting entity is relying on a competition it did not run and did not observe.
What makes a contract eligible to ride
Eligibility is decided by the original solicitation, not by the later buyer's convenience. Cooperative language that was not in the document the market bid against cannot be bolted on afterward. Every serious procurement office knows this, and it is the first thing counsel checks.
- The original award was competitively solicited, and the file proves it
- The solicitation itself contained cooperative or other-agency language
- The adopting jurisdiction's own procurement code permits piggybacking
- The requested work falls inside the awarded scope and the awarded price list
- The contract term, including exercised renewal options, is current at the order date
- The buyer documents price reasonableness in its own file
- Any funding-source rules layered on the purchase have been checked separately
Where AI and data work strains the vehicle
Most cooperative IT contracts were written for products, licenses, and staffing categories. They price hardware, they price software subscriptions, and they price labor categories with ceiling hourly rates. Modern AI and data work is often deliverable-based: a fixed-price data migration, a model evaluation with a defined acceptance test, a production pipeline delivered against milestones. If the awarded price list contains only hourly labor categories, a fixed-price outcome may sit outside what the vehicle can carry, and the buyer's contracting officer will say so.
Three specific stress points show up again and again. First, labor category fit. A master agreement written in 2023 may have no category for a machine learning engineer, a data platform architect, or an MLOps specialist, which forces the work into a generic senior developer line at a rate that does not reflect the skill. Second, hosting. Many cooperative contracts treat cloud hosting as a pass-through commodity and are silent about who holds the cloud account, who pays egress, and what happens at the end of term. Third, intellectual property. Cooperative masters are frequently quiet on data rights, and then a state participating addendum imports work-for-hire language that assigns everything, including model weights trained partly on the vendor's prior work. Read the addendum, not just the master.
Three ways two firms deliver under one vehicle
There are only a few honest structures, and they differ mainly in who has privity with the buyer.
| Structure | Privity with the buyer | Who invoices | Use when |
|---|---|---|---|
| Prime and subcontract | Vehicle holder only | Vehicle holder invoices; partner invoices the holder | Default for almost every state and local cooperative. Simple, familiar to buyers, fast to stand up. |
| Authorized dealer or reseller designation | Vehicle holder remains responsible; partner is named on the contract's authorized list | Depends on the program; often the partner transacts and remits to the holder | The cooperative program formally supports named dealers and the buyer wants a local delivery presence. |
| Contractor Teaming Arrangement (GSA MAS) | Each team member holds its own Schedule contract and its own privity with the ordering activity | Each member invoices under its own contract | Both firms hold MAS contracts with the needed SINs, and the buyer wants one solution with divided responsibility. See FAR 9.601(1). |
| Jurisdiction split across addenda | Vehicle holder in every state; partner named in the addenda where it delivers | Vehicle holder, with a per-state settlement | A NASPO ValuePoint style master where states join individually and in-state presence matters. |
The subcontract is the workhorse. It puts one name on the order, one insurance certificate, one W-9, and one remittance address, which is what a school district business office wants. The teaming arrangement under FAR 9.601(1) is worth understanding because it behaves differently: on a GSA order, each team member is in privity with the ordering activity for its own portion, which means each carries its own liability and each reports its own sales. Buyers who have used a Contractor Teaming Arrangement before like it. Buyers who have not will ask why there are two invoices.
Who is the contractor of record, and what that decides
Privity is not a technicality. It decides who is liable for performance, who receives and answers a protest, who gets named in a bid dispute, who signs the security addendum and the business associate agreement, who carries the certificate of insurance and any performance bond, whose sales report drives the administrative fee, and whose corporate records get pulled if a state auditor asks how the purchase was competed.
For a delivery partner, the practical translation is simple. If you are the sub, you take direction through the holder, your people appear in the holder's staffing plan under their own names and credentials, and your quality obligations are written into the subcontract rather than assumed. If you are the holder, you cannot delegate responsibility along with the work. The buyer bought your contract. A partner that disappears mid-project is your problem to solve, which is why the subcontract needs named key personnel, a substitution clause with approval rights, and a transition obligation that survives termination.
Splitting delivery across jurisdictions
The cleanest split line is jurisdictional, because the contract structure already draws it for you. Under a lead-state master agreement, each participating state signs its own addendum, and that addendum is where local terms attach: state-specific security requirements, insurance minimums, prompt-payment terms, small-business or in-state subcontracting expectations, additional administrative fees, and sometimes a list of authorized resellers permitted to deliver in that state. Two firms can therefore agree that the holder carries the first tranche of states and the partner is named in the rest, with one joint scope and one joint rate card underneath.
Local piggybacks split the same way, just at a smaller grain. A regional split works well when travel matters, when a state requires registration to do business locally, or when one firm has staff cleared for a particular data type in one jurisdiction and not another. What does not work is splitting by discipline inside a single order without telling the buyer. If the order says the holder is delivering the machine learning work and someone else's engineers show up on the calls, the relationship is already damaged. Name the partner in the response. Buyers rarely object to a named, qualified sub. They object to discovering one.
Standing up a two-firm cooperative delivery
Pricing that survives twenty jurisdictions
Ceiling rates on a master agreement are ceilings. Discounting below them is allowed and often expected; going above them requires a contract modification, which is slow and visible. That single fact should shape the joint rate card. Build the split so the partner's fully burdened rate plus the holder's margin plus every fee still clears the ceiling with room to discount, because a large buyer will ask for a discount and you need somewhere to go.
Fees are the line people forget. GSA Schedule sales carry the Industrial Funding Fee at 0.75 percent of reported sales, remitted quarterly through the FAS Sales Reporting Portal. State and national cooperatives charge their own administrative fee to the vendor, calculated on reported sales, usually in the low single digits, and a participating state can add a fee of its own on top. Those fees apply to the full value flowing through the vehicle, including the portion the partner performs. If the fee is not in the split before anyone quotes a rate, it comes out of somebody's margin later, and the argument about whose is unpleasant. Multi-year masters also cap annual rate escalation, so a partner whose labor costs rise faster than the cap absorbs the difference unless the subcontract says otherwise.
When federal grant dollars pay the invoice
A large share of state and local technology spending is federally funded, and federal money brings the Uniform Guidance with it. Under 2 CFR 200.317, states follow their own documented procurement policies when using federal awards; every other recipient type, including counties, cities, districts, tribes, and nonprofits, follows 2 CFR 200.318 through 200.327. That distinction alone changes which checklist applies to your buyer.
The provision that blesses cooperative purchasing is 2 CFR 200.318(e), which encourages recipients to enter intergovernmental or inter-entity agreements for the procurement of common goods and services. It does not waive the rest. Competition requirements at 2 CFR 200.319 still apply, and 2 CFR 200.324 requires the recipient to perform a cost or price analysis for every procurement above the simplified acquisition threshold, which currently sits at $250,000, with the micro-purchase threshold at $10,000 under the definitions at 2 CFR 200.1. Riding a cooperative contract satisfies the competition duty; it does not satisfy the price analysis duty. Two other provisions bite regularly: 2 CFR 200.216 prohibits obligating federal funds for covered telecommunications equipment and services, and 2 CFR 200.322 carries the domestic preference expectations for infrastructure work. A buyer who skips these gets a finding in the single audit, and findings travel back to the vendor as cancelled orders.
Security clauses change at the state line
A partner delivering in ten jurisdictions is delivering under ten slightly different security addenda. Cloud services increasingly need a state authorization: GovRAMP, formerly StateRAMP, is the multi-state program, and Texas runs TX-RAMP for state agency cloud services under Texas Government Code § 2054.0593. Data type drives the rest. Anything touching criminal justice information falls under the FBI CJIS Security Policy, with fingerprint-based background checks and a signed security addendum for every person with access. Federal tax information in a state revenue or human services system triggers IRS Publication 1075. Health data brings HIPAA and a business associate agreement. Student records at districts and public universities bring FERPA at 20 U.S.C. § 1232g, which is why school-facing analytics work so often stalls in counsel review.
The workable approach is to build one joint control baseline at the strictest level in the target set and run it everywhere, then map that baseline to each jurisdiction's addendum rather than maintaining ten security programs. It costs more on day one and far less by the fourth state.
Where these partnerships come apart
Scope drift. The order describes work the original solicitation never contemplated. A competitor notices, the buyer's counsel pulls the order, and both firms lose the jurisdiction for years.
Fee math done last. Rates get quoted, then someone finds the administrative fee, the participating state fee, and the escalation cap. The partner is asked to absorb all three.
The partner treated as a staffing pool. A delivery partner brought in to own outcomes and then managed as hourly bodies will underperform, and the buyer will see it.
Reporting gaps. Sales through the partner never make it into the quarterly report, the cooperative reconciles at renewal, and the vendor owes back fees with interest.
Silence on data rights. Nobody asks who owns the trained model until the buyer's attorney does, in week nine.
Term expiry. An order placed while the contract is current generally survives its expiration according to its own terms. A new order placed the week after does not exist.
What we bring to a vehicle we do not hold
Precision Federal is an SBIR and STTR shop that builds production AI, ML, data, and cloud systems, and we are open for federal, state, and commercial work as prime or subcontractor. Our team is led by a former professor in technology who ranks in the Kaggle top 200 of more than 200,000 competitors, the top 0.1 percent, and holds seven cloud certifications, with twenty years building production systems for federal agencies across five consulting firms, three of them federal. We are SAM.gov active, CAGE 1AYQ0, and JCP / DD-2345 certified. Behind that sits a standing bench of named engineers, licensed professional engineers, and domain specialists across defense, health, energy, transportation, and public-sector data, which is what lets us put real names and real credentials into a staffing annex rather than placeholders.
On a cooperative vehicle we are usually the sub, and we like that position. The holder keeps the customer relationship, the privity, and the credit. We supply the engineering: data platforms, model development and evaluation, pipeline and MLOps work, document and records automation, and the security documentation that gets it accepted. We move at the pace a purchase order demands, and we write scopes that a procurement office can approve on the first read.
Frequently asked questions
Cooperative purchasing usually means a formal program, such as a lead-state master agreement with participating addenda or GSA's Cooperative Purchasing authority at 40 U.S.C. § 502(c), where the joining process is defined in advance. Piggybacking is the informal version, where one jurisdiction adopts another's competitively awarded contract because the original solicitation permitted it. The formal programs are easier to defend in an audit.
Yes, in almost every program, provided the prime remains responsible and the buyer is told who is performing. Some cooperatives also maintain an authorized dealer or reseller list, which formalizes the partner's role. Check the master agreement's subcontracting clause and the participating addendum, since a state can add approval requirements the master does not have.
It addresses the competition requirement, because 2 CFR 200.318(e) encourages inter-entity agreements for common goods and services and the underlying award was competed. It does not remove the recipient's obligation to perform a cost or price analysis above the simplified acquisition threshold under 2 CFR 200.324, or the domestic preference and prohibited-equipment provisions at 2 CFR 200.322 and 2 CFR 200.216.
The fee is assessed on sales reported through the contract, which includes work performed by a partner. Decide in the subcontract whether the fee is deducted before or after the split, and write the treatment of any additional state participating fee into the same clause. GSA Schedule sales carry the Industrial Funding Fee at 0.75 percent of reported sales, reported quarterly.
The contract number, the awarded scope and price list, the jurisdictions in play, and a short description of the work. That is enough to determine scope fit, rate fit under the ceiling, and whether the security requirements in those jurisdictions are achievable on the schedule the buyer wants.