You Spent £5,000 on a CRM Nobody Uses. Here's Why.

Somewhere in your office, or more likely on a browser tab nobody's opened since February, there's a CRM.

Maybe it's HubSpot. Maybe it's Salesforce Essentials. Maybe it's Monday.com with a sales pipeline bolted on. Doesn't matter which one. The result is the same.

Nobody uses it properly. Half your team logs in once a week out of guilt. The other half quietly went back to Excel and Outlook three months ago. And you're still paying the subscription.

You're not alone. Research puts the CRM failure rate at 50-70%, depending on who you ask. Gartner says 50%. Forbes says as high as 75%. The most rigorous study I've seen, from Johnny Grow in 2025, landed at 55%.

More than half. Of all CRM implementations. Fail.

And that's across every industry. For small structural engineering firms doing £10,000 to £50,000 a month in revenue? The odds are worse. Because the tools weren't built for you in the first place.

The CRM wasn't designed for your firm. It was designed for a SaaS sales team.

This is the part nobody tells you when you're watching the demo.

Salesforce was built for sales teams with pipelines, quotas, and commission structures. HubSpot was built for marketing teams running inbound campaigns. Monday.com was built for project teams at software companies.

None of them were built for a 12-person structural engineering practice in Birmingham that needs to track fee proposals, site visit schedules, building reg submissions, and which version of the GA drawing the architect actually issued last Thursday.

So what happens? You sign up. You spend £2,000 to £10,000 on setup, customisation, and training. You pay £20 to £50 per user per month. For a 10-person firm, that's £2,400 to £6,000 a year in subscriptions alone, on top of the setup cost.

That's real money when your monthly revenue is £30,000.

And then the customisation starts.

Need to track structural calculations? Custom field. Site visit scheduling? Third-party integration. Fee stage tracking? Another plugin. Building regulation compliance documentation? Good luck, you're now deep in Zapier territory, duct-taping three tools together and praying nothing breaks when Salesforce pushes an update.

Every customisation costs money, breaks with the next software update, and requires training that your team forgets within a month.

Your engineers are not salespeople. Stop giving them sales tools.

Here's the fundamental mismatch.

CRMs are built around a sales pipeline. Lead comes in. Lead gets qualified. Lead moves through stages. Deal closes. Repeat.

Structural engineering doesn't work like that. A project starts with a client enquiry or an architect referral. Then there's scoping. Then a fee proposal. Then negotiations. Then the project itself, which has design stages, site visits, calculations, drawing reviews, building control submissions, and a dozen other things that don't fit into "Stage 1 → Stage 2 → Stage 3 → Closed Won."

When you force engineering workflows into a sales pipeline tool, your team spends more time fighting the software than using it. That engineer who told you "I spend more time updating the CRM than I do actually engineering" wasn't exaggerating. Studies show the average CRM user spends over an hour a day on manual data entry. For engineers managing complex project data (specs, site photos, calculations, client approvals) it's worse.

And here's the kicker. The number one reason CRM implementations fail? Poor user adoption. Not bad software. Not missing features. People just don't use it. Because it doesn't match how they actually work.

You don't need a CRM. You need an operating system for your firm.

There's a reason vertical software companies, tools built for one specific industry, are eating horizontal platforms alive.

The pattern is the same everywhere. A generic tool tries to serve every industry. A purpose-built tool shows up that actually understands the workflow. The purpose-built tool wins. Every time.

It happened in restaurants (Toast replaced generic POS systems). It happened in legal (Clio replaced generic project management). It happened in construction (Procore replaced spreadsheets and email). Vertical SaaS companies now account for nearly half of all new billion-dollar software companies, according to Bessemer Venture Partners.

Why? Because when software understands your workflow, it stops being a thing you have to maintain and becomes the thing that runs your business.

For a structural engineering firm, "understanding your workflow" means:

The system knows what a fee proposal looks like. Not a generic quote template. An actual structural engineering fee proposal with stages, assumptions, and scope descriptions that make sense for your work.

Client onboarding captures the right information. Project specs. Site details. Building regulation requirements. CDM obligations. Not "company size" and "industry vertical" and "lead source."

Project tracking follows the actual rhythm of engineering work. Pre-sale assessment. Fee agreement. Design. Site visits. Deliverables. Completion. Not a Kanban board with coloured cards.

Invoicing connects to your accounting. Xero or QuickBooks integration that actually works. Not as a £30/month add-on, but as a core part of the system. Quotes turn into invoices. Payments get tracked. You stop chasing fees in Outlook.

The real cost of your broken systems.

Forget the subscription fees for a second. The real cost is time.

If you have 8 engineers and each one loses even 5 hours a week to admin caused by disconnected tools, switching between Outlook and Excel and your CRM and Xero and WhatsApp, that's 40 hours a week. An entire full-time employee's worth of time. Gone. Every week.

At a charge-out rate of £85/hour, that's £3,400 a week. £176,800 a year. In a firm doing £360,000 to £600,000 in annual revenue, you're losing 30-50% of your potential billing to system friction.

You don't notice it because it's distributed across every person in tiny increments. Ten minutes here. Twenty minutes there. An hour chasing an email thread that should have been tied to a project. Forty-five minutes rebuilding a fee proposal because the template is in someone else's folder.

But it adds up to a number that should make you furious.

What the firms pulling ahead actually use.

The structural engineering firms that are growing right now, winning more work, responding to tenders faster, retaining better engineers, share one thing in common.

They stopped trying to make generic tools work. They use purpose-built systems designed for how engineering firms actually operate.

That means one platform. Not six subscriptions that don't talk to each other. One place where project data, client communication, fee tracking, timesheets, and documents all live. When a new enquiry comes in, the response takes hours, not days. When an architect asks for a project update, the answer is three clicks away, not buried in someone's inbox.

Automation that matches engineering workflows. Fee proposal reminders. Payment follow-ups. Client onboarding that captures the right information the first time. Review requests timed to project completion, so your Google rating goes up without anyone having to remember to ask.

And here's the one that matters most: your engineers actually use it. Because it was built for them. Not for a marketing team in San Francisco. Not for a recruitment agency in London. For structural engineers in the UK.

The honest checklist.

Your current setup is costing you if:

You're using three or more separate tools for client management, accounting, and communication. And none of them are connected.

Your team quietly stopped using the CRM months ago. But nobody wants to admit it because someone spent good money on it.

You lose track of project details in email threads. And occasionally discover that a fee reminder never went out because it was on someone's to-do list that got buried.

You're spending hours each month reconciling invoices, chasing payments, and manually updating trackers.

You've tried to customise a generic CRM for engineering work and ended up with something that works for nobody and costs more than you planned.

You've considered hiring an admin person specifically to manage the systems that were supposed to save you from needing an admin person.

If three or more of those are true, the tool isn't helping. It's the problem.

Stop wrestling with software that treats you like every other industry.

Generic CRMs had their moment. They were better than nothing. For a while.

But "software that does everything" does nothing particularly well. And for a structural engineering firm doing £10,000 to £50,000 a month, you can't afford to burn time and money on tools that don't fit.

The firms winning right now are the ones who've accepted that industry-specific beats industry-generic. That the right system should feel like it was built by someone who's actually worked in a structural engineering practice. That your team should spend their time engineering, not administrating.

Your CRM was supposed to make your life easier.

Did it?