Product design, information architecture

Product design, information architecture

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

HubSpot contact record in a browser window with the redesigned Marketing submenu and an inline upgrade panel.

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

Challenge

Challenge

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

Approach

Approach

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.

Clicking Marketing from a contact record used to open a generic submenu, with no sign of who you had just been looking at. Now the submenu opens with actions for that contact first ("Add to a marketing email", "View email engagement") and the regular Marketing tools below, and the Contact stays visible behind it. I extended the menu people already use instead of adding a new panel, so there is nothing new to learn.

Clicking Marketing from a contact record used to open a generic submenu, with no sign of who you had just been looking at. Now the submenu opens with actions for that contact first ("Add to a marketing email", "View email engagement") and the regular Marketing tools below, and the Contact stays visible behind it. I extended the menu people already use instead of adding a new panel, so there is nothing new to learn.

HubSpot contact record in a browser window, before and after. Before, the Marketing submenu is a generic list of tools. After, it opens with actions for the contact above the regular Marketing tools.

2. Give sections weight by relevance, not equality.

The right column showed six Hub sections in a flat list, all with the same weight. I grouped them by Hub and let the lifecycle stage decide what opens: Sales is expanded for a Lead, and Service collapses when it is empty. When every section looks important, none of them are.

The right column showed six Hub sections in a flat list, all with the same weight. I grouped them by Hub and let the lifecycle stage decide what opens: Sales is expanded for a Lead, and Service collapses when it is empty. When every section looks important, none of them are.

HubSpot contact record in a browser window, before and after. Before, the right column is a flat list of equal sections. After, sections are grouped by Hub, with Sales open for a Lead and Service collapsed.

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

Clicking a paid tool used to send you out of HubSpot to a pricing page, which destroyed the context you were working in. Now each tool carries a lock and a tier badge, and an upgrade prompt appears inline with a description and a trial button while the Contact stays visible behind it. The product stops selling to the user mid-workflow.

Clicking a paid tool used to send you out of HubSpot to a pricing page, which destroyed the context you were working in. Now each tool carries a lock and a tier badge, and an upgrade prompt appears inline with a description and a trial button while the Contact stays visible behind it. The product stops selling to the user mid-workflow.

HubSpot in a browser window, before and after. Before, a paid tool opens a pricing page and the user leaves their work. After, locks and tier badges appear in the menu and an inline panel keeps the contact in view.

06

Outcome

Outcome

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.

0 new features

0 new features

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.

Have a project in mind? Write to me.

bozena@studioaura.ioClick to copy

© 2026 Bozena Bulat · Croatia

Have a project in mind? Write to me.

bozena@studioaura.ioClick to copy

© 2026 Bozena Bulat · Croatia