When a business tells us HubSpot is not working, the software is rarely the problem. In almost every case the portal is doing exactly what it was configured to do. It was just configured around a process nobody follows.
The symptoms are always the same
- The pipeline is not trusted, so the real forecast lives in a spreadsheet.
- Deal stages describe what the business wishes happened, not what actually happens.
- Half the team logs activity, half does not, so reporting is meaningless.
- Automations were built for a team structure that changed eighteen months ago.
- Nobody can say who owns the portal.
If you recognise three or more of those, the licence is not the issue. The operating model is.
Why it happens
Most portals are implemented at a moment of optimism. The business buys the platform, configures it around an idealised sales process, trains everyone once, and moves on.
Then reality arrives. Deals do not move in a straight line. A stage gets skipped because it never made sense. Someone finds a faster way and stops updating the record. Within a year the data is patchy, and patchy data quietly teaches everyone to stop relying on it.
A CRM does not fail loudly. It fails by slowly becoming optional.
Audit or rebuild?
The honest answer depends on one question: is your data still worth keeping?
An audit is the right call when the core records are broadly sound and the problems are in reporting, automation or a handful of badly designed stages. It is faster, cheaper, and less disruptive.
A rebuild is the right call when the object model is wrong, when properties have been added ad hoc for years, or when the data has degraded to the point where cleaning it costs more than starting again with a considered migration.
What a fix actually involves
Either way, the work is mostly not in HubSpot.
- Map the process people actually follow, not the one on the whiteboard.
- Agree the small number of fields that genuinely drive decisions, and delete the rest.
- Rebuild stages so each one represents a real, observable customer event.
- Automate the admin so keeping records current is easier than not doing it.
- Name an owner, and review the portal quarterly.
Where AI fits
Once the process is sound, AI is what keeps it sound. Call and meeting notes get summarised into the record. Enquiries get classified and routed. Follow-ups get drafted rather than remembered.
Adoption stops being a discipline problem, because the system fills itself in. That is usually the point at which a CRM finally starts returning what it cost.