Project profitability: a worked example for agency owners

A project can finish on time and still consume more effort than its price supports. To understand the result, start with the revenue for the project and the direct cost of delivering it. Time records connect the work to labor cost, which is often a major part of agency delivery.

This is an illustrative management calculation, not a financial reporting policy. Define your cost categories consistently before comparing projects.

Begin with a clearly defined project margin

For the examples below, project contribution equals project revenue minus direct delivery cost. Direct delivery cost includes the labor assigned to the project and project-specific outside costs. It excludes general overhead.

Project contribution = revenue − direct delivery cost.

Project contribution margin = project contribution ÷ revenue × 100.

This is not necessarily company net profit. Rent, general software, sales time, and other overhead may still need to be covered by the contribution left over from projects.

A worked fixed-fee example

Consider a website project with an $8,000 fee. Design takes 35 hours at an illustrative internal cost of $50 per hour. Development takes 45 hours at $60 per hour. Project management takes 10 hours at $45 per hour. The project also uses $400 of outside services.

• Design cost: 35 × $50 = $1,750.
• Development cost: 45 × $60 = $2,700.
• Project management cost: 10 × $45 = $450.
• Outside services: $400.
• Total direct delivery cost: $5,300.

The resulting project contribution is $8,000 − $5,300 = $2,700. The contribution margin is $2,700 ÷ $8,000 × 100 = 33.75%, before the overhead excluded from this example.

Use a cost rate, not the client billing rate, to calculate labor cost. Decide whether that cost rate includes employer costs or other allocations, document the choice, and keep it consistent. Changing the definition midway through a comparison changes what the number means.

Compare actual effort with the estimate

Suppose the original estimate assumed 25 design hours, 40 development hours, and 10 project management hours, with the same cost rates and outside services. Estimated direct cost was $4,500, leaving an estimated contribution of $3,500, or 43.75%.

The actual result is $800 below that contribution estimate. The difference comes from 10 additional design hours at $50 and five additional development hours at $60. That breakdown gives the project review somewhere concrete to start: what caused those extra hours?

Look for additional scope, a missed dependency, revision cycles, or an estimate that left out necessary work. The number alone cannot tell you which explanation is correct.

Check effective hourly revenue alongside margin

Effective hourly revenue = project revenue ÷ project delivery hours.

The actual project took 90 hours, so $8,000 ÷ 90 is approximately $88.89 per delivery hour. This is revenue per hour, not profit per hour. It does not deduct labor or outside services.

Effective hourly revenue helps compare fixed-fee engagements with similar cost structures. Margin answers a different question by including costs. A project with a higher effective rate can still leave less contribution if its delivery costs are much higher.

Forecast before the project ends

Do not wait for final delivery to look at the economics. Combine cost incurred so far with an estimate of the remaining work. If the forecast exceeds the original budget, decide whether to change scope, adjust staffing, or discuss a change request where the agreement allows it.

For example, after $3,000 of delivery cost, an expected $2,800 remaining cost predicts a $5,800 total. On an $8,000 fee, that implies $2,200 contribution, or 27.5%. The forecast is useful precisely because there is still time to respond.

Make the next estimate better

Keep all delivery time in the record, including nonbillable revisions. Review the result by activity, capture what was missing from the estimate, and reuse that learning on the next comparable project. Avoid treating one unusual engagement as a universal pricing benchmark.

Consistent inputs matter more than a complicated dashboard. Establish a weekly time review, distinguish billable duration from billing rules, and keep your cost definition visible when sharing the result.

Try the numbers yourself

Open the free project profitability calculator with the same $8,000 example. Change actual and estimated hours by role, internal cost rates, and direct outside or AI costs. The results show contribution before overhead, contribution margin, effective hourly revenue, and cost overrun. Download the values as a CSV worksheet for your next review.

For this example, an extra five development hours at $60 per hour adds $300 of cost. Contribution falls from $2,700 to $2,400 and margin from 33.75% to 30%. That makes the impact of a revision concrete without assuming that reducing time is always the right decision.

Connect the calculation to your time records

In TrackTimer, keep billing rates and team pay rates separate, record delivery work against the right project, and include nonbillable effort. An administrator can review agency analytics by client, project, and team member. Billable value minus recorded team pay provides a view of gross profit from those records; it is not the same as the fixed-fee contribution model above and does not automatically include every outside expense or company overhead item.

Use the calculator for the fixed fee and additional costs, and use reviewed time records as evidence for the hours. The current product should not be treated as a general ledger or as proof of collected revenue. For hourly invoicing, follow the time-to-invoice workflow.