Project profitability for agencies: complete guide

Project profitability for agencies is the margin a single project earns after the direct costs of delivering it. It is the clearest measure of whether the work you sell actually makes money, and it is where most agency margin is won or lost. A firm can grow revenue and headcount every year while individual projects quietly slip below the margin they were priced at.

This guide is the hub for the topic. It covers what project profitability is, the formula and the costs that belong in it, the metrics that predict margin before the invoice goes out, where margin leaks, and the levers that protect it. Each section points to a deeper post when you want the full treatment of one part.

What project profitability is and why agencies miss it

Project profitability is project revenue minus the direct cost of delivering that project, expressed as a margin. It answers one question: after you pay for the people and resources that did the work, how much of the fee did you keep?

Agencies miss it for a structural reason. Most financial reporting happens at the firm level and after the fact. The monthly profit and loss statement tells you what the whole business earned last month. It does not tell you that three of your twelve active projects are running below cost right now. A healthy firm-level margin can hide a portfolio where strong projects subsidise weak ones, which means the problem stays invisible until a slow quarter removes the subsidy.

The second reason is timing. Project profitability only helps if you can see it while the project is still running. Once the work is delivered and the invoice is paid, the number is history. You can learn from it for the next estimate, but you cannot recover the margin. The agencies that treat project profitability as a live number rather than a post-mortem are the ones that catch a slipping project while there is still scope to renegotiate, reassign, or reset expectations.

The third reason is data. Calculating project profitability accurately means connecting time logged, cost rates, and revenue for each project. When those live in separate tools, assembling the number is a manual job that most teams do quarterly at best. The mechanics of doing it well are covered in the companion how-to on tracking project profitability for agencies.

There is also a simpler reason worth naming. Project profitability feels like a finance responsibility, so it often sits with whoever owns the accounts rather than with the people running delivery. By the time finance closes the month, the project managers who could have changed the outcome have moved on to the next job. Profitability improves fastest when the number is owned by the person accountable for the work, updated as the work happens, and read as a delivery signal rather than a quarterly finance output.

The formula and what belongs in cost

The formula is simple. Project gross profit is project revenue minus direct project costs. Project gross margin is gross profit divided by revenue, multiplied by 100. A project billed at 50,000 with 28,000 of direct costs earns 22,000 of gross profit and a 44% margin.

The formula is not where agencies go wrong. The cost inputs are. The single biggest driver of an inaccurate profitability number is understated staff cost, because staff time is the largest cost on almost every agency project and the easiest to under-count.

What belongs in direct cost:

• Fully loaded staff cost. Not just salary, but salary plus employer taxes, benefits, and an overhead loading that reflects the real cost of employing the person. Salary-only cost rates make every project look more profitable than it is.
• Freelancer and contractor cost, at the rate you were invoiced, charged to the specific project they worked on.
• Project-specific software, licences, or tools bought to deliver one client or deliverable.
• Third-party production and vendor costs, such as print, paid media, or specialist subcontractors, even when they are rebilled to the client.

What does not belong in direct cost is general overhead: rent, utilities, shared administration, and tools used across the whole firm. Those sit below the gross profit line as operating expenses. Pushing them into individual projects produces margin numbers that swing too much to act on. The full breakdown of which costs count, with the loaded-rate logic, is in the project profitability tracking guide.

The metrics that predict project profitability

Project margin is a lagging number. It tells you the result. Three operational metrics move earlier and let you predict where margin is heading: billable utilisation, effective hourly rate, and the wider set of agency KPIs that connect delivery to money.

Billable utilisation is the share of your team's available hours that go to billable client work. It predicts profitability because unbilled capacity is a cost with no revenue against it. A project with a senior person allocated but billing only half their time to it is carrying cost it is not recovering. Utilisation also warns in the other direction: a team running above 90% for months is usually heading toward burnout or hiding untracked hours. The benchmarks by role, and how to lift the number without exhausting the team, are in the guide on billable utilisation rate.

Effective hourly rate is total revenue on a piece of work divided by the total hours actually worked on it. It is the most honest cross-model measure of profitability because it works the same for fixed-fee, time-and-materials, and retainer work. A project quoted at an implied 150 per hour that took twice as long has an effective rate of 75, and if your blended delivery cost is near that number, the margin you thought you had is gone. The formula and a worked example are in the post on effective hourly rate.

