If you are a CFO or finance lead at a 100-person company, you are probably spending between $250,000 and $450,000 per year on SaaS subscriptions. That is $2,500 to $4,500 per employee — and according to Flexera State of the Cloud, most organisations underestimate their actual SaaS spend by 20-30%. The number on your books is almost certainly lower than your real exposure.
The question is not whether that number is "right." It is whether you know what you are getting for it, and whether any of it is waste. This article gives you the benchmarks, the breakdown, and a practical framework for auditing your own spend against industry standards.
The Benchmark
SaaS spend per employee varies significantly by industry, growth stage, and technology intensity. But the data points converge around a consistent range for mid-market organisations that you can use as a starting reference.
According to Gartner, the average mid-market company spends $3,200 per employee per year on SaaS applications. The SaaS Management Index places the median slightly higher at $3,500 per employee, with a range of $2,200 to $5,800 depending on industry. These figures include only direct subscription costs — not implementation, integration, or administration overhead.
For a 100-person company, that translates to:
- Conservative estimate: $250,000 per year ($2,500 per employee)
- Median estimate: $350,000 per year ($3,500 per employee)
- High-technology or fast-growth: $450,000 or more ($4,500+ per employee)
Technology companies and financial services firms skew higher because they rely on more specialised tools — development platforms, security tooling, compliance software, and data infrastructure. Professional services and manufacturing firms tend to sit at the lower end, with more spend concentrated in a few core platforms like Microsoft 365 or Google Workspace.
The Okta Businesses at Work report found that the average company now uses 89 SaaS applications, up from 58 just four years ago. That growth has not been matched by proportional increases in value — much of it represents tool overlap, departmental shadow IT, and subscriptions that outlived their usefulness. The question for your finance team is not "are we using too many tools" but "are we getting value from each one?"
These benchmarks are useful as directional guidance, not as targets. An organisation spending $4,500 per employee is not necessarily wasteful — it depends on whether that spend supports business operations productively. An organisation spending $2,000 per employee may be underinvesting in tools that could improve efficiency. The benchmark tells you where to look. The audit tells you what to do.
How SaaS Spend Scales
SaaS spend does not scale linearly with headcount. Smaller organisations spend more per employee because they need the same core infrastructure as larger ones — email, CRM, accounting, project management — but spread the cost across fewer people. Understanding this scaling curve helps you set realistic expectations for your company size.
According to SaaStr, the scaling pattern looks roughly like this:
- 10-50 employees: $4,000-$6,000 per employee. You are buying full-suite tools at startup scale. The per-seat cost is high because you cannot negotiate volume pricing, and you need nearly as many categories of software as a 500-person company. A 20-person company still needs email, CRM, accounting, project management, and HR tools — the same categories a 200-person company uses. The fixed costs are just divided by fewer people.
- 50-200 employees: $3,000-$4,500 per employee. You start to gain some negotiation leverage. Vendors offer mid-market pricing tiers, and annual commit discounts become available. But this is also the stage where departmental purchasing accelerates — new teams spin up their own tools without central oversight, and the finance team loses visibility into what is being purchased and by whom.
- 200-500 employees: $2,500-$3,500 per employee. Economies of scale emerge. Volume discounts become available. Dedicated vendor management roles may exist. But portfolio complexity increases significantly. The SaaS Management Index reports that organisations in this range average 120-180 active SaaS applications, many of which overlap in functionality.
- 500+ employees: $2,000-$3,000 per employee. Enterprise agreements, volume licensing, and dedicated vendor management reduce per-employee costs. But the absolute spend is substantial — a 1,000-person company at $2,500 per employee is spending $2.5 million annually on software subscriptions. And waste percentages remain consistent at 25-30% regardless of company size.
The critical transition happens between 50 and 200 employees. This is when SaaS spend typically shifts from a controllable line item to a sprawling, multi-department budget that no single person fully understands. Departments start making independent purchasing decisions. Credit card subscriptions accumulate without finance oversight. And the gap between what finance knows about and what the organisation actually uses widens with every hire.
According to Gartner, organisations that implement structured SaaS governance during this transition phase spend 20-25% less per employee by the time they reach 200 employees compared to those that wait until spend becomes a visible problem. The earlier you establish visibility, the less waste accumulates.
Where the Money Goes
Not all SaaS spend is equal. Understanding where your budget concentrates helps you prioritise optimisation efforts on the categories with the highest waste potential. You cannot audit everything at once, so start with the categories where the dollars are largest and the waste is most likely.
For a typical 100-person company spending $350,000 annually on SaaS, the allocation breaks down roughly like this:
Productivity and collaboration (25-30%): $87,500 to $105,000. This includes email, calendar, document management, messaging, and video conferencing. Most organisations standardise on one or two platforms here — Microsoft 365 or Google Workspace plus a messaging tool like Slack or Teams. The waste risk is low in the core platforms but high in supplementary tools that overlap with built-in features. A common example: paying for a standalone survey tool, a standalone form builder, and a standalone document signing service when the core productivity suite includes basic versions of all three.
CRM and sales tools (15-20%): $52,500 to $70,000. CRM is often the single most expensive SaaS contract for companies with sales teams. According to Gartner, CRM licence utilisation averages 65% — meaning 35% of seats are either unused or used so infrequently that a lower tier would suffice. This category also includes sales engagement platforms, prospecting tools, and revenue intelligence software, which often duplicate functionality found in the core CRM.
Engineering and development (10-20%): $35,000 to $70,000. For technology companies, this category can be the largest. It includes source control, CI/CD pipelines, monitoring and observability, cloud development environments, and specialised tooling. Engineering teams tend to adopt tools quickly and deprecate them slowly, creating a long tail of low-use subscriptions. A developer who evaluates three monitoring tools and picks one often forgets to cancel the other two. Multiply that pattern across an engineering team of 30, and the orphaned subscriptions add up.
Finance and operations (10-15%): $35,000 to $52,500. Accounting, payroll, expense management, and procurement tools. These tend to be well-justified but often over-seated. Not every employee needs access to the accounting platform, and many finance tools offer viewer-only tiers at significantly lower per-seat costs. Review whether all users are on the right tier for their actual usage pattern.
HR and people (5-10%): $17,500 to $35,000. HRIS, recruiting, learning management, and employee engagement tools. This category has grown significantly as remote and hybrid work drove adoption of new tooling for onboarding, performance management, and team communication. According to the SaaS Management Index, HR SaaS spend increased 18% year over year in 2025, faster than most other categories.
Security and compliance (5-10%): $17,500 to $35,000. Identity management, endpoint protection, email security, and compliance platforms. According to the SaaS Management Index, security tooling is the fastest-growing SaaS category, with spend increasing 22% year over year. This growth is largely justified — security is not the place to cut corners. But even security tools can be over-seated or overlapping, so they deserve the same utilisation review as any other category.
Everything else (10-20%): $35,000 to $70,000. Marketing tools, analytics platforms, design software, project management, and the long tail of departmental purchases. This is where shadow IT lives and where utilisation audits find the most waste. Individual subscriptions may be small — $200 to $500 per month — but they accumulate rapidly across departments.
Hidden Costs Most Teams Miss
The headline subscription price is not the full cost of a SaaS tool. Several categories of hidden cost inflate your actual spend beyond what appears on the invoice. When you calculate your true SaaS cost per employee, these hidden costs can add 30-50% to the sticker price.
Overlapping functionality. According to the Okta Businesses at Work report, the average organisation has 2-3 tools with significant feature overlap in each major category. Two project management tools, three document signing services, two survey platforms. Each individually justified, collectively redundant. The SaaS Management Index estimates that functional overlap accounts for 12-15% of total SaaS waste. The root cause is usually departmental autonomy — marketing chooses one project management tool, engineering chooses another, and neither team has a reason to consolidate because neither pays the full cost.
Orphaned accounts. Employees leave, contractors finish engagements, and their SaaS licences persist. Most organisations take 30-90 days to fully deprovision a departing employee's software access, according to Gartner. During that window, you are paying for unused seats. At scale, this adds 5-8% to your effective SaaS cost. A 100-person company with 15% annual turnover and a 60-day average deprovisioning lag is paying for roughly 7-8 ghost users at any given time across every SaaS application.
Tier creep. Teams start on a basic tier, upgrade to access a single feature, and never evaluate whether the premium tier is still justified. The difference between a $15 per user and $30 per user tier is 100% — and the premium features driving that cost may only be used by 10% of the team. According to SaaStr, 40% of SaaS customers are on a higher tier than their usage warrants. The upgrade was justified when it happened. The question is whether it is still justified 12 months later.
Integration and administration costs. Every SaaS tool requires setup, maintenance, user management, and integration with your existing stack. These labour costs do not appear on the SaaS invoice but can add 15-25% to the total cost of ownership, according to Gartner research on total SaaS TCO. A $500 per month tool that requires 4 hours of IT time per month for administration and integration maintenance has an effective cost that is significantly higher than the invoice amount.
Annual price escalators. Many SaaS contracts include built-in price increases of 5-8% per year. Over a three-year contract, a 7% annual escalator increases your cost by 22.5%. These escalators are often buried in contract terms and applied automatically at renewal. If you are not reading the renewal terms of every contract, you are absorbing these increases passively.
Switching costs. The cost of staying with a tool you should replace includes the ongoing subscription premium over a better-priced alternative, minus the one-time cost of migration. Many teams overestimate switching costs and underestimate the cumulative cost of overpaying for years. A $10,000 annual overpayment on a tool that would cost $5,000 to switch means the migration pays for itself in six months.
How to Audit Your SaaS Spend
If you have never conducted a structured SaaS audit, start with these five steps. The process takes one to two weeks for a 100-person company and typically identifies 15-25% in addressable waste. That is $37,500 to $87,500 in savings potential on a $350,000 annual SaaS budget.
Step 1: Build the inventory. Pull every recurring software charge from three sources: corporate card statements, accounts payable records, and your identity provider (SSO) application list. Cross-reference to catch subscriptions that appear in one source but not others. You will likely discover 10-20 subscriptions that no one on the finance team knew existed. Include contractor and freelancer tools that may be billed to personal cards and reimbursed through expenses.
Step 2: Categorise by owner and function. Assign each subscription to a department owner and a functional category. This creates accountability — someone is now responsible for justifying the spend. Tag each subscription as "core" (essential to operations), "productivity" (enhances efficiency), or "discretionary" (nice to have). The "discretionary" tag does not mean the tool should be cancelled — it means it should be reviewed more frequently.
Step 3: Pull utilisation data. For your top 20 subscriptions by cost, check the vendor admin console for active user counts. Compare assigned seats to active seats (logged in within 30 days). According to Gartner, this step alone reveals an average of 30% unused licences across the portfolio. Document the utilisation rate for each tool and flag any below 70%.
Step 4: Identify quick wins. Look for three categories of immediate savings: subscriptions to cancel outright (unused tools with no active users), subscriptions to right-size (reduce seat count to match active users plus a 10% buffer), and subscriptions to renegotiate (approaching renewal with utilisation data as leverage). Prioritise by annual savings potential and action urgency. Renewals approaching within 90 days get immediate attention.
Step 5: Establish ongoing governance. A one-time audit captures current waste. Ongoing governance prevents future waste. Set up quarterly reviews of your top 20 subscriptions by cost, require finance approval for new SaaS purchases above a threshold (many teams use $500 per month), and implement a structured renewal management process with staged alerts. Designate a single person — typically in finance or IT — as the SaaS portfolio owner with visibility across all departments.
The SaaS Management Index reports that organisations conducting regular SaaS audits spend 22% less per employee than those that do not. The audit itself is not the savings — the discipline it creates is. The first audit finds the obvious waste. The second audit finds the structural waste. By the third audit, your organisation has built the habits that prevent waste from accumulating in the first place.
Summary
A 100-person company should expect to spend $250,000 to $450,000 per year on SaaS, or roughly $2,500 to $4,500 per employee. If your number is significantly above that range, you almost certainly have optimisation opportunities. If your number is within range, you likely still have 20-30% waste hiding in unused licences, overlapping tools, and unmanaged renewals. Even a "normal" spend level contains addressable waste.
The path to optimised SaaS spend starts with visibility. You cannot manage what you cannot see. Build the inventory, categorise the spend, audit utilisation, and establish governance. The savings compound every quarter as your team builds the muscle memory of structured software spend management. The first quarter is the hardest. Every quarter after that gets easier and more productive.
For a 100-person company, a 20% reduction in SaaS waste represents $50,000 to $90,000 in annual savings. That is not a one-time benefit — it recurs every year and grows proportionally as your team and SaaS portfolio expand. The ROI on structured SaaS management is among the highest of any finance operations initiative because the savings are immediate, measurable, and compounding.