How to Run a SaaS Stack Audit: A Step-by-Step Guide

Most companies discover the true size of their SaaS footprint only when something goes wrong — a data breach, an unexpected renewal charge, or an offboarding process that reveals a dozen tools no one remembered purchasing. By that point, the cost of poor visibility is already paid.

A SaaS stack audit done proactively, on a quarterly or semi-annual basis, gives ops and finance teams the visibility needed to make intentional decisions about what to keep, consolidate, or cancel. This guide walks through the process end to end.

Step 1: Build a Complete Tool Inventory

You cannot audit what you cannot see. The first step is compiling a full list of every SaaS tool in use across the organization. This is harder than it sounds.

Start with four sources:

Finance and accounts payable records. Pull every software vendor payment from the past 12 months. Include annual subscriptions, monthly charges, and one-time purchases. Your credit card reconciliation and AP system are the most reliable starting points.

SSO and identity provider logs. If you use Okta, Azure AD, or Google Workspace, pull a list of connected applications. This will surface tools that have been authorized through SSO even if they are not on any official list.

Browser extension and endpoint management data. Tools like Jamf or Microsoft Intune can surface installed software. This catches desktop applications and browser extensions that do not show up in finance records.

Team surveys. Ask department leads to list every tool their team uses, including free tiers and personal accounts used for work purposes. This is where shadow IT surfaces.

Compile everything into a single inventory spreadsheet with columns for: tool name, vendor, department owner, contract type, renewal date, monthly cost, and number of licensed seats.

Step 2: Categorize by Function

Once you have the full inventory, group tools by business function. Common categories include:

• Communication and collaboration
• Project and task management
• CRM and sales enablement
• Marketing automation
• Data and analytics
• Finance and accounting
• HR and people ops
• Engineering and DevOps
• Security and compliance
• Legal and contracts

Categorizing by function makes the next step — identifying overlap — significantly easier.

Step 3: Identify Redundancy and Overlap

Look across each functional category and flag cases where two or more tools are serving the same purpose. Common examples:

• Multiple project management tools (Asana, Linear, and Monday all active simultaneously)
• Overlapping note-taking and documentation tools (Notion, Confluence, and Google Docs all in use)
• Duplicate CRM or contact management functionality
• Both a paid analytics tool and underutilized Looker or Tableau licenses

For each identified overlap, document: which tool is more widely used, which has better integration coverage, and which is more expensive. This sets up the consolidation decision in step five.

Step 4: Assess Utilization for Each Tool

Usage data is the most important input to any stack audit. For each tool, gather:

• Number of licensed seats vs. number of active users in the past 30 days
• Login frequency (daily, weekly, monthly)
• Core feature adoption — are users engaging with the primary functionality, or only peripheral features?
• Integration activity — are connected integrations active?

Most SaaS vendors expose this data in admin dashboards. For tools that do not, request a usage report from your vendor contact. For tools where you cannot get usage data, treat them as at-risk by default.

A utilization rate below 50% (fewer than half of licensed seats actively used) is a red flag. A rate below 25% is a strong signal to right-size or cancel.

Step 5: Score and Prioritize Each Tool

Now that you have inventory, categorization, overlap mapping, and utilization data, score each tool on four criteria:

Business impact (1-5): Does this tool drive measurable outcomes? Can stakeholders articulate what would break if it went away?

Adoption rate (1-5): What percentage of licensed users are actively using it?

Overlap risk (1-5): Is there another tool in the stack that duplicates this functionality?

Total cost (1-5): Relative to its impact and adoption, is the price appropriate?

Tools with low impact, low adoption, high overlap, and high cost are the obvious candidates for cancellation or consolidation. Tools with high impact, high adoption, low overlap, and appropriate pricing get renewed without question. Most tools fall somewhere in between and require judgment calls.

Step 6: Make Decisions and Document Them

Based on the scoring, assign each tool to one of four outcomes:

Renew as-is. High-impact, high-adoption tools that are priced appropriately.

Renegotiate. Tools that are worth keeping but are over-priced relative to utilization. Reduce seats, negotiate discounts, or switch to a lower tier.

Consolidate. Tools that duplicate functionality of a higher-scoring tool. Migrate users and cancel the redundant contract.

Cancel. Tools with low adoption, low impact, and no clear path to improvement.

Document the rationale for every decision. This creates an audit trail that helps with future renewals and informs what to look for in replacement tools.

Step 7: Build a Renewal Calendar

The audit output should feed a forward-looking renewal calendar. Every tool's renewal date should be visible to the ops or finance team at least 90 days in advance. This provides time to conduct a utilization review, initiate renegotiation conversations, or run a replacement evaluation before auto-renewal locks you in.

A spreadsheet or lightweight tool management platform works. The key is that renewal dates are tracked and owned, not discovered by surprise.

Run Audits on a Cadence, Not as a Reaction

The companies that manage SaaS spend well do not run audits because a CFO noticed a line item. They run them quarterly or semi-annually as a standard operational process. Each audit builds on the last, making the next one faster and more accurate.

When you evaluate new tools during the audit cycle, Trackr can accelerate research by generating a structured 7-dimension report for any tool under consideration — so new additions get the same scrutiny as the existing stack.

Trackr automates SaaS tool research. Submit any tool URL and get a scored 7-dimension report in under 2 minutes. Start free →