Software is now the second-largest operating expense for most knowledge-based businesses, behind payroll. And unlike payroll — where every salary represents a deliberate hiring decision — software spend accumulates through dozens of small decisions made by different people at different times, with no one coordinating the total picture.
The result is predictable: duplicate tools, unused licenses, over-provisioned tiers, forgotten subscriptions, and auto-renewals that slip through without scrutiny. Industry benchmarks consistently show that 25–30% of enterprise SaaS spend is wasted. For a company spending $1 million annually on software, that’s $250,000–$300,000 in recoverable value.
This 90-day framework is how procurement-mature organizations find and recover that money. It’s not theoretical — it’s operational, step by step.
Phase 1 — Days 1–30: Discovery (Build the Complete Inventory)
You cannot optimize what you cannot see. The first phase is entirely about building a complete, accurate picture of your software portfolio.
Step 1: Financial system discovery. Pull every software-related transaction from your accounts payable system for the past 24 months. Filter for SaaS, software, and technology vendor payments. This is your baseline — every tool you’re paying for, at what frequency, and from which budget. Most organizations discover 20–40% more tools than any single person thought they had.
Step 2: Corporate credit card and expense scan. Shadow IT — software purchased on individual credit cards and expensed — is a significant inventory gap in the AP approach. Review 12 months of T&E expense reports for software-related charges. Look for recurring charges to vendors like Notion, Loom, Grammarly, Canva, Zoom (individual accounts alongside the corporate account), and similar productivity tools. These are often duplicate capabilities you’re already paying for through enterprise licenses.
Step 3: SSO/identity provider audit. If you use Okta, Azure AD, or Google Workspace as your identity provider, the apps connected to your SSO system represent a nearly complete catalog of cloud tools your organization actively uses. Pull the app list from your identity provider — it will include tools you’ve never seen in an AP report because some were purchased through free trials that converted to paid, charged to individual cards, or provisioned by IT without AP involvement.
Step 4: Aggregate into a master inventory. Combine all three data sources — AP transactions, expense reports, and SSO catalog — into a single spreadsheet. For each tool, capture: vendor name, product name, annual cost, contract renewal date, number of licenses purchased, primary business owner, and business function. This document becomes your SaaS register — the single source of truth for every software decision going forward.
Phase 2 — Days 31–60: Analysis (Find the Waste)
With the inventory built, Phase 2 identifies specific areas where spend is recoverable. There are five categories of waste to look for systematically.
Category 1: Unused licenses. For every major SaaS tool (any tool costing more than $10,000/year), request a usage report from your vendor portal or through your Customer Success contact. Compare licensed seats against active users (typically defined as users who logged in at least once in the past 30 days). Industry benchmarks suggest 15–25% of licensed seats are inactive in a typical enterprise environment. For Salesforce, Microsoft 365, and similar platforms, even a 15% reduction in licensed seats generates significant annual savings.
Category 2: Redundant tools. Map each tool in your inventory to the business function it serves. Common redundancy patterns:
- Multiple project management tools (Asana AND Monday.com AND Notion AND Jira — all paid for simultaneously across different teams)
- Multiple video conferencing platforms (enterprise Zoom license alongside Teams, sometimes alongside Webex from a legacy contract)
- Multiple e-signature platforms (DocuSign at the enterprise level alongside individual Adobe Acrobat Sign or HelloSign subscriptions)
- Multiple analytics tools (enterprise Tableau or Power BI alongside individual Looker Studio, Mode, or Observable subscriptions)
Redundancy is rarely the result of deliberate decisions — it’s the accumulation of independent choices made by teams who didn’t know what others were using. The fix requires a consolidation decision, which requires stakeholder engagement, which is why Phase 2 analysis needs to feed a stakeholder process rather than unilateral IT action.
Category 3: Over-provisioned tiers. Many organizations are on premium plan tiers for features they don’t use. The most common example: organizations on an enterprise-tier SaaS plan because someone decided they might need a feature — and that feature was never configured or adopted. Audit your top 10 tools for actual feature utilization against your contracted tier. For each tool, ask: what would we lose if we dropped to the tier below? Often the answer is “nothing we actually use.”
Category 4: Auto-renewals that nobody reviewed. Pull every contract from your SaaS register that renewed automatically in the past 12 months. For each, answer: did anyone consciously review this renewal and confirm the tool was still needed at the contracted scale? Most organizations discover 20–30% of their renewals happen without any active review — which means any waste in those contracts is locked in for another year.
Category 5: Individual subscriptions duplicating enterprise capabilities. If you have enterprise Microsoft 365, you have enterprise versions of Word, Excel, PowerPoint, OneDrive, Teams, SharePoint, and Viva (depending on tier). Any individual or team subscriptions to tools that duplicate these capabilities — Box or Dropbox alongside OneDrive, Slack alongside Teams, Google Docs through individual Google accounts — are likely redundant. Same pattern applies to Google Workspace, Salesforce, and other broad-platform enterprise investments.
Phase 3 — Days 61–90: Action (Recover the Money)
Analysis without action is just documentation. Phase 3 converts findings into recovered budget through three specific actions:
Action 1: Immediate license right-sizing. For tools with documented unused licenses and upcoming renewal dates, contact the vendor to right-size your license count at renewal. This is the lowest-friction, highest-value action in the entire framework. Vendors will sometimes push back on mid-contract reductions, but most will accommodate right-sizing at renewal rather than risk losing the account entirely. For tools renewing in 60+ days, start the right-sizing conversation now.
Action 2: Consolidation decisions for redundant tools. For each identified redundancy, make a documented decision: which tool stays, which goes, and by when? The decision process should include the business owners of each tool, IT or security (to evaluate any integration or compliance dependencies), and finance (to validate the savings case). Consolidation decisions without stakeholder buy-in become shelfware — the “eliminated” tool keeps getting used because no one communicated the change or migrated the workflows.
Action 3: Renegotiation of over-priced renewals. For tools renewing in the next 90–180 days where competitive alternatives exist, initiate a renegotiation. The 90-day audit gives you the utilization data and alternative landscape knowledge to negotiate from a position of information rather than urgency. Vendors know you need their product most when you’re inside 30 days of an auto-renewal — give yourself the time advantage.
What Good Looks Like: Building Ongoing SAM Capability
The 90-day audit recovers historical waste. Preventing the waste from accumulating again requires ongoing Software Asset Management (SAM) capability, which doesn’t have to be elaborate:
- A centralized SaaS register maintained monthly with new tool purchases requiring manager and IT approval
- Calendar alerts set for every renewal date 90 days in advance
- Quarterly utilization reviews for tools above $10,000/year
- A defined off-boarding process that includes license deprovisioning when employees leave
Organizations with these four practices in place consistently spend 20–30% less on software than comparable organizations without them — not because they use less software, but because they use it more deliberately.