How to Measure Project Profitability at a Professional Services Firm

Project profitability is the revenue a project generates minus the full cost of delivering it — labor, subcontractors, and direct expenses — expressed as a dollar amount or a margin percentage. It answers the question a firm-level profit and loss statement cannot: which engagements make money, which lose money, and why.

Most services firms know their overall profit. Far fewer can say which of their twenty active projects produced it — and in almost every firm that measures for the first time, a handful of engagements turn out to be subsidizing the rest. This guide covers the formula, the two rates you need to understand it (utilization and realization), how to compute fully-loaded labor cost, the mistakes that hide losing projects, and a monthly review cadence that takes less than an hour once the data is in place.

The project profitability formula

The formula itself is simple:

Everything difficult about project profitability lives inside those two inputs:

• Project revenue is what the client actually pays for the engagement — not the proposal value, not standard rates times hours, but recognized revenue net of discounts and write-offs. On fixed-fee work it is the contracted fee; on retainers it is the portion of the retainer earned by the project in the period.
• Direct project costs are every cost that exists because the project exists. The dominant component is labor: every hour anyone worked on the engagement — billable or not — multiplied by that person's fully-loaded hourly cost. Then add subcontractors and freelancers, project-specific software or data, travel, and any pass-through costs not rebilled to the client.
• What to leave out: general overhead like rent, admin salaries, and marketing. Keep project margin as a clean gross margin so projects are comparable to each other; overhead gets absorbed at the firm level. Most healthy services firms target project-level gross margins of 30 to 50 percent on this basis.

Two practical requirements make the formula work: everyone tracks time to projects (including partners, and including non-billable project time like rework and internal meetings about the client), and your accounting is structured to capture costs by project. If your chart of accounts and time data cannot support this, that is a systems problem to fix first — it is one of the most common gaps we close for professional service firms.

Utilization rate vs. realization rate

Project margin tells you the outcome. Utilization and realization tell you the cause. They are frequently confused, and the distinction matters because they fail in different ways.

Utilization rate is the percentage of a person's available time spent on billable work:

Realization rate is the percentage of the standard value of work performed that is actually billed and collected:

The two rates diagnose different diseases. Low utilization means you are paying for capacity nobody is buying — a sales, staffing, or bench problem. Low realization means the work is being done but not converted to cash at full value — a pricing, scoping, discipline, or collections problem. A firm can run 85 percent utilization and still lose money if realization is 60 percent: everyone is busy, and the firm is effectively donating a third of its work.

Measured together at the person, project, and firm level, these two rates explain most margin surprises before the profit and loss statement does.

Fully-loaded labor cost

Fully-loaded labor cost is the true cost per working hour of each person: base salary plus payroll taxes, benefits, bonuses, and (optionally) an overhead allocation, divided by realistic annual working hours.

Three rules keep this honest:

• Use a load factor, not base salary. Payroll taxes, health insurance, retirement match, and bonuses typically push true cost to 1.25–1.4× base salary. Costing projects at base salary understates labor cost by 25–40 percent and flatters every margin in the firm.
• Divide by realistic hours. Nobody works 2,080 productive hours. After holidays, paid time off, and internal time, 1,800–1,950 working hours is a realistic denominator for most roles. Using 2,080 quietly understates hourly cost.
• Be consistent about overhead. Either allocate overhead into loaded rates for everyone or for no one. Mixing approaches makes projects incomparable. The simpler convention — loaded labor without overhead, overhead absorbed at the firm level — works well for most firms.

Common mistakes that hide losing projects

When firms measure project profitability and get numbers that feel wrong — or comfortably, suspiciously right — it is usually one of these:

• Ignoring bench time. If unassigned time simply disappears from the analysis, the projects you do measure look artificially cheap because idle capacity is free in the model and expensive in reality. Track bench time explicitly as its own category. It does not belong to any single project, but it must be visible, because the fix — better pipeline, better staffing, or smaller team — is a management decision someone has to own.
• Not counting unbilled scope creep. The extra revision round, the "quick call" that became a workstream, the deliverable added mid-project without a change order. If those hours are worked but never logged to the project — or logged and written off without being counted — the project's reported margin is fiction. Log all hours to the engagement that caused them, at full value, and let realization show the gap. Scope creep you can see is a client conversation; scope creep you cannot see is a silent margin leak.
• Blended rates hiding the losers. Costing every hour at one firm-wide average rate makes partner-heavy projects look cheaper than they are and junior-heavy projects look more expensive. The distortion runs in both directions: the average hides which engagements depend on your most expensive people. Use person-level (or at least role-level) loaded costs.
• Measuring only at project close. A post-mortem on a finished fixed-fee project tells you what you already cannot change. Comparing budget consumed against percent complete monthly — while staffing and scope can still be adjusted — is what makes the measurement worth doing.
• Confusing invoiced with collected. A project is not profitable until the cash arrives. Slow-paying clients and quiet write-offs at collection time belong in realization, not in a footnote.

