SaaS Spend Per Employee by Department: 2026 Benchmarks

Understanding SaaS spend in aggregate is useful. Understanding it by department is actionable. The per-employee SaaS spend varies dramatically across functions, and knowing what normal looks like for each function helps you identify where your organisation is out of line.

Applying that discipline at scale usually means a proper system of record for software spend — which is where a platform like Liceo comes in.

Engineering and Product

Engineering and Product teams consistently run the highest per-employee SaaS spend — typically £5,000–£8,000 per head per year. Developer tools (GitHub, Jira, Figma, cloud development environments, monitoring and observability platforms) are expensive at the professional and enterprise tiers required for team use. This spend level is generally justified by productivity impact, but it also means Engineering is where the largest absolute savings opportunities live when tools go underused.

Sales and Marketing

Sales and Marketing combined typically spend £3,500–£5,500 per employee per year. CRM and sales engagement tools (Salesforce, HubSpot, Outreach, LinkedIn Sales Navigator) dominate sales spend. Marketing adds analytics, content, and paid acquisition tools. This is the category most prone to tool proliferation — marketing teams adopt new tools aggressively and retire them slowly. A consolidation review in Marketing commonly surfaces two to four redundant subscriptions.

Operations, Finance, and HR

These functions typically spend £1,800–£3,000 per employee per year. Core tools are productivity (M365 or Workspace), HRIS, finance system, and a handful of function-specific tools. Spend in this bracket is usually well-controlled because purchasing decisions are more centralised. The optimisation opportunity here is mainly in unused seats — these functions tend to have higher staff turnover than Engineering, meaning licences linger after departures.

Using Benchmarks to Drive Action

Compare your actuals against these benchmarks department by department. Functions spending significantly above benchmark warrant a usage audit — pull active user data and compare against seat counts. Functions spending below benchmark may be under-tooled, which is a less common but real problem that affects team productivity and should be investigated before assuming it represents good cost discipline.

Share these benchmarks with department heads during budget planning conversations. When a business unit can see that their per-employee SaaS spend is 40% above the benchmark for their function, it creates a productive conversation about whether that premium is justified — and often surfaces consolidation opportunities that IT alone would never have found.