GrowPad Blog

From HubSpot User to HubSpot Partner: Part 3

Written by Kimberly Finnegan | Mar 13, 2026 1:00:02 PM
GrowthPad

Part 3: When the Numbers Didn't Add Up (The Moment HubSpot Stopped Feeling Simple)

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 had adopted HubSpot, I decided to dig in myself.

Two definitions of annual sales revenue

It did not 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 was not wrong. But it was not aligned with how we defined revenue inside the business. I could see what was causing the discrepancy: deal stages, close dates, pipeline assumptions and reporting defaults. What I could not see was how to fix it. Neither could my sales or marketing team.

The first real warning sign

This is where the frustration kicked in. How could it be that three bright, capable people using HubSpot every day for more than four years did not know how to change something this fundamental? Even worse, they did not know where to start. That was my first real warning sign. Because when your revenue reporting is not aligned, you do not have a marketing problem or a sales problem. You have a leadership visibility problem.

"Fine. I'll do it myself."

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 our data, our processes, our definitions and our reporting standards. That is when I uncovered the real issue.

It was not one system. It was three.

As I started pulling threads, the picture became painfully clear. We did not have one HubSpot system. We had three people using the same platform with three completely different sets of standards. Different ways of naming deals, creating records, updating stages and entering data. Reports were unreliable, data was inconsistent, leadership confidence was eroding and we were nowhere near optimizing our HubSpot investment. It was not malicious. It was not incompetence. It was the absence of ownership and governance. In hindsight, it was a system that had grown without structure.

The uncomfortable realization

This was not a HubSpot problem. It was a leadership problem. I had allowed a critical system to grow organically without clear definitions, shared standards, accountability or an owner. We had adopted the software. We had not adopted the discipline. And now it was too central to ignore.

Taking ownership

So I made a decision. I would own HubSpot. Not to micromanage it and not to become a sales ops expert overnight. But to define what truth meant for our business, establish consistent standards, align reporting with leadership expectations and create governance where none existed. 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 will 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 have ever opened a CRM thinking how hard can this be, you will recognize what came next.