Reconnecting HubSpot's Hubs
Speculative study, not commissioned by HubSpot. HubSpot's seven Hubs share one database but not one mental model. I redesigned three moments where that breaks, using only what HubSpot already has.
Client
Self-initiated study
Role
Self-initiated: research, information architecture, interaction design
Year
2026
Services
User research synthesis · Cross-product navigation · Speculative product design

01
Context
HubSpot started as marketing automation in 2006 and is now seven Hubs on one shared database. Each Hub began as its own product, so navigation, settings and page density differ from Hub to Hub. I took this on as an unsolicited study of what it costs a user to cross from one Hub to another. I had no access to HubSpot's team or data.
02
The database is unified. The surface above it isn't.
Every time a user crosses from one Hub to another, the system treats it as a fresh start. Context resets and the user has to translate again.
03
Constraints
No new features. Every fix had to re-express architecture HubSpot already has.
My evidence is public sources and a free-account test. I did not see paid tiers from the inside.
04
I read r/HubSpot threads, G2 and Capterra reviews and the HubSpot Community forum. I also opened a free HubSpot account and tried basic cross-Hub work as a new user. I used AI to cluster the sources and to argue against my own hypothesis, and I only kept patterns that appeared in three or more independent sources.
Two patterns repeated. Users call navigation between Hubs "overwhelming", and they say the UI isn't consistent across the platform.
The strongest evidence came from the product itself. In my own test account I found a banner saying Brand Identity had moved to Marketing, so HubSpot is rearranging its own architecture and explaining it with banners.
A 2024 HubSpot Community request points the same way: an admin asked to hide tools users don't have, because a user who clicks into a tool they don't own gets "a giant banner" for it.
05
Key decisions
1. Make the Hub click aware of what you were looking at.

2. Give sections weight by relevance, not equality.

3. Show what's available before the click, and keep the user in their work.

06
This is a concept. It has not been tested, and I won't claim it solves HubSpot's architecture. The three decisions rest on assumptions I would test first:
Context in the submenu: do users reach the contact action in fewer clicks than the current route to the same task?
Hub-aware density: do users find a given section faster, and does the lifecycle default match what people actually open?
Lock indicators: do fewer users click into a tool they can't use and leave the workflow?
I have no numbers for any of these. I would test them with a small task-based study before anything else.
Speculative · not tested
Want this for your product?
The Fix: one workflow that hurts, redesigned end to end, with specs your developers can build from. Five days, fixed price.


