Why your CRM isn't fixing your sales process

The CRM went in eighteen months ago. There was a kick-off meeting, a consultant set up the pipeline and everyone got a login. For a few weeks the deals got updated. Now the pipeline shows forty deals sitting at "Proposal sent", some from last year, the sales manager keeps a separate spreadsheet because nobody trusts the reports, and the main use of the system is looking up phone numbers.

In my view the problem usually sits outside the software. A CRM is somewhere to record a sales process. If the process wasn't clear before the software arrived, the CRM ends up recording the confusion, very neatly.

Stages that describe what you did

Have a look at your pipeline stages. In a lot of CRMs they read something like New, Contacted, Meeting, Proposal sent, Negotiation, Won, Lost. Most of those describe what the salesperson did. They say nothing about where the buyer's at.

"Proposal sent" might mean the buyer's about to sign, or that they wanted a price to compare with their current supplier and haven't thought about it since. Both sit in the same column with the same odds attached, and any forecast built on them is fiction.

Stages work better when each one is defined by something the buyer has done or agreed, like "need confirmed and budget discussed", "decision maker has seen the proposal" or "verbal yes, waiting on paperwork". A deal moves on when that thing happens, and anyone looking at the pipeline knows roughly what it means.

Nothing ever leaves

Deals go in easily and hardly ever come out. A quote that's been silent for nine months stays at "Proposal sent" because closing it as lost feels like giving up, and nobody wants to be the one who did it.

That leaves a pipeline full of deals that'll never happen, which makes every report useless. Set a rule: if a deal's had no contact from the buyer for a set time, say three months for a typical sale, it gets closed as lost with "no decision" as the reason. If they come back, reopen it. Now the pipeline shows deals that are actually alive, and the "no decision" count tells you something about your follow-up.

It asks for too much and gives back too little

Salespeople often stop updating a CRM for a simple reason: it costs them time and gives them nothing back. If logging a call means answering nine questions and nobody ever looks at the answers, the questions stop getting answered.

Cut the required questions down to the ones somebody actually uses. Then get the system doing some of the recording itself. Most CRMs can connect to your email and calendar now, so messages and meetings land on the right deal without anyone typing them in. People are far more likely to keep a record up to date when most of it is already there.

Nobody uses it in the room

One of the clearest signs of a healthy CRM is whether it's on the screen in the weekly sales meeting. If the meeting runs off memory, a spreadsheet or a printed list, the CRM is a side project and everyone knows it.

Run the pipeline review from the CRM itself. Go through the deals that moved, the ones that are stuck and the ones due a follow-up this week. Once the meeting runs off the system, people keep it accurate, because an out-of-date deal gets noticed in front of everyone.

Fix the process, then the software

If your CRM isn't helping, don't rush to replace it. A new system with the same fuzzy stages, the same missing rules and the same meeting habits will end up in the same state, possibly faster, because everyone's seen it happen once already.

Start with one page, in plain English, on how a sale should move from enquiry to invoice: what each stage means, what moves a deal on, when a deal gets closed and who's responsible for what. Then set your current CRM up to match it. Often the software you've already got can do it. If it genuinely can't, at least you'll know exactly what to look for in the next one.