Ask any sales team what tools they run and two names come up almost immediately: Salesforce and HubSpot. Often both, wired together, treated as a single system.
Here's what usually gets left out of that story. Even after you connect them, there's a basic gap that stays open.
Neither tool automatically pulls in LinkedIn data. Verified email, direct phone number, current job title, company size and industry. None of it flows into a CRM record on its own. Someone on the team still has to open LinkedIn, find the person, and copy the details over by hand.
Multiply that across every new lead your team gets in a week, and it adds up to real hours spent on work a "connected" system was supposed to remove.
Why this keeps surprising people
The word "connected" does a lot of work it hasn't earned. When people say Salesforce and HubSpot are connected, they usually mean one specific sync is running, like new HubSpot contacts becoming Salesforce leads. That's real, and it's useful. But it solves one problem, not the whole picture.
Most teams run somewhere between 8 and 12 systems that all touch the same customer data at some point: billing, support, marketing, product analytics, maybe a data enrichment tool, maybe an applicant tracking system if sales and recruiting overlap. Salesforce and HubSpot connecting to each other doesn't mean any of those other systems are talking to anyone.
What this actually costs
It's rarely one big dramatic failure. It's a rep spending ten minutes finding contact details a paid enrichment tool should have supplied automatically. It's marketing building a list that doesn't match what sales is actually working. It's small, repeated, and invisible on any dashboard, which is exactly why it survives so long.
What's worth doing about it
Before adding another point-to-point integration, it helps to map out which systems actually need to see the same customer record, and where the manual handoffs are happening today. Often the fix isn't a new tool. It's noticing that the "connection" everyone assumed was doing more than it actually is.
Next week: what breaks when a workflow that worked fine for 100 users suddenly has to handle 10,000.
Emmanuel