Why Good Project Margins Hide a Struggling Firm

Your last five projects all hit 35% margins or better. Your clients are happy, your delivery teams are sharp, and your project managers are tracking every hour. So why is your firm barely clearing 10% EBITDA? Plenty of professional services owners are asking the same question right now.

The Numbers That Don’t Add Up

The data is worth a close look. According to Deltek’s 2025 Professional Services Benchmark, project margins held steady at 35.9% in 2024, right around the five-year average. Meanwhile, EBITDA fell to 9.8%, down from 15.4% the year before and 16.1% at its peak in 2022. Projects are delivering healthy margins. Firms are not converting those margins into profit.

This isn’t a delivery problem. It’s an overhead problem. The gap between what your projects earn and what your firm keeps is growing, and most of the leakage happens in places that project-level reporting never shows you.

Where the Margin Disappears Between Projects

When you measure profitability at the project level, you capture a clean picture: revenue in, direct costs out, margin calculated. What you miss is everything that happens around and between those projects.

Bench time is the biggest silent cost. Billable utilization across the industry dropped to 68.9% in 2024, according to Deltek’s benchmark report. That means roughly 31% of your team’s available time isn’t generating revenue. Some of that is expected: PTO, training, admin. But when utilization falls well below the 75% threshold that SPI Research identifies as the floor for healthy firms, the excess isn’t “investment in people.” It’s unplanned cost.

Internal initiatives eat delivery capacity. Transformation projects, tool migrations, AI pilots, process improvement efforts. Runn’s 2026 State of Resource Management report found that some sectors are dedicating up to 40% of their budgets to internal transformation. Those projects don’t generate client revenue, but they consume the same people who do.

Cost of sales never shows up in project margins. The time your senior consultants spend on proposals, scoping calls, and presales activities is real cost. It sits between won projects and doesn’t get allocated to any of them. For firms with win rates below 30%, this invisible overhead compounds fast.

Why Project Margins Alone Are Misleading

Project margin is a delivery metric. It tells you whether your team executed efficiently on a specific piece of work. It does not tell you whether your firm is healthy.

Consider a firm with 50 consultants:

• Average project margin: 36%
• Billable utilization: 69%
• Average billing rate: $180/hour
• Annual revenue per consultant: approximately $199,000

Those project margins look great in isolation. But if the firm’s overhead, including leadership, sales, operations, HR, office costs, and bench time, runs at $150,000 per consultant, the math gets uncomfortable. You’re making $199,000 per head, spending $150,000 on overhead per head, and the “36% project margin” suddenly translates to less than 10% at the firm level.

The Deltek benchmark data confirms this pattern across the industry: revenue per consultant sits at $199,000, while EBITDA has dropped to single digits. The project-level numbers don’t lie, but they don’t tell the full story.

What Is Driving Overhead Growth?

Several forces are pushing firm-level costs up even as project execution improves.

Hiring ahead of demand. When pipeline looks strong, firms hire. But new hires take months to become fully billable. If the pipeline softens or projects get delayed, you carry those salaries at zero utilization. Deltek’s data shows headcount growth slowed sharply to 1.9% in 2024, down from 5.2% the year before, suggesting firms are feeling the cost of prior over-hiring.

On-time delivery is slipping. The same benchmark shows on-time project delivery fell to 73.4%, down from 80.2% in 2021. Project overruns rose to 11.3% in 2024 from 9.6% in 2023. Overruns don’t just hurt the overrun project’s margin. They cascade: the people who should be starting the next project are still finishing the last one. That delays the next engagement, extends the bench for the team waiting, and creates a ripple of non-billable time across the firm.

Administrative complexity grows with firm size. More clients mean more contracts, more invoicing, more compliance, more reporting. These back-office functions scale slower than delivery, and their cost per consultant creeps upward. When these processes depend on spreadsheets and manual workarounds, the overhead is even higher.

Non-billable roles multiply. Operations managers, project coordinators, internal IT, HR. As firms grow, the ratio of delivery staff to support staff can shift. Each additional overhead role needs to be funded by billable margins from an increasingly stretched delivery team.

How Do You Measure What Projects Don’t Show You?

Most firms track project margins religiously but have limited visibility into the overhead layer that determines what the firm actually keeps. These are the numbers worth adding to your reporting.

Revenue per consultant is the bridge metric. It combines utilization, billing rate, and bench time into a single number that reflects the firm’s actual earning power. When this number is declining while project margins are stable, you know the problem is between projects, not within them.

Overhead ratio per consultant reveals the cost side. Take your total non-project costs, including sales, operations, facilities, leadership, technology, and internal projects, and divide by headcount. Track this quarterly. If it is growing faster than revenue per consultant, your margins are eroding even if every project hits its target.

