How to Audit Your SaaS Stack in 60 Minutes — A Step-by-Step Framework

Your company is probably paying for software it doesn't use. According to a 2025 study by Zylo, the average mid-size company wastes 29% of its SaaS budget on underutilized or completely abandoned subscriptions. For a team spending $50,000 per year on software, that's $14,500 going nowhere.

The fix isn't complicated. It's a structured audit that takes about 60 minutes — less time than most team meetings — and can save thousands annually while actually improving how your team works. This guide walks you through the process step by step, with frameworks you can reuse every quarter.

Why Most Companies Never Audit Their Software Stack

The reason is simple: nobody owns it. Sales buys their own CRM. Marketing chooses their own email platform. Engineering picks their own project tracker. Finance approves each purchase individually but never sees the full picture. The result is a stack that grows organically, accumulates redundancies, and bleeds money in overlapping subscriptions that nobody notices because no single person has visibility across all of them.

The second reason is psychological. Canceling software feels risky. What if we need itlater? What if that one team member who uses it gets upset? What if we lose the data? These fears keep zombie subscriptions alive for months or years after their last meaningful use.

A structured audit eliminates both problems. It creates visibility and it replaces emotional decisions with data-driven ones.

Pre-Audit:GatherYour Data (10 Minutes)

Before you start evaluating anything, collect three pieces of information:

1. The Subscription Inventory

Pull every recurring software charge from the last 90 days. Sources to check:

• Company credit card statements (all cards, all departments)
• Bank account recurring debits
• Expense reports with software receipts
• IT department's license management tool (if you have one)
• Individual team member expense submissions

Create a spreadsheet with columns: Tool Name, Monthly Cost, Annual Cost, Category, Owner (who manages it), Users (how many), Contract End Date.

2. The Login Audit

For each tool, check the admin panel for active users and last-login dates. Most SaaS platforms show this in Settings → Users or Team Management. You're looking for accounts that haven't been accessed in 30+ days.

3. The Integration Map

List which tools connect to which. Check yourZapier/Makeaccount, review API integrations, and ask team leads which tools feed data to other tools. This prevents you from accidentally canceling something that's quietly powering an important workflow.

Phase 1: The Elimination Round (15 Minutes)

With your data collected, run every tool through these three filters. Any tool that hits a filter gets flagged for immediate action.

Filter 1: TheGhostTest

Question:Has anyone logged into this tool in the last 30 days?

If no → flag for cancellation. If the answer is "I think so" or "maybe someone in [department]" → that's a no.

Exception: Tools with annual billing cycles that are only used seasonally (tax software, annual planning tools). Check the last 12 months instead of 30 days.

Filter 2: The Overlap Test

Question:Do we have two or more tools that do the same primary job?

Common overlaps we see repeatedly:

• Slack + Microsoft Teams (two communication platforms)
• Asana + Monday + Trello (multiple project managers)
• Mailchimp + HubSpot email (duplicate email marketing)
• Google Workspace + Microsoft 365 (parallel office suites)
• Zoom + Google Meet + Teams calls (three video tools)

When you find overlap, keep the tool with more active users and deeper integrations. Migrate the stragglers within 30 days.

Filter 3: The Tier Test

Question:Are we paying for a tier we've outgrown — or undergrown?

Two scenarios to catch:

• Over-provisioned:You're on a 50-user Enterprise plan but only 12 people use it. Downgrade.
• Under-provisioned:You're on a free plan and spending 10 hours/week on workarounds. Upgrade — the paid plan is cheaper than the lost time.

Phase 2: The Value Assessment (20 Minutes)

For every tool that survived the elimination round, score it on three dimensions:

Dimension 1: Usage Depth (1-5)

• 1 = Only basic features used (could be replaced by a spreadsheet)
• 3 = Core features used regularly, some advanced features explored
• 5 = Deep usage including automations, integrations, custom configurations

Dimension 2: Business Impact (1-5)

• 1 = Nice to have, business runs fine without it
• 3 = Important for efficiency, but workarounds exist
• 5 = Mission-critical, business stops if it goes down

Dimension 3: Cost Efficiency (1-5)

• 1 = Expensive relative to usage and alternatives
• 3 = Fairly priced for what we use
• 5 = Excellent value, would be hard to replicate for less

