The project wrapped on a Friday. The client sent a warm thank-you email. The team took a long lunch to celebrate. Monday morning, the principal pulled the final numbers to close out the job and stared at them for a moment longer than expected.
The fee had seemed reasonable when it was proposed. The team had worked hard, stayed organized, hit the milestones. But the actual margin was less than half of what the proposal had assumed. Nothing about the project had gone dramatically wrong. It just hadn’t gone quite right, in a hundred small ways that no one had been tracking.
This wasn’t new. Looking back, several projects over the recent past told the same story; good client relationships, solid design work, thinner margins than expected. The revenue was there. The profitability wasn’t.
The Misdiagnosis
Most firms in this position assume they have a revenue problem; they need more projects, better clients, higher fees. So leadership focuses on business development, on winning more work to offset thin margins on individual projects.
But a busy firm and a profitable firm aren’t the same thing. Chasing more revenue without understanding where margin actually disappears just means running the same leak at a larger scale.
A client once asked an architecture firm for help in a sector the firm hadn’t worked in before. Because the firm was already handling the core and shell of the building and wanted to protect the relationship, they said yes. The project turned out to be unexpectedly profitable, and leadership got excited about breaking into the sector more broadly. What took longer to recognize was that the profitability hadn’t come from the sector itself, it came from how tightly that particular project had been run. The lesson nearly got misattributed entirely.
The real issue isn’t how much work is coming in. It’s that most firms lack the operating visibility to see where profitability erodes while projects are still active; not through one dramatic failure, but through dozens of small, reasonable-seeming decisions that compound quietly.
Where It Actually Happens
A client asks for “just one more revision.” A consultant needs extra coordination. A meeting runs three hours instead of one. None of this gets tracked against budget because each moment feels too small to matter.
Multiplied across a firm’s project load, these moments add up to hundreds of unbilled hours a year; hours the team spent, hours the firm paid for, hours that never reached an invoice. The problem isn’t that scope expands. It always will. The problem is that most firms have no consistent practice for recognizing when accommodation has become scope change, no habit of tracking it as it happens, and no comfortable way to raise it with the client once it has. No one wants to nickel-and-dime a client; that breeds resentment on both sides. But when the moment comes to propose a change order, the project manager needs evidence to justify it.
On one project, a manager flagged a scope change to the principal during a routine check-in and noted it likely warranted a change order. The shift wasn’t large enough on its own, and the principal wanted to preserve the relationship, so they agreed to log it and wait. Scope crept further, as it tends to. Eventually the accumulated changes justified one larger, well-documented change order—and the client approved it without pushback.
Fee proposals compound the issue. A principal estimates hours based on experience, instinct, and a read of what the market will bear, without a clear record of what similar phases actually took on past projects. The guess is optimistic more often than not. By schematic design, some projects are already behind budget, and the only levers left are rushing later phases, cutting internal review, or pulling a principal off other work to help the team catch up.
Then there’s the time that gets logged but never billed. A project manager decides certain hours “don’t look good” and quietly writes them off. A principal spends real hours on a project but doesn’t track them, because that time feels like “running the firm” rather than delivering it. Each decision seems minor. Together, they represent a steady, invisible leak.
The Principal Time Nobody Prices
The most consistent hidden cost is often the principal’s own time.
Design reviews, client calls, consultant coordination, quality checks; in many firms, this work never gets tracked against a project budget. It’s absorbed as overhead, as simply part of the job. But when that time is totaled against what the project was priced to cover, the gap can be significant.
This isn’t only a financial issue. It’s a visibility issue. When principal time is invisible, it becomes impossible to price similar work accurately next time, impossible to know which project types are genuinely profitable, and impossible to have an honest conversation about which clients are worth pursuing at which fee levels.
Where the Pattern Compounds
Every revision cycle carries real cost; internal reviews, file updates, team communication, client presentations. When a single design element goes through four or five rounds, that cost accumulates fast, often because decision authority was never clear enough for the client or the team to resolve things the first time.
Some firms keep one team through the entire project. Others hand work between phase-specific teams. Either way, handoffs create a similar drain. The incoming person spends time rebuilding context that was never documented. Small mistakes creep in because the reasoning behind earlier decisions wasn’t captured anywhere and when different people are involved at each stage, the lessons from a mistake often don’t reach the person positioned to prevent it next time.
Then there are the problem projects every firm carries longer than it should; kept alive by relationship obligations or a reluctance to have a hard conversation, quietly consuming capacity that could go toward better work.
One client kept requesting additional marketing materials well beyond what the agreement covered. The project manager notified them more than once that the scope had been fulfilled. The requests continued until the manager finally told the client that continuing would require an amended or new agreement. The client walked away unsatisfied, and the relationship ended. It wasn’t a comfortable outcome, but the alternative, absorbing indefinite scope creep to preserve a relationship that had already stopped being reciprocal, wasn’t actually protecting anything.
What Firms With Healthy Margins Do Differently
The firms that protect profitability consistently haven’t found a smarter way to negotiate fees. They’ve built operating practices that make these patterns visible while there’s still time to act on them.
They track actual hours by phase after every project closes, so future proposals are built on real data instead of optimistic memory. They’ve defined, in advance, what counts as a scope change and built that conversation into normal client communication rather than treating it as an awkward exception; resisting the instinct to treat every project as unique and instead watching for the patterns that repeat across most of them. They review project financials regularly, not just at closeout, so course corrections happen while they’re still cheap. And they’ve built enough clarity around decision authority that revisions and approvals don’t cycle endlessly waiting for someone to weigh in.
None of this requires a transformation of the firm. It requires treating profitability as something the firm actively watches, the way it reviews design daily, rather than something the accounting reveals after the fact.
What to Notice
Pull up your last five completed projects in a sector your firm regularly serves. For each one, compare the original fee to what the work actually cost; every hour, including principal time, including hours quietly written off before invoicing, including the coordination calls and internal reviews that never made it onto a timesheet.
Notice what that comparison tells you. Often the pattern isn’t catastrophic, it’s consistent. The same phases run over. The same types of client relationships generate more unbilled work than others. The same kinds of requests get absorbed instead of addressed.
The margin isn’t hidden in some accounting black hole. It’s sitting in scope conversations that didn’t happen, in hours nobody tracked, in fee assumptions built on memory instead of data. Once the pattern is visible, the question isn’t whether to fix it, it’s whether your firm has built the operating habits to see it before the project closes, or only after.
