A practical look at what an ERP does for an architecture practice, where the value sits, and how to choose a platform built for staged fees, long programmes and resource planning across multiple projects.
Architecture practices carry projects for years, bill against work stages that slip, and depend on a small number of people whose time is the entire product. That combination makes cash flow and resourcing the two things that most often hurt.
An ERP (enterprise resource planning system) holds projects, fee stages, costs, timesheets, invoicing and reporting in one place, so the practice can see where the money and the people are committed.
It does not replace design tooling. CAD, BIM and document management stay where they are. The ERP covers the commercial side: what was quoted, what has been earned, what has been billed and what is left.
In most practices, an ERP becomes the single home for the following:
The practices that feel in control are not the ones with the fanciest software. They are the ones where fee, time and cost all sit against the same project record.
Billing tied to work stages and milestones means invoices go out when a stage completes rather than when someone remembers. In a practice where a single stage can be six figures, that is the difference between comfortable and overdrawn.
Costed hours by project and stage show recoverability while the job is live. Practices routinely find one or two projects consuming double the planned effort and subsidising everything else.
Forecast workload against actual availability shows the crunch three months out, so you can move people, phase work or recruit rather than absorbing it in unpaid overtime.
When residential, education and commercial work sit in the same reporting structure, you can see which sectors genuinely pay and where the practice should be pitching.
Structural, M&E and survey costs recorded against the project with purchase orders mean recharges are complete, and nothing gets absorbed because it was never coded to the job.
Committed fees, billing schedules and expected receipts give a rolling cash forecast, which matters in a business where a delayed planning decision can hold up a stage payment for months.
Data taken from a survey we commissioned in December 2024. Click here to view
of businesses are utilising an ERP
businesses are dissatisfied with their current ERP
of businesses say using an ERP has contributed to achieving business outcomes
Six everyday situations where one connected system changes the outcome.
The accepted fee proposal becomes the project budget with stages, rates and a billing schedule already in place, so the team starts work against real numbers rather than a proposal document.
Architecture is project-based professional services with long timescales and staged fees. These are the questions worth asking before you shortlist.
Finance, purchasing, stock, projects and reporting should sit in one system. Anything left in a spreadsheet quickly becomes the version everybody argues about at month end.
A system designed for a different sector rarely suits architecture practices. The platform should reflect your real processes, approvals and cost structures rather than forcing a rewrite of how you operate.
Consolidation, reconciliation and management reporting should be routine rather than a fortnight of manual work. Ask to see a month end demonstrated, not described.
Role-based permissions, approval workflows and a complete audit trail should be built in, so compliance is a by-product of daily work rather than a separate exercise.
Cloud platforms with standard processes go live in weeks rather than years. A long implementation is usually a sign the system is being bent into shape.
New sites, entities, currencies or product lines shouldn't need a replacement system. Check licensing and functionality for where you expect to be in five years.
Once you know what an ERP should do for a practice, the question becomes which platform fits how your teams already work. Microsoft Dynamics 365 Business Central brings finance, projects, resourcing and reporting into one cloud system connected to the Microsoft tools you already use.
For architects that means job and project costing as standard, staged billing and WIP handled properly, and Power BI dashboards showing recoverability by project without anyone rebuilding a spreadsheet each month.
It is modular, so you can start with finance and project costing and add service or Dynamics 365 CRM as the practice grows - without another migration when you open a second studio.
It isn't just an accounting package. These are the capabilities teams tell us make the biggest difference day to day.
Ledgers, budgets, cash flow and management reporting run from the same data, with Power BI dashboards leadership can open themselves rather than waiting for a pack.
AI drafts descriptions, reconciles bank entries, chases anomalies and answers questions about your data, taking a chunk of routine admin off the finance team.
Approvals, quotes and reports work inside Outlook, Teams and Excel, so people use the tools they already know instead of learning another interface.
Approvals, alerts and handovers can be automated with Power Automate using low-code tools your own team can maintain.
Role-based access, approval limits and full traceability protect the financial and operational data architecture practices are accountable for.
Start with finance and operations, then add supply chain, projects, service or Dynamics 365 CRM as you grow - without another migration.
No. Design tools, model management and document control stay exactly where they are. The ERP covers fees, costs, time, billing and reporting, and connects to the tools your teams already use.
Yes. Staged fee schedules, percentage-of-fee billing and applications for payment are standard project accounting capabilities and should be demonstrated with your own fee structure during a demo.
Not necessarily. Mid-market cloud platforms are licensed per user, so a small practice typically starts with a handful of finance and project management users and adds timesheet-only users cheaply.
By tying billing to stages and tracking committed fees against receipts, it gives a rolling forecast rather than a snapshot, which is what most practices are missing when cash gets tight.
A single-studio practice on standard processes is usually live within weeks. Migrating historic WIP and part-complete projects is the part that needs care and planning.
Tell us how the practice bills, resources and reports today and we will talk through what an ERP would change, which capabilities matter most and where to start. No obligation, just a straight conversation.
