The real cost of your bench (and the number most agencies never calculate)

Hi everyone. I spent years as the product owner of an internal HR system at an IT services company, watching delivery managers and accountants use it every day. Now I'm building Helia HR, and there's one number I keep asking agency founders for that almost nobody has ready.

It isn't utilization. Everybody has a utilization percentage. The number is: how many euros is your bench costing you this month? Blank stares, every time.

Utilization is a percentage. Payroll is euros. The gap is your bench.

A percentage is easy to look at and easy to ignore. "We're at 75%" sounds fine — healthy, even. But you don't pay salaries in percentages. You pay them in euros, for every hour, whether that hour was billed or not. The difference between what you pay for and what you bill for is your bench, and until you put a currency sign in front of it, it stays abstract enough to do nothing about.

The math nobody runs

Take one mid-level engineer. Fully loaded — salary plus employer taxes, benefits, tools, a share of overhead — they cost you somewhere around €8,000 a month. Run them at 60% billable utilization and roughly 40% of that person is idle-but-paid: about €3,200 a month of bench, from one engineer.

Now do it across everyone sitting under 100%. A 30-person shop can quietly carry €20,000–€40,000 a month of bench without a single person ever saying the figure out loud. And that's just the cost side — the capacity you didn't sell is revenue you didn't earn on top of it. The bench bills at zero and costs at full price.

Why the percentage hides it

"75% utilization across 30 people" is the same thing as seven and a half people showing up, getting paid, and not touching billable work. Nobody would walk past seven idle desks every morning and feel calm. Framed as "25% bench," the exact same reality is invisible — a rounding error in a dashboard instead of seven salaries. The percentage isn't wrong; it's just anaesthetic.

What to do — five things, none of which need a big ops team

1. Put the bench in euros, every month. One line next to your utilization number: bench headcount × their fully-loaded cost × the share they're idle. The moment it's a currency figure, it gets an owner and a deadline.
2. Make the bench a visible report, not a shame list. It's inventory, not a verdict on people. You can only staff from availability you can actually see — hiding the bench doesn't shrink it, it just delays the day you find out how big it got.
3. See roll-offs coming. An engineer whose project ends in three weeks is next month's bench. That conversation — the next assignment, or the next deal to staff them on — belongs in today's pipeline review, not on their last Friday.
4. Fill the bench on purpose. Genuinely free weeks are for internal tools, learning, certifications, and pre-sales — planned in, not backfilled with busywork nobody will bill or remember.
5. Don't over-hire ahead of pipeline. The most expensive bench is the one you created yourself, hiring for deals that hadn't closed. Match hiring to signed and near-signed work, not to optimism.

When a little bench is completely fine

100% utilization is not the goal — it's a fragile team with no slack for sales support, interviews, mentoring, or someone simply being off sick. Healthy services teams live around 70–85% and treat the rest as the cost of not burning people out. The goal was never zero bench. It's a bench you can see, priced in euros, that's short and shrinking — the difference between managed slack and quiet bleeding.

A percentage is something you can argue about in a meeting. A euro figure is something you have to do something about. Put your bench in euros, and most of the decisions make themselves.

More on the metrics behind this: [billable utilization benchmarks](/guides/billable-utilization-benchmarks) and [capacity planning for agencies](/guides/capacity-planning-for-agencies).