You opened HubSpot this morning. The last activity on a deal you're about to review was logged three weeks ago. The close date hasn't been touched since the deal was created. The stage says "Proposal Sent" but you know that proposal is dead.
This isn't a HubSpot problem. HubSpot is exactly what it's supposed to be. The problem is a behaviour problem — and behaviour problems don't get fixed by adding required fields or threatening reps with admin consequences.
Why reps don't update the CRM
Ask a rep why they didn't log their last call and you'll get some version of the same answer: they were going to get to it, they forgot, they didn't think it mattered, or — honestly — they didn't see the point.
None of those are excuses. They're signals. They tell you that the cost of logging is higher than the perceived benefit, and that no one has made the case that accurate data helps the rep — not just the manager or the RevOps team.
The three real reasons CRM data goes stale:
- Logging happens after the fact. The call ends, the rep moves on, and by the time they open HubSpot, the context is half-gone. They're reconstructing from memory instead of capturing in the moment.
- The tool isn't where the rep lives. Reps live in Slack, in their calendar, in their email. HubSpot is a destination — and destinations get visited less often than the places you already are.
- There's no feedback loop. When a rep updates a deal, nothing happens. There's no confirmation that it mattered, no visibility that someone acted on it. Logging feels like shouting into a void.
Why enforcement makes it worse
The typical response to stale data is enforcement: required fields, locked stages, manager check-ins, admin lockdowns. These create compliance, not adoption. There's a difference.
Compliance means reps fill in the field to make the warning go away. They type something — anything — and move on. The field gets filled. The data stays garbage.
Genuine adoption means the rep actually wants to log, because logging does something useful for them. That's a completely different problem to solve, and enforcement doesn't touch it.
Reps who feel like HubSpot serves them will use it. Reps who feel like HubSpot is for their manager won't — no matter what you make required.
The meeting-prep test
Here's a useful diagnostic. Ask a rep: "Do you open HubSpot before a customer call?" If the answer is "sometimes" or "not really," you have a signal problem.
Reps who find HubSpot useful will open it before calls. Reps who find it painful will skip it. The data-staleness problem and the pre-call prep problem are the same problem — HubSpot doesn't fit into how reps actually work.
The fix isn't to make HubSpot easier to open before calls. It's to bring the relevant data to the rep in the tool they're already in — usually Slack — at the exact moment they need it, which is 15 minutes before the call starts, not "when they have time."
The right loop to fix
The data staleness problem is a loop:
- Reps don't update HubSpot → data goes stale
- Stale data means HubSpot isn't useful → reps trust it less
- Reps who trust HubSpot less update it even less → loop continues
You can't break this loop by pushing harder on step 1. You break it by making step 2 better — by making HubSpot data genuinely useful to the rep, not just to the people who review the rep's work.
That means:
- Surfacing relevant deal context at the moment a rep needs it — pre-call, pre-email, pre-QBR
- Making it possible to update HubSpot without switching context (from Slack, from a notification, from wherever the rep already is)
- Closing the feedback loop so reps can see that accurate data produces better outcomes for them — better coaching, less admin chasing, faster deal movement
What a good hygiene workflow actually looks like
Good hygiene workflows don't nag. They notify. The difference is context and timing.
A nag is: "You haven't updated this deal in 14 days." A notification is: "Your call with Acme is in 15 minutes — last activity was 14 days ago, here's what's on record, do you want to add a note?"
The first one creates friction. The second one creates a moment — a natural entry point where updating feels useful rather than administrative.
When you stack enough of these moments across a team, you stop having a data hygiene problem. Not because you forced behaviour, but because you made the right behaviour the easiest one.
Sidekick is built around this idea — that CRM adoption improves when you meet reps in the tools they already use, at the moments that matter. If you're thinking about this problem for your team, book a call and we'll walk you through how other teams have approached it.