Headcount Equivalent

Headcount equivalent (HCE) is the conversion of AI workforce output into the number of full-time human employees it replaces — used for budgeting, ROI, and capacity planning.

An AI employee doesn't fit on an org chart line item the way a human does. HCE is the bridge: 'this AI SDR is doing the work of 3.4 human SDRs at our volume'. The number translates AI capacity into the language a CEO and a board already speak. The right way to compute HCE is by output, not effort: how many of the same outcome does the AI produce in a week vs. a benchmark human? That number, times the loaded human cost, is the value the AI is generating. Comparing that to the AI's cost gives you ROI.

Example

Maya (AI SDR) sends 1,200 personalized emails and books 14 meetings per week. A senior human SDR averages 350 emails and 4 meetings. HCE = 14 / 4 ≈ 3.5 senior SDRs replaced.

How OpenLabor uses it

OpenLabor reports HCE per employee on the weekly review — a single number to take to your board.

Isn't HCE just spin?

Only if you compute it dishonestly. Output-based HCE — counting only outcomes a human would also produce — is real and defensible.

Does HCE mean I should fire that many humans?

Almost never. HCE is capacity gained. Most teams reallocate humans to higher-leverage work rather than reduce headcount.

Related: cost-per-task, ai-employee.

AI Labor Glossary