Guide
How to Know if an Agency Project Is Profitable
A project can be fully paid, delivered on time, and the client happy—and still lose the agency money. This page is about reading the specific numbers that tell you, mid-project or after, whether that happened.
The question, precisely
“Was this project profitable” really means: did the revenue exceed the true cost of the hours it took to deliver, including the ones spent on revisions, internal reviews, and fixing mistakes, not just the hours in the original plan. This builds on how to track agency profitability, applied to one specific project rather than the whole agency.
Reading planned versus actual hours
Compare hours actually logged to the hours the project was quoted or budgeted for. A project running close to plan is a good sign, but check where the difference came from before concluding anything: hours over plan spent on legitimate scope, versus hours spent on unbilled extras, tell two very different stories even though the total looks the same.
Turning hours into a cost figure
Multiply actual hours by each person’s real cost rate, not their billing rate, to get the true cost of delivery. Compare that total to what the client actually paid. The gap is the project’s margin. A project can look fine on a billing-rate basis and still be unprofitable once cost rates are used instead—this is the single most common place the calculation goes wrong.
Accounting for scope changes
If the scope changed mid-project through a documented change order, compare actuals to the revised plan, not the original one— otherwise a properly billed scope increase looks like an overrun that was never actually a problem. If extra work happened without a change order, that unbilled time is a real cost the client never paid for, and it belongs in the analysis as exactly that.
When the answer is no
An unprofitable project is worth understanding, not just noting. Was it underpriced from the start, did scope creep go unrecorded, or did the work genuinely take longer than a reasonable estimate would have predicted? Each cause points to a different fix—better estimating, tighter scope discipline, or a pricing change for similar future work.
Common mistakes
Comparing actuals to the wrong baseline
Using the original scope as the baseline when a documented change order revised it produces a misleading overrun figure.
Only checking profitability at project close
By then nothing can be adjusted. A mid-project check leaves room to raise concerns with the client while the project is still live.
Not distinguishing billed extras from unbilled scope creep
Both show up as extra hours, but only one of them is actually a problem worth fixing.
Frequently asked questions
Can a project be profitable even if it ran over the original hours?
Yes, if the extra hours were billed through a documented change order that covered the additional cost.
What margin should a project target?
There is no universal target margin. What matters is knowing your own number consistently and reacting when a specific project falls well below it.
How soon should we know if a project is off track?
As early as the budget-vs-actual view shows meaningful drift, not only at the halfway point or the end.
Conclusion
Judging a single project’s profitability means comparing true cost, not billing rate, to what was actually paid, against the right baseline once scope changes are accounted for. Do the comparison while the project is live, not only afterward.
Find My Software Stack