Cost per output measures what you get for your workforce spend - cases resolved, deals closed, units shipped - rather than simply how many people you employ. It's a direct response to a limitation of cost per head: two teams can have identical headcount and radically different costs relative to what they actually deliver, and cost per head alone can't tell you which is more efficient.
This shift shows up clearly in current research on what executives are actually asking for: fixed versus variable workforce cost, and cost per output rather than cost per head, alongside fewer metrics presented with a clearer narrative and explicit recommendations rather than raw numbers.
Why cost per head stopped being enough
Cost per head is easy to calculate and easy to compare year over year, which is exactly why it became the default. But it answers a limited question: how much are we spending on people. It doesn't answer whether that spend is producing proportionate value, or whether a team that costs more per head is actually more productive per dollar than a cheaper one.
In a budget environment where every function is being asked to justify its cost, that limitation becomes a real liability. A CFO comparing two teams on cost per head alone has no way to tell which one is a better investment - they can only tell which one is cheaper, which isn't the same question.
What cost per output actually requires
A defined, countable unit of output. This is the hard part, and it looks different by function - cases resolved for support, deals closed for sales, features shipped for engineering, or a function-specific proxy where output isn't naturally countable.
Accurate cost allocation, not just salary. Fully-loaded cost per output should reflect total cost of a team - salary, benefits, tools, overhead - not just base compensation, or the comparison across teams or time periods won't be fair.
A way to separate fixed from variable cost. Fixed cost per output changes slowly; variable cost per output can shift quickly with volume. Reporting the two together, without separating them, hides which part of a cost change is structural and which is just a short-term volume swing.
Where this gets hard, and how to handle it
Not every function has an obviously countable unit of output. A strategy or a people team doesn't ship units in the way engineering does. The useful move here isn't to force an artificial metric - it's to find the closest proxy that's still honest (projects completed, requests resolved, initiatives delivered) and be transparent that it's a proxy, not a precise unit economics figure the way it might be for a production function.
The goal isn't false precision. It's giving the CFO a more complete picture than cost per head alone provides, even when the output metric is imperfect.
Why this matters beyond the reporting format
This isn't just a different number to put in a slide. Reporting cost per output changes the conversation from "how many people do we have" to "are we getting proportionate value for what we spend" - which is a fundamentally better question for a CFO evaluating where to invest or cut, and a stronger position for any function that can answer it clearly.
FAQ
Is cost per output meant to replace cost per head entirely?
Not necessarily - they answer different questions. Cost per head is still useful for straightforward headcount tracking; cost per output adds the efficiency dimension that headcount alone can't show.
What if my function doesn't have an obvious unit of output?
Use the closest honest proxy available (projects completed, requests resolved) and be explicit that it's an approximation, rather than skipping the metric entirely or forcing an artificial one.
How does this connect to fixed vs. variable cost reporting?
They're complementary. Fixed vs. variable cost shows how flexible your cost base is; cost per output shows how efficiently that cost - fixed or variable - is converting into actual delivery.
What kind of tool makes cost-per-output reporting practical to maintain?
A platform that connects workforce and financial data continuously - the category Illoominus operates in - is what makes cost-per-output reporting sustainable past a one-time analysis, since it depends on current, fully-loaded cost data rather than a manual pull redone each quarter.
