Implementation
{Read Time} min read

Why your sales team doesn't use HubSpot, and how to fix it

Vitaly Kan, Founder of ProfitPad
Vitaly Kan, Founder, ProfitPad
October 28, 2026
Illustration of a HubSpot record the team skips while work flows to a spreadsheet

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.

Signs your sales team isn't using HubSpot

Owners rarely say "our reps don't use HubSpot." They say something closer to one of these:

  • "It's basically just notes." Deals get logged once, then never move.
  • "I'd have to ask the rep." The real pipeline lives in someone's head or inbox.
  • The Monday pipeline review happens in a spreadsheet someone rebuilt over the weekend.
  • Reports exist, but nobody trusts the numbers enough to act on them.
  • Reps open the ERP, the quoting tool, or their email to find what they need, and HubSpot is the last stop.

If two or more of those sound familiar, the system is the problem.

Why sales teams avoid HubSpot

1. It was built for the admin, not the rep

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.

2. There is too much in it

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.

3. The pipeline doesn't match how you actually sell

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.

4. What reps need lives in another system

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.

5. Nobody owns it after launch

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.

What doesn't fix it

  • Mandates. "Log everything in HubSpot or else" gets you data entered at 5pm on Friday to satisfy the rule. It doesn't get you a system reps rely on.
  • More training on the same system. If the system is the problem, training people to use it harder doesn't help.
  • More reports. Reports are only as good as the data reps put in, and they put in less when the system fights them.
  • A new CRM. Moving the same setup to a different tool moves the same problems with it.

How to get your sales team to use HubSpot

Five changes do most of the work:

  • Start from the rep's day. What do they need to see before a call or a quote? Build that first, and hide the rest.
  • Delete before you add. Remove the properties, reports, and workflows nobody uses. A lighter system gets used.
  • Standardize the milestones, not the work between them. Leadership needs every deal to pass the same stages with the same entry rules, so the numbers mean something. Reps need room to sell their way between those stages.
  • Bring the rep's data in. If reps live in the ERP, connect it, so customers, orders, and pricing show up where they sell.
  • Check adoption after launch. Thirty days in, look at what reps actually use, fix what they work around, and train on what changed.

What it looks like when it works

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.

A 10-minute check for your own HubSpot

Open your portal and answer these:

  1. Could a rep log a call and move a deal in under a minute?
  2. How many deal properties are there, and how many get filled in?
  3. Does each pipeline stage match something your team actually does?
  4. Can a rep answer a customer's order or pricing question without leaving HubSpot?
  5. Would you run Monday's pipeline meeting from a HubSpot dashboard, as is?

Two or more "no" answers means your team is working around the system. That is fixable, usually without starting over.

Frequently asked questions

Why don't sales reps update the CRM?

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.

Should we switch to a different CRM?

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.

How long does it take to fix HubSpot adoption?

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.