The Review Nobody Books

Most businesses review their finances, their suppliers, their insurance and their staff structures. Very few have looked at their CRM since the day it went live — and that’s where CRM drift begins.

Think about the reviews that happen as a matter of course in a well-run business.

The system that holds your customer relationships, your pipeline, your service history and the numbers your board makes decisions from is often the one thing nobody has formally looked at in years.

That’s rarely negligence. It’s usually because nothing has visibly broken. There’s no outage, no invoice shock, no letter from a regulator. Instead, the cost shows up as a quiet, compounding drag — and by the time it’s obvious, it’s already been expensive for a while.

Which is the whole problem. Poor CRM health rarely causes catastrophic failure. It causes friction.

None of these are serious on their own. Nobody escalates five minutes. Together, though, they quietly increase the cost of growth every year — and they are already on your P&L, whether or not anyone has named them.

So this isn’t just a list of reasons to book a review. It’s a list of costs your business is most likely already paying.

The problem has a name, and naming it helps, because it’s much easier to review something you can describe.

How CRM Drift Begins

Most CRM projects start well. The system is configured around how the business works, users are trained, and management finally gets a clear view of sales and customer activity. For a year or two, it does exactly what was promised.

Then the business changes — because businesses always do.

Meanwhile the CRM often stays exactly as it was on day one. The fields are the ones that mattered in 2021. The sales stages describe a process two managers ago. The reports answer questions nobody is asking any more.

Nothing breaks. The system simply stops describing the business it was built for.

That’s drift. What follows are the ten signs of it — in roughly the order businesses tend to notice them.

This is usually the first visible sign of drift, and almost everyone recognises it. A spreadsheet appears for one specific job, and then it never leaves.

It’s tempting to treat this as an adoption failure and push people back into the system. That rarely works, because the spreadsheet is a solution to something.

We’ve written before about what happens when this becomes the operating model rather than the exception — how spreadsheets, Outlook folders and memory end up as a customer database. The version that matters here is subtler, because there is a CRM. It’s just being routed around.

Ask three simple questions in your next management meeting:

Trust in reporting is binary in practice. Once a forecast has been wrong in a memorable way, people stop treating the number as fact and start treating it as a starting point for a conversation. From then on, the real forecast lives in someone’s head or someone’s spreadsheet — which is drift moving from the front line into the boardroom.

The most dangerous CRM is not the one with bad reports. It’s the one with reports that look right but aren’t trusted.

Bad reports get fixed, because they’re obviously broken. Plausible reports get quietly worked around, which is far more expensive. If you’re not sure where yours sit, our guide to the reports you should be running is a reasonable benchmark.

No single record causes a problem. The aggregate does — and data is where drift is easiest to measure.

Left alone for a few years, the business impact is entirely predictable.

It’s also a moving target rather than a one-off clean-up. Contacts change jobs, companies move, phone numbers are reassigned — customer data decays continuously whether anyone touches it or not, so a database left alone for three years is measurably less accurate than the day it was migrated.

Data quality is the least glamorous item on any review and usually the one with the fastest payback.

This is drift in its purest form, and it’s often invisible from the top of the organisation, because the reports still run.

If the process lives outside the CRM, the CRM stops being the system of record.

The consequence isn’t only reporting. It’s continuity. When the person who understands the workaround is on holiday, off sick or leaves, the knowledge leaves with them — and their inbox goes with it.

Most businesses implement a CRM, automate the handful of things that were obviously painful at the time, and never revisit it. Drift here isn’t about things going wrong — it’s about improvements that were never made.

Over several years, though, the ground moves.

This is the section where a review most often pays for itself outright. Nobody misses automation they never had — but hours a week spent copying, chasing and re-entering are hours a week, every week. There are plenty of practical starting points in our CRM automation tips.

Here’s a quick test. Ask someone who joined in the last six months how they learned to use the CRM.

If the answer is “Sarah showed me how she does it,” you’ve found drift before it shows up in any report. What new starters are being taught is not the designed process. It’s the accumulated set of local habits that grew up around it, workarounds included.

Two or three intakes of this and different parts of the business are genuinely using different systems — in the same database.

Integrations are configured once, at a point in time, against the processes and products that existed then — so they drift for exactly the same reason the CRM does.

Since then the accounts package may have changed, the website may have been rebuilt, the marketing platform may have been swapped, and the product list has almost certainly grown. Somewhere in there, somebody started re-entering data by hand to bridge a gap — and never mentioned it, because it only takes a minute.

It’s worth listing every system your CRM should be talking to and checking, one by one, whether the connection still reflects how the business actually operates. Our overview of CRM integration is a useful frame for that exercise.

At go-live there was a project. There was a sponsor, a plan, a budget and someone whose job it was to make the thing work.

Then the project closed.

In many businesses, ownership quietly dissolves at that point. The CRM belongs to IT, who don’t use it; or to sales, who only own their part of it; or to whoever happens to be most confident clicking around in the admin screens. Requests for change go nowhere in particular, so people stop making them and build a workaround instead. This is the sign that allows all the others to persist — drift needs no cause when nobody is watching for it.

A system with no owner cannot evolve. It can only age.

This is probably the most consequential sign of all, because it covers the change that drives drift fastest — structural change.

Each of these should have prompted a look at the system. New products need somewhere sensible to live. A new department needs its own view of the customer. An acquisition brings a second set of data, a second way of working and often a second system entirely.

