I do HubSpot consulting for a living (former HubSpot employee, now at a partner agency), and this is probably the single most common thing clients bring to me.

Leadership pulls a dashboard, sees a number, and sales says "that's not right." Then everyone spends an hour arguing about the dashboard instead of the real issue, which is usually one of three things:

- Deal stages don't mean the same thing to everyone. One rep moves a deal to "negotiation" the moment they get a reply. Another waits until there's a verbal commit. Same stage, two different realities.

-A property got redefined at some point and nobody updated the old records, so you're comparing pre- and post-change data like it's consistent.

-Data entry is inconsistent because updating the CRM feels like extra work, not part of the job, so people log things late, log them differently, or skip fields entirely.

None of that gets fixed by rebuilding the dashboard. You're just getting a cleaner-looking view of bad data.

What's actually worked, in the setups I've seen recover from this: stop touching the reports first. Get sales and marketing in a room and agree, in writing, on what each stage and each key property actually means. Assign someone ownership of that definition so it doesn't quietly drift again in six months. Then rebuild the dashboard on top of that.

It's a boring fix. Feels slower than tweaking a report. But it's the only version that stops the same argument from happening next quarter.

Does anyone else have a solution to this? Curious what's actually worked for other teams.

The technical setup is rarely the hard part. Getting people to actually use it the way it's designed is the harder problem, and it's not something you can configure your way out of.

I've seen beautifully built portals sit half-used because logging a call or updating a deal stage felt like one extra step in someone's day. And I've seen rougher, simpler setups get used constantly because they fit into how people already worked.

The pattern I keep coming back to: adoption follows friction, not features. If updating a record takes longer than just remembering it in your head, people will remember it in their head and the data will always lag behind reality.

What's actually moved the needle for you on adoption? Training, simplifying the ask, incentives, something else?

I've noticed that activity history and deal context aren't the same thing, even though we often treat them like they are.

A deal can have emails logged, meetings recorded, tasks completed, and everything looks up to date.

But then someone asks a simple question like "Why did this deal stall?" or "What changed after the last call?" and the answer isn't obvious. The activities are there, but the context isn't.

Usually the important details are buried somewhere else. A concern mentioned during a call or a budget issue that came up briefly.. an internal approval process that's slowing things down. The deal record looks complete, but you still end up digging through notes or recordings to piece the story together.

Curious if others have run into this. How do you make sure the "why" behind a deal actually makes it into the CRM?

Working with a lot of clients I’m often noticing gaps between strategy and execution in a lot of setups. Ideas, plans, and decisions live somewhere outside the CRM, but the connection between those and what actually happens inside HubSpot isn’t always clear.

That’s usually where things start to feel disconnected, especially when people are working across different tools.

What seems to help is making that connection a bit more explicit, even in small ways. For example, linking key workflows or processes back to a defined plan, or making it clearer why something exists in the first place.

It doesn’t require moving everything into HubSpot, but having a visible link between planning and execution tends to make the system feel more intentional and easier to follow.

Curious if others have similar experiences and how you connect those two parts.