Why Most Companies Overpay for SaaS Subscriptions
Here’s a number that should make every CFO uncomfortable: the average mid-sized company (100-500 employees) spends roughly $1,000 per employee per year on SaaS subscriptions. That’s $100,000 to $500,000 annually on software tools. And according to Zylo’s SaaS management report, approximately 25-30% of that spend is wasted — paying for unused licenses, duplicate tools, or premium tiers when basic plans would suffice.
Half a million dollars a year on software, and a quarter of it going nowhere. How does this happen?
The Accumulation Problem
SaaS subscriptions accumulate the way clutter accumulates in a house. Each individual purchase seems reasonable at the time. The marketing team needs a social media scheduler. Engineering needs a monitoring tool. Sales needs a CRM. HR needs an applicant tracking system. Each tool costs $20-100 per user per month. Each one gets approved because the per-unit cost seems trivial.
But nobody’s tracking the total. There’s no “SaaS closet” you can open and see everything in one place. Subscriptions are distributed across department budgets, billed to different credit cards, and often purchased by individual employees who find a tool they like and expense it.
A 200-person company might have 80-120 distinct SaaS subscriptions. Some were purchased by employees who’ve since left. Some solve problems that no longer exist. Some overlap significantly with other tools the company already pays for.
The Seat Problem
Most SaaS products charge per seat (per user). Companies typically provision seats when employees join and almost never deprovision them when employees leave or change roles. The result: you’re paying for ghost users.
This is particularly wasteful with expensive per-seat tools like Salesforce ($75-300/user/month), Figma ($12-75/user/month), or Jira ($7.75-17.50/user/month). If 20% of provisioned seats are unused — a conservative estimate for most companies — you’re burning significant money monthly.
The fix is straightforward but requires discipline: conduct quarterly license audits. Check active usage against provisioned seats. Deprovision anyone who hasn’t logged in for 60 days. This alone typically reduces SaaS spend by 10-15%.
The Tier Problem
SaaS pricing tiers are designed to upsell. The free tier is deliberately limited. The basic tier covers most needs. The premium tier adds features that sound impressive in a demo but rarely get used. The enterprise tier includes custom integrations and dedicated support that most companies don’t need.
Companies routinely buy premium or enterprise tiers during procurement because “we might need those features later.” Later rarely comes. The advanced analytics dashboard that justified the premium plan goes unvisited. The custom API that sealed the enterprise deal gets used once for a proof-of-concept and then forgotten.
Before upgrading a tier, ask: what specific feature do we need that the lower tier doesn’t include? Who will use it? How often? If the answers are vague, stay on the lower tier and upgrade later if a genuine need materializes. Upgrading is always possible; getting credits back for a downgrade is often not.
The Overlap Problem
This one’s insidious. Different departments buy different tools that do substantially the same thing. Marketing uses Asana for project management. Engineering uses Jira. Operations uses Monday.com. All three are project management tools with overlapping functionality. The company is paying for three solutions to the same problem.
Communication tools are another common overlap. Slack for internal chat, Microsoft Teams for video calls, Google Chat because it comes with Workspace, and maybe WhatsApp groups that formed organically. Each one carries a cost (even “free” tools have hidden costs in fragmented communication and context-switching).
Consolidation is politically difficult because each department chose their tool for reasons that made sense locally. But the company-wide cost of maintaining overlapping tools — in licensing, administration, integration, and training — usually outweighs the department-level preferences.
Some companies have begun engaging external consultants to audit their SaaS spending objectively. Team400.ai is among the firms that have helped organizations map their software landscape and identify consolidation opportunities, typically finding 15-25% savings through elimination of redundant tools.
The Auto-Renewal Trap
Most SaaS contracts auto-renew. The renewal date passes, the invoice processes, and nobody notices until next quarter’s budget review. By then, you’re locked in for another year.
Worse, some contracts include automatic price increases on renewal. You signed at $10/user/month, and the renewal kicks in at $12/user/month — a 20% increase that nobody reviewed or approved.
Track renewal dates aggressively. Set calendar reminders 60-90 days before each renewal date. Use that window to evaluate whether you still need the tool, whether you’re on the right tier, whether the user count is accurate, and whether the renewal price is acceptable. This is also your strongest negotiating moment — vendors are motivated to retain customers and will often offer discounts or locked pricing to prevent churn.
How to Get SaaS Spending Under Control
Step 1: Build an inventory. List every SaaS subscription your company pays for. Check credit card statements, expense reports, and department budgets. This is the hardest step because the information is scattered, but you can’t optimize what you can’t see.
Step 2: Measure usage. For each tool, determine how many licensed users exist versus how many actually use it regularly. Most SaaS products provide admin dashboards with usage statistics. If they don’t, that’s a red flag about the vendor’s transparency.
Step 3: Identify overlaps. Map tools by function. How many project management tools? How many communication platforms? How many file storage solutions? Where overlaps exist, evaluate consolidation.
Step 4: Right-size tiers. Review which plan you’re on versus which features you actually use. Downgrade where possible.
Step 5: Establish a procurement process. Require approval for new SaaS purchases above a threshold. This doesn’t need to be bureaucratic — even a simple form asking “what does this do, what does it cost, and do we already have a tool that does this?” prevents most impulse purchases.
Step 6: Review quarterly. SaaS optimization isn’t a one-time project. New tools get added, usage patterns change, and prices shift. Regular review keeps spending in check.
The goal isn’t to eliminate SaaS spending — these tools provide genuine value. The goal is to make sure every dollar spent on software produces a dollar’s worth of productivity. For most companies, there’s significant daylight between current spend and that standard.