The loss you find at the final account

Why a busy, respected firm can still run out of money, and why it only finds out when it is too late to act.

The principal of a Lagos architecture firm told me about the worst kind of surprise.

Not a lost bid. Not a client walking away. A project everyone had felt good about, delivered, closed, and then, at the final account, the numbers came in and it had lost money. Not a little. Enough to matter. And the thing that stayed with him was not the loss itself. It was that he had no way of knowing until it was over. By the time the number arrived, there was nothing left to do about it.

This is the quiet killer in an architecture practice. Not bad design. Not a shortage of work. A firm can be busy, respected, and admired, with good projects going out the door, and still be bleeding money on half of them without anyone able to see it happening.

Here is why the bleeding is invisible.

A fee that is fixed, and effort that is not

An architecture firm agrees its fee near the start of a project, often as a percentage of the construction value. That number is fixed. The client is not going to pay more because the design took longer.

But the effort is not fixed at all. The hours poured into a project rise and fall with revisions, with a difficult client, with a stage that turned out harder than expected. And in most firms, nobody is measuring those hours against the fee while the work is happening. Timesheets are filled in late, or not at all. The fee lives in a proposal document. The hours live in people's heads. The two never meet until the project is closed and someone finally does the sum.

By then the story is already written. The firm did the work, spent the hours, and the fee was whatever it was. The loss is a historical fact, not a decision anyone got to make.

What it looks like to see it in time

Now picture the same firm with one difference. Every person logs their hours against a project and a stage as they work. Every person carries two numbers: what the firm bills for their time, and what that time costs the firm. The gap between those two numbers, across everyone on a project, is the project's real margin, visible today, not at the final account.

This changes what a principal can do. Suppose the developed-design stage was budgeted at 200 hours and has already burned 280, with the deliverables not yet finished. In the old world, that fact surfaces at the end, as a loss. In this world it surfaces now, as a warning, while there is still a next stage to reprice, a scope conversation to have, or a decision to staff the work differently. The firm acts on the project instead of reading its obituary.

Go the other way and the same numbers answer a different question: which people, doing which kinds of work, generate the most value per billable hour. Not who works the most hours. Who earns the firm the most for the time they spend. For a principal deciding who to put on the next important project, that is a real signal, and it was sitting in the timesheets all along.

None of this is exotic accounting. It is the ordinary discipline of knowing your cost and your price at the same time. Most firms simply have no place to put it.

Why the usual software has no place to put it

Here is the deeper reason. Business software is mostly built for companies that sell things. It has a natural idea of a product, a stock level, a purchase of materials, a sale of goods. An architecture firm does almost none of that. It sells professional time and judgement, and it administers contracts between a client and a builder.

The objects that matter in a practice, the fee agreed as a percentage of construction value, the quantity surveyor as a role, the interim payment certificate, the variation register, do not exist in a system built for selling widgets. So the profitability view a firm needs is not a report you switch on. It has to be built, on top of a system flexible enough to hold objects it did not ship with. ERPNext, the open-source business platform, can hold them, because it lets you add the objects a practice actually runs on. That is the difference between software that tolerates an architecture firm and software that fits one.

The insight

A design firm rarely dies of bad design. It dies of not knowing, in time, which of its projects are quietly losing money. The fee is agreed once, near the beginning, when everyone is optimistic. The hours accumulate slowly, in a hundred small revisions nobody is counting. And the two numbers only meet at the final account, when the meeting is a post-mortem.

The firms that stay healthy are not the ones that never have a bad project. Every firm has bad projects. They are the ones that can see a project going bad while it is still going, so that the loss they find at the final account is one they chose to accept, not one that was waiting for them all along.