Total Score = Usage Depth + Business Impact + Cost Efficiency

Tools scoring 12-15: Keep as-is. These are your stack's pillars.

Tools scoring 8-11: Review — can you negotiate a better rate or downgrade the plan?

Tools scoring 3-7: Seriously evaluate whether this tool earns its place. Consider alternatives or elimination.

Phase 3: The Optimization Pass (15 Minutes)

Now that you know what to keep, what to cut, and what to review, take three optimization actions:

Action 1: Negotiate Renewals

For your top-scoring tools approaching renewal, contact the vendor 45-60 days before the contract ends. Three leverage points:

• Annual pre-payment (typically 15-25% discount vs. monthly)
• Multi-year commitment (additional 10-15% on top of annual discount)
• Competitive alternatives (mention you're evaluating other options — even if you aren't)

Action 2: Consolidate Vendors

If you're using HubSpot CRM and a separate email marketing tool, check if HubSpot's built-in email covers your needs. Same for project management suites that include time tracking, or communication platforms that include video calling.

Consolidation doesn't always mean fewer features. Often, using one vendor's integrated suite works better than stitching together best-of-breed tools, because the integration is native rather than through a third-party connector.

Action 3: Set Review Triggers

Don't wait for the next annual audit. Set calendar reminders for:

• 30 days before each annual renewal (negotiation window)
• When team size changes by ±20% (plan tier review)
• When a tool hasn't been used in 14 consecutive days (ghost alert)
• Quarterly 15-minute check: any new subscriptions added? Any tools deprecated?

The Audit Output Template

After your 60-minute audit, you should have a clear one-page summary with four sections:

1. Cancel immediately:Ghost tools, redundant subscriptions (savings: $X/month)
2. Downgrade:Over-provisioned plans (savings: $X/month)
3. Negotiate:Top tools approaching renewal (target savings: $X/month)
4. Upgrade:Under-provisioned tools where the paid tier ROI is clear

Share this summary with your team leads and finance. Make the cancellations within 48 hours — delay is where good intentions go to die.

What Companies Typically Find

Based on the audits we've observed across hundreds of teams, here are the most common findings:

• 3-5 ghost subscriptionsper company that nobody uses
• 2-3 overlapping toolsthat can be consolidated
• 1-2 over-provisioned plansthat can be downgraded
• 15-30% total savingsachievable without losing any functionality
• 1-2 tools that should be upgradedbecause the free/basic tier is creating hidden costs (see our guide on the hidden cost of free software)

The audit itself takes an hour. The savings compound every month. Run it quarterly, and your software stack stays lean, effective, and aligned with how your team actually works — not how it worked eighteen months ago when someone signed up for a free trial and forgot to cancel.

Real-World Case Study: How a 47-Person SaaS Company Saved $78,000 in One Audit

Meridian Analytics, a B2B SaaS company based in Austin, ran its first formal audit in early 2025 after noticing its software budget had crept from $12,000/month to $19,400/month over 18 months with no corresponding growth in output. The ops team spent one morning with the 60-minute framework and surfaced findings that paid for themselves within 30 days.

The Ghost Subscriptions: Immediate Cancellations

• Intercom ($890/month):The team had migrated to HubSpot Service Hub 11 months prior. Intercom was still billed on auto-renewal, used by zero active team members, but nobody had flagged it because the charge lived on the CTO personal company card.
• Figma Organization Plan ($480/month):The design team had shrunk from 6 to 2 people. They were on a 25-seat Organization plan. Two Professional seats at $15/seat would have cost $30/month. Annual savings from right-sizing alone: $5,400.
• Loom Business ($420/month):Redundant with the Notion built-in video feature, which the company already paid for. Only 3 people had used Loom in the previous 60 days.

The Downgrades and Right-Sizing

• Salesforce Enterprise to Professional:The sales team used fewer than 40% of Enterprise features. The downgrade reduced the bill from $7,200/month to $3,600/month with no functionality loss for their actual workflow.
• Slack upgrade from Pro to Business+:Actually a necessary upgrade in disguise. The team discovered 900-day message history gaps creating compliance issues. Business+ resolved this at $7.25 per user per month and eliminated costly workarounds.

