State governments, cities, counties, and special districts buy Microsoft through NASPO ValuePoint, state cooperative vehicles, and direct master agreements. The cooperative rate is widely treated as the deal. It is the ceiling. The negotiated price inside the cooperative depends on how the entity structures the ask and what data it brings to the table. $420M+ recovered. 340+ engagements. Buyer side only.
State and local buyers carry CJIS compliance on every law enforcement system, IRS Publication 1075 on every revenue system, HIPAA on every health and human services system, and a public records perimeter that the inspector general and state auditor care about. The Microsoft estate has to flex against all of it.
CJIS across the law enforcement footprint, IRS Publication 1075 across the revenue and tax systems, HIPAA across health and human services, PCI for the payment surface, and state public records law across every record. Microsoft prices the security and compliance bundle as if every seat needs every control. Most do not.
Microsoft 365 G3 or G5 in GCC. F3 across field crews, first responders, and frontline operations. Azure for case management, benefits administration, and unemployment systems. Power BI Premium across performance reporting. Dynamics 365 for citizen and case management. Defender across the endpoint estate. Sentinel inside the SOC where one exists.
The NASPO and state cooperative published rates are not the negotiated price. Volume tiers, multiyear ramp, and product allocation flex inside the cooperative exist.
We do not replace the cooperative. We negotiate the entity specific deal inside the cooperative and align the GCC allocation to the actual mission.
State biennial budget cycles and local fiscal years drive procurement timing. The right multiyear posture aligns the renewal to the budget cycle.
We advise across the state and local map. State enterprise agencies on global G3 and G5 allocation. Cities on right sized F3 across public safety and field operations. Counties on case management and benefits administration Azure economics. Special districts on the right Microsoft channel for smaller seat counts. Same discipline, scaled to the contract.
The pattern that fails: a procurement officer who treats the NASPO ValuePoint rate as the negotiated price and renews on the cooperative published terms. The pattern that works: an entity that brings mission consumption data, accurate workforce census, and a structured ask into the cooperative and negotiates the entity specific deal underneath.
Microsoft anchors state and local renewals against a workforce headcount that has not been reconciled to current employment in three quarters, a security bundle priced as if every seat needs E5, and a cloud commit aligned to a modernization plan that has not yet been funded in the next biennium. F3 is licensed across the entire field workforce when only the first responder population requires the full bundle. Azure is committed against a citizen experience plan the legislature is still debating.
The most common pattern we see: a state agency paying E5 across the entire workforce when the case workers only need E3 with targeted security add ons, an F3 footprint sized against the peak seasonal field count, and an Azure commit aligned to a benefits modernization that the legislature deferred. The renewal arrives priced against an entity that does not exist.
We start with the entity reality. Current workforce census by program, current Azure consumption against the funded mission, current Defender deployment against the active endpoint estate, and the funded modernization roadmap aligned to the biennial or annual budget. From those we rebuild the Microsoft consumption profile against the appropriation.
We do not opine on policy or program strategy. We translate the workforce, the funded mission, and the actual consumption into commercial terms and run the deal desk negotiation inside the cooperative or master agreement the entity uses.
Anonymized but verifiable on reference call. Drawn from active engagements in the trailing twelve months across the practice.
The opening quote sized E5 across the entire workforce when only program offices and SOC staff required the full security bundle, committed Azure against a benefits modernization that the legislature had deferred, and proposed Defender across an endpoint estate that included program transitions. We rebuilt from the active workforce census, the funded mission roadmap, and the active endpoint inventory.
We had been paying the cooperative published rate as if it were the negotiated rate. Once we built the state specific picture, the cooperative gave us room.Chief Information Officer · State enterprise
Every state and local government engagement produces written deliverables your CFO, CIO, operations leader, and audit committee can read directly. Nothing lives only in our heads.
Board ready narrative of where the contract sits, what leverage exists, and what the disciplined ask is. Signed off jointly with internal stakeholders.
Concession data from signed contracts in your sector, your spend tier, and your renewal quarter. Sourced from active practice engagements.
Calendar of milestones, internal alignment checkpoints, Microsoft engagement touch points, and decision dates from posture through signature.
Live tracker of every ask, every counter, every Microsoft concession landed, and every term we have not yet closed. Updated through signature.
Two analyst calls. No pitch. We tell you what we would do, what the leverage actually is for a state or local entity, and whether we are the right firm for this engagement.