Most architects can feel when a project loses money. What they usually cannot do is say exactly why. The fee looked fine at the start, the work got done, and yet the profit evaporated somewhere along the way. Knowing exactly why a project went over budget is the difference between repeating the mistake and pricing the next one right, and it comes down to one honest comparison: fee versus actual hours.
Without that comparison, every over-budget project is a mystery, and you are left guessing which phase, which client type, or which kind of scope quietly drained the fee. With it, the answer is usually obvious, and it points straight at a fix.
Fee versus actual hours is the whole game
A project's fee is a bet: you are wagering that the work will take a certain amount of effort. Profitability is simply whether that bet paid off. To know, you need two numbers side by side: the fee you agreed, and the hours the team actually spent. Everything else is downstream of those two.
The catch is that the second number, actual hours, is the one most studios do not have reliably. If time is reconstructed from memory at the end of a week, the comparison is built on fiction and tells you nothing. Honest hours, captured as the work happens, are what make the diagnosis possible.
Find the phase that bled
Overruns are rarely spread evenly. Usually one phase quietly consumed far more effort than its share of the fee. Breaking the comparison down by phase turns a vague sense of loss into a specific, actionable finding.
- Schematic design that spiraled through too many options
- Construction documents that took longer than the fee ever assumed
- Construction administration that absorbed endless unbudgeted coordination
- A phase where scope crept in without a change order to match
You cannot fix an overrun you cannot locate. The phase-level comparison of fee to hours is what turns a vague loss into a specific lesson.
Separate a pricing problem from a process problem
Once you see where the hours went, the next question is why. Sometimes the fee was simply too low for the scope, and the lesson is a pricing one: charge more for this kind of project next time. Sometimes the scope was fine but the process leaked, with rework, unlogged scope creep, or coordination overhead eating the margin. Those are different problems with different fixes, and only the fee-versus-hours breakdown tells you which one you have.
Close the loop while it is fresh
The most valuable moment to look at profitability is right at the end of a project or a phase, while the memory is fresh and the numbers are complete. Compare the hours actually spent against the fee you budgeted, note where they diverged, and carry that lesson into the next proposal. Over a handful of projects, patterns emerge: the phases you chronically underestimate, the clients who demand more, the work you should be charging more for.
Turning hindsight into pricing power
An over-budget project is only a loss if you learn nothing from it. Diagnose it properly and it becomes the most useful pricing data you own. All it takes is honest hours, compared against the fee, broken down by phase, reviewed while it is fresh.
Spreadbox gives a studio the raw material for that diagnosis. Per-task time tracking captures real hours as a byproduct of the work, so the actual-effort number is one you can trust rather than reconstruct. Project status tracking across phases means those hours line up against the phases where the fee was earned, so you can see exactly where a project drifted. And Spreadie, the built-in AI assistant, can draft a plain-language summary of where a project's effort went, turning a pile of time entries into the lesson you carry into your next proposal.