How Much Is Your SaaS Stack Really Costing You?

Most companies have a reasonable sense of what they pay for their top two or three SaaS tools. What they almost never know is the full saas stack cost across every active subscription, every user tier, every add-on, and the hours spent moving data between tools that do not talk to each other. A 2024 survey by Zylo found that the average company wastes 25% of its SaaS budget on unused licences alone. For a 50-person company spending $120,000 a year on software, that is $30,000 disappearing without producing anything. This post walks through the real arithmetic of modern software spend: how per-user pricing compounds at scale, where businesses consistently overpay, and the practical method to calculate your actual saas stack cost in under 30 minutes.

The Actual Size of the Problem

Gartner estimates that global SaaS spending crossed $230 billion in 2024 and is growing at roughly 18% per year. At the company level, the numbers are just as striking. Torii’s 2023 SaaS Management Benchmark found that the average company uses 130 distinct SaaS applications. Most finance teams are tracking fewer than a third of those.

The gap exists for a structural reason. SaaS procurement is decentralised by design. A marketing manager signs up for a social scheduling tool using a corporate card. An engineer subscribes to a monitoring service during an incident and never cancels it. A sales director buys individual seats for a prospecting database before the company negotiates a volume deal. None of those decisions is unreasonable in isolation. The problem is that nobody adds them up.

When companies do conduct a proper SaaS audit, the discovery phase alone typically uncovers 20 to 40 applications that the IT or finance team had no record of. These are not trivial tools. In many cases they include licenced databases, paid analytics platforms, and communication tools that handle sensitive customer data, all operating outside any formal procurement or security review.

Understanding your saas stack cost is not simply a finance exercise. It is also a security and compliance question. Every untracked application is a potential data leak waiting for a question nobody has thought to ask.

How Per-User Pricing Compounds at Scale

The single biggest driver of unexpected SaaS spend is per-seat pricing applied across multiple tools for the same population of users. Here is a realistic illustration for a 25-person team:

That is $71,400 a year for a 25-person team using nine tools at their listed prices, before any add-ons, premium integrations, or API overage charges. Add a sales intelligence platform at $95 per user for the five people in sales, an analytics tool for the three people in marketing, and a security scanning tool for two developers, and you have added another $22,000.

The scaling effect is non-linear. When the team grows to 50 people, the base cost does not double cleanly. New users often trigger tier upgrades at each vendor, pushing per-seat costs higher across the board. A company that paid $65 per user per month for a CRM at 25 seats may find itself on a plan at $89 per user at 50 seats because the previous tier had a cap.

Where Companies Consistently Overpay

Not all overpayment looks the same. Three categories account for the majority of wasted spend.

CRM tier mismatch

CRM platforms are the single biggest source of overpayment in most mid-market companies. The typical pattern: a company buys an enterprise-tier CRM because a sales consultant recommended it, uses roughly 30% of its features, and pays for capabilities it will never activate. Workflow automation, AI scoring, advanced reporting, and territory management modules are all bundled into high-tier plans. If your sales process involves fewer than five stages and your team does not run complex multi-touch attribution, you are almost certainly over-licensed.

The reverse also happens. Companies on starter-tier CRMs buy third-party tools to compensate for missing features, paying more in aggregate than the mid-tier plan would have cost.

Helpdesk and customer support

Helpdesk tools are priced per agent, which means a company with 10 support agents and 15 occasional responders (managers who sometimes reply to tickets) is often paying full agent licences for people who touch the system once a week. Most platforms distinguish between full agents and light agents or collaborators at different price points. Many companies never configure this distinction.

HR and people operations

HR platforms often charge per employee, including inactive employees who are in the system for compliance records but are not actively using the tool. Combined with the fact that many companies use separate tools for payroll, onboarding, and performance management when a single platform covers all three, this category routinely doubles its necessary cost.

Hidden Costs Beyond Licensing

The per-seat subscription fee is visible on your credit card statement. The costs below are not, but they add up faster.

Integration and middleware

When CRM data does not sync automatically with your billing system, someone exports a spreadsheet and imports it manually. When your helpdesk does not connect to your project tracker, someone copies and pastes ticket details into a task card. These workflows are invisible until you start measuring them. A conservative estimate of 30 minutes per day per person spent on manual data transfer costs a 25-person team over 1,500 person-hours per year. At an average fully-loaded cost of $40 per hour, that is $60,000 in labour spent compensating for tools that should talk to each other automatically.