Beyond those two, a small set of ratios predicts firm and project health together: realisation rate, gross margin, revenue per employee, and revenue leakage among them. The full set, with formulas and benchmark ranges, is in the guide to the agency KPIs that predict profitability. The point of tracking ratios rather than totals is that ratios reveal efficiency, and efficiency is what margin is made of.

Where agency margin leaks

Margin rarely disappears in one large decision. It leaks through small ones that each feel too minor to bill or flag, and that compound across a project. The most common leaks are consistent enough to plan for.

Scope creep is usually the largest. Extra revision rounds, small client requests inside the grey area of the brief, and favours to keep the relationship warm each add cost without adding revenue. Individually they seem trivial. Together they can add 15 to 25% to the cost of delivery. The practical fix is a change process that turns scope changes into billable change orders instead of absorbed work.

Unlogged time leaks twice. Hours worked but never recorded cannot be billed now, and they also corrupt your cost data, so you under-scope the next similar project and repeat the loss. Under-scoping at proposal stage leaks from the moment the quote is signed, because the fee never covered the real work. Write-offs and discounts, missed reimbursable expenses, and late or missed invoicing round out the pattern.

These leaks share a property: they are invisible on standard financial reports, which show what you billed rather than what you could have billed. Making them visible is the whole game. The seven places margin disappears, and how to close each one, are covered in the guide to revenue leakage in agencies. Scope creep specifically often traces back to budget discipline, which is why real-time project budget tracking catches it earlier than a month-end review does.

The levers that protect margin

Four levers move project profitability: pricing, scope control, resourcing, and billing model. Each one connects to a metric you can watch and a deeper post that treats it in full. The table below is the map for the rest of this cluster.

Pricing is the first lever because it sets the ceiling. If a project is underpriced, no amount of delivery discipline recovers the margin. The right test is not your rate card but your effective rate against your blended delivery cost. When effective rate sits comfortably above cost across a project type, the pricing is working. When it does not, you are learning which work to reprice or stop selling.

Scope control is the lever that protects the price you set. A tightly scoped project with a documented change process keeps the margin you quoted. A loosely scoped one gives it away one small request at a time. Watching realisation rate and revenue leakage tells you whether scope is holding. The mechanism that keeps scope control working is boring on purpose: a written scope, a change process everyone actually uses, and a habit of pricing changes as they arrive instead of absorbing them to keep the peace.

Resourcing decides how much of your capacity turns into revenue and at what cost. Two dynamics matter most. Putting a senior person on junior tasks bills junior rates while incurring senior cost, which compresses margin directly. Leaving capacity idle between engagements wastes cost you are already paying for. Better pipeline visibility and allocation keep utilisation healthy without overloading anyone, which is the subject Pike's resourcing features are built around.

Billing model is the lever agencies think about least and that often matters most. The same rate card produces different margins under time-and-materials, fixed fee, retainer, and value-based pricing, because each shifts delivery risk differently. Fixed fee rewards efficiency and punishes scope creep. Retainers give predictable revenue and invite scope expansion. The full comparison of how each model shifts risk and when to use it is in the guide to agency billing models, and the specific discipline that keeps recurring work profitable is in the guide to retainer management.

How often to review profitability

Review project profitability weekly for active projects and run a structured post-project review within two weeks of every job closing. Weekly is the cadence that catches margin erosion while you can still act on it. Monthly reviews are useful for portfolio trends but too slow to save a project that is burning ahead of plan.

A weekly review does not need to be long. For each active project, the project manager looks at three numbers: hours logged against hours budgeted, current margin against target margin, and percentage of budget spent against percentage of work complete. Any project where budget spent is running more than about ten points ahead of completion warrants a closer look. A simple red, amber, green status on each project makes the portfolio readable at a glance and turns the review into a short decision meeting rather than a data-gathering exercise.

The post-project review closes the loop. Comparing the estimate to the actual outcome across hours, cost, and margin is how estimates get more accurate over time and how you spot systemic patterns: the work type that always runs over, the clients who generate the most revision cycles, the service lines that look profitable at proposal and rarely are in delivery. The point is not blame. It is a better next estimate.

The reason most agencies do not review weekly is effort rather than willingness. When time, cost rates, and budgets live in separate tools, a live margin view is a manual assembly job nobody wants to do every week. When they are connected, the number updates as the team logs time, and the weekly review becomes a glance rather than a project. Pike's finance features exist to make that view live, so margin, utilisation, and budget burn come out of the system instead of a spreadsheet. If you want to see the whole approach in one place, start with the project profitability tracking guide and the agency KPIs guide, then check pricing when you are ready to try it.

Frequently asked questions