Tracking Cost per Head Across a Global Workforce

Fully loaded cost per head should include base pay, statutory employer contributions, benefits, and any EOR or payroll platform fees, calculated the same way for every country. Skipping employer statutory contributions in some countries and including them in others, a common inconsistency when data comes from different local providers, makes any cross-country comparison meaningless.

Build the calculation once as a template, then apply it consistently as you pull data from each country's payroll source, rather than letting each region report its own version of the number.

A lower cost per head in one country isn't automatically a win if output per head is proportionally lower too, and a higher cost per head isn't automatically a problem if that team is meaningfully more productive. Pair the cost number with a relevant output metric for each function, tickets resolved, revenue influenced, deals closed, so the comparison actually informs a decision rather than just ranking regions by raw cost.

This is where a workforce analytics view earns its keep: not as a cost-cutting scorecard, but as a way to see where cost and output are out of line in either direction.

A single quarter's cost per head is a snapshot, and snapshots are noisy: a benefits renewal, an FX swing, or a hiring surge in one region can distort a single period's number without reflecting a real underlying trend. Track cost per head quarterly over at least a year before drawing conclusions about whether a region's cost is genuinely rising or falling relative to output.

Say G&A spend runs around 24% of revenue for a comparable business¹: that kind of external reference point is useful context for your own G&A-heavy headcount, but only once you're comparing it against your own multi-quarter trend, not a single snapshot.

A few patterns that undermine the usefulness of this analysis:

• Calculating cost per head inconsistently across countries, sometimes including statutory contributions and sometimes not
• Comparing raw cost across regions without any output context, leading to decisions that cut cost in a highly productive region
• Reacting to a single quarter's number instead of a multi-quarter trend
• Never revisiting the calculation methodology as your provider mix or country footprint changes

Each of these turns a potentially useful analytics practice into a source of bad decisions made with confidence.

Deel and Rippling both provide cost and headcount reporting as part of running payroll across countries, which is a more consistent data source than stitching together reports from several local providers by hand. Where a country still runs through a specialized local provider, get that provider reporting into your standard cost-per-head template so the comparison stays complete.

Review the full cost-per-head and output view quarterly with whoever owns headcount planning, so the analysis actually feeds into hiring and budget decisions rather than existing as a report nobody acts on.

Say your fully loaded cost per head in Poland runs $54,000 a year against $71,000 in the UK for the same engineering role, and on a first look that reads as the UK team being overpriced. Layer in output, and say the Poland team closes 22 features a quarter against 26 for the UK team of the same size: the UK's cost premium is about 31% for roughly 18% more output, a real gap worth a conversation, but a smaller one than the raw cost numbers alone suggested.

The decision rule that falls out of this: don't act on a cost gap until you've checked whether output moved proportionally. If your UK team's output had matched Poland's exactly instead, that same premium would be a clear case for either renegotiating the local package or shifting future headcount toward Poland. Since it didn't, the more useful next step is asking what's driving the UK team's higher output, a more senior mix, better tooling, different scope, before treating the cost difference as a problem to solve.