The Outcome

Total monthly savings: $6,500. Annualized: $78,000. The entire audit was completed in 54 minutes by two people. They now run a 20-minute version quarterly and set Slack reminders 45 days before every annual renewal to renegotiate. The key lesson: the biggest savings came not from obscure tools but from the most expensive ones — the enterprise licenses auto-renewed without review because nobody wanted to risk disruption.

The 7 Most Common SaaS Audit Mistakes

These are the failure modes that consistently cause teams to either miss savings or break workflows during the cleanup process.

Mistake 1: Auditing Without an Integration Map

The most expensive audit mistake is canceling a tool that quietly powers something important. One team canceled their Airtable subscription without realizing it was the backend for their client-facing status portal. The portal broke immediately, and rebuilding the integration cost more than two years of Airtable fees. Before canceling anything, check Zapier, Make, n8n, and any native integrations. Ask engineering whether any tool connects to external systems via API. Document the integration map before touching anything.

Mistake 2: Treating Usage Data as Binary

Labeling a tool as used simply because someone logs in is a costly error. One project manager logging in once a week does not justify a $1,200/month Business+ plan for 40 seats. Look at who uses a tool and how deeply, not just whether a login occurred. Most enterprise SaaS platforms provide feature utilization reports in their admin panel. A tool used at 10% of its capability is a candidate for downgrade or replacement with a cheaper alternative covering only the features actually used.

Mistake 3: Not Accounting for Data Portability

When you cancel a tool, what happens to the data? Platforms like Notion, Coda, and Airtable make export easy. Others — certain CRMs and legacy accounting tools — make it painful or charge for bulk exports. For any tool being canceled, run the data export before the subscription ends. Store archives in a shared folder with clear naming. Retention should match your legal requirements — typically 7 years for financial records in most jurisdictions.

Mistake 4: Canceling During Peak Periods

Canceling project management or communication tools mid-quarter disrupts active work. The right time for major stack changes is at the end of a sprint or quarter, when in-flight projects have natural pause points. Separate findings into immediate actions (ghost tools with zero users) and scheduled actions (live tools needing migration). Execute ghost cancellations the same week. Schedule live tool consolidations for the next quarter boundary.

Mistake 5: Skipping the Negotiation Step

Most teams jump straight from evaluating a tool as too expensive to canceling it without attempting negotiation. SaaS companies typically offer 20 to 40% discounts to retain customers who are genuinely evaluating alternatives. The leverage points are: approaching renewal time 30 to 60 days out, having a credible alternative, agreeing to annual pre-pay, and increasing seat count if in a growth phase. A realistic expectation is 15 to 30% off list price for tools over $500/month when negotiating directly with the account team.

Mistake 6: Auditing Once and Forgetting

A one-time audit captures a snapshot, but SaaS stacks drift. New tools are added, team members leave, usage patterns change, and within six months you are paying for software nobody uses again. Implement a quarterly 20-minute check: new subscriptions added this quarter? Any tools with zero logins? Any renewals in the next 60 days? This prevents the annual cleanup from becoming a 6-hour project every year.

Mistake 7: Making the Decision Alone

Finance sees the cost but does not know whether a tool is business-critical. Ops knows the workflows but not the budget impact. After collecting audit data, send a one-page summary to team leads with a 72-hour comment window before making changes. This surfaces edge cases without turning the audit into an endless committee exercise.

SaaS Category Overlap: Consolidation Reference Table

Identifying where you pay for two or more tools that do the same job is one of the most valuable audit outputs. The table below shows the most common overlapping categories and the consolidated alternatives teams migrate to most often.

Metrics to Track After Your Audit

Running the audit is step one. These metrics tell you whether your stack is staying healthy or drifting back toward bloat. Track them quarterly and share with your finance lead.

