A couple of years after we started using HubSpot, it was time to update our website.
The existing site had done its job, but it no longer reflected who we were or how we operated. We engaged a local design and development firm to rebuild it.
At that point, HubSpot was still firmly categorized in my mind as a sales and marketing tool.
Then the conversation shifted.
Early in the process, the agency asked what tools we were using internally. When we mentioned HubSpot for sales, their reaction was immediate.
They strongly encouraged us to:
From their perspective, it made perfect sense.
From mine, it sounded like this: you’re already spending money, so why not spend a little more and go all in?
I had already agreed to invest in a new website.
Now I was being asked to:
I remember thinking:
To me, it felt like scope creep disguised as strategy.
What I didn’t yet understand was this: disconnected systems create invisible inefficiencies.
And invisible inefficiencies don’t show up until scale exposes them.
To their credit, the agency didn’t push blindly. They laid out a thoughtful argument.
They talked about:
They framed it as operational clarity, not additional complexity.
Eventually, I agreed. Reluctantly.
I later learned the agency was a HubSpot partner and benefited from guiding us in that direction.
At the time, I didn’t know that.
And in an odd way, I’m glad I didn’t.
Had I known, I might have dismissed the recommendation as self-interested. I might have chosen a different path out of skepticism alone.
Instead, I made the decision based on the business case in front of me.
And that distinction matters.
Because tool decisions should be strategic, not reactive, whether the recommendation comes from a partner or not.
Here’s what still stands out.
I’m glad we chose HubSpot.
The website launch went smoothly. But more importantly:
Without fully realizing it, we had crossed a line.
HubSpot was no longer just a sales tool.
It was becoming part of our operational foundation.
And once your website, sales pipeline and marketing automation live in one ecosystem, that ecosystem becomes infrastructure.
Even then, I kept my distance.
The team lived in HubSpot.
The website lived in HubSpot.
I still lived outside of it.
From my seat, things were working:
So I stayed focused on running the business and let the system expand around me.
But the center of gravity was shifting.
And when your growth engine lives inside a platform you don’t understand, you eventually reach a point where you have to decide:
Will you own it, or will it quietly own you?
In Part 3, I’ll share the moment HubSpot stopped feeling helpful and started feeling fragile when dashboards, reports and “the numbers” began telling different stories depending on who you asked.
That’s when I finally had to pay attention.