How to scale an architecture practice without hiring more staff

To take on more projects without another office hire, an architecture practice needs the admin each project adds to stop landing on one practice manager's desk. Every project brings a fee proposal, written terms of engagement, timesheets against its stages, stage invoices, a planning set to validate and minutes to chase. An AI worker can draft and chase all of that. The architects keep the design, and a director keeps every decision about fees and clients.

What forces the next office hire in an architecture practice?

A familiar sign is a project architect giving half a day a week to admin. Architects' time is the practice's product, and a practice watches chargeable hours closely, but the ratio that forces the hire is the number of live projects for each person who runs the office. A studio manager's advertised job at one London practice is monitoring timesheets, invoicing clients, fee proposals, payment schedules, forecasts, HR and helping the architects with document control. Each line is done per project, per month or per stage, so adding projects leaves the list the same length and makes every item on it come round more often.

A small practice can run on one person doing all of it. At some point, often when the invoicing slips or a planning set goes in late, the practice hires a second administrator or lends the office that architect's half day. The first is a fixed cost carried through the quiet months. The second is chargeable time given away, which is the one thing a practice cannot afford to give.

A practice doing a hundred small residential jobs and one doing four schools carry very different loads, so the number of projects one practice manager can run is each practice's own.

What admin does each new project bring?

• The fee proposal and the terms. The fee is priced stage by stage against the RIBA Plan of Work. ARB's guidance of June 2025 to Standard 4 of the Architects Code expects clear written terms of engagement, including the fee or how it is worked out, in the client's hands before work starts.

• Timesheets against stages. Everyone books hours to the right project and the right stage, and until they do nobody can say whether a stage is inside its fee.

• Stage invoices. Each is raised when the project lead confirms the stage is reached, then chased until paid.

• The planning set. In England the application is valid only with the form, the national requirements, the fee and whatever the council's local list asks for, and the decision period does not start until it is. Somebody chases the consultant's report that is holding it up.

• Minutes and actions. They are owed after every design team meeting, to the engineer, the services consultant and the client.

Everything in the list is done by the practice manager, or by an architect who should be designing.

Why does a fee overrun show up a month late?

Because the timesheets arrive late and the stage report is built from them. A stage running over its fee is visible only once hours are in, and in a practice where the practice manager chases timesheets at the end of the month, it is visible a month late. The practice then absorbs the overrun or raises a variation it has to argue for. Neither comes from the design; both come from admin arriving late, and more projects mean more of both.

Which of this can AI staff take on?

The two jobs to hand over first are time and invoices. An AI worker can chase the missing timesheets ahead of the invoice run, leaving alone everyone who has already filed, so the stage report is true when it is read. It can prepare each stage invoice for the project lead to confirm and follow up the unpaid ones, so the architect is not the person asking a client for money. Each such worker has one written job, someone in the practice who signs off what it produces, and measures reviewed with you each month.

The fee proposal, the planning checklist and the minutes follow the same pattern. An AI worker can assemble the fee proposal for a director to price; our guide to writing a fee proposal against the RIBA Plan of Work sets out what goes in one, and our page for architects covers each role. Time and invoices still come first, because they recur every month on every live project, which is the load that forces the hire.

What stays with a director?

The Architects Code puts the fee and the terms of engagement on the architect. An agent can draft them; a director sets the fee, checks the scope and signs. Anything sent to the planning authority in a client's name is checked and submitted by one of your team; the agent's part stops at showing what the set still lacks. What to do about a stage that has run over its fee is a director's call, and so is a disputed fee. Nobody's timesheet is filled in for them, and project leads approve the time.

What should a practice hand over first?

Start with timesheets, because every other number in the practice depends on them. Agree the cut-off, who approves, and which rules a submitted entry must pass, such as no hours on a closed stage. Measure the share of timesheets in by the cut-off and the days to a complete set. When the stage report can be trusted, move the stage invoices across. The wider case is in how to scale a business without hiring more staff, how such a worker is managed is in our explainer on managing AI workers, and our starting price is on the homepage.

In an architecture practice an AI worker would chase the timesheets and prepare the stage invoices without a second administrator, and a director would still set the fee and sign the terms. Is your stage report still a month behind the timesheets? Talk to our agent.