A practical look at what a CRM does for an architecture practice, where the value sits, and how to choose a platform that suits long commissioning cycles.
Architecture practices work on long timescales. A conversation at an industry event can turn into a fee three years later, and a client who commissioned a scheme in 2019 may well be the one appointing again next year. Very little of that history is written down anywhere useful.
A CRM (customer relationship management system) gives the practice a shared memory. Clients, developers, contractors, consultants and local authority contacts all sit in one place, with the projects, bids and conversations attached to them.
It doesn't replace your project or resourcing tools. It covers everything around the work: where the next commissions are coming from, which relationships are worth nurturing and what was discussed the last time someone spoke to them.
For most practices, a CRM is where the following live:
The value of a CRM isn't the software itself, it's what stops happening once it's in place: submissions rushed at the deadline, relationships going cold and forecasts built on optimism.
Directors carry decades of contacts in their heads. Recording those relationships means a practice keeps the value when someone retires or moves on, and a lead partner's holiday doesn't stall a live conversation.
Framework applications, PQQs and fee proposals all have hard deadlines and multiple contributors. Tracking them centrally means the work is planned rather than compressed into the final week, and the quality of what you submit improves.
Long lead times make forecasting difficult. A pipeline with weighted values and expected appointment dates gives directors an honest picture of workload six and twelve months out, which is the basis for sensible resourcing decisions.
Enquiries arriving to a personal inbox, a promised call after planning committee, a client who asked about a second phase - all of it can be captured and assigned rather than relying on someone remembering.
Data taken from a survey we commissioned in December 2024. Click here to view
of businesses are utilising a CRM
of businesses are planning to invest in AI or automation tools
of businesses say using a CRM contributes to increasing customer retention
A CRM earns its place through everyday use rather than grand transformation. These are the areas where architecture practices typically see a difference first.
Enquiries, invited bids and speculative conversations sit in defined stages with expected values and dates. Directors can see what's genuinely likely to convert, which makes decisions about resourcing and recruitment far less speculative.
Most CRM platforms can store a contact. The differences show up in adoption, how well they handle long cycles, reporting and whether the practice outgrows them.
Design teams won't tolerate heavy data entry. Look for something that captures most of what it needs from email and calendar automatically, with a small number of fields anyone can complete in a minute.
A pipeline built for monthly deal cycles doesn't suit a three-year commissioning process. The platform needs to support long-dated opportunities, dormant relationships and staged appointments without distorting your forecast.
Email, document storage, project management and finance should feed the same record. If a project win has to be typed into three systems, at least one will be wrong within a month.
Pipeline by sector, win rate on invited bids, fee value by client type and repeat business share should all be readily available rather than reconstructed by hand each board meeting.
Practices hold commercially sensitive development plans, often before they are public. Role-based access and a clear audit trail should be part of the platform, not an afterthought.
Studios open, specialisms are added and practices merge. A platform that scales avoids a disruptive migration at exactly the point the practice is busiest.
Having worked with practices of all sizes, the platform we consistently recommend is Microsoft Dynamics 365. Most practices already work in Microsoft 365, so contacts, email, submission documents and reporting sit in one connected environment rather than being stitched together after the fact.
It also copes well with the way architecture actually works: long lead times, dormant relationships and staged appointments, all reflected properly in the pipeline instead of forced into a monthly sales cycle.
If you'd like to see what that looks like in practice, read more about Dynamics 365 CRM for architects.
It isn't just another contact database. These are the capabilities practices tell us make the biggest difference day to day.
AI drafts follow-ups, summarises long client histories and helps pull together submission content, so directors spend less of their evening on business development admin.
Outlook, Teams, Word and SharePoint work against the same record, so fee proposals and framework submissions stay attached to the client and project they belong to.
Pipeline value, win rates and fee mix by sector come from live data through Power BI dashboards, which makes resourcing conversations far more grounded.
Submission checklists, review reminders and post-completion follow-ups can be automated with Power Automate, using low-code tools your practice manager can maintain.
Role-based access and audit trails protect commercially sensitive development information long before a scheme becomes public.
Start with core CRM, then add project operations or Business Central as the practice grows - without another platform migration.
It holds every client, developer, consultant and contractor relationship in one place, along with the enquiries, bids and projects attached to them, so the practice has a shared memory rather than relying on individual directors.
Spreadsheets work until several people need to update them, or until you want to know how many invited bids you won last year by sector. A CRM keeps the same information current, shared and reportable.
Small practices often benefit quickly, because business development sits with one or two directors alongside their project work. A CRM makes sure enquiries and follow-ups don't get lost during a busy delivery phase.
Opportunities can sit dormant with future review dates, and relationships can be nurtured with scheduled touchpoints. That's much more realistic for architecture than a pipeline designed to close within a quarter.
Yes. Submissions can be tracked with deadlines, owners and documents, and previous responses stored for reuse, which cuts the effort involved in each new application considerably.
Look at win rate on invited bids, the proportion of fees from repeat clients, pipeline accuracy against actual appointments and how many enquiries get a response within a day.
It depends on the size of the practice and the systems you already use. Practices working in Microsoft 365 often find Dynamics 365 the most natural fit, because contacts, email, documents and reporting sit in one connected environment.
Tell us how your practice wins work today and what's getting in the way. We'll help you understand whether a CRM is the right next step, what it would need to do, and what a sensible first phase looks like.
