Cost-per-productive-hour: the one workforce metric that actually matters

Most workforce dashboards measure the wrong things beautifully. Headcount, total hours logged, attendance percentage — they're easy to chart and easy to feel good about, and none of them answer the only question leadership actually cares about: are we getting our money's worth?

To answer that, you need a metric that puts cost and output in the same sentence. We call it cost-per-productive-hour, and once you start looking at it, the older numbers feel like noise.

Defining "productive"

The trap in any productivity metric is the denominator. If you divide cost by total hours, you reward people for being present. If you divide by productive hours — hours tagged as real, classified work, excluding breaks and idle time — you reward people for actually moving the business forward.

Wieeo enforces this at the source. Every minute claimed must be justified by a tagged, classified activity entry. A break is a break. meeting is meeting. development is development. The system already knows which hours are productive because the classification happens at entry time, not in a quarterly clean-up.

The formula

cost per productive hour  =  fully-loaded weekly cost  ÷  net productive hours

Net productive hours are expected hours minus break time — the productive denominator, not the clock-in-to-clock-out one. Two teams with identical payroll can have wildly different cost-per-productive-hour, and that gap is the most honest signal you have about which team is actually healthy.

What it reveals

Cost-per-productive-hour exposes things headcount hides:

• The overstaffed team with great attendance and mediocre output — high cost-per-hour despite looking "compliant".
• The lean team quietly carrying more than its size suggests — low cost-per-hour, a flight risk you didn't know you had.
• The seasonal drift where cost creeps up not because anyone's slacking, but because productive hours quietly shrank under meeting load.

Headcount tells you how many people you have. Hours-worked tells you they showed up. Cost-per-productive-hour tells you whether the arrangement is working — which is the only one of the three a CFO can act on.

Comparing fairly

The metric only earns trust if comparisons are fair. A senior team will have a higher absolute cost, so the point isn't to rank teams by raw cost — it's to track each team against itself over time and to compare like-for-like roles. Wieeo's team and peer comparison does exactly this: same-department peers, side by side, on cost-per-productive-hour rather than gut feel.

Set a target, not just a chart

A metric you only observe is a hobby. The next step is a minimum productive percentage target — the floor of productive-to-expected hours you expect a healthy team to clear. Below the floor, you investigate; above it, you leave people alone. That single threshold turns a dashboard into a management tool: it tells you where to look and, just as importantly, where not to.

Stop optimizing for presence. Start optimizing for the cost of an hour that actually moved something. It's the one number that survives contact with a budget review.