.png?width=170&height=53&name=Untitled%20design%20(2).png)
Part 2: The Website Decision (That Pulled Us Deeper Into HubSpot)
A couple of years after we started using HubSpot, it was time to update our website. Then the conversation shifted.
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.
"If you're using HubSpot for sales..."
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 upgrade our Marketing Hub, build the new website directly in HubSpot and consolidate sales, marketing and the website in one platform. From their perspective it made perfect sense. From mine, it sounded like this: you are already spending money so why not spend a little more and go all in.
My initial reaction: absolutely not
I had already agreed to invest in a new website. Now I was being asked to increase our HubSpot spend, commit more of the business to a tool I still did not personally use and go deeper into a platform I still viewed as optional. I remember thinking: we already have a website, the sales team already has HubSpot and why does everything need to be connected? To me it felt like scope creep disguised as strategy. What I did not yet understand was this: disconnected systems create invisible inefficiencies. And invisible inefficiencies do not show up until scale exposes them.
The case they made
To their credit, the agency did not push blindly. They laid out a thoughtful argument covering centralized analytics, better lead tracking from first touch to close, easier content updates and fewer integrations to manage. They framed it as operational clarity, not additional complexity. Eventually, I agreed. Reluctantly.
What I did not know at the time
I later learned the agency was a HubSpot partner and benefited from guiding us in that direction. At the time I did not know that. In an odd way, I am glad I did not. Had I known, I might have dismissed the recommendation as self-interested and chosen a different path out of skepticism alone. Instead, I made the decision based on the business case in front of me. Because tool decisions should be strategic, not reactive, whether the recommendation comes from a partner or not.
The unexpected outcome
Here is what still stands out. I am glad we chose HubSpot. The website launch went smoothly but more importantly, marketing finally had real performance visibility, sales could see what prospects were interacting with and leads stopped feeling like anonymous handoffs. 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. Once your website, sales pipeline and marketing automation live in one ecosystem, that ecosystem becomes infrastructure.
Still not my system yet
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: the site looked stronger, leads were coming in and sales numbers were increasing. So I stayed focused on running the business and let the system expand around me. But the center of gravity was shifting. When your growth engine lives inside a platform you do not 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 will 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 is when I finally had to pay attention.
