I’ve been analyzing and thinking about this as I continue to grow in the HubSpot ecosystem from a RevOps and Super Admin perspective.
One thing I’ve noticed is that many businesses seem to focus on using HubSpot for individual tasks, sending marketing emails, tracking deals, or managing tickets but not necessarily as the central system that connects teams, processes, and data.
HubSpot places a huge emphasis on inbound methodology, clean data, data governance, shared processes, and breaking down silos. Yet in practice, many organizations still operate in silos and only adopt the features they immediately need.
For those of you who have implemented HubSpot across organizations, how do you help stakeholders understand that HubSpot isn’t just another CRM, but a platform designed to support scalable operations? What conversations, strategies, or change management approaches have worked best for helping teams embrace that mindset?
This is something our company struggled with for quite some time as well. We had siloed Sales Teams all logging things everywhere, a Marketing team that just did stuff without consulting any other departments, and a service team doing their best to help customers with limited Data input from anyone else.
Alignment took time for us, as many teams were hesitant to make process changes, but I redirected that fear of change into hope and excitement for the future by showing what could be possible, with just a little bit of compromise on their part.
I started small - like picking one sales team member with awesome CRM usage to have access to the Prospecting Agent, everyone else was locked out. Once other members saw their success, they were suddenly way more willing to enter the Data I’d been begging them to enter for years to gain access.
Another example is not as fun, but effective - showing the pitfalls. I was once asked by Marketing to provide Revenue reporting on Companies by parent account relationship, to see how we perform in our large Groups, but because the Sales team did not keep associations up to date at that time, I was not able to provide that report as requested. When I pointed out the fact that the Sales Team’s lack of data input or updates was now greatly affecting the marketing team’s capabilities down stream, it was very eye opening for the Team leaders, and adoption became easier to secure.
Hopefully that helps! I look forward to seeing some other answers on this post, thank you for sharing!
Great Question, One way I’ve seen this work well is to start with the business process before the HubSpot features.
A good place to begin is by getting Marketing, Sales, and Service aligned on a few shared definitions: what qualifies a lead, when ownership changes, what information needs to follow the customer, and what the teams should be able to report on together.
Once those definitions are agreed on, HubSpot can operationalize them through lifecycle stages, ownership, standardized properties, automation, reporting, and clear SLAs for key handoffs. Data governance becomes much easier to introduce as well, because teams can see how the information they maintain supports the next team rather than feeling like additional CRM admin.
When it comes to getting teams to adopt this way of working in HubSpot, I’d introduce it gradually rather than changing everything at once. Start with one cross-functional process or handoff, get the ownership and data right, and use a shared dashboard to show the impact. Once that approach is working well and teams see the value, it becomes much easier to apply the same model across other processes and departments.
That’s usually where the mindset begins to shift naturally. HubSpot becomes less about maintaining a CRM and more about giving everyone a shared system for delivering a better customer experience.