How to run a small architecture practice profitably

Almost every small architecture practice that is struggling is busy. That is the confusing part, and it is why the problem persists for years: the diary is full, the staff are working late, invoices are going out, and the bank balance does not move.

Busy is not the same as profitable, and the gap between them is made of information the practice does not have.

The five numbers

• —**Fee earned but not invoiced.** Work you have completed that nobody has billed. In a practice with no stage-closing discipline this is routinely a month of revenue.
• —**Invoiced but not collected, by age.** Not a total — an ageing. Thirty days and ninety days are different problems.
• —**Cost to date, per project.** Staff time, at real cost, against the fee.
• —**Committed forward work.** Signed appointments not yet started. This is the only forward-looking number here and it is the one that decides whether you can hire.
• —**Fixed monthly cost.** Rent, salaries, software, the things that happen whether you win work or not.

A practice that can produce those five on a Monday morning is running a business. A practice that cannot is running a studio and hoping.

Why utilisation is the wrong number

Utilisation — the share of paid hours spent on billable work — is easy to measure, which is why everyone measures it. It answers whether people are busy. It says nothing about whether being busy was worth it.

A fully utilised team delivering an under-priced project is a practice losing money efficiently, and it will feel like success right up until the year-end. Cost against fee, per project, is the number that matters. Utilisation is a diagnostic you reach for after that number goes wrong.

The three habits

**Close stages formally.** Not because ceremony is good, but because a closed stage is an invoice and an open stage is a hope. See how to structure architect fees by stage.

**Claim variations as they happen.** Every practice absorbs small changes to protect the relationship, and none of them records the absorption. Record it even when you do not bill it — at year end, the pattern tells you which clients cost what, and that is a pricing decision for next time. See handling client variations.

**Review project cost while the project is live.** A profitability review at completion is history. The same review at 40% is a decision: re-scope, re-staff, or have the conversation with the client while there is still something to negotiate.

The thing that actually blocks all of this

None of the above requires software. It requires the numbers to exist somewhere a principal can look at them without spending an evening assembling them — and in practice, that is where it fails. The five numbers live in a fee spreadsheet, an invoice book, an attendance register and one person's memory, and reconciling them takes long enough that nobody does it monthly.

This is the honest case for architecture practice management software, stated without exaggeration: it does not make you profitable. It removes the assembly step, which is the reason the review does not happen.