How to Build a SaaS Spend Report Your CFO Will Actually Read

Most finance teams produce a SaaS spend report every quarter and watch it get skimmed for thirty seconds before the CFO moves to the next agenda item. The problem usually is not the underlying data. It is the format: a flat list of vendor names and dollar amounts tells a CFO what was spent, not what to do next. A report that earns attention has to answer three questions immediately: where is the money going, is it being used, and what decision needs to be made before the next renewal.

Why most SaaS spend reports get ignored

The typical SaaS spend report is an export from the accounting system: a list of vendors, the amount billed to each one this quarter, and a total at the bottom. It is accurate, and it is nearly useless for decision-making. It does not show whether a tool is being used, whether its price is in line with what comparable companies pay, or whether a renewal is coming up in six weeks that needs a decision now.

The scale of the problem is well documented. Zylo's 2026 SaaS Management Index, which analyzed more than 40 million SaaS licenses and $75 billion in tracked spend, found that the average organization now spends $55.7 million a year on SaaS, up 8% year over year, with median spend of $9,455 per employee. Within the last 12 months, 78% of IT leaders reported unexpected charges tied to consumption-based or AI pricing models, and 61% were forced to cut projects because of unplanned SaaS cost increases. Business units now control 81% of total SaaS spend, while IT directly manages just 15%, which means most of the spend a CFO cares about is not visible through any single procurement or IT system.

That fragmentation is exactly why a report built from a single data source, usually the general ledger, misses the picture. A useful report has to pull from billing data, the contract terms behind each charge, and actual usage, then organize all three around the decisions a CFO is about to make.

What a CFO actually wants to see

A CFO reading a SaaS spend report is trying to answer four things in under five minutes: is spend trending in a direction that matches the budget, which tools are costing money without being used, what renewals are coming up that need a negotiation decision, and where is the company exposed to a contract term that could cause a surprise charge. Everything in the report should be organized to answer one of those four questions. Anything else, including granular line items better suited to an expense audit, belongs in an appendix or a linked spreadsheet, not the report itself.

The five sections every SaaS spend report needs

1. Total spend and trend. Total annualized SaaS spend, the prior period for comparison, and the year-over-year or quarter-over-quarter change. Break this into committed spend (active contracts) versus discretionary or month-to-month spend, since the second category is what a CFO can act on immediately.
2. Spend by department or cost center. Software spend allocated to the department that owns the tool, not just the vendor name. This is the section that surfaces shadow spend, the subscriptions a department bought outside of any approval process, which is typically where the fastest savings are found.
3. Utilization and waste. License counts purchased versus licenses actively used, by tool. This is consistently the highest-leverage section in the report because unused licenses are pure waste with no offsetting value. Even a partial accounting (login activity for tools where you can get it, headcount changes for tools where you cannot) is more useful than omitting this section entirely.
4. Renewal risk and upcoming decisions. Every contract renewing in the next 90 days, with the auto-renewal status, the notice deadline, and a one-line recommendation: renew as-is, renegotiate, or cancel. This is the section that turns a report into a to-do list instead of a status update.
5. Contract and pricing risk flags. Any contract with an escalation clause that increases price automatically at renewal, any vendor where actual usage has grown past the contracted tier (creating true-up exposure), and any vendor whose total spend has grown disproportionately to headcount or usage growth.

A step-by-step framework for building the report

