The EBIT Metric Your Accountant Isn't Tracking

Your accountant tracks EBIT. They send you the quarterly report. They tell you where the margin is going. In most cases, they will start tracking it more seriously the moment you begin preparing to sell your business. That is when it becomes real.

The problem is that the number they hand you does not tell you what to do about it. Especially if you are a small consultancy firm.

The metric that drives EBIT inside an IT services firm is not on your standard P&L. It is utilisation by consultant, by week, by client. Without that view, you are managing the symptom. With it, you are managing the cause. Most EBIT problems in IT services are utilisation problems hiding behind an averaged number on a monthly report.

The Real Issue

An averaged EBIT number tells you the temperature of the room. It does not tell you which corner is on fire.

If your firm-wide EBIT is at 12% and you know it should be at 20%, the accountant's recommendation is almost always the same. Cut overheads. Reduce SG&A. Tighten discretionary spend. Some of that might help. Most of the time, it treats the wrong problem.

The reason your EBIT is at 12% is rarely because your overheads are bloated. It is because your billable time is unevenly distributed. Some consultants are underused. Some are burning out. The averaged number smooths both extremes into a single dial that reads "margin compression."

You can spend a quarter cutting overheads and end up with the same EBIT and a smaller cost base. You can spend the same quarter fixing the utilisation distribution and end up with a better EBIT and the same cost base. Only one of those moves changes the trajectory of the firm.

Why IT Services Founders Are Most At Risk

IT services firms carry a specific version of this blind spot. Your revenue is a function of consultant time. Your cost is largely fixed. The gap between the two is where your EBIT lives.

But your accountant is looking at that gap through the wrong window. They see total revenue divided by total headcount cost, aggregated monthly. That view averages six consultants into one performance line and hides everything that matters.

Meanwhile, at the consultant level, three things are happening that never show up in the monthly report.

One consultant is at 88% utilisation and quietly heading toward burnout.

Two consultants are at 55% utilisation and their delivered rate is dragging the firm's average down.

The client mix on the highest-utilised consultant is loaded with your lowest-margin accounts.

Every one of those signals is actionable. None of them is visible in an aggregated EBIT line. The founders who fix EBIT sustainably are not the ones who cut overheads. They are the ones who install a weekly view at the consultant, client, and week level.

The Framework. The Utilisation Layer

Here are the three action steps I take founders through to install this layer.

Action Step 1. Pull Weekly Utilisation Per Consultant

Pull utilisation per consultant per week for the last 8 weeks. Not monthly. Weekly. And not firm-wide. Per person.

Anything below 65% needs a reason. Maybe they are on parental leave. Maybe they are in training. Maybe a project rolled off unexpectedly. Whatever the reason, it is a data point that needs a name.

Anything above 80% needs a recovery plan. Sustained utilisation above that line is where you start losing quality, cutting corners on delivery, and burning out your strongest people. Two quarters at 88% is how you lose a senior consultant to a competitor.

If you cannot pull this view from your current system, that is a systems problem to fix before the metric one.

Action Step 2. Measure the Gap Between Highest and Lowest

Identify the gap between your highest and lowest utilised consultant. If it is more than 25 points, you have a load-balancing leak.

A firm with utilisation ranging from 55% to 88% is not a firm with a margin problem. It is a firm with a distribution problem. The averaged EBIT hides the fact that half the team is idle while the other half is overloaded. Every dollar you spend on the idle half is dragging margin down. Every extra hour the overloaded half puts in is buying you short-term revenue at the cost of medium-term retention.

The 25-point gap is the tell. Under 25 and you are running a reasonably balanced firm. Over 25 and you have a leak that will not close on its own.

Action Step 3. Build the Weekly Resourcing Meeting

Build one weekly resourcing meeting to close that gap. 20 minutes is enough. Same time every week. Standing agenda. One owner.

The agenda is simple. Where is every consultant this week? Where are they next week? Where is the utilisation risk? What are we moving to close the gap? Twenty minutes. Every Monday morning. Someone owns the metric.

The moment someone owns it, it improves. Not because the meeting is magic. Because the metric now has a person attached to it, and no one wants to walk into the same meeting next week with the same numbers.

A founder I worked with was reviewing a flat EBIT line for two quarters. The standard accountant report showed margin compression and recommended cutting overheads. We pulled utilisation per consultant for the same period. Three of his five consultants were at 52% billable. Two were at 88% and approaching burnout. EBIT was not a margin problem. It was a load-balancing problem. He did not need to cut. He needed to redistribute. EBIT recovered in one quarter without a single overhead change.

What Changes When You Track The Right Metric

Founders who install the weekly utilisation view describe the same shift. The monthly EBIT number stops being a source of anxiety and starts being a lagging confirmation of what they already know.

They stop reacting to margin compression as if it is a mystery. They see it coming three weeks out, at the consultant level, and they intervene before it hits the P&L. They stop cutting overheads that were not causing the problem. They start moving people, adjusting workloads, and pruning low-margin clients.

The quieter outcome is that their team stops burning out. When you can see that a consultant has been at 88% for six weeks, you can move work before they resign. You cannot see that in an EBIT report.

The ConsultancyOS Play

This is one of the key metrics we have built into ConsultancyOS. Utilisation by consultant, by week, by client, running live against your firm's data. Not a monthly report. Not a spreadsheet you rebuild every Friday. A live layer that sits underneath your EBIT and shows you the cause, not just the symptom.

If you are running an IT services firm and wondering whether your current PSA is giving you this view, jump on the ConsultancyOS waitlist at consultancyos.ai. This is one of the exact problems it solves.