Already Subscribed to Too Many SaaS Tools? Here Is How We Ran a Full Software Audit

# Already Subscribed to Too Many SaaS Tools? Run a Software Audit --- A Practical Diary

*By Elena Voss, Senior Procurement Analyst*

Day 1: The Wake-Up Call

Today, I opened our finance dashboard to reconcile Q2 cloud spend --- and nearly spilled my coffee. Our SaaS line item totaled $94,231. That's up 37% YoY. Worse, Finance flagged 12 overlapping tools: three project management platforms, four analytics dashboards, and two HRIS connectors nobody remembers provisioning.

I pulled the master SSO log. We have *47* active SaaS subscriptions. Only 28 appear on the official IT asset register. The rest? Ghost licenses --- paid for, rarely used, quietly renewing.

This isn't just budget leakage. It's security risk, compliance friction, and employee fatigue. Time for a full SaaS subscription audit --- no fluff, no vendor spin. Just facts, dates, and decisions.

Day 3: Mapping the Landscape

I started with three data sources:

- Corporate credit card statements (filtered for SaaS keywords: 'cloud', 'app', 'software', 'subscription')

- Okta admin console (active users per app, last login date)

- Contract repository (renewal dates, auto-renew clauses, user caps)

Cross-referencing them revealed stark gaps. For example: 'Flowly' (project management) shows 120 licensed seats but only 17 active users in Okta --- and its G2 rating is 3.8/5, with recurring complaints about API instability. Meanwhile, 'AspirePM' (G2: 4.5/5) has 42 active users on only 30 licenses --- meaning we're overpaying *and* risking license violations.

I built a simple spreadsheet: App Name | Monthly Cost | Licensed Seats | Active Users | Last Login | Renewal Date | G2 Rating | Primary Use Case | Owner (Dept)

So far: 47 rows. 19 marked 'Low Utilization' (<20% seat usage). 7 flagged 'Redundant' (functionally identical to another tool).

Day 7: The Department Deep Dive

I scheduled 30-minute interviews with department leads --- no slides, just two questions: "Which three SaaS tools do you *truly* rely on weekly?" and "What's one tool you pay for but haven't opened in 60 days?"

Marketing admitted they hadn't touched 'VizMetrics' since January --- but Finance still renews it monthly ($2,499). Sales uses 'DealPulse' daily, yet also pays for 'SalesGraph' ($1,850/mo), which hasn't generated a single report since March.

The biggest insight? Ownership is fragmented. No single person owns the 'SaaS stack' --- not IT, not Procurement, not even the CIO. Responsibility defaults to whoever clicked 'Subscribe' on a free trial.

Day 12: Prioritizing & Negotiating

I grouped tools into four buckets:

- Keep: High utilization (>75%), strong G2 rating (>4.2), critical workflow integration (e.g., 'NexusCRM' --- G2: 4.6/5, 92% seat usage)

- Consolidate: Medium utilization, functional overlap (e.g., merging 'DocuVault' and 'SignFlow' into one e-signature solution)

- Cancel: <10% utilization, no recent activity, poor reviews (e.g., 'CloudTidy' --- G2: 2.9/5, zero logins in 90 days)

- Renegotiate: High cost, decent usage, but inflexible contract (e.g., 'DataHive' --- $14,200/yr, but we only use 3 of 12 modules)

For renegotiation targets, I gathered usage reports, competitor pricing (G2 and Capterra benchmarks), and internal stakeholder quotes. 'DataHive' agreed to a 22% discount and module-downsizing after I shared our Okta usage heatmaps.

Day 18: The Vendor Comparison Table

Here's how three overlapping analytics tools stacked up during our audit:

We sunsetted MetricLens (low usage + high cost + weak adoption) and consolidated into DashCore --- saving $2,700/month with higher team satisfaction.

Day 22: Policy & Prevention

The audit delivered $182,350 in verified annual savings --- 14% of our SaaS spend. But the real win is systemic change. We drafted a new policy:

- All new SaaS requires a 30-day 'trial justification form' signed by Procurement, IT Security, *and* the requesting department head

- Quarterly SaaS health reviews (utilization %, renewal alerts, G2 sentiment trends)

- Centralized dashboard showing spend, usage, and contract expiry dates --- visible to all department leads

- 'SaaS Sponsor' role assigned per tool (not 'owner' --- sponsors must validate quarterly usage)

IT is building this in Power BI next sprint. Finance has approved automated alerts for contracts renewing within 60 days.

Final Reflection: Why This Isn't Optional Anymore

Two years ago, I thought SaaS audits were 'nice-to-have'. Now I know: they're infrastructure maintenance --- like patching servers or reviewing access controls. Unchecked SaaS sprawl erodes margins, slows decision-making, and creates silent attack surfaces.

This wasn't about cutting tools. It was about clarity: knowing what we pay for, why we pay for it, and who truly benefits. The 47 subscriptions shrank to 29 --- all purposeful, all measured, all accountable.

If your finance team can't name every SaaS on your books --- or if your Okta 'last login' column reads like a graveyard --- start your audit tomorrow. Not next quarter. Not after the next funding round. Today.

Your budget --- and your engineers' sanity --- will thank you.

*Elena Voss is a Senior Procurement Analyst with 12 years of experience optimizing enterprise SaaS portfolios across fintech, healthcare, and SaaS-native companies. She advises mid-market firms on vendor rationalization, contract intelligence, and usage-based procurement.*