How to calculate project margin in a studio

Your bank balance at the end of the quarter tells you the studio survived. It doesn't tell you which projects paid for the others. Project margin is the number that does — and you can know it for every project in real time, instead of reconstructing it months later.

What project margin actually is

Margin is what's left after paying for the time your team spent on the project.

Revenue is what the client pays: fixed price, or hours × rate. Team cost is the real cost of every hour your people spent on the project. The gap between them is the only number that tells you whether it was worth taking.

One important note: project margin is not studio profit. It's the gross margin of a specific project, before overhead, rent, and marketing. But it's where everything starts. If a project has no margin, nothing else matters.

Why the client rate is not your cost

The rate you bill the client is revenue, not cost. Your hourly cost is determined by salaries, not invoices, and is almost always lower than your rate — that's where the margin comes from.

This sounds obvious. But in practice, many studios use the client rate as a proxy for cost when estimating, then wonder why the numbers don't add up. Getting it right is a topic of its own: see how much a developer hour really costs.

What goes into team cost

This is where most studios make mistakes. They take the salary — and stop there. But that's not the cost, it's only part of it. Here's what to count:

• Every payroll hour on the project at its full cost — not the client rate. Full cost includes salary, employer taxes and contributions, and a share of overhead. The difference is usually 30–50%. The lower the team utilization rate (billable hours as a share of available hours), the higher the cost of each hour at the same salary.
• Overtime. The silent killer of margin. The hours happened, cost real money, and never made it into the estimate. A developer worked 20 extra hours — if they're not in the cost calculation, margin is inflated.
• Everyone who touched the project — PM, design, QA, not just developers. A PM hour on a client call costs money. A lead dev's code review too. A QA test before release too. If they're not in the calculation, the margin is fiction.

How project margin changes by contract type

With time-and-materials, margin is relatively predictable: every hour is billed to the client, and as long as the rate exceeds cost, the studio is in the black. Time overruns are automatically covered by additional invoices.

With fixed price, it's different. The price is set upfront, and the real cost only becomes clear at the end. Any overtime, untracked tasks, or scope expansion reduces margin — and the studio is the last to know. That's why fixed-price margin must be tracked throughout the project, not just at delivery. Understanding how much you actually earn per hour on a fixed-price project — your effective rate — is a topic of its own.

A worked example

Website redesign at fixed price:

Now run the same project at 360 hours due to unbilled overtime — cost rises to roughly $26,700, and margin drops to roughly $5,300 (17%). Same invoice — less than half the profit.

This shift is invisible until you count hours honestly.

More importantly: if you don't calculate by project, profitable ones will cover for unprofitable ones. The quarter closes in the black — and nobody knows that one project ate the margin of two others.

What's a healthy project margin

Benchmarks for dev studios and agencies:

• Below 20% — danger zone. Any time overrun or minor scope creep drives the project to zero or negative.
• 20–35% — the working range for most studios. Provides a buffer for overruns and covers overhead.
• 35%+ — good. Usually means rates are set correctly and the project was estimated with a buffer.

But it's not just the average that matters — the spread matters too. You need to see margin for every project individually.

Why the end-of-quarter spreadsheet fails

By the time timesheets are reconciled, the project is already shipped and the next fixed price has already been quoted from the same blind spot. Margin you learn about after the fact won't change your decision.

Here's what happens in practice. The project went negative in week six — but that's only visible a month and a half later when finance closes the period. All that time the team keeps working, overtime accumulates, the PM thinks they're on track.

The problem isn't the spreadsheet. The problem is the spreadsheet updates once a month. Retrospective margin changes nothing.

Margin is not a result — it's a tool

Why track margin during the project, not at the end?

To make decisions while they still matter. If margin drops below target in week three — you can renegotiate scope or talk to the client. If a project consistently comes out at 10% instead of 30% — that's a signal to revisit pricing or estimation. Without this number, running a studio means running on gut feeling.

Good margin on one project doesn't mean the others are profitable too. And the reverse — one unprofitable project can hide behind a good quarter until you look at the breakdown.

Where to start: the minimum setup

If you're currently tracking margin after the fact — or not at all — here's where to start.

• Step 1 — Calculate the full hourly cost for each team member. Salary + taxes + share of overhead, divided by actually billable hours per month. Without this number, everything else is guesswork.
• Step 2 — Track time by project. All participants, including PM and QA. Without honest hour tracking, the formula doesn't work.
• Step 3 — Track margin during the project, not at the end. At least weekly. This shows where you are now, not three months ago.
• Step 4 — React to deviations. Margin fell below target — that's a signal to investigate, not just a data point in a report.

How much work these steps require depends entirely on the tool. In a spreadsheet it's hours of manual work each week. In a system that connects time tracking to cost — it happens automatically.

AltOrbit tracks margin for you while the team logs time — see how it works. Now in early access.