SaaS Spend Management: How to Find, Cut, and Control Software Costs

Software is often one of the fastest-growing lines in a company's budget, and it is one of the hardest to see. A large platform renewal gets board attention. The 80 subscriptions under $5,000 a year, bought on cards by individual teams, mostly do not. Together they can add up to real money and real security risk.

This guide is about getting that under control without becoming the department that blocks every tool request. For the broader category picture, see our overview of indirect spend management.

Step 1: Discover every subscription

No single system has the full list. Combine several sources:

• AP and PO data for larger contracts billed by invoice.
• Corporate card transactions filtered by software merchant categories and known SaaS vendors.
• Expense reports, where employees reimburse themselves for tools.
• Single sign-on (SSO) and identity provider logs, showing which apps people log into.
• Browser extensions or discovery tools, if your IT team uses them, to find apps outside SSO.

Merge everything into one list. Expect to find tools nobody in IT or procurement knew about, including some that store customer or employee data.

Step 2: Build a SaaS inventory with the right fields

For each application, record:

Most of this can be pulled automatically once you have a SaaS management or procurement tool connected to SSO and finance data. At the start, a spreadsheet is fine.

Step 3: Measure real usage

Pull login and activity data for each app. Define "active" sensibly: someone who logged in once in 90 days is not really using an expensive seat. For collaboration tools, look at meaningful actions like creating documents or projects, not just logins.

Sort findings into three groups:

1. Shelfware: licenses paid for but unused.
2. Duplicates: several tools doing the same job.
3. Wrong tier: users on premium plans who only use basic features.

Step 4: Act at renewal, not mid-term

Most SaaS contracts do not allow you to reduce licenses mid-term, so renewal is when savings happen. Work backward from each notice date:

• 90 to 120 days before notice for large contracts: review usage, confirm the owner still wants the tool, and collect alternatives.
• 60 days before notice: decide to renew, reduce, switch, or cancel, and start negotiating.
• 30 days before notice: send the cancellation or reduction notice in writing if needed.

When negotiating, bring usage data. "We have 400 seats and 260 active users" is hard for a supplier to argue with. Ask for the right to adjust seat counts at each anniversary in the new contract. Our contract negotiation prep playbook covers the preparation in detail.

For duplicate tools, pick a standard with input from the teams that use each one. Migrate before the losing tool renews.

Step 5: Control new SaaS purchases

Discovery and cleanup are wasted if new tools keep appearing unchecked. Set up a single intake path for software requests that:

1. Asks what problem the tool solves and whether an existing tool already covers it.
2. Routes to IT security for review when the tool will handle company or customer data.
3. Checks for an existing enterprise agreement with the vendor.
4. Sends approved purchases through procurement or a controlled card with a vendor-specific limit.

Keep it fast for low-risk tools. If a $30-a-month utility takes three weeks to approve, teams will expense it anyway. Many companies set a threshold, such as tools under a small annual amount with no sensitive data, that gets approved within a day.

Don't forget offboarding

When employees leave, their SaaS accounts often keep running, and keep costing. Connect as many apps as possible to SSO so access is removed centrally. For apps outside SSO, include them in the IT offboarding checklist and reclaim the license.

Security and compliance angle

Every SaaS tool holding company data is a vendor relationship with risk attached. Your vendor risk and compliance program should cover SaaS tools by data sensitivity, including SOC 2 reports for tools with access to sensitive data and data processing agreements where privacy laws apply.

Metrics to track

• Total SaaS spend and growth rate.
• Number of applications, and number per employee.
• License utilization rate for your top 20 apps by cost.
• Share of SaaS spend reviewed before renewal.
• Savings from reductions and cancellations at renewal.

Report these quarterly. Once leadership sees shelfware in dollar terms, getting support for the intake process gets much easier.