Most companies expect their SaaS budget to grow as they scale. More employees means more seats. More departments means more tools. The surprise is the rate - not 10% growth that mirrors headcount, but 25-40% year-over-year growth even when headcount grew 15%. At some point, someone in finance asks why the software budget is climbing faster than everything else, and the honest answer is: compounding.
The Compound Mechanics
SaaS spending has compounding characteristics that operating expense budgets don't usually exhibit. Understanding the mechanism explains why the number keeps climbing.
New tools add to the stack, not replace it. When a team adopts a new tool, it rarely retires an old one. It adds alongside. The new tool was bought to solve a problem the old tool didn't solve well - but the old tool's renewal is still on autopilot. Over three years, a 10-person team might accumulate 15-25 SaaS subscriptions because each new problem gets a new solution and the old solutions never get evaluated for retirement.
Seat-based pricing scales with headcount automatically. Tools priced per seat increase spending as you hire. This is expected. The non-obvious part: the scaling often happens in pricing tier jumps, not linear increases. A tool at $10/seat/month for teams under 25 suddenly becomes $15/seat/month for teams of 25-100 when you hire person 26. The entire account reprices, not just the new seat.
Vendor cross-selling expands tool scope. Once you're a customer, vendors want to sell you more. Usage limits encourage upgrades. Feature paywalls push you to higher tiers. Ecosystem tools get packaged into bundles. A team that started paying $200/month for a core tool often finds themselves at $600/month two years later for "the plan that includes everything we actually use now."
Annual renewals default to the same or higher prices. Without active renewal management, subscriptions renew at current pricing or with vendor-initiated price increases (often 5-10% annually "to reflect market rates"). Over five years, a tool that started at $500/month is at $650-700/month through accumulated annual increases, even if usage hasn't grown.
The Decentralized Purchasing Problem
SaaS spending is high partly because the purchasing decision is distributed. Engineering can expense developer tools without a procurement process. Marketing buys HubSpot without checking whether sales already has a CRM. A department head signs up for a project management tool that engineering adopted three months ago under a different name.
Zylo's annual SaaS management report consistently finds that the average enterprise has 65% more SaaS applications than IT knows about. The tools that IT doesn't know about are the ones that don't get reviewed for waste.
The structural issue is that SaaS procurement is frictionless by design. A $200/month SaaS tool requires a credit card, not a purchase order. No approval workflow, no vendor security review, no integration assessment. The low barrier to entry that makes SaaS tools easy to adopt is the same barrier that makes the inventory unmanageable.
"Most companies don't have a SaaS spending problem. They have a process problem. The tools are fine - the gap is that nobody owns the renewal conversation until the invoice already landed." -- Dennis Traina, founder of 137Foundry
The Renewal Trap
Annual renewals are the primary mechanism through which SaaS budgets grow without deliberate decision-making.
Here is how the renewal trap works: you're 30 days from the renewal date. You get an invoice or an auto-renewal notification. The person who receives it is in finance, not the tool's daily user. They approve it because canceling would disrupt someone. The decision gets made by inertia.
The 30-day window is too late to negotiate effectively. Most SaaS vendors require 30-60 days notice to cancel or modify a contract. If the renewal notification arrives at day 28, you've already lost the negotiation window.
The tool that looked reasonably priced 12 months ago has accumulated a year of utilization data - some of which you no longer have because the vendor's reporting is 90 days rolling. The opportunity to push back with data is gone.
What Actually Stops the Growth
The tools and practices that actually control SaaS budget growth share a common characteristic: they make spending visible before the renewal event, not after.
SaaS management platforms like BetterCloud, Productiv, and Vendr centralize the inventory, surface utilization data, and flag renewals far enough in advance to act. The investment in a management platform pays back when it prevents even one major tool from auto-renewing at full price on an underutilized seat count.
A renewal calendar with 90-day advance entries. This is the minimum viable process improvement. For every annual subscription, a calendar entry 90 days before renewal gives the tool owner time to review utilization, benchmark pricing, and have a meaningful vendor conversation. Without this, renewals manage themselves.
An assigned tool owner for every subscription. "Who is responsible for this?" is the question that unlocks action. When a tool has no owner, nobody reviews it. When the owner gets the 90-day renewal reminder, the utilization check happens. Most waste reduction is downstream of this single accountability assignment.
Centralized approval for new subscriptions. Not procurement bureaucracy - just a lightweight review. Before a new $100/month tool gets added, someone checks whether an existing tool already covers the use case. The procurement overview on Wikipedia covers the governance frameworks that formal procurement uses; a simplified version of that logic applied to SaaS subscriptions catches most of the overlap.
The combination of these four practices creates a closed loop. New tools enter with accountability. Existing tools get reviewed on a cadence. Renewals get decided rather than defaulted. The initial setup takes a day or two - building the inventory, assigning owners, creating renewal calendar entries, and choosing a management platform or spreadsheet as the starting tool. After that, the process runs on the calendar rather than on a crisis.
The most common implementation mistake is starting with the platform and skipping the process. A SaaS management tool that sits unused because nobody owns the review cadence adds cost without adding value. The process comes first. The tool accelerates a process that is already working.
The Compounding Works Both Directions
The same compounding that creates SaaS budget growth can be reversed. Tools eliminated at renewal stay eliminated. Seat reductions at this year's renewal reduce the base that next year's tier pricing applies to. A vendor negotiation that achieves 15% discount saves 15% every year the subscription renews.
The companies with the lowest SaaS cost per employee aren't usually the ones who went through an aggressive cost-cutting exercise. They're the ones who built a renewal management habit early and let it compound the other direction. Each cycle of the process - discovery, utilization review, renewal management, procurement discipline - reinforces the others. Discovery reveals tools to review. Utilization review informs renewal decisions. Renewal management creates accountability for future purchasing. Procurement discipline slows the rate at which new tools enter the stack.
How to Reduce SaaS Spending Without Disrupting Your Team covers the full systematic approach: audit, utilization review, renewal negotiation, and governance structure. 137Foundry works with companies building this process from scratch and with teams that need to accelerate an existing rationalization effort.
Top comments (0)