OneGov is no longer an experiment
GSA launched the OneGov Strategy in April 2025 to operationalize Executive Order 14240 (Eliminating Waste and Saving Taxpayer Dollars by Consolidating Procurement) and Executive Order 14271 (Ensuring Commercial, Cost-Effective Solutions in Federal Contracts). One year in, GSA has signed nearly two dozen OneGov agreements covering software, AI platforms, and cybersecurity tools — including direct OEM agreements with Anthropic, OpenAI, Google, Microsoft, Meta, xAI, Perplexity, Broadcom, and Cohesity.
If you sell into the federal government and you still think OneGov is a slogan, you are already behind. When I was a Contracting Officer, the single biggest predictor of who survived a procurement consolidation was who read the strategy document the day it dropped, not the day their pipeline collapsed.
Here is what OneGov actually means for your contract — and the moves you should be making in Q3 and Q4 of FY2026.
What OneGov actually does
OneGov is a procurement consolidation framework. Instead of every agency negotiating its own enterprise license agreement with the same OEM, GSA negotiates one government-wide agreement with standardized terms, ceiling pricing, and standard cyber/AI provisions. Agencies then order against it.
Three things follow from that:
- OEM-direct relationships matter more. GSA's Federal Acquisition Service is partnering directly with original equipment manufacturers to scope products and price them centrally. If you are an authorized reseller of a major OEM, the OEM's OneGov posture now drives your federal market access.
- Reseller margins are under a microscope. GSA's January 22, 2026 RFI (announced as "GSA Seeks Industry Ideas to Enhance Reseller Market Oversight and Value") is explicitly looking at reseller markups for IT hardware and software. Federal News Network reported that vendors are reading this as a precursor to standardized markup ceilings or required disclosure. I read it the same way.
- AI- and software-specific terms are coming. Senior procurement executive Jeffrey Koses confirmed in February that GSA is rewriting solicitation language to handle AI risk, including AI-generated protests with fabricated citations. Expect new representations and certifications on AI use, model provenance, and training-data disclosure to appear in MAS solicitations over the next 12 months.
What changes for your MAS contract
If you are an OEM on Schedule. OneGov is your fast lane. GSA wants direct relationships and is willing to invest negotiation cycles to get standard pricing. Your job is to come prepared with a published commercial price list, a defensible discount structure for the federal customer, and a story about why your terms beat the patchwork of agency-by-agency ELAs you currently support.
If you are a reseller or channel partner. Read the reseller RFI carefully and submit a response. Do not assume your OEM will fight for your margin. The questions GSA is asking — about value-add services, warehousing, integration, and small business pass-through — are exactly the questions that will appear in next year's MAS solicitation refresh. The contractors who shape those questions in 2026 will own the answers in 2027.
If you are a services contractor. OneGov is currently focused on software, AI, and emerging tech. But the same logic — "one negotiation, one set of terms, many agencies" — is already showing up in MAPS, OASIS+, and the FAR rewrite. Services contractors who price like every agency is unique are pricing themselves out of the next vehicle.
What I would do this quarter
This is the playbook I would run if I were sitting in your seat:
- Map every OEM relationship to OneGov posture. For each line of business on your Schedule, identify whether the OEM has signed (or is negotiating) a OneGov agreement. If they have, your customers can buy at OneGov pricing — through you, around you, or instead of you. Know which.
- Audit your reseller markup story. GSA will be asking, and your contracting officer is going to ask too at your next contract-level pricing review under the GSAR 552.238-82 Modifications clause framework. Have a written, defensible explanation of the value you add beyond the OEM transfer price.
- Update your pricing narrative. The old MAS pricing narrative — "Most Favored Customer plus a discount" — is dead alongside the Price Reduction Clause. The new narrative is "transactional data plus market evidence plus value-add." Build that narrative now, before TDR data starts flowing into your contracting officer's dashboard.
- Prepare for AI representations. If you sell anything with an AI component, draft your model and training-data disclosures now. Do not wait for the clause to land in a refresh.
When I was a CO, consolidations always created winners
When I worked acquisitions at GSA, IRS, DoD, and DOI, every consolidation cycle produced the same pattern: a small number of contractors saw the strategic shape early, repositioned, and gained share. Everyone else complained about the new clause and lost share quietly.
OneGov is that kind of moment. The procurement-officer-of-record is shifting from agency-level to GSA-level for an expanding list of categories. If you only sell to one agency, your political capital with that agency now matters less than your terms inside the next OneGov agreement.
Bottom line
OneGov is not a memo — it is a structural change in who negotiates federal price and terms. The contractors who win the next 24 months are the ones who treat OEM OneGov posture, reseller markup defense, and AI representations as Q3 priorities, not Q4 problems. Read the January reseller RFI, respond if you sell IT hardware or software, and rewrite your pricing narrative around transactional data and value-add — because that is the world your contracting officer is already living in.