Project profitability is the difference between what a project earns and what it costs to deliver. A project can finish on time, the client can be satisfied, and the team can still have lost money. Usually it’s because scope crept, hours were underestimated, or billing rates didn’t match actual effort.
For professional services firms, profitability varies significantly between projects, even with the same client. Company-level revenue hides this. A profitable quarter can be driven by two strong engagements while three others quietly drain margin. Tracking at the project level is the only way to see which work is actually worth doing.
Below are the five metrics that give you that picture: what each one measures, how to calculate it, what a healthy number looks like, and what to do when it isn’t.
Quick reference
| Metric | What it measures | Formula |
|---|---|---|
| Utilization rate | Billable time as a share of total available time | Billable hours ÷ Total available hours × 100 |
| Project overrun | How far actual cost exceeded the estimate | (Actual cost − Estimated cost) ÷ Estimated cost × 100 |
| Project margin | Net profit as a percentage of project revenue | (Revenue − Total costs) ÷ Revenue × 100 |
| Revenue per billable employee | Average financial output of client-facing staff | Total revenue ÷ Number of billable employees |
| Revenue per employee | Average financial output across all headcount | Total revenue ÷ Total headcount |
1. Utilization rate
Utilization rate is the share of your team’s working hours that goes to billable client work, expressed as a percentage.
Formula
Example: An employee works 160 hours in a month and logs 112 billable hours. Their utilization rate is 112 ÷ 160 × 100 = 70%.
Benchmark
According to the 2024 SPI Professional Services Maturity Benchmark, industry-average billable utilization sits at 70.7%. Top-performing firms target 80% or higher.
Why it matters
Non-billable time is unavoidable: admin, internal meetings, training, proposals. The problem is when it goes untracked, so no one knows how much of it there is. A team with measured utilization below 60% is either overstaffed or absorbing significant unbilled work that isn’t showing up anywhere.
What to do with it
Calculate utilization by person and by project type. A senior consultant at 55% is a different problem from a junior employee at 55%. One signals misallocation; the other may point to inefficient task assignment. Utilization also helps with staffing decisions: before hiring, check whether the team is consistently above 80%. If it is, you’re at capacity. If it’s sitting at 65%, you likely have room.
2. Project overrun
Project overrun measures the percentage by which actual project cost exceeded the planned estimate.
Formula
Example: A project budgeted at $50,000 ends up costing $62,000 to deliver. The overrun is ($62,000 − $50,000) ÷ $50,000 × 100 = 24%.
Industry context
54% of organizations with low project management technology maturity report going over budget on projects, according to the Wellingtone State of Project Management Report.
Why it matters
A single 20% overrun on a fixed-fee project can erase the entire margin. The metric is most useful tracked across projects over time. Patterns tell you whether the problem is estimation, a specific project type, a specific client, or a specific delivery phase.
What to do with it
Compare overrun rates by project category. If IT implementation projects consistently run 15–20% over while audit engagements don’t, the issue is probably the estimation process for that category, not execution quality. Use the historical overrun average as a contingency factor when pricing new work of the same type.
3. Project margin
Project margin is net profit expressed as a percentage of project revenue. It’s the direct measure of whether a project made money.
Formula
Example: A project billed $80,000 and cost $58,000 to deliver (labor, overhead, direct expenses). Project margin = ($80,000 − $58,000) ÷ $80,000 × 100 = 27.5%.
Benchmark
Consulting and agency work typically targets 20–40% gross margin. Under 15% is a warning: either the project was underpriced, scope was not controlled, or costs ran higher than expected. Comparing margin across projects of the same type shows which clients and engagement structures are consistently profitable.
Why it matters
Revenue without margin context is misleading. A firm billing $2M a year at 8% margin is in a worse position than one billing $1.2M at 32%. Project margin tells you where to focus business development and which types of work to reprice or deprioritize.
What to do with it
Sort your last 12 months of projects by margin. Look at the bottom 20%: were they underpriced from the start, or did costs run over? The answer determines whether the fix is better estimation, tighter scope control, or not taking that type of work again.
4. Revenue per billable employee
This metric divides total revenue by the number of employees who do billable client work. It measures the average financial output of your revenue-generating staff.
Formula
Example: A consulting firm generates $3.6M in revenue with 18 billable staff. Revenue per billable employee = $3.6M ÷ 18 = $200,000.
Why it matters
Comparing this figure to the average labor cost of your billable staff gives you a quick read on whether the firm generates enough revenue to justify its people costs. If revenue per billable employee is $180,000 and average fully loaded employment cost per billable employee is $140,000, you’re operating on thin margins before overhead.
What to do with it
Track this year over year. A declining number with stable headcount means rates are dropping, utilization is falling, or both. Rising revenue per billable employee is one of the clearest signs that a professional services business is gaining leverage over time.
5. Revenue per employee
This metric divides total revenue by total headcount, including non-billable staff: management, operations, finance, HR. It measures the overall financial productivity of the business.
Formula
Example: The same firm with $3.6M revenue and 24 total employees (18 billable, 6 support) generates $3.6M ÷ 24 = $150,000 revenue per employee.
Why it matters
The gap between revenue per billable employee and revenue per total employee reflects the cost of administrative overhead. A wide gap means a large support function relative to delivery staff. That’s sometimes necessary, but it’s worth watching as the business scales. Support headcount that grows faster than billable headcount will compress overall margins even when delivery is running well.
What to do with it
If the two figures are close, you have a lean support structure. If revenue per total employee is significantly lower than revenue per billable employee, your overhead ratio may be limiting profitability even when project-level margins look healthy.
How to track these metrics in practice
Calculating all five metrics requires two data sets: time records (who worked on what and for how long) and financial records (billing rates, cost rates, revenue per project). When these live in separate systems, the numbers lag, or don’t get calculated at all.
actiTIME connects time tracking directly to cost of work and billing, so utilization figures and project margin update automatically as hours are logged. The Profit/Loss Report shows revenue vs. costs by project and customer, with overtime and leave time included, removing the manual reconciliation step that delays most profitability reviews.
Frequently asked questions
How do you calculate project profitability?
Revenue minus total project costs. Costs include labor (tracked hours × hourly cost rate), overhead allocations, subcontractor fees, and direct expenses. Dividing net profit by revenue gives project margin as a percentage, which is easier to compare across projects of different sizes than a raw dollar figure.
What is a good project margin for professional services?
Consulting and agency work typically targets 20–40% gross margin. Under 15% is a warning that either pricing is too low or costs ran over. The benchmark matters less than the trend: if margin is shrinking project by project with the same client, something is worth investigating.
How often should you review project profitability?
Three points matter: at kickoff to pressure-test the budget estimate, at the midpoint to catch overruns while there’s still time to act, and at close to calibrate future pricing. For ongoing retainers, monthly reviews are standard.
What’s the difference between project margin and utilization rate?
Margin measures the financial result of a specific project. Utilization rate measures how much of the team’s available time is billable versus absorbed by non-billable work. You need both: high utilization with shrinking margins usually means billing rates are too low or costs are rising quietly.
Why do projects lose money even when delivered on time?
Most often it’s additional work absorbed without a budget adjustment (scope creep), a fixed-fee contract where hours exceeded the estimate, or non-billable time logged against project tasks without anyone noticing. Comparing planned vs. actual hours at the task level shows exactly where the overrun happened.
What tools help track project profitability?
Any tool that connects time tracking to cost rates and billing data can calculate these metrics automatically. The key is having both sides of the equation in one place: hours logged and rates applied, so margin figures don’t need to be assembled manually after the fact. actiTIME does this through its Cost of Work and Profit/Loss Report features.
