How to Tell If Your HubSpot Portal Was Built by Someone Who Never Carried a Quota
Someone can know every setting in HubSpot and still build a portal that's miserable to work in.
This is the pattern I run into more than any other. The person who configured it knew the software. They knew what the platform could do, they knew where every toggle lived, and they built something that is technically correct in every respect. What they never did was live in it — eight hours a day, as a rep with a number, or as a Service rep with a queue of tickets and someone waiting on each one.
So the portal got optimized for what's possible. Nobody optimized for what your rep is actually doing at 4:40 on a Thursday with six deals to update before the forecast call.
Start with your best user, not your settings
When a client comes to me suspecting HubSpot could be more efficient, I don't open the admin panel first. I ask for time with whoever uses HubSpot most fluently.
Not the admin. The power user — the rep or CS person who's already gotten good at it.
I don't need much. Fifteen minutes is plenty, and I've had five-minute walkthroughs that told me everything I needed to diagnose the portal. Just: show me what you do. Walk me through a normal day.
The reason it's the best user and not a struggling one is that struggling users tell you they're struggling, which you already knew. Proficient users have quietly built workarounds instead — and their workarounds are a precise map of where the software stopped helping. They've stopped complaining because they solved it themselves, by hand, every day, forever.
What I'm watching for
Copy and paste. Any time information moves from one place to another by hand, that's a configuration gap. It's the single loudest signal in the walkthrough, and it's never just once — if they copy-paste in front of me, they do it forty times a week.
Tab sprawl. Nine tabs open across two windows usually means the rep has built their own work queue out of browser tabs, because the portal never gave them one. That's what task queues are for: you work the list, it tells you what's next, you never go hunting.
Data entered twice. Watch for anything a rep fills in knowing they'll change it later anyway. If the information isn't real yet, don't make them commit it — and never make them enter something the system could derive or the next stage will overwrite.
Repetition. The same sequence of clicks, several times a day, in the same order. That's a workflow that hasn't been built yet. Reps are remarkably tolerant of this, which is the problem — they'll absorb it silently for two years.
Manual relay between teams. A rep pasting deal context into Slack so Customer Success knows what's coming. A CS rep emailing sales to ask what was promised. Every one of those handoffs is a place where the portal should be moving the information and isn't.
The bar
A well-built HubSpot portal should feel a little like a good video game. It tells you what to do next. It responds when you do something. It keeps score in a way you actually care about. You move through it quickly because the thing is built around how you play.
That's not a soft goal — it's the difference between a CRM your team uses and a CRM your team works around. Adoption problems are almost never discipline problems. They're design problems wearing a discipline costume.
The test is simple enough to run yourself: sit with your best user for five minutes and count the workarounds. If you find more than two, your portal was built by someone who never had to use it.
KoiShark Consulting is a certified HubSpot Solutions Partner. Our founder ran enterprise sales before starting KoiShark, then led a full CRM migration and trained the team from the inside. We work in English and Spanish with startups and midsize teams across the US, Canada, and Latin America. Book a free 15-minute call or email contact@koishark.com.
