Department-Level SaaS Spend: How to Allocate, Track, and Optimise

A single organisation-wide SaaS spend number is useful for benchmarking but not for optimisation. To find the waste, you need to break spend down by department — and then by tool within each department.

Allocation Methodology

The cleanest allocation methodology is seat-based: the cost of each tool is allocated to departments in proportion to their share of active seats. If Engineering has 40 of the 100 active seats in Figma, 40% of the Figma cost is allocated to Engineering. This is calculable from your SaaS management platform and is directionally accurate even if not perfectly precise.

Per-Employee Spend by Department

Calculate per-employee SaaS spend for each department. This normalised metric makes departments comparable regardless of size. Engineering and Product departments typically run 2–3× the company average; Operations and HR typically run below average. Significant deviations from these norms are worth investigating.

Department-Specific Optimisation

Different departments have different waste patterns. Engineering often has high spend on developer tools that are lightly used outside of core teams. Sales often has CRM and sales engagement tool proliferation. Marketing often has multiple analytics and content tools with overlapping functionality. Targeted reviews by department are more effective than top-down cuts.

Engineering the Conversation with Department Heads

A cold presentation of "your department is spending £X on SaaS" rarely produces productive optimisation conversations. The more effective approach is to come with a specific question: "We've identified three tools in Engineering where more than 40% of seats are inactive — can we walk through these together?" A narrow, specific question with supporting data is much easier for a department head to engage with than a broad cost reduction mandate.

Align the conversation with the department head's priorities. For Engineering leaders, frame optimisation as releasing budget for tools that have better developer experience or more active adoption. For Sales leaders, frame it as ensuring the sales team has access to the best tools rather than duplicating capabilities across multiple subscriptions. Meeting department heads on their terms, rather than leading with a cost reduction agenda, produces more willing partners and better outcomes.

Tracking Department-Level Trends

Month-over-month changes in department-level spend are as informative as the absolute numbers. A 20% increase in Marketing's SaaS spend in a single month warrants investigation — is it a planned tool addition, an auto-seat expansion, or an unapproved purchase? A 10% decrease in Engineering's spend might reflect a successful licence optimisation or might reflect a planned tool cancellation that's created a gap in the team's toolset. Trend data adds context that point-in-time spend figures alone don't provide.

Build a department-level spending trend chart into your monthly SaaS management reporting. When significant changes appear, follow up directly with the relevant department head or their IT business partner. Proactive communication about changes — both up and down — keeps stakeholders engaged with the programme and prevents surprises in the quarterly budget review.