We Need to Talk About the CRM
If you manage a sales team, you've had The Conversation. You know the one. The one where you pull up the CRM, look at a deal that was supposed to close two weeks ago, and ask your rep what's going on.
What follows is one of the most creative exercises in the English language.
I've spent 20 years in field sales — training teams, coaching managers, and building a company that exists specifically because of the CRM data problem. Along the way, I've heard every excuse in the book. And honestly? Most of them are at least partially valid. That's what makes this so funny and so painful at the same time.
Here are the 7 CRM excuses every sales manager has heard — and why they're all kind of true.
1. "I Was Going to Update It Tonight"
Translation: I have not thought about the CRM since the last time you asked me about it.
"Tonight" is the sales rep equivalent of "I'll start my diet on Monday." It's a sincere intention that will be overtaken by reality the moment the rep gets home, sees their family, opens a beer, and remembers that they have to do it all again tomorrow.
The data says the average rep spends 10-11 hours per week on CRM data entry. That's 25% of their workweek. But here's the thing — that's the reps who actually do it. The ones who say "tonight" are usually running a deficit that compounds like credit card interest.
Truthfulness rating: 8/10. They really were going to do it. They just also really weren't.
2. "The Deal Is Further Along Than It Looks in the System"
Translation: I had a great conversation, but haven't logged anything from it. Or the last three conversations.
This one is actually the most honest excuse on the list. The rep is telling you, in so many words, that the CRM is a lagging indicator of what they know, which is true. The problem is that if it's not in the system, it doesn't exist for forecasting, for management visibility, or for the next person who touches the account.
The gap between what the rep knows and what the CRM shows is where forecasts go to die.
Truthfulness rating: 9/10. This is almost always true. The CRM is almost always behind reality.
3. "I Didn't Want to Move It Forward Until I Had the Verbal"
Translation: I am superstitious about deal stages and believe that updating the CRM will jinx the opportunity.
Sales reps have developed an entire folklore around pipeline stages. Moving a deal to "Proposal Sent" feels like tempting fate. Moving it to "Verbal Commit" before the ink is dry? That's basically asking the universe to ghost you.
This is not a data entry problem. This is a psychological problem. And it's more common than anyone admits.
Truthfulness rating: 6/10. They're sincere, but the real reason is that updating the CRM is boring, and this narrative is more interesting.
4. "The Fields Don't Match What Actually Happened"
Translation: Your CRM was configured by someone who has never been in a sales meeting.
Okay, this one is genuinely valid. Most CRM field structures are designed by operations teams or consultants who are optimizing for reporting, not for the person who has to fill it in after a 90-minute meeting while sitting in a Chick-fil-A parking lot.
"What stage is the deal in?" Well, the prospect said they love us, but they also said their budget is frozen, and they also introduced us to the CFO. What dropdown option covers that?
When the system doesn't match reality, reps either force-fit the data (which corrupts it) or skip it entirely (which eliminates it). Neither outcome is good for your forecast.
Truthfulness rating: 10/10. CRM field design is almost always a compromise between what ops wants to measure and what actually happens in the field. The field usually loses.
5. "I Updated It Last Week — Did It Not Save?"
Translation: I am testing whether you actually check the CRM or just ask about it in meetings.
This is a bold play. It's the CRM equivalent of "the dog ate my homework," but with the added gambit of suggesting a technology failure. Some reps have gotten surprisingly good at this. They'll furrow their brow, pull out their phone, and say, "Huh, that's weird, it was definitely showing on my end."
What makes this work is that CRMs actually do have sync issues sometimes. Just often enough to give this excuse plausible deniability. Once in a while, the system really did eat the data. The other 97% of the time? The rep is bluffing.
Truthfulness rating: 2/10.We both know what happened here.
6. "I Was Focused on Closing the Deal, Not Documenting It"
Translation: I prioritized revenue over data entry. Please don't punish me for this correct business decision.
This is the excuse that managers hate because it's logically airtight. The rep is doing exactly what you hired them to do. Selling. The fact that they didn't also do the administrative work that supports the selling is a reasonable trade-off that they made in real time, under pressure, while trying to hit quota.
It's also the excuse that reveals the fundamental tension in every sales organization: we want reps to sell and document and forecast and attend meetings and do pipeline reviews. But we only compensate them for closing.
Truthfulness rating: 9/10. They were absolutely focused on closing. And they should be.
7. "I'll Batch-Update Everything on Friday"
Translation: I will reconstruct an entire week of customer conversations from memory, filling in fields with whatever sounds right, while simultaneously counting down the minutes until the weekend.
Friday batch updates are the fiction factory of sales data. A rep who had 12 meetings this week is now trying to remember, in order, what each prospect said, what the next steps were, and what stage each deal should be in. The result is a CRM that looks complete but is actually a creative writing exercise.
Studies suggest 37% of sales reps admit to fabricating CRM data. Friday afternoon is when most of that fabrication happens. Not out of malice. Out of exhaustion, deadline pressure, and the simple fact that human memory doesn't work that way.
Truthfulness rating: 7/10.They will batch-update on Friday. The data just won't be accurate.
The Real Problem Isn't the Excuses
Here's the thing. I'm laughing about this, and you're probably laughing about it, because every single one of these scenarios is immediately recognizable. We've all been there — either as the rep making the excuse or the manager hearing it.
But the underlying problem is real, and it's expensive. When meeting intelligence doesn't make it into the CRM — or makes it in late, incomplete, or optimistically edited — everything downstream suffers. The forecast is fiction. The pipeline review is theater. Coaching is guesswork.
The reason I built CallJune wasn't to eliminate excuses. It was to eliminate the need for them.
If a rep can call a number after a meeting — on the walk to the car, while the details are fresh — and have that conversation become structured CRM data automatically, most of these excuses disappear. Not because reps become more disciplined, but because the workflow finally matches how they actually work.
No laptop. No app. No 17 fields. No Friday batch fiction. Just a 3-minute phone call, and the data is done.
Which Excuse Is Your Favorite?
I've shared mine. Now I'm curious — what's the best CRM excuse you've heard? The most creative dodge? The most impressive display of plausible deniability?
Drop a comment, send me a message on LinkedIn, or just shake your head knowingly. We've all been there.
And if you want to see what happens when the excuses stop being necessary, check out the demo at calljune.ai. Call the demo line yourself. It takes about 3 minutes — roughly the same amount of time your reps spend not updating the CRM after every meeting.