Companies that do use integration platforms like Zapier or Make to connect tools add another layer of cost: time to build and maintain automations, plus monthly subscription fees that grow with the number of tasks processed.

Duplicate data entry and data quality

When contact records exist independently in a CRM, an email platform, and a helpdesk, the data diverges over time. Someone updates a phone number in the CRM but not in the helpdesk. A churned customer still receives marketing emails because the two systems were never synced. The downstream cost is poor decision-making based on fragmented data, which is difficult to quantify but consistently shows up in reporting that teams do not trust.

Admin and onboarding time

Each additional tool adds administration overhead: user provisioning, access reviews, security settings, vendor negotiations, and the time new employees spend learning systems that partially overlap with tools they already know. IT teams in mid-market companies often report that SaaS sprawl is their single largest source of unplanned work.

How to Calculate Your Real SaaS Stack Cost in 30 Minutes

This is a practical process, not a theoretical one. You need three inputs: a credit card statement, a list of tools from your IT systems or a quick survey of department heads, and 30 minutes.

Step 1: Build the inventory (10 minutes)

Pull the last three months of corporate card and expense statements. Look for recurring charges at any amount: monthly subscriptions are typically constant, annual subscriptions show up as a single large charge. Categorise each charge by tool name. This alone usually reveals six to ten subscriptions that nobody in finance had on record.

Check your SSO provider or identity management tool if you use one. Any application connected via single sign-on is active and in use by someone. Cross-reference the SSO list against the finance list. Items appearing in SSO but not in finance may be on a free tier or billed directly to a department budget.

Step 2: Map to users (10 minutes)

For each tool, note the number of active users. Most SaaS platforms show this in the admin console under user management or billing. Compare active users to licenced users. A gap of more than 20% in any tool is a flag for immediate review.

Mark tools with fewer than 10 active users that are on a per-seat plan. These are candidates for plan downgrades or consolidation.

Step 3: Calculate total cost and overlap (10 minutes)

Sum all subscription costs. Then identify functional overlaps: are you paying for two tools that both do project management, or two tools that both do email marketing? Functional overlap is common in teams that have grown through acquisition or organic expansion where each function chose its own tools independently.

Use the Zoho One savings calculator to model how consolidating multiple point solutions onto a single platform compares in cost. The calculation takes current per-seat costs and maps them against the unified pricing of an integrated suite.

At the end of this process, you should have four numbers: total annual spend, number of redundant tools, estimated admin hours per month, and an estimate of manual data transfer cost. These four numbers form your baseline for a consolidation decision.

What the Number Usually Reveals

Companies doing this exercise for the first time typically discover that their actual saas stack cost is 1.4 to 1.8 times what the finance team believed. The gap comes from three places: shadow IT (tools bought without central approval), underutilised licences that nobody cancelled, and manual labour costs that were never counted as part of software spend.

The most common decision that follows is not a wholesale platform replacement. It is a two-step rationalisation: cancel tools with fewer than five active users, and consolidate two or three overlapping categories onto a single platform. These two moves alone typically recover 20 to 30% of total software spend without any change to core workflows.

For companies running eight or more separate SaaS tools across CRM, marketing, support, HR, accounting, and project management, a consolidated suite is worth a serious cost comparison. Platforms like Zoho One offer the full application set for a flat per-user fee, which eliminates the tier-mismatch problem and the integration overhead in a single move.

The important caveat is that consolidation has its own implementation cost. Moving data, retraining staff, and rebuilding automations takes time and requires careful planning. A rushed migration that saves $20,000 in licences but costs $40,000 in lost productivity is not a win. The right approach is a phased plan that prioritises the highest-cost overlaps first and maintains continuity for critical workflows throughout.

Understanding your real saas stack cost is the first step toward making intentional decisions about software spend. The 30-minute audit described here gives you enough information to identify the highest-value actions: cancelling unused seats, eliminating functional overlaps, and evaluating whether a consolidated platform changes the economics of your stack. Most companies find that the exercise pays for itself in the first quarter.