When those changes happen without a corresponding change to the CRM, the system starts describing a company that no longer exists.

This is the punchline, and it’s the reason the other nine matter.

Poor CRM health almost never produces a dramatic failure. There’s no day when the system falls over and forces a decision. Instead it produces:

All of it compounding, quietly, over years. The business grows anyway — just with more friction than it needed, and with a growing sense that things don’t feel as efficient as they used to.

That feeling is data. It’s usually the first honest signal that drift has set in.

What This Actually Costs

Drift never arrives as an invoice, which is precisely why it survives. So it’s worth translating the ten signs into the language a board actually uses.

Each of these is survivable. That’s the trap. A business can carry all five for years and still grow — just more slowly, more expensively and with less certainty than it needed to.

The question isn’t whether a review is worth doing. It’s how long you’re willing to keep paying for not having done one.

The Other Half of Drift: What You’re Already Paying For

Everything so far has been about cost. But drift has a second face, and it’s the more interesting one: the capability you already own and have never turned on.

Most CRM implementations go live with the modules the business needed on day one. Sales, contacts, activities, a handful of reports. Everything else stays switched off — not rejected, just not needed yet. Then the project closes, nobody owns the system, and “not yet” quietly becomes “never.”

This is especially true on a single-tier platform, where every feature is included in the licence rather than sold as an upgrade. There’s no paywall between you and the rest of the system. There’s just nobody looking.

These are the areas businesses most often discover they’ve had all along:

None of these are exotic. They’re standard functionality that went unused because the business didn’t need it in year one, and nobody revisited the question in year four.

Some of what a review uncovers isn’t a fix. It’s a capability you’ve been paying for since go-live.

That’s why a review is worth doing even when nothing feels broken. Half the value is in closing the gap; the other half is in finding out what your system could already be doing for a business that has grown into features it didn’t need when it started.

The Good News, and What a Review Actually Covers

If several of those signs sound familiar, that’s normal rather than alarming. Almost every organisation that has run a CRM for more than a few years has some degree of drift.

The good news is that drift develops gradually and can be corrected long before it becomes serious. Very few cases require a new system.

A structured CRM health check works through the areas where drift accumulates — essentially, it measures the gap and tells you which parts of it are worth closing:

Sometimes the outcome is a simple process change. Sometimes it’s a module you already own that removes a job someone has been doing by hand for three years. Sometimes it uncovers an opportunity to save hours of manual work every week. Occasionally it confirms that everything is working as it should, which is worth knowing too.

Either way, taking a step back to review how your CRM supports the business today is one of the more valuable exercises an organisation can undertake — and one of the least often done.

Conclusion

Nobody sets out to let a CRM drift. It happens because the system keeps working while the business keeps changing, and because there’s never an obvious week to stop and look at it. Drift is the default condition of any system nobody reviews.

But the reviews we do as a matter of routine — the accounts, the suppliers, the insurance — all exist because small problems are cheaper to fix than large ones. A CRM is no different. The difference is that a CRM never sends a renewal notice, so the cost of ignoring it never appears on a statement. It appears in the forecast, in the follow-ups and in how much effort your next stage of growth takes.

Frequently Asked Questions

How often should you review your CRM system?

A light review every six months and a more in-depth one every twelve to eighteen months suits most organisations. Beyond that, the trigger is change rather than the calendar: new products, new departments, an acquisition, a new service process or a significant intake of staff are all good reasons to check that the system still matches the way the business works.

What is CRM drift?

CRM drift is the gradual widening gap between how a business operates and how its CRM was originally configured. New staff, new products, evolving processes and rising customer expectations all change the business, while the system usually stays as it was at go-live. No single decision causes it, which is why it goes unnoticed until the symptoms appear: spreadsheets, distrusted reports, workarounds and manual re-entry.

What is a CRM health check?

A structured review of how your CRM supports the business today. It looks at adoption, data quality, reporting, customer service processes, automation, integrations and future growth planning, then identifies where the system has drifted away from how the business actually operates and what would bring the two back together.

Are we using all the features of our CRM?

Most businesses are not. Systems typically go live with the modules needed on day one and the rest stay switched off, then never get revisited. On a single-tier CRM where every feature is included in the licence, that unused functionality is capability you are already paying for: customer self-service portals, case and helpdesk management, quote and document generation, marketing segmentation and project tracking are the areas most often found sitting unused after a few years.

Why has our team gone back to using spreadsheets?

Usually because the CRM no longer supports a process properly, not because people prefer spreadsheets. A spreadsheet appears where the system asks for more effort than the task deserves, so it is best treated as a symptom worth investigating rather than a habit to be stamped out.

Does a CRM review mean replacing the system?

Rarely. Most reviews end in configuration changes, tidier data, a handful of new automations and some retraining. Replacement only makes sense when the platform genuinely cannot support how the business now operates, and that is far less common than the frustration suggests.

How do we improve CRM adoption after a few years?

Start with why people are avoiding it. Adoption problems are almost always process problems in disguise: too many fields, a stage that does not match the real sales cycle, or a report nobody trusts. Fix the process, remove the friction, then retrain. Enforcement on its own tends to produce compliance rather than good data.

What should we prepare before a CRM review?

Very little. It helps to know which reports management actually uses, where data is being kept outside the system and which teams have built their own workarounds. Everything else usually comes out in conversation, and the workarounds themselves tend to be the most useful evidence.