SaaS spending benchmarks

Per-seat SaaS cost roughly triples between micro-teams and the 500+ band. The 11-50 band shows the steepest jump because growing teams add specialist tools (sales engagement, BI, observability) before they hit the volume discount thresholds that larger companies negotiate.

Tool count grows roughly 1.4x faster than headcount once a team passes 50 people. Most of the new entries are department-specific niche tools that never get audited until the renewal cycle. Founders running consolidated stacks under 30 tools tend to report higher satisfaction in the same dataset.

Mid-market companies waste roughly one in five SaaS dollars on overlapping tools — typically two project trackers, three file-storage accounts, and a parallel CRM that only one department uses. The duplicate share keeps climbing past 200 employees because procurement gets fragmented across lines of business.

Observability vendors command the highest annual contract values because pricing scales with log volume rather than seats. CRMs sit in the middle of the pack but often add per-feature line items that push effective ACV 30-40% higher by year two.

Sales and marketing together account for 43% of total SaaS spend across the dataset. Engineering tooling under-indexes because cloud infrastructure (AWS, GCP) is excluded — when included it would add another ~22 percentage points and push engineering to the top.

Annual contracts cut year-one churn by roughly two-thirds versus monthly. The trade-off: teams locked into annual deals report 40% more buyer's remorse in qualitative interviews, especially when the tool turns out to be a poor fit by month four.

Negotiating leverage scales roughly linearly with seat count. Companies under 10 employees rarely break double-digit discounts, while teams above 500 routinely extract a third off list. The fastest gains come from threatening a competitor switch within 60 days of renewal.

Sales teams roll out new tools fastest because the buying decision is usually made by the same person who will use them daily. HR and finance lag because rollouts trigger compliance reviews, vendor security questionnaires, and cross-department training that engineering teams typically skip.