

Your sales team doesn't use HubSpot because, for them, it costs more than it gives back. Every record asks for fields they don't need, the information they actually sell from lives somewhere else, and nothing in it helps them close a deal today. So they keep notes in their heads or a spreadsheet, and HubSpot becomes a place to log things after the fact, if at all.
The fix is in the setup. This article covers how to spot the problem, the five causes we see most, what doesn't fix it, and what does.
Owners rarely say "our reps don't use HubSpot." They say something closer to one of these:
If two or more of those sound familiar, the system is the problem.
Most portals are set up from the settings menu: every property someone might want, every workflow someone asked for in a meeting. Nobody sat in the rep's chair and asked what they need to see in the three seconds they have between calls. When logging a call takes eight clicks, reps stop logging calls.
Fifty properties on a deal. Twenty reports nobody opens. Automation that sends tasks nobody acts on. Each piece made sense when it was added. Together they make the system heavy, and a heavy system gets avoided. The fix usually starts with deleting things.
Stages copied from a template ("Appointment scheduled", "Decision maker bought in") don't describe what your reps do. If a counter sale, a bid, and a six-month project all go through the same pipeline, none of them fit, and reps stop moving deals because the stages mean nothing to them.
For distributors and manufacturers this is the big one. Order history, customer pricing, and stock sit in the ERP. If a rep has to open the ERP to answer a customer, HubSpot is extra work. Connect the ERP and the reason to open HubSpot appears. How ERP and CRM integration works.
The system went live, the person who built it moved on, and nobody was trained beyond a single walkthrough. Small problems pile up: a broken workflow, a field nobody understands, a report that stopped matching reality. Within a year the team has quietly gone back to the old way.
Five changes do most of the work:
At Fairbank Equipment, an equipment distributor whose outside reps worked in two systems, we connected Epicor Eclipse to HubSpot so reps could request bids and orders without opening the ERP. In one 90-day window, 9 outside reps created 49 bids from HubSpot.
At California Mobility, territory routing put an owner on new contacts within a minute 56% of the time, up from 26% in a sample of the year before.
At MAI Agents, a SaaS company, we built the lead process, routing, follow-up, and pipeline reporting. Lead-to-opportunity conversion on non-imported leads went from 8.6% to 14.6% in the 180 days after go-live.
Open your portal and answer these:
Two or more "no" answers means your team is working around the system. That is fixable, usually without starting over.
Because updating it costs them time and gives them nothing back. When the CRM asks for fields they don't use and lacks the information they sell from, reps keep their own notes and update HubSpot only when someone asks. Make the system useful to the rep first, and updates follow.
Usually not. Most adoption problems come from how the system was set up, not from the tool. Moving the same setup to a new CRM moves the same problems. Fix the setup first. Switch only if the tool truly can't do what your sales process needs.
A new setup goes live in 3 weeks, with an adoption check at day 30; our packaged sales process setup is $5,000 fixed. For an existing portal, the $3,000 Adoption Diagnostic delivers written findings in 1 to 3 business days: what reps use, what leadership can trust, and what to delete.
If your team works around HubSpot instead of in it, start with the Adoption Diagnostic.