Someone in your firm, maybe you, has at some point searched for 'CRM for engineering firms.' You looked at Salesforce. The pricing page made you close the tab. You looked at HubSpot. You got fourteen emails from their sales team before you'd finished the trial. You looked at Pipedrive. It seemed promising until you realised it's a sales pipeline tool that doesn't know what a building control approval is.
So you went back to the spreadsheet. Or you half-implemented something and abandoned it. Or you're still using Outlook contacts and hoping that's enough.
The problem isn't that you made the wrong choice. The problem is that the products you evaluated weren't designed for how structural engineering firms actually operate.
What CRMs assume about your business
Salesforce and HubSpot were built for B2B sales teams. Their model is: you have a lead, you qualify it, you move it through a pipeline, you close a deal. Revenue follows. That's the workflow.
That workflow doesn't describe a structural engineering practice. Your workflow is: an architect contacts you about a residential extension. You do a site visit. You send a fee proposal. They accept it or come back with questions. The project starts. It runs for four months. You produce calculations, coordinate with building control, manage revisions, invoice at milestones. The architect comes back with another job eighteen months later.
There's no 'deal' in that sequence. There's a relationship, a project, and a repeat engagement. The CRM paradigm, leads into pipeline into close, is a bad map of that territory.
What the right CRM for an engineering firm actually does
Enquiry management with automatic follow-ups. When an enquiry comes in, it's logged. If you haven't responded in 48 hours, you get a reminder. If you sent a fee proposal and haven't heard back in a week, a follow-up goes out. This isn't aggressive sales behaviour. It's basic professionalism that most firms don't have time to do manually when they're running three projects simultaneously.
Quote-to-project conversion without a data handoff. When an enquiry becomes a project, all the context, the client details, the agreed scope, the fee, carries forward automatically. You don't retype it into a new system. You don't update three separate records to reflect that this enquiry is now an active project.
Project delivery in the same system. This is where most generic CRMs fall apart completely. A CRM that closes at 'deal won' has nothing to say about the next six months of project delivery. The right tool for a structural engineering firm keeps the project record, the correspondence, the documents, the invoices, and the compliance notes all in one place from first contact to final certificate.
Client communication history inside the record. When that architect comes back for their third job with you, you should be able to open their record and see everything: every project you've worked on together, every email in context, every invoice paid and outstanding. Not search for it across email and Dropbox.
Accounting sync that works automatically. Xero and QuickBooks are your accounting tools. The CRM is your project and relationship tool. They should share data in real time, so the view of a client in your CRM includes current payment status without you manually reconciling the two.
Why One Uncle calls itself the anti-CRM
The anti-CRM positioning isn't contrarianism. It's a description of what the product doesn't do. It doesn't have a sales pipeline. It doesn't have deal stages or a lead qualification score.
What it has is an enquiry record that becomes a project record, with email integration, automated invoicing, a client portal, Xero and QuickBooks sync, and compliance documentation built around CDM and Building Safety Act requirements. The workflow it tracks is the engineering workflow, not the sales workflow.
According to Statista's CRM adoption data for UK SMEs, only 34% of firms with under 20 employees use a dedicated CRM. Among engineering consultancies, the number is lower. Most are using email, spreadsheets, and memory. The firms that have tried generic CRMs and abandoned them are using the same combination.
The question is whether the right tool for a structural engineering firm looks like Salesforce with engineering fields added, or something built around how engineering firms actually work from the start. One Uncle is the latter.
What to actually ask when evaluating options
Ask any vendor: does your system have a concept of a project that connects enquiry, quote, delivery, and invoice in a single record? Does email correspondence attach to projects automatically, or does someone have to file it? Can clients access documents and pay invoices through a portal without calling you? Does it sync with Xero in both directions?
If the answer to any of those is 'with some configuration, yes,' that's a no. Configuration takes time. Time you don't have. And configured systems break when the person who configured them leaves.
The right CRM for a structural engineering firm shouldn't require configuration to understand what structural engineering is.
