Utilization Is High Because Pricing Is Broken

The healthiest-looking number on your dashboard can be measuring the disease.

Most founder-led service firms watch one number above the rest: utilization. How busy is the team. How much of the week turns into billable work.

High utilization reads as health. Busy means demand, demand means the model works, and the dashboard glows green.

It is also, often, the most misleading number in the building. Not because anyone is gaming it, but because of what it cannot see.

High for exactly the wrong reason

Utilization can be high because business is genuinely good. It can also be high precisely because pricing and scoping are broken. From the dashboard, the two are indistinguishable.

Watch how it happens. An underpriced engagement consumes more hours than the fee accounted for. Those extra hours do not show up anywhere as a loss. They show up as busy people, which the metric scores as a win. A loosely scoped engagement keeps growing, and the unpaid growth registers the same way. More work, more hours, more utilization.

So a firm can be fully booked because every project takes half again as long as it was priced for. The metric cannot tell the difference between a strong pipeline and a leaking one. It just measures motion.

Which means the dashboard can reward the disease. If a firm fixed its pricing and scoping tomorrow, utilization might actually dip for a quarter while margins recovered. That dip would be health. Most dashboards would read it as decline, and most weekly reviews would treat it as a problem to fix.

The hours the metric cannot see

There is a second distortion, and it sits closer to home.

In a founder-led firm, the founder usually carries the glue work. Scoping the next engagement. Reviewing the deliverable before it goes out. The reassurance call that keeps a wobbly project on the rails. Stepping in wherever the work queues. Hours of it, most weeks.

Almost none of that is billed, and almost none of it appears in the utilization number. The metric counts the team's logged hours and never sees the founder subsidy holding the whole thing together. The firm runs on hours that exist on no report.

So the number flatters the firm twice. It scores unpaid absorption as productive busyness, and it leaves the most expensive person's unpaid hours off the books entirely.

This matters for the H2 plan you may have just written. A plan that takes the utilization number at face value is planning with capacity that is partly fiction. Some of those hours are already spoken for by underpriced work, and some of the real load is sitting on the founder, uncounted.

Busy is not the same as sound

Yesterday's piece argued that chronic overwork, scope creep, and margin squeeze are usually a pricing decision being faithfully executed, not a workflow failing. It closed with three questions that tell you which layer a recurring problem actually lives on.

Utilization is where that pattern hides in plain sight. If your utilization is high and your margins are thin, that combination is not a paradox. It is the signature. Run yesterday's three questions against whatever problem keeps resurfacing, and pay attention if the answers keep pointing below the workflow, down at the price.

What to do with this

This week put two tools on the table, no gate, no email. Wednesday's load test puts five questions to your H2 plan. Thursday's layer test tells you where a stubborn problem lives. Most readers can run both themselves this weekend, with the plan in one hand and an honest hour in the other. That is the point of publishing them in full.

Q3 2026 starts Wednesday, July 1. From there, the H2 plan stops being a document and starts being tested against the operation as it actually is. If you would rather not run that test alone, one more option below.

If you run the questions and want a structured outside look at the plan as Q3 gets underway, that is what a fit call is for: a short conversation that decides whether the Blueprint fits where you are, and "not yet" is a fine answer.

The Blueprint is our fixed-scope, fixed-fee diagnostic. It produces five things: a written diagnosis of the real bottleneck, a prioritized operating roadmap, a decision framework for the calls your firm keeps making inconsistently, a scoped brief you could hand to an execution resource, and a clear map of your options at the end, including running the whole thing yourself.

Book the fit call: altvina.com/fit-call

Continue the series

This is part 5 of a 5-part series on Load-Test the Plan. Then Look at the Price.. The full arc:

• Monday: Your H2 Plan Is a Forecast of Your Bottleneck
• Tuesday: The Line You Copied From January
• Wednesday: The 15-Minute H2 Load Test
• Thursday: The Workflow Is Not Broken. It Is Executing the Price.
• Friday: Utilization Is High Because Pricing Is Broken (this post)

Content and Accuracy Disclaimer

This article was drafted with AI assistance and reviewed by the Altvina team. We rigorously fact-check all content to ensure reliability.

Should you notice any inaccuracies or outdated information, please contact us so we can correct it. Your feedback helps us maintain high standards of accuracy and transparency.