What per-employee SaaS spend looks like by company size — and where most teams overpay.
Understanding what other companies spend on SaaS is essential context for every budget and negotiation conversation. The figures below are drawn from aggregated spend analysis across hundreds of organisations.
Companies with fewer than 50 employees spend approximately £2,800 per employee per year on SaaS. Spend per employee increases with company size — at 50–200 employees it reaches around £3,400, and at 200–1,000 employees it climbs to £4,100. Above 1,000 employees, per-employee spend typically moderates to £3,600–£3,800 as volume discounts and more rigorous procurement take effect.
Across all company sizes, three categories account for the majority of SaaS spend: productivity and collaboration (Microsoft 365 or Google Workspace, plus video conferencing) typically accounts for 25–30% of total spend. Business applications (CRM, ERP, finance tools) account for 30–40%. And department-specific tools — engineering, marketing, design, data — make up the remaining 30–40%.
The largest consistent sources of overpayment are: purchased seats that exceed active users by more than 20% (found in 68% of organisations audited), premium tier licences with unused advanced features (found in 54%), and duplicate tools serving the same function across different departments (found in 47%).
SaaS spend per employee tends to grow by 8–12% annually even without headcount growth, driven by price increases, tier creep, and new tool adoption. Organisations that proactively manage their SaaS estate hold this growth to 3–5% by offsetting price increases with utilisation optimisation and negotiation. The delta — 3–9% of total SaaS spend — is the financial value of an active SaaS management programme.
Year-over-year spend growth by category is a useful diagnostic. If your collaboration tool spend has grown by 40% while headcount has grown by 10%, something is driving that gap: tier upgrades, seat over-provisioning, or the addition of complementary collaboration tools to an already expensive stack. Each of these has a different resolution, and identifying the right one requires category-level spend tracking rather than just total spend.
Benchmarks are most powerful when used as a negotiating data point rather than just an internal planning tool. Telling a vendor that their per-seat pricing is 25% above the industry median for your company size is a stronger opening than simply asking for a discount. Most enterprise SaaS vendors have pricing flexibility that they rarely volunteer — but they respond to customers who demonstrate market awareness.
Combine benchmark data with your own utilisation data for the strongest negotiating position: "We're paying 25% above market rate, our active user count is 62 of 100 seats, and we have an alternative evaluation underway. We'd like to right-size to 70 seats at a rate in line with market." This is a specific, data-driven ask that gives the vendor a clear target to reach rather than an open-ended negotiation.
External industry benchmarks are useful for relative positioning; internal benchmarks — your own historical data — are more actionable for budget planning. Track your per-employee SaaS spend by department, month over month, for at least four quarters before trying to benchmark externally. Understanding your own baseline and variance first makes external benchmarks interpretable: you know whether a deviation from industry norms reflects an investment choice or a governance gap.
Track every licence, cut waste, and automate renewals — in one platform.
Comments are moderated before appearing publicly.
No comments yet. Be the first to share your thoughts.
Ronke
Liceo product guide · AI assistant
Hi, I'm Ronke, Liceo's product guide. I can help you understand how we bring licence, vendor, and spend visibility together, or walk through plans and integrations. What are you trying to solve today?