The accumulation of SaaS subscriptions across small and mid-sized businesses has been a steady problem for several years. The combination of the easy free-tier-to-paid conversion pathway, the proliferation of specialist tools across every function, and the lack of disciplined procurement at smaller scale has produced tool stacks that are larger, more expensive, and more fragmented than they need to be. The May 2026 picture in most small businesses is ripe for a proper audit. Here is a practical guide to running one.

The starting position.

The typical small business in 2026 is running between thirty and seventy SaaS subscriptions across the various business functions. The annual SaaS spend at a thirty-employee company easily reaches into the low six figures when all the per-seat costs are added up. The mid-size business with one hundred to three hundred employees can easily be spending into the high six figures.

The honest position for most businesses is that:

• Some subscriptions are not being used.
• Some subscriptions overlap with other subscriptions.
• Some subscriptions are at the wrong tier — either paying for features that are not used or struggling under feature limitations of a lower tier.
• Some subscriptions could be consolidated into a broader platform that is already being paid for.

The audit framework.

The audit should be structured rather than ad hoc. The framework I recommend:

Inventory. The first step is a complete inventory of every SaaS subscription. The inventory includes the vendor, the contract terms, the renewal date, the seat count, the actual user count (which is usually lower than the seat count), the annual cost, the business function the tool serves, and the criticality.

The inventory should be built from multiple sources:

• The finance team’s spending records, which capture the paid subscriptions.
• The IT team’s identity-provider data, which captures the SaaS-with-SSO subscriptions.
• The employee survey, which captures the shadow IT and the tools paid through personal cards.
• The discovery tools (the SaaS management platforms) if any are in use.

The combined inventory is typically larger than any single source. The shadow IT element is usually the most significant under-counted category.

Usage analysis. The next step is to assess actual usage of each tool. The usage data comes from:

• The vendor’s admin dashboards where available.
• The identity provider’s sign-in data.
• The integration with productivity tools (e.g., calendar, email) where relevant.
• The user survey for tools that don’t have other usage data.

The typical finding is that 15-30% of paid seats are unused or barely used. The seats that have not been used in 90 days are typically the strongest candidates for removal.

Overlap analysis. The next step is to identify overlapping tools. The common overlaps include:

• Multiple project management tools (often Asana, Monday, ClickUp, and Trello in various combinations).
• Multiple communication tools (Slack, Teams, Discord, Workplace).
• Multiple file storage tools (Google Drive, Dropbox, Box, OneDrive).
• Multiple meeting tools (Zoom, Google Meet, Teams).
• Multiple CRM tools, often a primary CRM plus several specialist tools that duplicate features.
• Multiple analytics tools.
• Multiple ATS or HR tools.

The overlap analysis should identify where the consolidation is technically feasible and where the political or operational resistance is too high.

Tier analysis. The next step is to assess whether each subscription is at the right tier. The common issues:

• Paying for the highest tier when the team only uses features from a lower tier.
• Paying for a lower tier and struggling with feature limitations that would be solved at a higher tier.
• Paying per-seat for features that should be flat-rate, or vice versa.

The tier analysis often produces immediate savings without any change in tool selection.

Contract analysis. The next step is to assess the contract terms. The common issues:

• Multi-year contracts at unfavourable rates compared to current market.
• Auto-renewal clauses that have not been actively managed.
• Bundle discounts available that have not been negotiated.
• Volume discounts available at the actual user count that have not been pursued.

The contract analysis can produce significant savings on the next renewal cycle.

The consolidation decisions.

The audit findings inform the consolidation decisions. The framework for making these decisions:

The criticality assessment. The tools that are mission-critical (e.g., the primary CRM, the email system, the accounting system) should be conservative with consolidation decisions. The cost of switching a mission-critical tool can outweigh the consolidation savings.

The user adoption risk. The tools that have strong user adoption should be conservative with consolidation decisions. The cost of forcing users from a tool they like to a tool they don’t can outweigh the consolidation savings.

The opportunity cost. The consolidation decisions should consider the opportunity cost of the time required for migration. A consolidation that saves $20,000 per year but requires 500 hours of staff time may not be worth the trade-off in the short term.

The strategic direction. The consolidation decisions should align with the broader strategic direction. The tool decisions should support where the business is going, not where it has been.

The typical consolidations.

The consolidations that are typically possible:

Project management. The consolidation to one primary project management tool is usually feasible and typically saves meaningful money. The “right tool” depends on the team mix but the savings from running one tool rather than three are real.

Communication. The consolidation of internal communication to one platform (typically Slack or Teams) is usually feasible. The historical multi-platform environment is often a legacy of acquisitions or departmental preferences rather than a real operational need.

File storage. The consolidation to one primary file storage platform is usually feasible if it can be combined with the productivity suite (Google Workspace + Drive, or Microsoft 365 + OneDrive).

Meeting tools. The consolidation to one primary meeting tool is usually feasible. The exception is when the customer-facing meetings have specific tool requirements.

Productivity suite. The consolidation to either Google Workspace or Microsoft 365 (rather than running both) is usually possible.

Identity and access. The consolidation to one identity provider (typically Okta, Microsoft Entra ID, or Google Workspace’s identity service) is usually feasible and typically improves security and reduces administrative burden.

The consolidations that typically don’t work.

Some consolidations look attractive in theory but don’t work well in practice:

The “do everything in one tool” approach for very different functions. The marketing automation, the CRM, the project management, and the accounting are different domains with different requirements. The single tool that claims to do all of them well is rarely as good as the specialised tools.

The forced consolidation of tools that serve different audiences. The customer-facing tool and the internal-facing tool can rarely be the same tool. The attempt to make a single tool work for both audiences typically produces a tool that works for neither.

The consolidation that overrides the team’s strong preference. The consolidation that the team resists usually fails through poor adoption regardless of the technical merits.

The audit cadence.

The SaaS audit is not a one-time exercise. The audit should run on a regular cadence — typically annually with smaller quarterly check-ins. The audit cadence should be built into the procurement and finance processes.

The renewal management is the most important ongoing activity. The renewal dates should be tracked. The renewal negotiations should happen with sufficient lead time. The auto-renewal clauses should be actively managed rather than passively accepted.

The realistic savings.

The realistic savings from a disciplined SaaS audit are typically in the 15-30% range of total SaaS spend in the first audit. The savings come from removing unused seats, eliminating overlaps, optimising tiers, and renegotiating contracts.

The ongoing savings from disciplined SaaS management are typically in the 5-15% range annually compared to undisciplined management. The compound effect over multiple years is meaningful.

The audit work pays back quickly. A focused SaaS audit at a mid-sized business typically takes one to two weeks of staff time and produces savings that exceed the staff time cost in the first month. The ongoing management requires a few hours per month and continues to produce returns.

The SaaS sprawl problem is solvable. The discipline is mostly about process rather than about technology. The businesses that run a disciplined SaaS audit and ongoing management process operate at meaningfully lower cost than the businesses that allow SaaS sprawl to continue unchecked. The May 2026 environment is a good time to start if you haven’t already.