Here’s an uncomfortable finding from Flexera’s 2025 State of ITAM research: 59% of organizations actively track SaaS usage, 56% are rightsizing contracts, yet 35% still report increasing SaaS waste. Companies are watching their software spend more closely than ever, and the waste is growing anyway.
The reason is timing, not visibility. Consider a common scenario: finance flags a $30,000 analytics tool with eleven active users out of eighty seats. Everyone agrees it should be downgraded. But the contract auto-renewed three weeks ago, because the 60-day notice window closed while the finding sat in a spreadsheet. The audit was accurate. It was also useless.
A SaaS spend audit is a structured review of every software subscription a company pays for: who owns it, how it’s used, what it costs, and what should happen before the next renewal. The goal is not to cancel as much software as possible. It’s to separate valuable tools from avoidable spend early enough to act.
That last part matters more than most guides admit. BetterCloud’s 2025 State of SaaS notes that consolidation often takes place over multiple years, because contracts and operational risk prevent organizations from simply switching tools off. An unused subscription can still be impossible to cancel this quarter.
Before you begin: define the audit scope
Pick a review period and a coordinator. One person should run the process; no one person should make every decision. Finance, IT, Procurement, Security, and the business owners each hold a piece of the answer.
For a first audit, review the entire portfolio. For recurring audits, prioritize where the money and risk concentrate:
- Money: high-spend vendors, renewals inside the next 90 days, AI subscriptions and usage-based services
- Risk: tools with no clear owner, vendors with missing contracts or invoices
- Waste signals: low-usage applications, duplicate categories, department and card purchases
Step 1: Build a complete SaaS inventory
Start with discovery, not with last year’s spreadsheet. The spreadsheet tells you what someone once knew; the financial and identity data tells you what’s actually being paid for and used.
Pull evidence from corporate cards and bank transactions, AP and expense systems, shared finance inboxes, contract repositories, SSO and identity logs, vendor admin portals, and procurement or security-review records. The FinOps Foundation recommends exactly this cross-referencing approach (financial records, identity logs, and security data) to surface shadow SaaS before centralizing everything into one inventory (FinOps for SaaS).
For each application, capture four clusters of information:
- Identity: vendor, product, business purpose, department or cost center
- Ownership: business owner, technical owner, financial/procurement owner
- Money: monthly and annual cost, billing model, plan, paid seats or committed usage
- Exposure: renewal date, cancellation notice period, auto-renewal terms, contract and invoice locations, recent usage
If you can’t find every subscription reliably, stop and complete a proper SaaS discovery process first. An audit built on a partial inventory produces confident conclusions about the wrong total.
Step 2: Verify ownership
Every application needs a current owner who can explain why the tool exists and participate in the renewal decision. This sounds trivial. It’s usually where the audit finds its first surprises.
The purchaser is rarely the owner anymore. The employee who signed up changed roles two reorgs ago. Procurement holds the contract without understanding the workflow. IT administers access while a business team quietly depends on the tool every day.
Assign three roles per application: a business owner accountable for the outcome and renewal decision, a technical owner responsible for administration and integrations, and a financial owner responsible for contract and payment details.
One rule worth stating plainly: unowned software is a review priority, not an auto-cancel. Orphaned tools are sometimes dead weight, and sometimes load-bearing infrastructure nobody remembered to document. Find out which before you touch anything.
Step 3: Reconcile costs, contracts, and invoices
Confirm the amount being paid matches the agreement and the actual subscription. Check billing frequency, seat or usage commitments, add-ons, price increases, credits, taxes, duplicate charges, and the contracted entity.
Then link every recurring charge to its invoice or contract. This feels like busywork now. It’s what turns your next audit from a three-week archaeology project into a two-day review.
Step 4: Review usage and capacity
Compare what the company purchased with what employees actually use.
For seat-based tools, the questions are mechanical: paid seats versus assigned seats versus active users, former employees still provisioned, users who could drop to a lower tier. For consumption-based products, compare committed capacity against actual usage and forecast demand. For AI services, break costs down by provider, model, project, or token where the data exists. This category is growing fast enough to deserve its own review (AI Spend Management covers the framework).
One nuance most audits get wrong: don’t apply the same activity window to every product. A collaboration tool untouched for 30 days is a red flag. A quarterly planning tool untouched for 30 days is working exactly as intended. Judge usage against the tool’s business cycle, not a universal threshold.
Step 5: Identify duplicate and overlapping tools
Group applications by the job they do, not the vendor name. The usual overlap zones: project management, file sharing, design, video meetings, password management, CRM and sales intelligence, AI writing and research, data visualization, developer tooling.
Two tools in the same category are not automatically redundant, since different teams can have legitimate requirements. But “we’ve always used both” is not a legitimate requirement. Compare users, features, integrations, switching cost, security posture, and contract timing, then choose deliberately: standardize on one platform, restrict one tool to a specialist team, absorb users into existing capacity, or keep both with the reasoning written down.
Step 6: Review renewal and cancellation exposure
Here’s the sentence that should be printed above every finance team’s desk: a renewal date is not a decision deadline. If the contract requires 60 days’ notice, your real deadline is 60 days earlier, and expensive systems need internal review time on top of that.
For every material subscription, confirm the renewal date, notice period, auto-renewal language, price-escalation terms, true-up dates, downgrade rules, data-export requirements, and, critically, who owns the decision. The FinOps Foundation recommends tracking all of these, including price locks and entitlements, as core contract metadata (FinOps for SaaS).
Then schedule the internal review before the contractual notice deadline, with more lead time for anything expensive or operationally important. This single habit prevents more waste than any other step in this checklist.
Step 7: Place every application into an action category
An audit finding without a next step is trivia. Use a consistent decision framework:
| Action | When it fits |
|---|---|
| Keep | Strong usage, clear ownership, appropriate cost, no meaningful overlap |
| Right-size | Valuable tool with unused seats, excess capacity, or the wrong tier |
| Renegotiate | Tool remains necessary, but price or terms should improve |
| Consolidate | Another approved tool can meet the same requirement |
| Cancel | No current owner, usage, or defensible business need after validation |
| Investigate | Missing usage, contract, security, or ownership information |
Every action gets an owner, a deadline, and an expected outcome. If you finish the audit and the output is a color-coded spreadsheet with no names or dates attached, you’ve produced a report, not a result.
Step 8: Make the audit continuous
A point-in-time audit starts aging the moment it’s finished. New tools get purchased, employees leave, trials convert, prices creep. This is why organizations that track usage can still watch waste grow: tracking is a snapshot, and waste is a flow.
Replace the annual cleanup with an operating cadence:
- Weekly: review newly detected subscriptions and urgent renewals
- Monthly: reconcile charges, invoices, owners, and unexpected changes
- Quarterly: review usage, duplicate categories, and optimization actions
- Before every renewal: validate need, capacity, alternatives, and negotiating position
- After offboarding or reorgs: remove access and reassign ownership
The complete SaaS audit checklist
- Discover subscriptions across financial and operational data sources
- Create one inventory of every application and vendor
- Assign business, technical, and financial owners
- Record costs, plans, billing cycles, and payment methods
- Link contracts, invoices, and receipts
- Record renewal dates and cancellation notice periods
- Compare paid capacity with actual usage
- Check former employees and inactive seats
- Identify duplicate and overlapping applications
- Review AI subscriptions and usage-based costs
- Validate security and compliance review status
- Classify each tool: keep, right-size, renegotiate, consolidate, cancel, or investigate
- Assign an owner and deadline to every action
- Create recurring renewal and usage reviews
How ClearSpend supports the audit
ClearSpend automates the slow parts. It connects to Gmail, Google Drive, Slack, Google Workspace, and company cards to discover subscriptions, match spend to supporting documents, assign owners, surface usage context, and organize upcoming renewals. Renewal alerts fire before notice windows close, which, as covered above, is the difference between a finding and a saving.
The result isn’t a cleaner list. It’s an operating system for making software decisions before the deadline, not after it.
Turn your SaaS audit into a continuously updated system.
Start for Free or See a Live Demo.
FAQs
How often should a company run a SaaS audit?
Run a complete audit when establishing the inventory, then review usage and ownership quarterly. High-value applications need a dedicated review scheduled before each contractual notice deadline, not before the renewal date.
Who should participate in a SaaS spend audit?
Finance or FinOps, IT, Procurement, Security, and the relevant business owners. Each team controls different information needed for cost, usage, risk, and renewal decisions, so one coordinator should run the process without making every call alone.
What is the outcome of a SaaS audit?
A verified inventory and an owner-assigned action plan. Every application should be classified for retention, rightsizing, renegotiation, consolidation, cancellation, or investigation, each with a named owner and deadline.
Why do SaaS audits fail?
Most fail on timing, not accuracy. Findings surface after contractual notice windows have closed, so accurate conclusions can’t be acted on until the next renewal cycle, often a full year later.
Sources
- FinOps Foundation: FinOps for SaaS — framework for inventory, allocation, usage optimization, contracts, and renewals.
- BetterCloud: 2025 State of SaaS — application counts, consolidation timelines, and operational constraints.
- Flexera: 2025 State of ITAM (press release with key findings) — visibility, waste, usage tracking, and rightsizing findings.
- ClearSpend: Subscription Tracking — product capabilities referenced above.
- ClearSpend: Renewal Alerts — product capabilities referenced above.