You don't have a CRM problem
Here's the conversation I have most often. A founder or ops lead tells me their CRM "isn't really working" and they're wondering if they backed the wrong horse. Should they switch? Rip it out? Start again?
Almost never. The tool is fine. HubSpot is doing exactly what it was told to do — which, in most cases, is very little.
What they actually have is a configuration problem. The CRM got stood up in a hurry, somebody imported the contacts, a couple of pipelines got created, and then everyone got back to the actual job. Nobody owned the architecture. The setup stalled at "it technically works," and that's where it's been ever since.
That's not a competence failure. It's a sequencing failure. And it's incredibly common.
The symptoms you've probably noticed
You don't need a diagnostic tool to spot a half-configured CRM. You can feel it. It shows up as friction nobody can quite name:
Sales chases contacts who already bought. No clean lifecycle stage to separate a customer from a lead, so people who paid you last month are still getting "just following up" emails.
Your lifecycle stages don't reflect reality. Everyone's an "MQL" or everyone's a "Lead" because the stages were never defined around how you actually sell. The data exists; it just doesn't mean anything.
Reports nobody trusts. You pull a dashboard, someone disputes the number, and the meeting becomes about whether the report is right instead of what to do. So you stop using the reports.
Lead source says "unknown" on half the database. You're spending on acquisition but can't say what's working, so every budget conversation is a guess.
Automation that fires at the wrong time, or not at all. A workflow somebody built eighteen months ago is still emailing people, and nobody's certain what it does.
Take one fintech client we worked with. On the surface, HubSpot was "working." Underneath, there were 2,200 duplicate records. Deals were orphaned from the right companies, and their account reports were quietly under-reporting the revenue they'd actually booked against their target accounts. The data was all there — it just wasn't connected. So the numbers leadership were steering by were wrong, and nobody knew.
If two or three of those landed, that's the configuration gap talking — not the platform.
Why this happens to good teams
None of this is because anyone did a bad job. It happens because of when the work gets done.
CRMs get implemented at the worst possible moment — when you're growing fast, everyone's busy, and the priority is "get it live" rather than "get it right." So the architecture decisions that matter most (how you define a lifecycle stage, what triggers a handoff to sales, how you attribute a lead) get deferred. "We'll tidy that up later."
Later never arrives, because there's no natural trigger for it. The CRM keeps running. It doesn't break loudly. It just quietly underperforms — and you absorb the cost as "that's just how it is."
The teams I work with are sharp. They didn't get it wrong. They got it started and never got the uninterrupted time to finish it properly.
An audit is the cheap diagnostic, not the rebuild
Here's the mistake I want you to avoid: jumping straight to a fix before you know what's actually wrong.
You wouldn't rebuild an engine before someone tells you what's failing. But with CRMs, people skip the diagnosis and go straight to expensive remedies — a full reimplementation, a six-month agency retainer, or worst of all, migrating to a different platform that'll have exactly the same problems because the problem was never the platform.
An audit is the cheap step that saves you the expensive one. It's a structured look at your portal that surfaces the three or four things actually costing you pipeline — not a hundred-point list of everything that's theoretically imperfect. Priorities, not perfectionism.
To give you a sense of what fixing the configuration looks like: on one engagement, paid leads were being tracked inconsistently and the nurture logic was firing on the wrong segment. Cleaning up the tracking and the lifecycle triggers took cost per lead from £160 down to £60. Same spend. The leverage was in the configuration that was already half-built — it just needed finishing in the right order.
That's the point of looking before you build: you find the leverage that's already sitting in your account.
What to do next
If your HubSpot feels like it's running but not pulling its weight, don't rip it out and don't pour money into a rebuild on a hunch. Look first.
That's what the CRM Health Audit is for: a focused diagnostic of your portal that tells you what's actually costing you pipeline and what to fix first — in priority order, with no jargon and no upsell to a six-month retainer you don't need.