• Software spend per employee:Total monthly SaaS cost divided by headcount. Healthy range for most companies is $200 to $500 per person per month. Over $700 suggests significant bloat or over-provisioned enterprise tooling.
• Average seat utilization rate:Percentage of licensed seats with a login in the last 30 days. Target 80% or higher for paid tools. Below 60% is a downgrade or cancellation signal.
• Tool-to-person ratio:Number of active SaaS tools divided by headcount. Well-run companies typically run 3 to 6 tools per person. Over 8 indicates stack sprawl that needs attention.
• Redundancy count:Number of categories where you have two or more overlapping subscriptions. Target: zero. One tool per job, fully utilized.
• Unreviewed renewals in next 90 days:Target zero subscriptions renewing in 90 days that have not been reviewed within the past 30 days.
• Zombie subscription cost:Total monthly cost of tools with zero active users. Target: $0. Even $50/month in zombie subscriptions is a process failure worth fixing immediately.

Frequently Asked Questions

How often should I run a full SaaS audit?

For companies spending over $10,000/month on software, a full audit should happen annually with a lighter 20-minute check every quarter. For smaller teams under 20 people, a quarterly 30-minute review is usually sufficient. The goal is to catch ghost subscriptions before they survive a second annual renewal. That is when they become truly invisible, because the renewal date gets normalized into the budget without anyone questioning it.

What is the best tool for tracking SaaS subscriptions automatically?

Several dedicated SaaS management platforms exist specifically for this problem:Zylo(enterprise, deep spend analytics),Torii(mid-market, strong automated discovery),BetterCloud(security-focused, good for compliance-heavy industries), andCledara(excellent for smaller teams, handles procurement workflow too). For teams spending under $5,000/month on SaaS, a well-maintained spreadsheet combined with a dedicated business credit card for software purchases is usually sufficient and free. The ROI of dedicated tooling becomes clear at $10,000 or more per month in SaaS spend, where automation saves more than the platform costs.

Can I actually negotiate SaaS pricing, or is it fixed?

Almost all enterprise SaaS pricing is negotiable, and a surprising portion of SMB pricing is too. The highest-leverage moment is 30 to 60 days before your renewal date, when the vendor account team is actively working to retain you and has budget for concessions. State your situation plainly: you are reviewing your software stack and evaluating alternatives at a lower price point, and you would prefer to stay if the pricing reflects your current usage. This approach reliably yields 15 to 30% discounts for tools over $500/month, and sometimes includes free seat additions or feature unlocks not previously available at your tier.

What if a team member resists canceling a tool they use?

Usage data is your neutral arbitrator. If a tool shows 2 active users out of 40 licensed seats, the question is not whether those two users like it but whether the cost per active user is justified. A conversation usually reveals one of three resolutions: the tool can be replaced by something the team already has; a smaller plan achieves the same result at a fraction of the cost; or the use is genuinely critical and the cost is justified. The goal is never to remove tools people need but to pay the right price for what gets actively used.

How do I prevent subscription creep from returning after the audit?

The single most effective control is a lightweight software purchase approval process. A dedicated Slack channel where anyone proposing a new software purchase posts the tool name, cost, and use case, and gets a thumbs-up from the ops or finance lead, prevents most uncontrolled additions. Pair this with a quarterly 20-minute review of new subscriptions added since the last check, and the annual audit becomes a confirmation exercise rather than an excavation. The audit solves the existing problem; the approval process prevents it from returning.

What to Do Next

If you have not run a structured audit before, the best time to start is now. Here is the minimal viable starting point:

1. Today, 20 minutes:Pull every recurring software charge from the last 90 days. List them in a spreadsheet with monthly cost and owner name.
2. This week, 30 minutes:For each tool over $100/month, check the admin panel for active users and last-login dates. Flag anything under 50% seat utilization.
3. This week, 10 minutes:Identify any categories where you have two or more tools. Mark the redundant ones for consolidation review.
4. Next 30 days:Cancel ghost tools, initiate negotiation conversations for your top 5 tools by spend, and set renewal calendar alerts for everything else.
5. Ongoing:Set a quarterly 20-minute calendar block for a stack health check. Assign a registry owner. Run this process until a lean stack is the default, not the exception.

The companies that stay lean do not do bigger audits. They do more frequent, smaller ones. The goal is to make software discipline a continuous habit rather than an emergency cleanup that happens once every two years when someone finally notices the budget has quietly doubled.

Related Comparisons

• Later vs Gather— Detailed comparison.
• Later vs Zapier— Detailed comparison.
• Later vs Make— Detailed comparison.