Who owns SaaS spend in the enterprise is the question that decides whether your software budget stays under control or quietly drifts upward every year. In most mid market firms the honest answer is that no one owns it cleanly. Finance signs the invoices. IT provisions the seats. Procurement runs the contract. Each function sees a slice, none sees the whole, and the chronic waste hides in the seams between them. The fix is not a new tool. It is a clear answer to the ownership question.
We work as an independent, buyer side advisor, paid only by the buyer, with no vendor relationship or commission. That vantage point means we see the same pattern across nearly every engagement: the overspend is rarely caused by one bad decision. It accumulates because accountability for total software cost is split so thinly that no single person is responsible for the number going up.
Why no one owns SaaS spend by default
Software arrives in an enterprise from many directions at once. A team lead expenses a collaboration tool. IT renews Microsoft 365 on the Enterprise Agreement. A department head signs a two year deal with a vendor they met at a conference. Each purchase makes local sense. None of them rolls up to a person who watches the total.
The result is predictable. Seats sit unused after people leave. Plans sit one tier too high because no one revisits the original sizing. Two tools do the same job because two teams bought them separately. Auto renewals fire because the renewal date lived in someone's inbox, not on a shared calendar. Every one of these is somebody else's problem, which is another way of saying it is nobody's problem.
This is the core mechanic behind most digital workplace cost optimization work. Before you negotiate a single renewal, you have to fix the question of who is accountable for the stack as a whole.
The three functions and what each should own
Healthy ownership does not mean one person controls everything. It means each function owns the part it is best placed to control, and the boundaries are written down. The split that works looks like this.
Finance owns the number
Finance should own the consolidated software budget, the annual savings target, and the renewal forecast. They are the only function with a complete view of cash and commitments. What finance should not do is decide which tools survive a rationalization. They lack the technical context, and cuts made on cost alone tend to break things and get reversed.
IT owns the technical decisions
IT should own plan tiers, seat allocation, security configuration, and the technical case for keeping or cutting a tool. IT knows that an E5 license duplicates a standalone security product, or that two video platforms overlap. What IT should not carry alone is the cost number, because much of the spend is invisible to them when business units buy directly.
Procurement owns the contract
Procurement should own the contract terms, the renewal process, and the negotiation. They protect against auto renewal traps, uncapped price increases, and unfavourable true up mechanics. What procurement needs from the other two is accurate demand data, so they are negotiating for what the business actually uses rather than what it bought three years ago.
The case for a single accountable owner
Splitting the work across three functions is necessary but not sufficient. Someone has to own the seams. The strongest model names one accountable owner for total software cost, often called a software asset manager or SaaS owner, who sits above the three functions and watches the whole picture.
This person does not buy tools or sign contracts. They maintain the master inventory, track every renewal date, monitor utilisation, and trigger a review before any meaningful renewal locks in. In a large enterprise this is a dedicated role. In a mid market firm it is usually a hat worn by someone in finance or IT, with a few hours a week of protected time. The size of the firm changes the staffing, not the principle.
| Function | Owns | Does not own |
|---|---|---|
| Finance | Budget, savings target, forecast | Which tools survive a cut |
| IT | Tiers, seats, security, technical case | The full cost number alone |
| Procurement | Contract terms, renewals, negotiation | Demand data it cannot see |
| Software owner | Inventory, renewal calendar, utilisation | Day to day tool choice |
How to assign ownership without slowing teams down
The fear that stops most firms from centralising is that a single owner becomes a bottleneck. It does not have to. The aim is visibility, not control over every keystroke. Business units keep autonomy over the tools they use day to day. The owner watches cost, contracts, and overlap, and intervenes only where the numbers say there is waste.
A light approval workflow makes this work. Any new subscription above a low threshold routes through a simple intake form that procurement and the software owner can see. This is not about adding friction. It is about catching the duplicate purchase before it happens, when a team is about to buy a tool the firm already owns inside Microsoft 365 or an existing platform.
For a practical view of how this connects to renewal discipline, our guide on building a SaaS renewal calendar shows the operational side of the owner role. The calendar is the single most useful artifact the owner maintains.
Where ownership and savings meet
Clear ownership is what makes savings stick. You can run a one time audit, reclaim unused seats, and right size a few plans, but if no one owns the total afterward the waste returns within a year. The teams keep buying, people keep leaving, and the inventory drifts back out of date. Ownership is the governance layer that stops the cycle.
Most of the savings still come from the familiar sequence. Right size and rationalize first, then negotiate renewals, then govern to keep the waste out. Ownership is the third step, and it is the one firms skip most often because it feels like overhead rather than savings. In practice it is the cheapest insurance you can buy against next year's drift. For more on the upstream work, see our overview of what digital workplace cost optimization is.
A simple way to start
You do not need a reorganisation to fix ownership. Start by naming one person accountable for the total software number and giving them the renewal calendar and the master inventory. Write down the boundaries between finance, IT, and procurement so the seams are owned. Add a light intake form for new purchases. That is enough to stop the drift, and it costs almost nothing.
If you want an outside read on where the gaps sit in your own stack, an independent assessment maps your current ownership against your actual spend and shows where the accountability is missing. That is usually the fastest way to see the waste your internal teams cannot, because they are each looking at their own slice rather than the whole.