When salespeople won't update CRM records, the reason is often in where their day actually goes.
Doug's phone buzzes in the cupholder before they're out of the parking lot. He glances at it at the light and leaves it there.
"Purchasing at Hartwell," he says. "They want to know if the price increase hits on the first. I'll call her after this stop."
Carla rides with each of her reps once a quarter, and today it's Doug's turn. He's sold bearings, belts and motors here for nineteen years, to about a hundred and thirty accounts, mostly plants within a couple of hours of the branch. Last night she pulled up his accounts in the CRM, the way she does before every ride-along. The system went live in April. His email is all there, since the sync logs it on its own, and so are the meetings on his calendar. He has two open opportunities. The last note on most of his accounts is from a Friday afternoon, and most of them say some version of "visited, follow up."
The first stop is a food plant that's shutting down one of its lines for two days in November. The maintenance planner has a list ready of everything he wants on the shelf before the line comes down, mostly bearings and belts, plus two gearboxes. He and Doug go through it at a table outside the maintenance office. Twice the planner changes a part number because Doug remembers what they ran last time.
Back in the truck, Doug calls Nina on the inside sales desk and reads her the list. Nina builds quotes in the ERP, since that's where the plant's pricing is kept and where a quote becomes the order once the customer says yes. She has this one built while he's still on the phone, and before they reach the highway it's in the planner's inbox, with Doug copied.
"Does that go in the CRM?" Carla asks.
"It's in the system," Doug says. "Nina's got it."
He means the ERP. What the CRM will show is Nina's email with a PDF attached. There's no opportunity behind it, so it has no amount and no close date.
Between the second and third stops he calls Hartwell back. The buyer has a list of questions about the price increase, and the call runs fifteen minutes. He makes it from his cell phone, like every call he's made today. The reps' phones aren't connected to the CRM, so none of those calls log.
When he hangs up, he types two lines into a text to himself. Carla can see the thread above it, months of account names, part numbers, "call Thurs" and "bid due 11/14."
"That's my notebook," he says. "Friday I put it in."
At the packaging plant, the project engineer walks them out to the end of a line where the new conveyor is supposed to go. It's the larger of Doug's two open opportunities, and in the CRM it closes October 31. The engineer says the money has moved into next year's capital budget, though purchasing will have the final word.
Back in the truck, Carla says, "That one's still October in the system."
"I know." Doug pulls out onto the road. "I want to hear it from purchasing first. If I move it now, it's the first thing we talk about Monday, and I won't have anything to tell you yet."
He isn't wrong about Monday. Carla asks about every date that's moved since the week before.
Over lunch she asks what he looks at before he walks into a plant. Doug turns his laptop around. It's the ERP, open to the account's sales history. It shows what they bought last time, what they paid and what's on backorder.
"Anything I need on the floor is in here," he says.
The CRM is open in another tab. He hasn't clicked on it today.
Doug's updates come in Friday, like every week. Five visits from Tuesday get a line apiece. The Hartwell account gets a note that says "pricing call." Purchasing at the packaging plant called him back Thursday, so the conveyor now closes in February.
There's still no opportunity for the shutdown order, and there won't be one. The planner's purchase order came in Thursday, and Nina entered it in the ERP that afternoon.
Monday morning, Carla puts the pipeline up in the conference room. Doug's list has one opportunity on it, the conveyor, closing in February. She asks him if there's anything new.
"The food plant's shutdown order," Doug says. "It ships Wednesday."
When a sales team's CRM falls behind, there's usually more than one reason, and it can be a different reason for each rep.
Much of a rep's selling may happen where the CRM can't see it. Email and calendar sync log a great deal on their own, which can make a record look current when it isn't. Calls log on their own only when they go through the CRM's app or a phone system connected to it. Calls from a phone's own dialer, texts and visits in person don't log unless someone enters them, and neither does what was said. When that's the reason, notes tend to be entered in batches from memory, after the last stop or at the end of the week. Most CRMs record when each note was entered, separately from the date of the visit, and an activity report can be sorted by it. A week of visits entered in one sitting is the sign.
Sometimes the work already has a home. Where quotes, pricing and order history live in the ERP and the CRM is a separate system, an opportunity in the CRM is a second copy of something that's already been written down once. The gap shows as quotes and orders with nothing behind them in the CRM, while the large new projects that pipeline meetings ask about are there. Setting a month of quotes from the ERP beside the CRM's opportunities usually makes it plain.
Many pipeline reviews look closely at deals whose close dates moved, since a date that keeps moving can mean a deal is stalling. Where the review works that way, a rep who isn't sure about a date often waits until they are before changing it. The dates then trail what the rep knows and tend to jump a month or more in the day or two before the meeting. Most CRMs keep a history of every close-date change, which shows when each one was made.
Some reps get little back from the CRM for what it asks. Its fields may have been chosen for reporting, while what a rep needs before a call, like pricing and what a customer bought last, sits somewhere else. When that's the reason, required fields get filled with the same few words across every record. What a rep opens before walking in the door tells you a lot. If it's the ERP or their own notes, the CRM isn't giving them something they use.
The number of systems a rep is asked to keep up with can matter too. In a Gartner survey of 1,026 B2B sellers in early 2024, half said they're overwhelmed by the amount of technology their job requires.
Then there are records that can't be trusted. A CRM loaded from old spreadsheets and contact lists can carry the same customer three times over, along with buyers who retired or moved on. Reps working from records like that tend to keep their own lists alongside, and to update only the records they're asked about. The largest accounts show it fastest, because the most people have touched them.
More required fields won't bring in a visit nobody logs, and a better mobile app won't bring in a quote that already lives in the ERP. Every fix asks the reps for something. A fix aimed at the wrong reason costs more than its own time, because the next request is harder to make.
Why don't salespeople update the CRM?
Often for several reasons at once. Calls from phones that aren't connected to the CRM, texts and visits in person don't log on their own, so updates get written later from memory. Where quotes and order history live in the ERP and the CRM is a separate system, an opportunity in the CRM is a second copy. Close dates that would draw questions in a pipeline review often wait until the rep is sure of them. The CRM may give reps little they use before a call, or its records may not be reliable. The number of systems matters too. In a Gartner survey of 1,026 B2B sellers in early 2024, half said they're overwhelmed by the amount of technology their job requires.
Why do CRM close dates keep getting pushed?
Sometimes the deals really are slipping, and sometimes the dates were never current. Where moved dates get questioned in a pipeline review, reps often wait until they're sure before changing one, so dates trail what the rep knows and then jump a month or more just before the meeting. The CRM's history of close-date changes shows which it is. Dates changed mostly in the day or two before reviews point to when updates get made rather than to the deals themselves.
Up to thirty minutes, confidential, and an honest read on what's keeping your CRM out of date.
Get Your Free Pulse Check →A CRM can look busy every day and still miss much of the business a company actually wins.
More in this cluster →Thirty minutes. Confidential. No card required.