Practice Management for Small Architecture Practices
What a 1 to 10 person UK practice really needs to run projects, fees and invoices, and what it can safely leave out.
Small practices do not need enterprise software, but they do need to know whether each job is making money. This guide sets out the minimum a small UK practice needs, what it can skip, why spreadsheets stop working and how to think about cost per head.
A small practice needs timesheets by stage, fees, invoicing, simple resourcing and an accounting link. Most other features can wait.
What a small practice actually needs
A UK practice of 1 to 10 people needs five things from practice management software: timesheets coded to RIBA stages, a fee for each stage, invoicing from that fee, a simple view of who is busy, and a link to the accounting package. Everything else is optional until the practice grows.
In a small studio the directors are also the project architects, the practice manager and the people chasing invoices. Time for administration is the scarcest resource in the building. Software earns its place only if it saves more time than it costs, and if it answers the one question that matters most: is each job making or losing money?
That question needs three numbers side by side for every live project: the fee agreed for each stage, the hours spent against it, and what has been invoiced and paid. If those three numbers live in three places, nobody looks at them together until the year-end accounts arrive.
- Timesheets by stage.Every hour coded to a project and a RIBA stage, marked billable or non-billable.
- Fees by stage.Each stage carries the fee from the appointment and an hours budget the team can see.
- Invoicing.Stage invoices, percentage-complete invoices and time-charge invoices, in pounds with VAT.
- Simple resourcing.A view of who is on what for the next few weeks, so new work is accepted with eyes open.
- Accounting sync.Invoices and payments flowing to Xero or QuickBooks, so nothing is typed twice.
What a small practice can skip
Many features sold to architecture practices were designed for firms with a finance team. A small practice can leave most of them switched off and lose nothing.
Needed now
Stage timesheets, stage fees, invoicing, a light resource view and Xero or QuickBooks sync.
Can wait
Multi-entity accounts, complex approval chains, custom report builders and detailed overhead allocation.
Start with the five essentials. Add the rest only when a real problem asks for it.
Features to leave off for now
Multi-office and multi-entity reporting matters only when there is more than one company or studio. Multi-step timesheet approval adds friction when the director can approve the whole week in ten minutes. Custom report builders tend to produce reports nobody opens. Detailed overhead allocation and earned value analysis are useful for larger firms with a finance lead, and are rarely worth the set-up time below ten people.
The same applies to configuration. A small practice should be able to set up a project, its stages and fees in a few minutes without help. If a product needs a consultant to configure it, it was built for a bigger organisation.
The spreadsheet trap
Most small practices start with a spreadsheet for fees and timesheets, and it works well at first. It stops working gradually, and the practice usually notices late.
A spreadsheet is free, flexible and familiar. With two or three people and a handful of projects, one person can keep it accurate. The trouble begins as the practice adds people and projects. Timesheets arrive late or in different formats, the fee tab and the invoice tab drift apart, and the one person who understands the formulas becomes the only person who can answer whether a job is on budget.
The cost is rarely the spreadsheet itself. It is the stage that overran without anyone noticing, the invoice raised a month late because the timesheets were not in, and the additional service that was never billed because nobody connected the extra hours to a change in scope.
Signs the spreadsheet has stopped working
- Timing: It takes more than half a day each month to pull together hours, fees and invoices.
- Ownership: Only one person can update it without breaking something.
- Visibility: Project architects cannot see their own stage budget without asking.
- Lag: You find out a stage overran after it was invoiced.
- Re-keying: Invoices are typed into Xero by hand from figures in the spreadsheet.
- Pricing: New fee proposals are written without looking at what similar stages actually took.
Two or more of these is a good reason to move to software. The guide to tracking time against RIBA stages explains the structure to set up whichever tool you choose.
Thinking about cost per head
Most practice management software is priced per user per month, so the right comparison is cost per head against the time it saves and the fee it protects.
Start with the time the current set-up takes. Count the hours each month spent chasing timesheets, reconciling fees, preparing invoices and re-keying them into the accounts. Then add the fee lost each year to overruns that were spotted too late and additional services that were never billed. Compare both with the annual subscription for the whole team.
- Practice
- Six people, all logging time.
- Admin time now
- One director spends 8 hours a month on timesheets, fee tracking and invoicing. At an internal cost of £60 per hour, that is £480 a month, or £5,760 a year.
- Missed fee
- One unbilled additional service of £3,000 a year, a modest assumption for many practices.
- Total at stake
- £5,760 plus £3,000 gives £8,760 a year.
- Break-even
- Software costing up to about £122 per user per month (£8,760 divided by 6 users divided by 12 months, which is £121.67) pays for itself on these figures, before counting better fee proposals.
The figures are illustrative. Use your own hours and rates. The point is that the subscription is rarely the largest number in the decision; the director's time and the unbilled fee usually are.
Watch for hidden costs
Ask about implementation fees, minimum seat numbers, charges for read-only users, annual price rises and the cost of the accounting integration. Check whether pricing is published in pounds and whether VAT is added on top. For a wider comparison of the options, see the buyer's guide to project management software for UK architects.
A minimum set-up checklist
A small practice can be up and running in a week if it sets up only what it will use. This checklist is the minimum that gives reliable fee and time information.
- Every live project created with its RIBA stages and the fee for each stage from the appointment.
- An hours budget for each stage, from the stage fee divided by a blended hourly rate.
- A short list of non-project codes: marketing and bids, practice administration, training and leave.
- Charge-out rates by person or role for time-charged work and additional services.
- The accounting connection to Xero or QuickBooks tested with one real invoice.
- A daily timesheet habit and a weekly approval by one named person.
- A 15-minute monthly look at fee used against progress for every live stage.
- 1
Set up
Load live projects, stages, fees and rates. Connect the accounts.
- 2
Log
Everyone logs time daily. Fix codes that confuse people.
- 3
Invoice
Raise the month's invoices from the system. Check they reach Xero.
- 4
Review
First monthly fee review. Retire the old spreadsheet.
One invoice run and one fee review in the new system prove it works. Extra features can be added once the habit is in place.
Questions practices ask
Short answers to the questions small UK practices ask most often about practice management software.
What software does a small architecture practice need?
At minimum, a system for timesheets coded to RIBA stages, fees by stage, invoicing and a simple view of who is working on what, connected to the accounting package. Most small UK practices use Xero or QuickBooks for accounts and add practice management software on top.
Is Xero enough for a small architecture practice?
Xero handles the accounts well: invoices, bank reconciliation and VAT returns. It does not track hours against stage fees or show whether a project is running over, so most practices pair it with timesheet and fee software. See the guide to Xero for architects.
When should a small practice stop using spreadsheets for timesheets?
When monthly reporting takes more than half a day, when only one person can maintain the spreadsheet, or when overruns are discovered after the stage is invoiced. For many practices that point arrives at around four to six people, though it depends on the number of live projects.
How much should a small practice spend on practice management software?
Compare the subscription with the admin time it saves and the fee it helps recover. Most tools charge per user per month, so multiply by headcount and by twelve, then set that against the director hours spent on timesheets and invoicing each month and any fees lost to late or missed billing.
Do sole practitioners need practice management software?
A sole practitioner can manage with a simple timesheet and the accounting package, as long as time is still coded to stages. The value of a system grows with each extra person and each extra live project, because that is when the numbers stop fitting in one head.
Where Avoice fits
Avoice gives a small practice the five essentials in one place, alongside the project work itself, so there is one system to learn and keep up to date.
Projects carry their RIBA stages and fees. Timesheets suggest hours from the documents and tasks people have worked on, split billable and non-billable time, and roll up against each stage. Approved time becomes an invoice in one click and syncs with Xero or QuickBooks, and financials and cash flow show fees invoiced, unbilled work and margin by project. People and staffing gives a simple view of capacity. The same project also holds specifications, drawing QA and contract administration, so a small team is not switching between tools all day.
Before committing, agree the migration scope, responsibilities, timescale and any costs with Avoice. To see it with one of your own projects, book a demo.