How to reduce unused SaaS spend in my company
The fastest way to reduce unused SaaS spend is to create one inventory of every subscription, match purchased seats to actual usage, reclaim inactive licenses, consolidate overlapping tools, and review contracts before renewal. Do not start by cutting software at random. Start with visibility, ownership and repeatable controls.
Last reviewed:
Unused SaaS spend usually comes from:
- Licenses assigned to former employees
- Seats purchased for people who rarely use the application
- Duplicate tools used by different departments
- Premium features that teams do not need
- Automatic renewals with no clear owner
- Software purchased outside procurement
- Annual contracts that cannot be reduced when headcount falls
The FinOps Foundation recommends treating license reclamation, SaaS ownership, renewal management and contract flexibility as ongoing processes rather than annual cleanup exercises.
SaaS Spend Reduction at a Glance
| Action | What to find | Typical decision |
|---|---|---|
| Build a SaaS inventory | Vendors, contracts, seats, owners and renewal dates | Create one source of truth |
| Analyze usage | Logins, active days, feature usage and assigned seats | Reclaim, downgrade or retain |
| Remove former-user access | Departed employees and inactive accounts | Deprovision and reclaim |
| Consolidate tools | Applications with overlapping functionality | Keep one approved platform |
| Review pricing tiers | Premium seats and unused features | Downgrade or change plan |
| Control renewals | Upcoming renewal dates and notice periods | Renegotiate, reduce or cancel |
| Prevent new waste | Unapproved purchases and uncontrolled access | Add approval and lifecycle rules |
1. Create a Complete SaaS Spend Inventory
You cannot reduce unused SaaS spend by reviewing only the invoices handled by IT. Build the inventory from every payment and access source:
- Accounts payable and corporate card statements
- Procurement and vendor management systems
- Microsoft 365, Google Workspace or another identity platform
- Single sign-on application catalogs
- Expense reports and employee reimbursements
- Department budgets
- Browser or cloud application discovery tools
- Vendor invoices and renewal notices
Track at least these fields:
| Field | Why it matters |
|---|---|
| SaaS application | Identifies the vendor and product |
| Business owner | Gives one person accountability |
| Department or cost center | Shows who benefits from the spend |
| Contract owner | Identifies who manages commercial terms |
| Renewal date | Prevents automatic renewal surprises |
| Cancellation notice period | Shows the latest date to act |
| Contracted seats | Shows the maximum entitlement |
| Assigned seats | Shows current allocation |
| Active users | Shows actual usage |
| Price per seat | Enables savings calculations |
| Plan or tier | Identifies downgrade opportunities |
| Payment method | Finds decentralized or shadow spend |
| Data sensitivity | Helps prioritize security and offboarding |
The FinOps Foundation recommends centralizing license management, tracking renewal dates and assigning clear ownership for SaaS costs.
Start With the Largest and Nearest Renewals
Do not try to audit every application at once. Start with:
- The ten highest-cost SaaS applications
- Contracts renewing within the next 90 to 120 days
- Applications with many inactive users
- Tools with unclear ownership
- Applications that duplicate another product
- Software purchased on corporate cards or by individual teams
This gives you a faster path to savings than spending weeks cataloguing low-cost tools.
2. Define What "Unused" Means for Each SaaS Application
A user who has not logged in recently is not automatically unnecessary. Some applications are used quarterly, seasonally or only during a specific project.
Use several signals instead of login activity alone:
- Last login date
- Number of active days in the past 30, 60 or 90 days
- Use of core features
- Files created, reports run or workflows completed
- API activity
- Assigned versus unassigned seats
- User role and department
- Contractual minimum-seat requirements
- Whether the user is seasonal, external or project-based
A starting policy could define:
- Inactive: no login or meaningful activity for 90 days
- Underused: occasional access that does not justify the current plan
- Unassigned: a paid seat that is not allocated to a user
- Duplicate: a tool that substantially overlaps with an approved application
- Exception: a seasonal, executive, service, compliance or project-based account
Adjust the thresholds for the application. A daily collaboration tool may justify a 30-day review, while tax, audit or annual planning software may need a longer window.
3. Reclaim Unused Licenses Safely
The clearest savings usually come from paid seats assigned to former employees, inactive accounts and unassigned licenses.
Use this sequence:
- Export the purchased-seat count from the vendor.
- Export current users and last activity.
- Match users against the HR directory.
- Identify leavers, contractors and duplicate accounts.
- Ask the business owner to confirm exceptions.
- Remove or downgrade approved users.
- Record the reclaimed seats and expected savings.
- Recheck the application after 30 days.
For example, a company paying $30 per month for 200 seats has annual spend of $72,000. If 40 seats are unused, reclaiming those seats could reduce annual spend by $14,400, assuming the contract permits a proportional reduction. That is a 20% unused-seat rate.
Do not delete accounts before checking:
- Data retention requirements
- Legal holds
- Ownership of shared files
- Workflow dependencies
- API and integration accounts
- Customer or regulatory records
- Whether the contract permits a mid-term reduction
For identity-managed applications, Microsoft Entra ID supports application access reviews that can be scheduled, assigned to reviewers and configured to remove access when users no longer need it. Microsoft Entra access reviews can also use last-sign-in information as one input to review decisions.
4. Automate Joiner, Mover and Leaver Processes
Manual user management creates two common forms of waste:
- Former employees keep paid seats.
- New employees receive the wrong plan or duplicate access.
Connect key SaaS applications to your identity provider through single sign-on and automated provisioning where supported. Microsoft Entra ID identifies SSO, user provisioning, synchronization and role-based access control as ways to manage SaaS access centrally.
Set rules such as:
- Remove access when an employee leaves
- Suspend accounts after a defined period of inactivity
- Assign applications through groups rather than individually
- Require manager approval for premium plans
- Review contractor access at a fixed expiry date
- Downgrade users who no longer need advanced features
- Require approval before restoring a suspended account
Automation should support business review, not replace it. A lack of recent login activity may not mean that the user has no business need.
5. Consolidate Overlapping SaaS Applications
Many companies pay for several products that solve the same problem. Common overlaps include:
- Project management
- Team messaging
- Document collaboration
- Customer relationship management
- Design and whiteboarding
- Marketing automation
- Password management
- Data visualization
- File storage
- Electronic signatures
Create a simple application review table:
| Application | Main use | Departments using it | Annual cost | Overlap | Recommendation |
|---|---|---|---|---|---|
| Tool A | Project tracking | Product, marketing | High | High | Make strategic platform |
| Tool B | Project tracking | One small team | Medium | High | Migrate or cancel |
| Tool C | Reporting | Finance | Medium | Low | Retain |
| Tool D | Occasional design | Marketing | Low | Medium | Downgrade |
Choose the application to keep based on:
- Adoption and active usage
- Required integrations
- Security and compliance
- Data portability
- Training cost
- Workflow disruption
- Total cost at current and expected headcount
- Contract flexibility
Do not consolidate only because two tools have similar names. Migration work, switching costs and lost productivity can exceed the subscription savings.
6. Downgrade Plans Before Cancelling Users
A license can be used and still cost more than necessary.
Check whether each user needs:
- Premium rather than standard functionality
- An administrator role
- Advanced reporting
- Higher storage limits
- Additional automation
- Extra environments
- High-volume API access
- Enterprise support
- A dedicated workspace
A useful decision rule is:
Keep the application if the business value is clear, but match each user and team to the lowest plan that supports their actual work.
Review plan-level usage before renewal. A company may have strong overall adoption while still paying for premium features that only a small number of employees use.
7. Review SaaS Contracts Before the Renewal Deadline
A renewal is too late to begin analyzing usage. Start at least 90 days before renewal, or earlier if the contract has a long cancellation notice period.
Ask the vendor about:
- Reducing seat counts
- Removing unused modules
- Moving users to lower tiers
- True-down rights during the contract
- Monthly or quarterly billing
- A shorter commitment
- A price cap
- Credit for unused seats
- Rollover rights
- Flexible ramp-up and ramp-down terms
- Renewal notice requirements
- Data export and termination assistance
- Migration support
- Volume discounts based on actual demand
The FinOps Foundation identifies contract terms, renewal accountability, exit flexibility, true-down pricing and automated reclamation as parts of SaaS cost management.
Calculate Your Negotiation Position
Before speaking with a vendor, prepare:
- Current annual contract value
- Number of purchased seats
- Number of active users
- Number of inactive users
- Expected headcount change
- Features actually used
- Comparable internal or external alternatives
- Renewal deadline
- Maximum acceptable price
A vendor is more likely to offer useful terms when you can show validated demand instead of simply asking for a discount.
8. Stop New SaaS Waste With an Approval Workflow
Cost reduction will not last if employees can keep purchasing overlapping products without review.
Create a lightweight approval process for new applications. Each request should answer:
- What business problem does the application solve?
- Does an approved application already provide this capability?
- Who will own the application?
- What data will be stored or processed?
- How many users need access?
- What is the expected annual cost?
- When will usage be reviewed?
- What happens to the data if the application is cancelled?
Require extra approval for:
- Applications handling sensitive data
- Multi-year contracts
- Automatic renewals
- High minimum-seat commitments
- Tools with unclear data-export capabilities
- Products that duplicate existing platforms
The FinOps Foundation recommends approval workflows for SaaS procurement and renewals, centralized discovery, cost allocation and alerts for unexpected renewals or spending anomalies.
9. Assign an Accountable Owner to Every Application
Each SaaS application should have three responsibilities:
- Business owner: confirms that the application creates value
- Technical or security owner: manages integrations, access and risk
- Commercial owner: manages contracts, invoices and renewals
One person can hold more than one role in a small company. The roles still need to be assigned.
The business owner should approve:
- New purchases
- Seat increases
- Premium access
- Renewals
- Exceptions to inactivity rules
- Cancellation or migration decisions
Without an owner, a subscription often renews by default because nobody is responsible for making the decision.
10. Measure the Right SaaS Cost Metrics
Track these metrics monthly or quarterly.
Unused-Seat Rate
Unused-seat rate =
Unused paid seats ÷ Total paid seats × 100
SaaS Utilization Rate
SaaS utilization rate =
Active users ÷ Purchased seats × 100
Recoverable Spend
Recoverable spend =
Unused or downgrade-eligible seats × Monthly seat cost × Remaining months
Spend per Active User
Spend per active user =
Total SaaS cost ÷ Active users
Also track:
- Annual savings from reclaimed seats
- Number of duplicate applications
- Spend without an assigned owner
- Renewals reviewed before the notice deadline
- Percentage of applications connected to SSO
- Average time to remove leaver access
- Number of auto-renewals prevented
- Percentage of SaaS spend allocated to a department or cost center
These metrics connect SaaS usage with financial accountability. The FinOps Foundation recommends cost allocation, showback or chargeback, usage analysis and forecasting as part of broader technology spend management.
A Practical 30-Day SaaS Cost Reduction Plan
Days 1 to 5: Find the Spend
- Export the past 12 months of software payments.
- Gather vendor invoices and renewal dates.
- Search corporate cards and employee expenses.
- Import applications from your identity provider.
- Identify the ten largest subscriptions.
Days 6 to 12: Assign Ownership
- Name a business owner for each major application.
- Add contract and cancellation dates.
- Record purchased seats, assigned seats and active users.
- Mark applications with no owner or unclear payment source.
Days 13 to 20: Reclaim Obvious Waste
- Remove former employees.
- Reclaim unassigned seats.
- Review accounts inactive for 90 days.
- Downgrade users who do not need premium features.
- Check for duplicate applications.
Days 21 to 25: Prepare Renewals
- List all renewals within the next 120 days.
- Calculate active demand and expected headcount.
- Contact vendors about lower tiers, seat reductions and flexible terms.
- Escalate contracts with long notice periods.
Days 26 to 30: Add Controls
- Create a SaaS purchase approval form.
- Add renewal reminders.
- Connect priority applications to SSO.
- Define inactivity and exception rules.
- Create a monthly SaaS spend report.
When Should You Use SaaS Management Software?
A spreadsheet may be enough when the company has a small number of applications, centralized purchasing and simple contracts.
Consider a SaaS management, IT asset management or spend management platform when you have:
- Dozens or hundreds of applications
- Multiple corporate card programs
- Frequent employee turnover
- Decentralized department purchasing
- Complex seat and usage models
- Many upcoming renewals
- Limited visibility into shadow IT
- Multiple identity providers
- Difficulty matching invoices to users
Do not buy another platform before defining the process. A tool can discover applications and automate workflows. It cannot decide whether sales, finance or engineering still needs a particular application.
The Most Effective Operating Model
For most companies, the operating model is straightforward:
- Keep one inventory of SaaS, payment and contract data.
- Assign a business owner to every material subscription.
- Review active usage before approving more seats.
- Remove or suspend leaver access automatically where possible.
- Reclaim inactive and unassigned licenses.
- Review overlapping tools before buying another application.
- Start renewal reviews at least 90 days before the deadline.
- Track utilization, savings and unowned spend every month.
The objective is not to eliminate software. It is to make sure that every paid SaaS seat has a current user, a defined business purpose and an accountable owner.