What Is Project Margin?

Project margin is the profit left on an individual project after subtracting the direct costs of delivering it. For professional services firms, it's the project-level version of gross margin, measuring not just whether the business is profitable overall, but whether each engagement is contributing to or eroding the firm's profitability.

Formula: Project Margin (%) = (Project Revenue − Project Direct Costs) / Project Revenue × 100

A project billed at £60,000 with £39,000 in delivery costs has a project margin of 35%. This margin must cover the firm's overhead, non-billable time, and profit. It is the engine that makes the business financially viable.

How Project Margin Is Calculated

Project margin requires two clean inputs: what the project earns and what it costs to deliver.

Project Revenue: The fee received for the engagement. On a fixed-fee project, this is the agreed contract value (adjusted for change orders). On a time-and-materials project, it's the invoiced hours × billing rates.

Direct Project Costs: The costs attributable to delivering this specific project. Primarily: the labour cost of time spent on the project (hours × cost rates for each team member), plus any direct expenses,  subcontractor fees, specific software licenses, and travel. Excludes: firm overhead, management salaries, and office costs.​

The practical challenge is that calculating meaningful project margin requires accurate time tracking. Without reliable data on who worked how many hours on each project, direct costs are estimated rather than measured. Project margin then becomes a guess rather than a metric.

A project without tracked billable time ends up with a margin figure based on invoiced fees and averaged overhead allocation. This number obscures significant variation. For example, one project running at 20% margin and another at 50% average to 35%, but they need completely different management responses.

Why Project Margin Matters for Professional Services Firms

Firm-level gross margin is the average of every project's contribution. Improving that average requires knowing which projects are above it and which are below, and why​

For an agency or consultancy with 20–40 concurrent projects, project margin data does what instinct and experience can't. It reveals:

• Which clients generate disproportionate effort relative to fee
• Which service lines are structurally more or less profitable
• Which account managers consistently win work at sustainable margins (or below)
• Which project types by scope, complexity, or contract structure carry the most margin rise

Without project margin data, leadership makes resource, pricing, and client decisions based on revenue volume. This can lead to growing relationships and service lines that actually destroy value for clients who feel premium but require disproportionate senior time.

SPI Research data consistently shows that PS firms in the top quartile of financial performance track margin at the project level, not just at the firm level. The capability to measure project margin and to act on that data is a structural advantage.

Project Margin vs Gross Margin

Both measure profitability by comparing revenue to direct delivery costs. The difference is scope:

‍

‍

Project margin feeds gross margin. A firm with a 38% gross margin is averaging across projects ranging from 15% to 60% - the project-level view is where the opportunities for improvement lie.

‍

Examples in Practice

Example 1 - The unprofitable "good" client. A digital agency has three anchor clients, each generating £200,000+ in annual revenue. Project-level margin analysis reveals: Client A (42% average project margin), Client B (38%), Client C (17%). Client C is an enterprise brand - prestigious, large retainer, regular feature in the agency's credentials. But the project margin data shows they require disproportionate senior account management time, generate frequent scope-adjacent requests that are absorbed rather than billed, and have a change-heavy workflow that adds significant revision hours. The agency reprices at the next contract renewal and restructures the service model. Client C's project margin rises to 29%.​

Example 2 - Service line margin comparison: A management consultancy tracks project margins by service line over 18 months. Strategic advisory work averages 48% project margin. Implementation support averages 31%. Managed services retainers average 22%. The data informs a deliberate shift in new business focus toward advisory and a decision to price implementation work more aggressively at the next rate review.

Example 3 - Real-time margin intervention A 12-person engineering consultancy uses Magnetic to track project margin in real time. In week 6 of a 10-week engagement, the project margin dashboard shows the project tracking at 22% against a target of 38%. Investigation reveals that two phases took longer than estimated due to a client data quality issue. The project manager raises a change order for the additional time, documents the root cause, and flags it for the estimation database. The final project margin is 31% below target but materially better than the 22% projection.

Common Mistakes

Not tracking time accurately. Project margin calculated from estimated hours rather than tracked hours is useful at best, misleading at worst. The only way to know your true project margin is through reliable time data linked to project codes.

Excluding senior time from project costs. Directors and principals who contribute to projects — client calls, quality review, strategic input — incur cost. If their time isn't tracked against projects, project margin is overstated for every engagement they touch. This is common in smaller firms where senior staff see tracking their own time as optional.

Looking at project margin only at completion. Post-project margin analysis is useful for learning but does not protect the current engagement. Reviewing project margin weekly during delivery with a clear threshold for escalation prevents the "we lost money on that one" retrospective.

Conflating project margin with project success. A project that delivers outstanding client outcomes but runs at 15% margin has a problem. So does a project that hits 45% margin by delivering mediocre work that costs the client relationship. Project margin is a financial metric, not a quality metric. Both need to be tracked.