Why Structure Sets the Price
The IT operating model is usually discussed as a question of delivery speed and innovation. For software licensing it is something more concrete: it sets the price. Whoever holds the buying authority, owns the contract, and sees the consolidated total determines whether your enterprise approaches a vendor with the leverage of aggregated scale or with the weakness of fragmented, duplicated purchasing. With roughly 70% of software spend now controlled by business units rather than central IT, that authority has drifted outward in most enterprises — and so has the cost.
This is the operational counterpart to the strategy we set out in the pillar, The CIO's Guide to Enterprise IT Contract Strategy. Strategy describes how to negotiate; the operating model decides whether the enterprise is even structured to negotiate well in the first place. The two have to be designed together.
Three Models and Their Licensing Consequences
Each operating model carries a distinct licensing signature. A centralised model concentrates buying authority in a single function, which maximises volume leverage and contract consistency but can become a delivery bottleneck. A decentralised model pushes procurement into business units, which accelerates delivery but fragments entitlements, duplicates tools, and spawns shadow SaaS — directly weakening every renewal. A federated model splits the difference, and is where most high-performing enterprises now sit.
| Operating Model | Licensing Leverage | Primary Risk | Typical Waste |
|---|---|---|---|
| Centralised | High — aggregated scale | Bottleneck; slow business response | Low, but over-provisioning if demand is opaque |
| Decentralised | Low — fragmented buyers | Duplicate tools; shadow SaaS; no single total | High — overlapping licences across units |
| Federated (hub-and-spoke) | High — central contracts, local execution | Requires real governance to hold | Low — when guardrails are enforced |
MIT CISR's 2025 research on operating models in the AI era makes a sharper point: the decisive question is not centralised versus decentralised at all, but how strongly the enterprise drives reuse of platforms and modules. Reuse is what prevents the same capability being licensed three times across three business units. That architectural discipline is the subject of enterprise architecture and licensing alignment, and it is inseparable from how the operating model is drawn.
The Pattern That Wins: Centralised Enablement
The dominant high-performing pattern, borrowed from FinOps practice, is centralised enablement with federated execution — a small central team that sets standards, owns the major contracts, and runs the tooling, while business units act with speed inside clear guardrails. In FinOps benchmarking, centralised enablement is the most common structure at around 60% of organisations, with hub-and-spoke models a further 21% and more common in large enterprises. The same shape applies to licensing: the centre negotiates the top vendors by spend, and the spokes consume against those agreements rather than striking their own.
The enterprise that buys as one and consumes as many will out-negotiate the enterprise that buys as many and reconciles as one — every renewal, every vendor, every year.
This is also where the unresolved question of who owns the vendor relationship — CTO or CIO becomes a structural decision rather than a turf dispute, and where a disciplined approach to vendor negotiation in 2026 can actually be executed instead of merely written down. The operating model is what turns negotiating intent into negotiating capacity.
Getting to that pattern is a deliberate redesign, not a reorganisation chart. The practical move is to define a short list of "enterprise vendors" — typically the ten to fifteen suppliers that account for the bulk of spend — and pull their contracts, renewals, and entitlement data into the centre, while leaving the long tail of low-risk, low-cost tools with the business units inside an approved catalogue. This concentrates effort where leverage actually exists: in most enterprises a small number of vendors drive the majority of software cost, so centralising those few contracts captures most of the available negotiating power without the bureaucracy of routing every $5,000 purchase through a central queue. The guardrails — standard contract clauses, an approved-tool catalogue, and a mandatory intake for anything new — are what let the spokes move quickly without recreating the fragmentation the model is meant to solve.
SAM and FinOps Convergence
Modern licensing is no longer one thing. It is part perpetual licence, part subscription, part cloud consumption, and increasingly part AI metering — and the operating model has to manage all of it in one view. Software Asset Management governs entitlements; FinOps governs consumption spend. Gartner projected that by 2025 around 50% of organisations would unify the two into a single discipline for portfolio cost management, precisely because waste hides in the gaps between them. Companies use only about half the SaaS licences they buy, and FinOps practices have delivered average cloud cost reductions of around 30% where they are run well.
A converged SAM-plus-FinOps function inside the central enablement team gives you the single source of truth that makes every other discipline work — the vendor risk framework, the benchmarking in IT Spend Benchmarking, and the trial controls in The Hidden Cost of Free Software Trials. Our CIO contract governance white paper sets out how to stand that function up without re-centralising everything.
Aligning the Model With Licensing Strategy
The practical rule is simple to state and hard to execute: centralise what creates leverage, federate what needs speed. Major vendor contracts, the renewal calendar, benchmarking, and the SAM/FinOps function belong in the centre. Day-to-day tool selection, within an approved catalogue and clear guardrails, belongs with the business units. Give the central team a mandate over the top vendors by spend and ownership of the renewal pipeline, and the enterprise stops leaking value at every uncoordinated purchase.
This alignment ripples into adjacent disciplines: it is the structural foundation under IT budget planning and contract optimization, it determines what can credibly be reported in Board-Level IT Spend Reporting, and it shapes how new dependencies are governed during digital transformation. Where the heavy lifting is licensing negotiation itself, our software licensing negotiation practice operates as the central team's specialist arm, and the multi-vendor coordination problem is addressed in our multi-vendor strategy white paper alongside the vendor intelligence hub. To pressure-test whether your operating model is helping or hurting your licensing position, request a confidential briefing.