Project Profitability in Consulting: Why High Utilization Doesn't Always Mean High Margins

Utilization is the metric most consulting firms live and die by, and for good reason. When your people are billing, revenue comes in. But utilization only tells you how busy your team is. It says nothing about whether the work is actually profitable.

It's entirely possible to run a firm at 85% utilization and still have disappointing margins. Projects that started at a healthy rate get extended under a fixed price. Scope creep adds weeks of work that clients don't pay for. Discounts close deals but compress the margin that was supposed to make the project worthwhile. By the time finance runs the numbers at quarter end, the gap between projected and realized margin can be significant, and it rarely announces itself in advance.

The gap between revenue and margin

Revenue is what you bill. Margin is what you keep after paying for the people who did the work. For most consulting firms, the single largest cost is labor, so project margin is essentially the spread between what a consultant bills and what they cost.

A senior consultant billing at 1,200 EUR per day with a fully loaded daily cost of 700 EUR generates 500 EUR of gross margin per day. If that same consultant spends three extra weeks on a fixed-price engagement because the scope wasn't controlled, those 15 days cost the firm 10,500 EUR in labor with zero additional revenue. The utilization number still looks fine. The project margin does not.

This is why margin needs to be tracked at the project level, not just at the firm level. A firm-wide margin number smooths over the individual projects that are quietly losing money.

How scope creep erodes margin without touching utilization

Scope creep is the most common margin killer in consulting, and it's particularly insidious because it doesn't show up in any single dramatic moment. It's an extra round of revisions here, an additional stakeholder meeting there, a client request that felt small but took a day and a half to execute.

On a time-and-materials project, scope creep gets billed. On a fixed-price project, it doesn't. The client pays the agreed amount regardless of how many hours the team puts in. This is why fixed-price projects require more careful margin tracking than T&M work. Every hour over the original estimate is a direct reduction in project profit.

The firms that manage this well track burn against budget in real time. If a project is 60% through its timeline but has consumed 80% of its estimated hours, that's a signal. The delivery lead can have a scope conversation with the client before the overrun becomes unrecoverable, not after.

Realized rate vs. planned rate

Every project starts with a planned billing rate. The rate on the contract is what the deal was priced at. But the realized rate, what the firm actually earns per consultant day after accounting for all the hours worked, can be very different.

Discounts are one factor. A client negotiates a 15% reduction off the standard rate to close the deal. That discount applies to every day every consultant works on the project. On a six-month engagement with five consultants, a 15% discount can represent 50,000 EUR or more in forgone revenue.

Rate mix is another factor. If a project was scoped assuming two senior consultants and one junior, but delivery required three seniors because the junior wasn't ready for the complexity, the labor cost is higher than projected even though the client is paying the same amount. The realized margin compresses even though the billing looks correct.

Tracking realized rate per project, and comparing it against the planned rate at the time of signing, gives leadership early warning when margin is drifting in the wrong direction.

Fixed-price vs. time-and-materials margin risk

Fixed-price and T&M projects carry fundamentally different margin risks, and managing them requires different disciplines.

On a T&M engagement, the risk is under-delivery. If a consultant works fewer days than expected because the project ends early or gets descoped, revenue falls short of the forecast. The margin percentage stays roughly the same, but the absolute margin shrinks. The risk is on the top line.

On a fixed-price engagement, the risk is over-delivery. Revenue is capped at the contract value regardless of effort. If the project runs long, the firm absorbs the cost. The margin percentage deteriorates while revenue stays flat. The risk is on the cost line.

Most firms have a mix of both. The key is knowing which projects are which and applying the right monitoring to each. Fixed-price projects need hours-to-budget tracking. T&M projects need timeline and scope tracking to ensure clients don't let work drift without extending the engagement.

Tracking project margin in real time

Project profitability tracking starts with two numbers for each engagement: planned gross margin (the expected spread between contract revenue and labor cost at signing) and realized gross margin (the actual spread based on hours worked and costs incurred to date).

For the realized side, you need assignment data: who worked on the project, on which days, and at what cost. When this comes directly from your resource planning tool, it updates automatically as assignments are logged. No manual timesheets, no end-of-month reconciliation. You can see, today, whether a project is on track or eroding.

The comparison between planned and realized margin over time is where the insight lives. A project that opens at a 40% planned margin and is trending toward 25% realized margin six weeks in has a problem that can still be addressed. The same project at 25% margin discovered at closeout is just a lesson for next time.

What good project profitability looks like

A well-run consulting firm should be able to answer these questions for any active project: What was the planned margin at signing? What is the realized margin today based on hours worked? How many hours remain in the estimate, and how does that track against the timeline? Are there scope changes that haven't been priced into the contract?

For fixed-price projects specifically, the firm should also know the break-even point: the number of consultant days at which the project transitions from profitable to unprofitable. That number should be visible to the delivery lead at all times, not reconstructed in a spreadsheet after a client call.

A target gross margin of 35 to 45% per project is common in IT consulting, though it varies significantly by service type and market. What matters more than the specific target is the consistency of tracking and the speed of detection when a project drifts below it.

Connecting project margins to firm-level decisions

Project-level margin data doesn't just help you manage individual engagements. It informs every major decision the firm makes.

When evaluating a new deal, you can compare its projected margin against the historical margin of similar projects. If every fixed-price implementation project you've done in the last 18 months has realized a margin 10 points below the planned margin, that's a pricing problem. You need to either increase rates, tighten scope definitions, or price in the overrun.

When making capacity decisions, margin data helps you prioritize. If two potential deals are competing for the same senior consultants, the one with stronger margin and firmer scope deserves the staffing priority. Utilization tells you both deals keep people busy. Margin data tells you which one is worth more.

And when reviewing firm performance, project-level margin roll-up gives leadership a cleaner picture than utilization alone. A month where utilization was 82% but average project margin was 28% tells a different story than a month where utilization was 78% but margin was 41%. The second scenario is likely a better business outcome, even though the utilization number looks worse.