Most agencies discover a project was unprofitable after it has closed. The hours are logged, the invoice is paid, and the post-mortem reveals that the job made far less money than it looked like it would at proposal stage. By the time that information surfaces, there is nothing left to fix.
Project profitability tracking is the practice of measuring revenue against direct costs at the project level, in real time, while delivery is still happening. It turns a lagging indicator into a leading one. When you can see that a fixed-price project is tracking toward 20% margin instead of the 40% you priced in, you can act: renegotiate scope, adjust resourcing, or at minimum protect the learning for your next estimate.
This guide covers the formula, the costs that belong in the calculation, the benchmarks that matter, and how to build a reporting process that catches margin problems while there is still time to respond.
A healthy firm-level margin can mask a serious problem. An agency running at 18% net margin might have six projects generating 45% gross margin and three generating 5% or less. The aggregate number looks fine. The underlying mix is unsustainable.
According to the 2025 SPI Research Professional Services Maturity Benchmark, EBITDA across professional services firms fell to 9.8% in 2024, the lowest level in five years. At the same time, project-level gross margins reached 37.7%. The gap between those two numbers is the cost of running the business, but it is also where margin leaks hide when firms do not track at the project level.
Project-level tracking also gives you information that firm-level reporting never will: which client types are profitable, which service lines carry margin and which compress it, and which project managers consistently bring work in on budget. That insight informs pricing, sales strategy, and resourcing decisions in ways that monthly P&L review cannot.
A further problem with relying only on firm-level margin is timing. Monthly or quarterly financials tell you what happened. Project-level tracking tells you what is happening, while the project is still running and while you can still influence the outcome.
The core calculation is straightforward:
Project gross profit = Project revenue minus direct project costs
Project gross margin (%) = (Project gross profit divided by Project revenue) multiplied by 100
For example: a project billed at 50,000 with 28,000 in direct costs produces a gross profit of 22,000 and a margin of 44%. That is a healthy outcome. The same project with 38,000 in direct costs returns a 24% margin, which is technically profitable but may be below your target and worth understanding before you reprice the next similar job.
The formula is simple. The complexity is in the cost inputs. Getting those right is where most agencies struggle.
For tracking during a live project, you calculate the same formula against earned or accrued revenue rather than invoiced revenue. A project that is 60% complete on a 50,000 contract has earned 30,000. If you have spent 19,000 in direct costs to reach that point, you are running at 36.7% margin. Comparing that to your target margin tells you whether you are on track or burning faster than expected.
The accuracy of your project profitability number depends entirely on which costs you include. The following belong in your direct cost calculation:
Staff costs, fully loaded: This is the most significant cost for most agencies and the most frequently understated. Fully loaded means salary plus employer taxes, benefits, and any overhead allocation that reflects the true cost of employment. Some agencies use a simple cost rate per hour (annual cost divided by available hours). Others include an overhead loading factor. Either approach is valid as long as it is applied consistently.
Freelancer and contractor costs: Any external resource billed specifically to deliver this project should be included at the rate invoiced. Do not average these across projects.
Project-specific software and tools: Licenses or subscriptions purchased for a specific client or deliverable belong in the project cost. Shared tools used across your entire operation belong in overhead and should be allocated via your overhead loading factor, not charged directly.
Third-party production, media, and vendor costs: Pass-through costs like print production, paid media, photography, or specialist subcontractors should be tracked per project. Even if they are invoiced to the client at cost plus a handling fee, you need to see them in the margin calculation to understand true profitability.
What does not belong in project profitability: general overhead such as rent, utilities, and shared administrative costs. These are firm-level costs that sit below the gross profit line. Including them at the project level typically produces margin numbers that are too low and too variable to be actionable.
The single biggest driver of inaccurate project profitability is understated staff cost. An agency that uses salary-only cost rates rather than fully loaded rates will consistently overestimate margin by 20 to 40%.
Industry benchmarks vary by agency type and size. For digital and creative agencies, a 2026 review of agency profit margins found that the average digital agency after-tax net margin runs at approximately 13%, down from a long-run average of 15%. After-tax net margin and project gross margin are very different numbers: the project gross margin needs to be high enough to cover firm overhead and still deliver that net.
A workable framework for most agencies:
Target project gross margin of 40 to 50% for time-and-materials work. This is the number after direct staff and delivery costs but before firm overhead.
For fixed-price work, target 35 to 45%. Fixed-price projects carry more risk because cost overruns compress margin directly. Pricing them at a higher target helps absorb the variance.
Project margins below 25% are a signal worth investigating. They may reflect pricing problems, scope bleed, resourcing inefficiencies, or a misaligned service offering. They are not automatically a crisis, but they need an explanation.
One additional benchmark to track alongside project margin is your win rate on estimates. If you consistently price at 40% margin but lose projects that go to cheaper competitors, you are learning something about your market position that pure profitability data will not show you.
Margin erosion during delivery follows recognisable patterns. Understanding where the bleed typically occurs helps you set up the right checkpoints.
Scope creep that does not get billed: The most common cause of project margin loss. Work expands through additional rounds of revision, extended stakeholder feedback, or client requests that fall just within a grey area of the brief. Each event individually seems too small to raise a change request for. Collectively they can add 15 to 25% to the cost of delivery with no corresponding revenue.
Underestimated time at proposal stage: Proposals are often written optimistically, especially for work that is complex to scope or that has dependencies on client-side delivery. When the estimate is too low, there is no way to recover margin without either cutting corners or having a commercial conversation. The best mitigation is tracking estimate accuracy over time, by project type and by the person who wrote the estimate.
Senior resource on junior tasks: When a senior person covers a gap because a junior team member is unavailable or the project gets reprioritised, you are billing junior rates while incurring senior costs. This is one of the most margin-compressing dynamics in agency delivery and one of the hardest to see without good resource visibility.
Low utilization on key resources: A project that has a senior developer allocated but only billing 50% of their time to it is carrying a cost that is not being recovered. This connects directly to billable utilization as a driver of both project and firm-level profitability.
Late-stage rework: Rework that happens in the final third of a project is the most expensive kind. The core work has already been completed, the team has moved on mentally, and the additional time comes at a moment when the project budget is already largely consumed. Building explicit revision limits into contracts reduces the frequency of late-stage rework.
The goal is a consistent review cadence that catches margin problems during delivery, not after the invoice. Here is a practical structure for agencies that do not already have one in place.
Before any work begins, every resource allocated to the project should have an internal cost rate attached. This is the fully loaded hourly cost of that person. Once the cost rates are set, you have the denominator that makes all project tracking meaningful.
A weekly project profitability review does not need to be long. The project manager should look at three numbers: hours logged against hours budgeted, current margin versus target margin, and percentage of project complete against percentage of budget spent. Any project where budget spent is running ahead of completion percentage by more than 10 points warrants attention.
Green: on track for target margin within 5 percentage points. Amber: margin trending 5 to 15 points below target, requires a plan to recover. Red: margin trending more than 15 points below target, or project is loss-making, requires an escalation and a decision: renegotiate, cut scope, or accept and learn.
Manual profitability calculations from spreadsheets are slow and prone to error. The data needs to flow: time tracking connects to cost rates, which connects to project budgets, which connects to a margin view updated in real time. The project management tools that support this end-to-end flow are the ones worth investing in.
A final project review, done within two weeks of closure, should compare the estimate to the actual outcome across hours, costs, and margin. The goal is not blame. It is to improve the accuracy of future estimates and to identify systemic patterns: the type of work that consistently runs over, the clients who generate the most revision cycles, the service lines that look profitable in proposals but rarely are in delivery.
Pike is built for agencies and consultancies that want project profitability visibility without the spreadsheet overhead. Time logged by the team flows directly into cost calculations, so your margin view is always current. See how it works.
Most agencies target 35 to 50% gross project margin, measured as gross profit divided by project revenue. Creative agencies tend to operate at the lower end of that range. Management consultancies and strategy firms often target 45% and above. What matters most is that your project margin is high enough, after firm overhead, to deliver the net profitability your business needs to grow. A useful starting point is to work backward from your target net margin and overhead cost to calculate the minimum project margin required.
Project profitability measures the gross margin generated by a single project: revenue minus the direct costs of delivering that project. Agency profitability is the firm-level view: gross profit from all projects minus overhead costs like rent, administration, shared tooling, and management. A firm can have healthy project margins and poor firm-level profitability if overhead is too high. Conversely, a firm can show decent firm-level margins even when individual projects are underperforming, if the winners are large enough to carry the losers.
Weekly is the right cadence for active projects. A brief check of hours logged versus budget consumed, and current margin versus target, takes less than ten minutes per project and surfaces problems early enough to act on them. Monthly reviews are useful for trend analysis and portfolio-level insights, but they are too infrequent to catch margin erosion in real time. Post-project reviews should happen within two weeks of every project closing, while the context is still fresh.
General overhead like rent, shared software, and administrative costs should not sit in the direct project cost line. They belong below the gross profit line as operating expenses. Including them at the project level produces margin numbers that are too variable to benchmark meaningfully and often too low to motivate the team. That said, staff cost rates should include a loaded overhead factor to reflect the true cost of employing that person, which is different from allocating general overhead directly to projects.
If your projects feel profitable but the numbers at month end tell a different story, project-level tracking is usually where the answer lives. Book a free demo to see how Pike helps agencies track project profitability in real time: book a free demo.
