CRM for architects: managing clients, projects, and practice admin
Architectural practices have an unusual CRM problem. The work involves very long projects (months or years), slow sales cycles, complex stakeholder relationships (property owners, contractors, planners, project managers), and the need to maintain client relationships over decades for repeat work and referrals.
Most CRMs were built for shorter, simpler relationships. This piece is about what architectural practices need from a CRM and what works in practice.
There's a broader piece on best CRM for service businesses for the wider context, and the full guide to Capsule for the product I most often recommend.
What architectural practices need from a CRM
Five things, specifically.
Very long-cycle pipeline tracking. Architectural projects can sit in the pipeline for months before a decision. The CRM needs to handle long cycles without records going stale or invisible.
Complex stakeholder mapping. Each project involves multiple parties: the client, the planning authority, the contractor, sometimes a project manager or developer. The CRM needs to map these relationships and let you see who's involved in what.
Long-project workflow management. Projects run for months or years. The CRM needs templated workflows for the project phases (concept, design development, planning submission, construction documentation, construction, completion).
Document linking. Architectural deliverables are document-heavy. The CRM doesn't need to store documents but should link to where they live (Dropbox, Google Drive, SharePoint).
Multi-decade relationship continuity. The CRM needs to make finding an old client conversation from five years ago easy, so you can pick up the next project or referral conversation properly.
Where most CRMs fall short
Patterns I see in architectural practices using the wrong tool.
The pipeline doesn't fit. Most CRMs assume sales cycles in weeks. Architectural cycles are in months. The pipeline view feels wrong because deals sit in stages for so long.
Project workflow is missing. Most CRMs don't have proper project templates. The architectural practice ends up running projects in Asana or Excel, with the CRM holding only contact details.
Stakeholder relationships aren't captured. The CRM treats each contact as an island. The fact that this developer works with that contractor on this project isn't visible.
Old conversations get lost. Without proper tagging and search, finding the conversation from 2021 about that potential project is harder than it should be.
What works for architectural practices
The setup I'd recommend for small to mid-sized UK architectural practices.
For small practices (one to ten people), Capsule with Tracks works well. Long-cycle pipeline tracking, templated project workflows for the project phases, contact-centric model for stakeholder relationships, light administrative burden. The full guide to Capsule covers it in depth.
For larger practices (more than ten architects), specialist practice management tools (Newforma, Total Synergy, ArchiOffice, Monograph) often handle the project-specific parts better. These tools were built for architects and have features like time tracking, fee structure management, and resource scheduling that general CRMs don't have. They typically integrate with a CRM for the relationship side.
For mid-sized practices, the choice is genuinely hard. Worth weighing the specialist features against the simplicity of a general CRM.
What I'd avoid for architectural practices:
Deal-centric CRMs (Pipedrive). The deal model doesn't suit project work.
Project management tools used as CRMs (Asana, Monday). They handle the project side but not the relationship side.
Enterprise CRMs (Salesforce). Overkill for most practices.
Generic accounting tools repurposed as CRMs. Wrong shape entirely.
How to set up Capsule for an architectural practice
Brief, since the pillar piece on CRMs with project management covers this in depth.
Build a pipeline that reflects the long architectural sales cycle. Stages might run something like: Initial contact, Brief discussion, Fee proposal, Decision pending, Won, On hold.
Build Tracks templates for the project phases. Concept design, design development, planning, construction documentation, construction, completion. Each phase has its tasks and milestones.
Use tags to capture project types (residential extension, new build, commercial, listed building), client types, and project status.
Set up custom fields for key project data: project value, project type, planning status, contract type.
Configure email integration so client correspondence captures automatically.
Build a weekly review habit that covers both pipeline and current projects.
What to do next
If you're a UK architectural practice considering a CRM, a discovery call is the no-pressure first conversation.
If you'd like a structured second opinion, a CRM Audit is an hour with me plus a written summary.
The piece on working with a CRM consultant covers what implementation typically involves. The piece on best CRM for service businesses covers related sectors.
Architectural practices that get their CRM working properly stop relying on memory and email archives to manage long client relationships. The institutional knowledge of your practice ends up in a system the whole team can use. For practices building over years, that compounding effect is significant.