Right-Sizing SaaS: When to Downgrade, Consolidate, or Cancel

Most organisations have usage data sitting in their SaaS management tools, their SSO logs, or their vendor portals. The hard part isn't collecting it — it's turning it into action. Here is a simple decision framework for the three most common right-sizing calls.

When to Downgrade

Downgrade when a subset of your users are on a tier that includes features none of them use. The most common example is a team on an Enterprise plan when they only use features available on Professional. Run a feature utilisation report (available in most major SaaS products under Admin → Analytics) and benchmark against the tier below. If no one is using Enterprise-only features, the conversation with your vendor is straightforward.

When to Consolidate

Consolidate when you have two or more tools solving the same problem across different teams. The consolidation conversation is organisational as much as technical — the team losing their preferred tool will push back. Start by mapping the workflows each tool supports, then identify a single tool that covers 80% of the combined use cases. Manage the migration carefully with a defined cut-over date.

When to Cancel

Cancel when a tool has fewer than 10% of paid seats actively used in the last 60 days and there is no credible plan to increase adoption. Don't let sunk-cost thinking extend a subscription that delivers no value. Give the vendor 30 days' notice and document the decision.

Getting the Data You Need to Decide

Each of these three decisions requires usage data, and the best source depends on the tool. For tools with an admin console, export the last-login report — most platforms show this under Settings → Users or Admin → Reports. For tools connected to SSO, your identity provider logs contain authentication events per application per user. For tools outside SSO, your SaaS management platform's browser discovery data is the most reliable source.

Define "active" consistently before you start pulling data. The most defensible definition is a user who has taken a meaningful action (not just logged in) within the last 60 days. Some vendors provide feature-level engagement data that lets you distinguish between users who logged in to check settings and users who actively completed work in the tool. Use the most granular data available.

Managing Stakeholder Pushback

Right-sizing decisions almost always face resistance from someone. The most common objections are "we might need those seats for growth" (counter: you can add seats when headcount actually grows), "that tool is important even if it's not used much" (counter: if it's important, why isn't it being used?), and "we just renewed and it would be embarrassing to cancel" (counter: the embarrassment cost is lower than the financial cost of another renewal).

The most effective way to manage pushback is to let the data lead the conversation. Present the usage numbers neutrally, invite the stakeholder to explain the discrepancy, and offer a trial period — 60 days for the team to demonstrate active use — before taking action. This approach respects the stakeholder's perspective while creating a clear and fair standard for the tool to meet.

Documenting Your Decisions

Every right-sizing decision should be documented — what the data showed, who made the decision, when it was made, and what the expected saving is. This serves two purposes. First, it creates an audit trail that demonstrates proactive governance if a vendor questions the seat reduction. Second, it provides the basis for tracking realised savings: compare the pre-action cost to the post-action contract and record the delta as confirmed savings.

Over time, this documentation builds an institutional record of your SaaS management programme's financial impact — which is invaluable when making the case for continued investment in the programme, or in the SaaS management tooling that supports it.