Utilization by category matters more than the top-line utilization number. Break utilization into: billable client work, presales and scoping, internal projects, administrative tasks, and unallocated bench time. Each category tells a different story. High presales utilization with low win rates signals a sales efficiency problem. High internal project utilization signals transformation overhead. High bench time signals a pipeline or staffing mismatch.

Time between projects is a metric most firms don’t track at all. How many days elapse between a consultant finishing one engagement and starting the next? Even three to five idle days per transition, across 50 people and ten transitions per year, adds up to 1,500 to 2,500 non-billable days. At $180 per hour, that’s $2.1 million to $3.6 million in absorbed cost annually.

Closing the Gap Between Project and Firm Profitability

Firms that convert good project margins into good firm-level results tend to operate a few ways differently from those that don’t.

They treat bench time as inventory cost, not an inevitability. Every day a consultant sits without a billable assignment has a dollar value. Tracking it, reporting it, and making it visible to leadership changes how the firm thinks about staffing decisions, pipeline management, and project scheduling.

They connect pipeline to capacity planning. The decision to hire, subcontract, or delay should be informed by real-time visibility into who’s available when, not by gut feel. When your pipeline data lives in a CRM and your staffing data lives in a spreadsheet, these decisions happen in a vacuum.

They standardize delivery to reduce project-level variance. When every project is delivered differently, the overhead of managing those projects grows. Standardized project intake, consistent milestone structures, and repeatable delivery frameworks reduce the management tax on each engagement. They also make project estimates more reliable, which reduces overruns.

They track the full cost of winning work. Presales time, proposal costs, and scoping effort should be visible at the firm level. If it takes 200 hours of senior consultant time to win a 500-hour engagement, your effective margin on that engagement is much lower than the project report shows.

They automate the back office. Invoicing, time approval, expense processing, client reporting. Every hour a billable consultant spends on admin tasks instead of client work is a direct hit to utilization. Every hour an operations person spends on tasks a system could handle is overhead that doesn’t need to exist. The goal is not eliminating people. It’s eliminating double entry, manual reconciliation, and process steps that add time without adding value.

Frequently Asked Questions

What is a good EBITDA margin for a professional services firm?

Healthy professional services firms typically target 15% to 20% EBITDA margins. According to Deltek’s 2025 benchmark, the industry average fell to 9.8% in 2024, well below the five-year average of 13.7%. Firms consistently above 15% tend to have utilization rates above 75% and strong overhead discipline, not just good project margins.

Why can project margins be high while firm profitability is low?

Project margins only measure direct delivery costs against revenue for a specific engagement. They exclude bench time, presales effort, administrative overhead, leadership costs, and internal projects. A firm can deliver every project at 35% margin and still lose money if these between-project costs consume the difference. The gap between project-level and firm-level profitability is the overhead layer.

What is billable utilization and what rate should a services firm target?

Billable utilization is the percentage of available working hours spent on billable client work. SPI Research identifies 75% as the threshold for healthy firms. The industry average sits below 69%, meaning roughly a third of available capacity isn’t generating revenue. Every percentage point of utilization improvement translates directly to revenue without adding headcount cost.

How do professional services firms reduce overhead costs?

Rather than cutting costs, the more durable approach is increasing the revenue-generating capacity of existing staff. That means reducing bench time through better pipeline-to-capacity alignment, automating administrative processes that consume billable hours, standardizing delivery to reduce management overhead, and tracking presales costs so you can improve win rates or reduce pursuit effort on low-probability deals.

What is the difference between PSA and ERP for services firms?

PSA (Professional Services Automation) focuses on delivery operations: resource management, time tracking, project billing, and utilization. ERP (Enterprise Resource Planning) covers the broader financial and administrative backbone: general ledger, accounts payable, HR, and consolidated reporting. Some firms use both, but an integrated system that connects delivery operations to financial management gives the clearest picture of where margin is leaking between the project level and the firm level.

How Tier2 Keel Connects Project Margins to Firm-Level Results

The gap between project profitability and firm profitability lives in the space between systems. When your project tracking, time management, billing, and financials operate in different tools, the overhead layer becomes invisible.

Tier2 Keel manages the full business lifecycle, from lead capture and scoping through project delivery, time tracking, invoicing, and financial settlement, in a single platform. The metrics that matter at the firm level, including revenue per consultant, overhead ratio, bench time, and presales cost, aren’t assembled from spreadsheet exports after the fact. They’re visible in real time, from the same system where delivery happens.

When a consultant finishes one engagement, the gap before their next project is tracked. When presales effort runs high on a pursuit, that cost is visible alongside the project margin if you win it. When internal projects consume delivery capacity, the impact on billable utilization surfaces immediately rather than showing up as a surprise in the quarterly P&L.

See how Keel handles full-lifecycle tracking or book a walkthrough.

The firms that close the margin gap aren’t the ones with the best project managers. They’re the ones who can see the full picture: what they earn on each project, what they spend between them, and where the difference goes.