CRM Strategy: The System Is Rarely the Problem

Two truths, one quarter-end

Ask marketing and sales about the same account and you get two answers. Marketing sees open rates and calls the account engaged. Sales says they will not even take the call. Both are looking at real data. Neither is looking at the same data.

The question that follows is almost always about software: is this the wrong CRM? Right behind it comes the second one, whether AI will replace the CRM anyway. Both skip the cause. A useful CRM strategy answers a different question — not which system, but why the one you already own is not being used. That question is about sales marketing alignment far more often than it is about features.

Three causes, one test question each

Separate the three before you shortlist a single vendor. It takes an afternoon and it answers the most expensive question of your next twelve months. Each test question is written so that "it depends" is not an available answer.

The second cause is by far the most common, and it is the one a migration does not fix. Manuel Hartmann, Founder and CEO of SalesPlaybook, puts the diagnostic question this way in his LinkedIn newsletter Diary Of A CRO: does the CRM work for you, or do you work for the CRM? Revenue leaders, he writes, almost always answer the second way.

From the LinkedIn newsletter Diary Of A CRO by Manuel Hartmann, issue of 4 June 2026.

The loop that gives it away early

An incentive problem does not break out on a Tuesday. It runs as a loop, which is why it is visible long before it becomes expensive. Four stages, in this order:

• Distrust in the numbers. Someone pulls a report and finds an error. That is enough to start it.
• Less maintenance. Nobody invests time in data they do not trust. Fields stay empty, notes go unwritten.
• Worse numbers. Now the report genuinely is wrong. The distrust was not imagined any more, it became a fact.
• Shadow spreadsheets. Each team builds its own version of the truth. From here the CRM is a cost line with a quarterly ritual attached.

The loop is self-reinforcing, and that is what makes it dangerous: every pass produces the evidence for the next one. Replacing the system does not reset it. It restarts it behind a different login screen.

The same issue explains why over-built systems make this worse. An enterprise CRM has "88 keys", Hartmann writes, while most users only ever want to play three of them — contacts, companies, deals. The job is to make sure each user only has to touch what moves the deal, with everything else available as context.

The sequence that changes the outcome

A CRM strategy that holds has three steps, and their order is not negotiable. Reverse it and you produce resistance instead of adoption.

Step 1 — give time back. Remove work before you ask for any. Call notes come out of the recording, contact data comes from enrichment instead of manual research, follow-ups run from templates. None of this is a roadmap item any more, and none of it takes a quarter.

Step 2 — prescribe the right activities. Only once the day is clear does "what should I do with it" have an answer. Who do I call today, which email do I write, which asset do I need. A CRM that answers those three questions gets maintained, because maintaining it makes tomorrow easier.

Step 3 — ask for accountability. Now, and not one step earlier, the sentence is legitimate: we cleared your day and we said what counts, so let us measure against it.

That this lands in weeks rather than quarters is on the record. The aumico case study reports "reducing the time for sending quotes by 80%", achieved in "less than 2 weeks". That is step one in its purest form — one recurring task that used to eat time and no longer does.

What an unused CRM actually costs

The licence invoice is the visible part and usually the smaller one. The expensive part is upkeep: the role that keeps it running, the exports somebody rebuilds every month, and the decisions taken on numbers nobody trusts.

The obvious reading of that table is: so migrate. It is the wrong one. Workist had a genuine technology case — the old system could not be run without a full-time role paid to run it. That is exactly the test question from row one, and there the answer was yes. Answer it with no and migrate anyway, and you buy the same costs behind a new interface.

A second reflex is just as expensive: hiring a RevOps person so that somebody finally maintains the CRM. That treats the symptom and cements the cause. The system stays something one person keeps up for everyone else, instead of something the people using it get value from.

When replacing it really is the answer

That case exists. It is rare, but denying it is as costly as seeing it everywhere. Three conditions, and all three have to hold:

The platform question is not dismissed here, it is simply placed after the diagnosis. Which system fits which revenue model is covered in our HubSpot and Salesforce comparison; what keeping the data clean through staff turnover takes is in CRM data hygiene through turnover. Both assume the diagnosis has already happened. If it has, and the answer is a platform decision, our HubSpot practice is where that conversation starts.

One point of fairness towards the systems that come off badly in this debate: Microsoft Dynamics and SAP CRM are strong systems of record with deep ERP proximity, and in organisations whose processes live there, they are the right choice. Their limit sits elsewhere — they were not designed for a sales rep to plan their day inside. That is a question of fit, not of quality.