1. Centralize the data before you build anything. Pull a full list of active SaaS contracts from accounts payable, your contract repository (or wherever signed agreements live), and your SSO provider if you have one. If these three sources do not already reconcile, that mismatch is itself a finding worth reporting: it usually means there is unmanaged spend the company is not tracking centrally.
2. Map every subscription to a cost center and an owner. A line item without an owner cannot be acted on. If a tool was bought outside of procurement and nobody internally can say who owns the relationship, flag it as unowned rather than guessing.
3. Pull utilization data wherever it exists. For SSO-connected apps, login frequency over the last 90 days is usually sufficient. For tools without SSO, ask department owners directly for an active-user count once a quarter rather than trying to automate it from day one.
4. Extract the renewal date, notice period, and auto-renewal terms from every contract. This is the step most reports skip, and it is the one that turns the report from a historical record into a forward-looking tool. If contracts are scattered across email and shared drives, this step alone often takes longer than the rest of the report combined, which is the strongest argument for centralizing contract data permanently rather than re-extracting it every quarter.
5. Build the report around decisions, not data. For every renewal in the next 90 days, write one sentence recommending an action. For every tool with utilization under 50%, write one sentence recommending a license reduction or cancellation. The report should read like a set of recommendations with data behind them, not a data dump with a summary at the top.
6. Set a fixed cadence and stick to it. A monthly summary view plus a deeper quarterly report works for most mid-market finance teams. Sending the report inconsistently undermines its credibility faster than any formatting issue.

What good looks like: benchmark data for mid-market teams

Mid-market SaaS portfolios (50 to 500 employees, $1 million to $15 million in annual vendor spend) tend to run less centralized than enterprise portfolios because there is rarely a dedicated procurement or SaaS operations function, even though per-employee spend is climbing. Gartner has projected global SaaS spend would approach $300 billion in 2025, with enterprise software spend overall growing 15.2% the following year, driven heavily by price increases and AI-linked feature tiers rather than net-new purchasing. That pricing pressure lands on mid-market teams just as hard as it does on enterprise ones, often harder, because mid-market companies have less negotiating leverage per vendor relationship.

If your report shows license utilization meaningfully below 70%, or if more than a small fraction of contracts lack a documented owner, those are not edge cases. They are consistent with what most mid-market portfolios look like before anyone has run a structured spend review, which is exactly why the first version of this report tends to surface the most savings.

How often to send it, and to whom

Send a one-page summary monthly to the CFO and finance leadership covering total spend trend, top three utilization findings, and any renewal decision due in the next 30 days. Send the full report quarterly to the broader leadership team, including department heads who own the tools being flagged for waste or renewal. Department heads should see the full report, not just the summary, because they are the ones who can confirm whether a flagged tool is actually unused or whether the usage data is simply incomplete.

Frequently asked questions

How much should a mid-market company budget for SaaS per employee?

Industry-wide median spend is $9,455 per employee per year according to Zylo's 2026 SaaS Management Index, though mid-market companies with less negotiating leverage and fewer enterprise-tier discounts often land on the higher end of that range. Use your own trailing 12-month total divided by headcount as the baseline, then track the trend quarter over quarter rather than anchoring to an external number alone.

What counts as a healthy SaaS license utilization rate?

There is no single industry-agreed threshold, but utilization meaningfully below 70% on a given tool is a strong signal worth investigating, and the average mid-market portfolio runs closer to 64% utilized given that roughly 36% of licenses go unused industry-wide. Tools below 50% utilization are typically strong candidates for a license reduction at the next renewal.

How far in advance should renewal risk be flagged in a spend report?

Flag any contract renewing in the next 90 days, since that is the window most finance and procurement teams need to evaluate usage, benchmark pricing, and start a negotiation before an auto-renewal clause locks the company in for another term. Contracts with shorter notice periods, sometimes 30 days or less, should be flagged even earlier given how little time that leaves to act.

Who should own building the SaaS spend report, finance or IT?

Finance typically owns the report because it is the function accountable to the CFO, but the underlying data usually requires input from IT or whoever manages SSO and from individual department heads who own specific tools. The report works best when finance owns the format and cadence while pulling data inputs from whoever actually has visibility into each piece.

What is the difference between a SaaS spend report and a software asset inventory?

A software asset inventory is a complete list of every tool the company has access to, regardless of cost or usage. A SaaS spend report is a subset of that inventory organized around financial decisions: what is being spent, what is being wasted, and what needs a renewal decision soon. You generally need the inventory as a foundation before you can build an accurate spend report on top of it.