A blanket mandate to “cut SaaS spend by X%” treats every dollar of spend as equally cuttable, which it isn’t. The more effective approach distinguishes genuine waste — unused seats, redundant tools, over-provisioned tiers — from spend that’s delivering real value, cutting aggressively in the first category while protecting the second.

Category One: Unused and Underused Seats

Covered in more depth in our companion guidance on seat reclamation, this is usually the lowest-risk, highest-confidence cost reduction category — removing licenses nobody is actually using doesn’t reduce anyone’s genuine capability.

Category Two: Redundant Tools

Where two or more tools serve essentially the same function, consolidating to one eliminates real cost without reducing overall organizational capability, assuming the retained tool adequately covers what the eliminated one provided — covered in more depth in companion guidance on CRM-specific stack consolidation, with the same principles applying to SaaS spend generally.

Category Three: Over-Provisioned Tiers

Teams sometimes sit on a higher pricing tier than their actual usage requires, paying for capability that goes largely unused. Right-sizing to the tier that actually matches genuine need, covered in more depth in our companion guidance on CRM tier selection, recovers cost without functional loss if done carefully based on genuine requirements rather than guesswork.

Category Four: Negotiation and Renewal Terms

Beyond usage-based cuts, renegotiating existing contracts — particularly at renewal, when you have more leverage than mid-contract — can reduce cost for the same capability you’re already using, without touching usage or tier at all.

Where Cost-Cutting Risks Real Capability Loss

Cutting into tools or tiers that are genuinely well-utilized and delivering real value, purely to hit an arbitrary percentage target, risks undermining actual business capability. This is the category worth protecting explicitly during any broader cost-reduction effort, distinguishing it clearly from the genuine-waste categories above.

A Cost-Cutting Priority Framework

Category	Risk to genuine capability	Priority
Unused/underused seats	Very low	Cut first
Redundant tools	Low, if consolidation is handled well	Cut second
Over-provisioned tiers	Low to moderate, verify carefully	Cut third, with verification
Well-utilized, high-value tools	High	Protect, don’t cut by default

How to Communicate a Cost-Cutting Effort Internally

Frame the effort around eliminating genuine waste specifically, not around an arbitrary blanket percentage target — this framing helps affected teams understand that well-utilized, valuable tools aren’t automatically at risk, which reduces the defensive reaction a broad, undifferentiated cost-cutting mandate often produces.

A Realistic Example

An organization facing budget pressure initially considered a flat 15% cut across all SaaS spend, which would have meant reducing capability in several genuinely well-utilized, valuable tools. Instead, running the categorized analysis above first revealed that unused seats, redundant tools, and over-provisioned tiers together already represented more than 15% of total spend — meaning the full target could be hit without touching any genuinely valuable, well-utilized tool at all, once the analysis distinguished waste from value rather than cutting indiscriminately across the board.

Frequently Asked Questions

How long does a thorough SaaS cost-cutting analysis typically take? For an organization with a reasonably well-maintained SaaS inventory already in place, a few days of focused analysis across these categories is often sufficient. Without existing tracking infrastructure, building that foundation first adds meaningful time but pays for itself in both this exercise and ongoing management.

Should cost-cutting targets be set before or after this categorized analysis? After is generally more realistic — setting a target blindly, before understanding how much genuine waste actually exists, risks either an unrealistically ambitious target or leaving genuine savings unclaimed because the target was set too conservatively without full visibility.

Is it ever appropriate to cut into genuinely valuable tools if targets can’t be met otherwise? Sometimes, if budget pressure is severe enough — but this should be a deliberate, informed trade-off decision made with full awareness of the capability cost, not a default first move before exhausting the lower-risk categories first and documenting why they weren’t sufficient alone.

How often should this kind of cost-cutting analysis be run? An annual pass is reasonable for most organizations, ideally timed to align with budget planning cycles, with the ongoing tracking and reclamation habits covered elsewhere handling smaller, more continuous optimization between these larger periodic reviews.

Does this approach work for organizations of any size? The categories apply broadly regardless of size, though smaller organizations with fewer tools may find the analysis quicker and the absolute dollar savings more modest, while larger organizations with extensive SaaS portfolios often find more substantial recoverable waste simply due to greater overall scale and complexity accumulating over a longer period.

Getting Buy-In From Tool Owners Before Cutting

Even within the lower-risk categories, individual tool owners sometimes resist a proposed cut, often because they’re not aware of the specific usage data driving the recommendation. Sharing the actual evidence — the specific unused seats, the specific overlapping tool, the specific tier mismatch — rather than simply announcing a decision, tends to produce far less friction and far more durable buy-in than a cut that lands as an unexplained directive from outside their area.

Sustaining Savings After the Initial Effort

A one-time cost-cutting pass recovers accumulated waste, but without ongoing discipline — the tracking, reclamation, and tier-review habits covered across our broader license management guidance — the same categories of waste tend to re-accumulate gradually over the following year. Treating this analysis as the start of an ongoing practice, not a single project with a defined end, is what keeps the savings genuinely sustained rather than requiring the same large, disruptive effort to repeat annually from scratch.

Next Step

Run the four-category analysis above against your current SaaS portfolio before setting any specific cost-cutting target, so any number you commit to is grounded in what’s actually there rather than an outside guess — understanding how much genuine waste already exists shapes a far more realistic and achievable target than guessing at a percentage upfront.