Keeping track of software costs gets harder as portfolios grow. A finance team might know what was paid for a subscription, but not necessarily who owns it, how widely it is being used or whether the current plan still makes sense. Those details can matter when budgets are set and contracts come up for renewal.
A June 2026 report from the U.S. Government Accountability Office (GAO) provides a useful example. It found that [22 of 24 selected federal agencies](https://www.gao.gov/products/gao-26-107530) relied mainly on historical procurement data when making cloud decisions, while 17 struggled to track cloud costs.
# Subscription spending is harder to predict
Traditional software purchases would often come with a defined upfront cost. SaaS introduces a different model. Organizations can pay monthly or annually, add users as teams grow, upgrade plans when requirements change or end up with several tools serving similar purposes. Yes that flexibility can be useful, but it can also make spending harder to follow.
A finance team looking only at invoices may see what the business spent last month without knowing why the figure changed. Perhaps a department added new employees. Maybe usage increased, a plan was upgraded or another application was introduced.
The bigger the software portfolio becomes, the harder it is to trace those changes. Having subscription details, user information, contracts and costs together gives finance and IT a more practical way to examine spending before it becomes a budget problem.
# Historical data only tells part of the story
The GAO’s findings also point to the limits of looking backward. Previous spending can establish a useful baseline, but it cannot show whether the same assumptions still apply.
A company might have paid for several applications for years without questioning whether each one is still needed. Different departments might also have adopted separate tools that perform similar functions.
Viewed individually, those subscriptions might not raise any concerns. Look at them as a group, however and there may be scope to simplify the software portfolio. Current usage data can add another layer to the budgeting process. It can show which costs are relatively stable and which are likely to move as [a business grows](https://www.techbuzz.ai/topics/startups).
# Usage connects technology with cost
Price alone doesn’t tell a company much about how a SaaS subscription is performing. An inexpensive application could be essential to hundreds of employees. A much more expensive service might have only a small number of regular users. Without that context, deciding whether to renew or change a subscription becomes largely a matter of guesswork.
Useful SaaS management data can include:
– Active and inactive users
– Subscription and renewal dates
– License utilization
– Department or team ownership
– Contract and pricing information
– Duplicate or overlapping applications
– Changes in subscription costs
An unused license isn’t automatically a waste. Some software may be required for occasional projects, compliance purposes or specialist tasks. The value of this information is that it gives teams something to work with when reviewing a subscription, rather than forcing them to make decisions based solely on its price.
# Procurement becomes an ongoing process
SaaS procurement doesn’t necessarily end when a contract is signed. A subscription can change several times before its next renewal. Users can be added or removed, plans can be upgraded and new services can be introduced. Each change can affect the eventual cost.
For procurement teams, that makes current information more useful than simply referring back to the original contract.
The GAO report also highlights the difficulty of tracking cloud costs and recommends greater use of FinOps practices, which bring financial and operational teams together to manage cloud spending.
The same principle can apply to businesses with large SaaS portfolios. IT might understand how a service is being used, while finance sees the cost. Bringing those two perspectives together makes it easier to review spending in context.
# A financial control layer for modern software
SaaS management is becoming part of the conversation around financial control because software costs are no longer isolated IT expenses. They can change with headcount, usage, contracts and business requirements.
A clear view of applications, users and spending gives organizations more information to work with when budgets are being prepared or renewals approach. As software portfolios grow, the important question isn’t just how much a company spent last year. It’s whether current spending still reflects what the business needs. For businesses operating across an expanding SaaS environment, keeping that information visible can make software spending easier to understand and manage rather than leaving it as a series of disconnected IT purchases.
