How to Calculate IT Spend per Employee and Judge If It's Reasonable

Decide the definition once, then stick to it. A workable scope for a small business has five buckets:

• Cloud and hosting. Servers, databases, storage, bandwidth and backups.
• Software subscriptions. Email and office suites, identity, collaboration, CRM, design and developer tools.
• Devices. Laptops, phones and peripherals, spread over their useful life instead of counted in the purchase month.
• Security and compliance tooling. Endpoint protection, password managers, audits and penetration tests.
• External IT help. Managed service providers, contractors and consultants.

Decide up front whether engineering salaries are in or out. For a product company they're usually a separate line, so treat internal IT support staff on their own, and keep the definition constant so comparisons stay honest.

Use a spreadsheet and follow these steps:

1. Pull twelve months of card statements, invoices and vendor billing into one sheet.
2. Tag every line with one of the five buckets. Untagged spend is a finding in itself.
3. Convert annual subscriptions and device purchases to a monthly cost.
4. Sum by bucket, then divide each bucket by average headcount over the period (not year-end headcount, which flatters you if you've grown).
5. Record the result each quarter so you build a trend.

For example, say your team averaged forty people last year. Dividing total spend by forty gives one figure, but dividing each bucket separately tells you far more, because a rise in cloud cost has different causes than a rise in software seats.

Be skeptical of any single per-employee figure. The industry, how much you build versus buy and how much of the team works remotely all move it, and sources rarely say what they included.

For software companies, one outside reference is solid because its scope is clear. Median hosting spend at private B2B SaaS companies is 5 percent of ARR¹. Compare your cloud bucket against your own recurring revenue, not headcount, and treat it as a rough check, not a target.

The better benchmark for everyone is your own history. A stable spend per employee with a growing team suggests you're scaling normally. A rising figure with flat headcount points to sprawl, which usually means unused licenses, duplicate tools or oversized cloud resources.

Work from the largest lines down and ask one question each: who uses it, and what would break if we canceled it?

• Licenses for people who left. Reconcile each tool's user list against your current employee list every quarter.
• Overlapping tools. Two chat apps, two project trackers or three design tools usually mean teams bought independently.
• Idle cloud resources. Unattached disks, forgotten test environments and oversized instances. If you run on AWS, start with its cost reporting and check whether tagging lets you split costs by team or product.
• Auto-renewals. Put every renewal date on a calendar sixty days ahead so you can renegotiate or cancel.

Cut spend that nobody can justify, but don't cut security tooling to make a ratio look better.

Use spend per employee as a budgeting input for new hires: each additional person brings seats, a device and some share of cloud and security cost. Add those up for a planned hire and you'll see the true cost beyond salary.

Then tie the figure to the plan. When a spending line traces back to an engineering plan, the technology roadmap worksheet helps you see which costs are tied to real goals. When you review cloud provider options, AWS vs GCP vs Azure for startups covers the trade-offs in more detail. And a written information security policy tells you which security spend isn't optional.