After a few years of my sales team confidently telling me they were crushing their numbers, I started to notice something.
Sales were up.
But not by the amount they were claiming.
Not even close.
At first, I assumed it was normal sales optimism. But the gap nagged at me. So for the first time since we’d adopted HubSpot, I decided to dig in myself.
It didn’t take long to find the issue.
My definition of annual sales revenue and HubSpot’s default calculation of annual sales revenue were not the same.
HubSpot wasn’t wrong. But it wasn’t aligned with how we defined revenue inside the business.
I could see what was causing the discrepancy:
What I couldn’t see was how to fix it. And neither could my sales or marketing team.
This is where the frustration kicked in.
How could it be that:
…didn’t know how to change something this fundamental?
Even worse, they didn’t know where to start.
That was my first real warning sign.
Because when your revenue reporting isn’t aligned, you don’t have a marketing problem or a sales problem.
You have a leadership visibility problem.
So I decided to step in.
If this system was going to be the source of truth for the business, I needed to understand it well enough to trust it.
That meant asking deeper questions about:
And that’s when I uncovered the real issue.
As I started pulling threads, the picture became painfully clear.
We didn’t have one HubSpot system.
We had:
Different ways of:
The result?
It wasn’t malicious. It wasn’t incompetence. It was the absence of ownership and governance.
In hindsight, it was a system that had grown without structure.
This wasn’t a HubSpot problem.
It was a leadership problem.
I had allowed a critical system to grow organically without:
We had adopted the software.
We had not adopted the discipline.
And now it was too central to ignore.
So I made a decision.
I would own HubSpot.
Not to micromanage it.
Not to become a sales ops expert overnight.
But to:
That decision changed everything.
Because once leadership takes ownership of the system, the system stops being a tool.
It becomes infrastructure.
And infrastructure requires stewardship.
In Part 4, I’ll talk about what happened next, how my instinct to “fix things” led me straight into the automation trap and what I learned the hard way about changing systems before changing processes.
If you’ve ever opened a CRM thinking, “How hard can this be?” you’ll recognize what came next.