A simple monthly review cadence

Project profitability is not a one-time analysis; it is a habit. Here is a cadence that works for firms from a few people to a few dozen, and takes under an hour a month once the data flows automatically:

• Monthly, within two weeks of month-end: review a one-page view of every active project showing revenue to date, loaded cost to date, margin percent, budget consumed vs. estimated percent complete, and unbilled hours. Flag anything with margin below your floor or budget burn ahead of completion. Alongside it, review utilization and realization by person.
• For each flagged project, ask three questions: Is this a scoping problem (we sold it too cheap), a delivery problem (we are overservicing), or a billing problem (we are not invoicing what we deliver)? Each has a different owner and a different fix — repricing at renewal, restaffing or a change order, or tightening the invoicing process.
• Quarterly: roll the same data up by client and by service line. Individual projects can be noisy; a client whose engagements are consistently below-margin for three quarters is a pricing conversation. A service line that persistently underperforms is a strategy conversation.
• Annually: refresh loaded cost rates after compensation changes, revisit standard billing rates against realized rates, and reset utilization targets against the coming year's capacity plan.

The prerequisite for all of this is an accounting and time-tracking setup that produces project-level data as a byproduct of normal operations — not a spreadsheet someone rebuilds by hand every quarter. If the monthly close does not already deliver margin by project, that is the place to start, and it is exactly the kind of infrastructure we build for professional service firms.

Frequently asked questions

Q: How do you calculate project profitability?

A: Project profitability is calculated as project revenue minus project costs, expressed as a margin: project margin percent equals project revenue minus direct project costs, divided by project revenue, times 100. Direct project costs should include fully-loaded labor for every hour worked on the project — including unbilled hours — plus subcontractors, project-specific software, travel, and any other direct expenses. Healthy project margins at professional services firms typically run 30 to 50 percent before overhead.

Q: What is the difference between utilization rate and realization rate?

A: Utilization rate measures how much of a person's available time is spent on billable work: billable hours divided by available hours. Realization rate measures how much of that billable work actually turns into collected revenue at full value: amount collected divided by the standard value of the hours worked. Utilization answers whether your people are busy on client work; realization answers whether that work is being billed and paid at full rates. A firm can have excellent utilization and still lose money if realization is poor.

Q: What is a fully-loaded labor cost?

A: Fully-loaded labor cost is the true hourly cost of an employee, including salary, payroll taxes, benefits, bonuses, and an allocation of overhead, divided by the hours they actually work. A common shortcut is that fully-loaded cost runs 1.25 to 1.4 times base salary before overhead allocation. Using base salary alone understates project costs by 25 to 40 percent or more, which makes marginal projects look profitable when they are not.

Q: What is a good project margin for a consulting or professional services firm?

A: Most healthy professional services firms target project-level gross margins of 30 to 50 percent, measured on fully-loaded direct labor and direct costs. After overhead, firm-level operating margins of 15 to 25 percent are common targets. Margins vary by discipline and pricing model — high-expertise advisory work often runs higher, while staffing-heavy or pass-through-heavy work runs lower — so the trend on each engagement matters more than any single benchmark.

Q: How often should a services firm review project profitability?

A: Monthly. A practical cadence is to review each active project's margin, budget consumed versus percent complete, and unbilled work within two weeks of month-end, alongside utilization and realization by person. Quarterly, roll the same view up to the client and service-line level to spot patterns. Reviewing only at project close means every lesson arrives too late to change the outcome.

This article is for informational purposes only and does not constitute legal, tax, or financial advice. Osprey CFO is not a tax firm and does not provide tax preparation or tax advisory services. Consult with qualified professionals for guidance specific to your firm and situation.