Why HubSpot Implementations Stall After Launch: Lessons from UNBOUND 2026
AUTHOR:
Category:
Before I worked for a HubSpot implementation partner, I was on the other side of the table. I was a HubSpot customer and the in-house admin, so I was the one building properties, cleaning up records, and asking coworkers (again) to please log their calls. Now at Holland Adhaus, I lead HubSpot onboarding for new clients, train their teams, and run HubSpot audits on accounts that have gotten messy over the years. In both jobs, the problem I run into most has little to do with the software. People just aren’t using it the way their team set it up.
That’s why one session at UNBOUND 2026 in Boston stuck with me. Josh from Protocol 80 walked through how teams close the gap between the sales process they wrote down and the one their reps follow day to day. A lot of it put words to things I’ve been saying in trainings for a while, so here’s my take on it, plus a few things I’ve learned along the way.
Why don’t reps follow the sales process in HubSpot?
Most of the time, reps skip the process because the rules live in someone’s head or a doc nobody opens, and HubSpot was never set up to enforce them. Josh made the point that most adoption problems start outside the CRM and only show up inside it. When a client tells me “nobody uses HubSpot,” the cause is usually a handoff nobody owns or a rule only one person knows.
He shared a stat from Supered’s 2026 State of Sales Enablement Report that I keep coming back to: 89% of teams say they have a defined sales process, and only 36% say their reps consistently follow it. That’s a 53-point gap between what a team writes down and what happens on a Tuesday afternoon when a rep is juggling six deals.
I see that gap in almost every HubSpot audit we do. Someone built the pipeline, and maybe they even documented what each deal stage means. Then you open up the deals and find closed-won deals with no amount, stages that haven’t moved in months, and contacts with no owner. Someone defined the process, and then nobody checked whether anyone was following it.
How can you tell if your team trusts your HubSpot data?
If your weekly pipeline meeting is spent going deal by deal asking for updates, that meeting is doing the CRM’s job. Josh called it a “CRM interrogation.” When the team trusts the data in HubSpot, the same hour turns into coaching. Managers can skip the status roundup and spend the time on stuck deals, blockers, and the patterns they’re seeing across the team.
I like this as a gut check because every sales leader knows which version of the meeting they’re running. A CRM your team trusts should answer a handful of questions without anyone asking them out loud: what stage a deal is in, who owns the next step, what has to happen before it moves, where a handoff is stuck, and whether the forecast holds up.
What are the four steps of a successful HubSpot implementation?
Josh’s framework has four steps, and he said most teams put about 80% of their energy into the first two. Adoption gets won or lost in the last two. That matches what I’ve seen. Setup has a clear finish line, so it gets all the attention, and the work after launch is easy to push off.
1. Map the expectations before you build
Before anyone touches a setting, you need four answers for every step of your process: who owns the next move, what information has to exist, what has to be true for the deal to move forward, and how you’ll know it happened.
His example was a step as simple as “engineering reviews the quote.” On most process maps, that’s one box. When you write it as an expectation, it has a named reviewer, a trigger (a rep submits the quote), a deadline of two business days, a completion signal (the reviewer records the approval), and a plan for when it runs late (it goes back to the sales manager). You can build the second version in HubSpot. The first version only describes what you hope will happen.
This is why our onboarding at Holland starts with a HubSpot glossary. We sit down with stakeholders and define what each lifecycle stage, lead status, and HubSpot deal stage means for their business before we build a single sales pipeline. It’s slow and can be extremely challenging for some clients who don’t have a well-defined process. But it also saves more cleanup later than anything else we do.
2. Build those expectations into HubSpot
Once the expectations are clear, the admin’s job is turning them into system mechanics. Ownership changes become assignment rules, approvals become a trigger plus a status, and stage movement becomes required properties and pipeline rules. Due dates turn into task reminders and escalations, and a finished handoff sends a notification to whoever is up next.
Small rules go a long way here. For a manufacturer we’re onboarding right now, one deal rule makes reps pick a market segment when they create a deal. It’s one dropdown, and it’s the reason their bids-per-segment report will mean something.
Josh made a point I wish more teams heard before launch: the build doesn’t create adoption on its own. It sets up the conditions for the next two steps. I’ve cleaned up plenty of accounts that someone set up well and then left alone.
3. Inspect what’s happening
Inspection means someone regularly checks whether the expectations are being met. In HubSpot, that usually looks like dashboards built around exceptions, like deals with no next step, approvals that have been sitting too long, or stages that haven’t moved. Managers need views that tell them where to look so they aren’t scrolling every record.
Training fits in here too. Clients often ask me to train their teams in person, and I love it, because people will ask the “dumb” question face to face that they’d never send me an email about. One afternoon of training still can’t carry adoption by itself, though. That’s why our HubSpot onboarding includes a virtual follow-up after the in-person session. By then, people have hit real questions and a few bad habits have started, so we look at what people log and what they skip and fix it while it’s still small.
4. Reinforce the behavior
Reinforcement is what you do with what inspection turns up. Josh broke it into three moves. Coach the miss by talking through what should have happened and what to do next time. Diagnose the pattern, and if it keeps happening, figure out whether the cause is the person, the process, or the system. Then improve the system by removing friction, clarifying the rule, or adding guidance in HubSpot where people need it.
Everyone owns a piece of this. Reps run the process, managers coach the gaps, leaders protect the standard, and admins remove the friction. That last one is my job and my favorite part of it. When a rep tells me a required field makes no sense at that stage, that’s useful feedback, and the fix is usually on our end.
Why does HubSpot adoption drop after launch?
Your business keeps changing after launch. You add products, approval steps, and new people. If HubSpot stays frozen with the old stages and the old dashboards, people start working around it in Slack, email, and spreadsheets. Managers lose trust in the data and respond with more meetings and more manual reports, which pulls even more work out of the CRM.
We’ve lived this one at Holland. A while back, we set up recurring revenue tracking in HubSpot for our retainers, and it took so much manual upkeep and gave us so little reporting that we stopped using it. The setup didn’t match how our retainer work runs, so the team went back to tracking it other ways. We’re rebuilding it now with HubSpot Contracts, and this time we started by mapping how our work happens before building anything.
Five questions to ask about your CRM
Here’s a short checklist to help guide conversations:
- Do people know what’s expected of them at each step?
- Can reps and managers quickly see what needs their attention?
- Is it obvious who owns the next move in a handoff?
- Are people bouncing between systems just to keep a deal moving?
- Are managers reinforcing the process after launch?
If you answered no to a few of these, your adoption is probably running on memory and meetings. That’s fixable, and in my experience the software is the easy part. If you’d like a second set of eyes on your HubSpot setup, our team can run an audit and show you where adoption is slipping.
Thanks to Josh and the Protocol 80 team for a session that gave me a lot to think about at UNBOUND 2026.
