You have two engagements. Same service type. Similar scope. Similar fee. Yet one delivered a healthy margin while the other quietly consumed far more time and cost than expected. Many leaders end up asking the same question: why do project margins vary in professional services firms when the work looks almost identical on paper? If someone asked you to explain the difference right now, could you answer it with confidence?
In most professional services firms, the honest answer is no. Not because the information doesn’t exist somewhere in the business, but because nobody has assembled it into a single, usable view.
This is the structural reality of how most smaller firms are set up: financial reporting captures revenue and cost in aggregate. It tells you whether the firm made money. It doesn’t tell you which projects made money, or why two similar-looking engagements landed at completely different margins.
Here are the four structural factors that explain why project margins vary in professional services firms, and why your current reporting almost certainly isn’t showing them to you.
1. Realization Rate
Utilization and realization are not the same metric, and treating them as interchangeable is one of the most common sources of invisible margin erosion in professional services.
- Utilization measures hours logged to a project.
- Realization measures how much of that logged time is converted into billed and collected revenue. It’s the revenue the client paid for.
In an ideal world, those two numbers are the same. In practice, realization is almost always lower. Hours get logged against client projects that weren’t contracted for. Rework consumes time that can’t be billed. Scope that crept in informally gets absorbed rather than invoiced.
The gap between utilization and realization is one of the most reliable indicators of hidden margin leakage. Most firms don’t track it at the project level, so they never see which engagements are consistently bleeding hours that go unbilled, and the aggregate utilization figure continues to look healthy.
2. Senior Time Allocation
When a senior person with a high cost rate spends time on work that should have been handled by someone more junior, the project absorbs the cost difference. The client was priced for a junior delivery model. The delivery model that was used was more expensive.
This isn’t about senior oversight, that’s necessary and should be costed into every engagement. It’s about senior capacity doing the work itself because the right junior resource isn’t available, isn’t ready, or simply because it was faster for the senior person to do it.
It happens constantly. And most project profitability calculations don’t isolate it, so it sits invisibly within your margin numbers, making some projects look worse than they should be without any clear explanation for why.
3. Scope Absorption
Unless every project you run is time-and-materials with no cap, scope drift is a margin problem. One small request here, one additional round of revisions there. We didn’t raise a change order because… we don’t want to upset the client. The team delivers it because it feels like the right thing to do.
It’s the ‘death by a thousand cuts’ scenario. Each individual decision makes sense in the moment. Accumulated across a project (or across ten projects), it quietly blows a significant hole in your margin.
The projects where scope was managed tightly look very different at the end from the ones where it wasn’t. The difference isn’t in the fee. It’s in what was allowed to happen during delivery. And without project-level margin tracking, that difference is invisible until after the engagement closes.
4. Overhead Allocation Accuracy
Most firms allocate overhead across projects using a simple formula (either a flat rate per hour or a percentage of revenue). But overhead isn’t uniform. Some projects consume far more internal coordination, management attention, and administrative time than others.
When overhead is spread evenly, the low-maintenance, efficient engagements end up subsidizing the high-maintenance, complex ones. Your most profitable work looks less profitable than it is. Your most difficult work looks better than it is. And your pricing decisions are being made on a distorted picture.
Two practical fixes that are often overlooked:
- Logging non-billable and administrative tasks directly against projects, and
- Creating a client management project for each client to capture relationship overhead separately.
Neither requires a systems overhaul, but both change what you can see.
Why Your Reporting Isn’t Showing You This
If these four factors are causing significant margin variation within your firm, why aren’t they visible in your financial reports?
The honest answer is that most financial reporting in smaller firms was built around the general ledger (GL). The reports are designed for compliance and tax, not for operational decision-making.
The GL captures revenue and cost. It doesn’t capture the cost to deliver each engagement once you factor in realization, staffing mix, scope absorption, and overhead consumption.
That project-level view requires combining your GL data with your timesheet data, billing records, and resource allocation, and assembling them in a way that shows you what each engagement genuinely costs. Most firms have all that data scattered across separate systems.
Some of it is reliable. Some isn’t.
And in many cases, the business started on spreadsheets and QuickBooks and hasn’t moved beyond them, not because the owner isn’t commercially sophisticated, but because they’re simply unaware that there are ERP and PSA (professional services automation) tools specifically built to consolidate this information.
Many of those tools are significantly more cost-effective than firms expect. And the visibility they create (project-level margin, realization rates, capacity by role), can have a material impact on every commercial decision the business makes.
The data needed to understand why project margins vary in professional services firms almost certainly already exists somewhere in your business. It just hasn’t been assembled. And until it is, pricing decisions, hiring decisions, and growth decisions are all being made on an incomplete picture.
Want to understand where your margins are coming from?
We run a four-week Profit and Capacity Diagnostic that maps exactly that – which clients and projects are generating real margin, where effort is being misallocated, and what to address first.
The starting point is a free 20-minute assessment call. No pitch, just a working conversation about your specific situation.
Frequently Asked Questions
Even when two projects have similar fees and scope, their actual margins depend on four factors that most financial reports don’t surface: realization rate (how much of the time logged was actually billed and collected), senior time allocation (whether work was delivered at the right cost level), scope absorption (how much uncontracted work was absorbed during delivery), and overhead allocation accuracy (whether the real coordination cost of each project was captured). Any one of these can produce a significant margin gap between two projects that look identical on paper.
Realization rate measures the proportion of logged hours that are converted into billed and collected revenue. Utilization only measures hours logged against projects. The gap between the two (hours worked but not paid for) is where the margin quietly disappears. A team running at 85% utilization might have a realization rate of 65% or lower once rework, scope absorption, and write-offs are taken into account. Most firms track utilization closely and realization rarely, which means they’re optimizing for the wrong metric.
Scope creep reduces project profitability by increasing the hours required to deliver a fixed-price engagement without a corresponding increase in revenue. Each individual request (an extra revision, an additional meeting, a small change that wasn’t in the original brief), may seem inconsequential in isolation. But accumulated across a project, they can consume ten, twenty, or more hours of unbilled time. Across a portfolio of ten projects, each absorbing ten hours, that represents a substantial amount of unpaid delivery. The projects where scope is managed with formal change orders consistently outperform those where it isn’t.
Standard financial reporting in most smaller professional services firms is built around the general ledger, which is designed for compliance and tax purposes. It captures revenue and cost in aggregate, but it doesn’t combine GL data with timesheet data, billing records, and resource allocation in a way that shows project-level margin. Producing that view requires either a purpose-built PSA (professional services automation) tool or ERP system, or a structured process for assembling the data manually. Many firms remain on spreadsheets and accounting software that wasn’t designed to answer this question.
Firm-level profitability is the aggregate view, total revenue minus total cost, often expressed as a net margin percentage. It tells you whether the business as a whole is making money. Project-level profitability breaks that down to individual engagement, showing the margin generated (or lost) on each piece of work once actual delivery costs are accounted for. The difference matters because firm-level profitability can look acceptable even when several individual projects are margin-negative. The profitable work subsidizes the unprofitable work, and the average obscures both. You cannot make reliable pricing, staffing, or client decisions from a firm-level view alone.
PSA (professional services automation) tools and ERP systems are specifically designed to consolidate the data sources that smaller firms typically hold in separate places (timesheets, project budgets, billing records, and financial accounts) into a single view. This makes it possible to track realization rates, monitor project budgets in real time, and see margin by client and engagement rather than in aggregate. Many platforms in this category are more cost-effective than smaller firms expect, and the commercial decisions they enable (around pricing, staffing, and client selection) often significantly justify the investment. A key first step is to understand which data you already have and which gaps need to be addressed before a system implementation produces reliable output.
Before changing a pricing model, a firm needs to understand its current project-level margin data: which service lines are performing, which client types consistently erode margin during delivery, and where the gap sits between what was quoted and what the delivery cost. Without that baseline, a pricing change addresses the output (the rate) rather than the cause (the delivery economics). If poor realization, scope absorption, or senior time misallocation are driving the margin pressure, a rate increase alone will not resolve them. The firms that reprice most successfully do so after establishing what delivery genuinely costs and then setting prices based on that evidence rather than on market comparison or intuition.
