Read the recap

Back to Hubsessed Office Hours: HubSpot Super Admin
Hubsessed Office Hours: HubSpot Super Admin

Hubsessed Office Hours - HubSpot Super Admin - Nov 6, 2026

  • Casey HawkinsHost
  • George B. ThomasHost

Friday, November 6, 2026

Sign in to watch the full replay and read the transcript.

Sign inSubscribe free
SharePost on X (opens in a new tab)Share on LinkedIn (opens in a new tab)

Casey Hawkins brought George B. Thomas two questions from her client work: how to make documentation for a big, complicated portal simpler, and whether to start fresh with a new portal. George answered with Claude on one portal at a time, a plan a human checks, and rebuilding in place.

Clips from this session

Key takeaways

When documentation for a big portal runs too long, ask AI connected to the portal to simplify the complex, be succinct and make nothing up, and to link to a knowledge article and to the actual tool in HubSpot where people need more detail.

Connect Claude to one portal at a time in the Claude app: connect, do the work, disconnect, so the AI pays attention to that portal only.

When Claude gets about 70 to 75 percent of the way, George asks it for a Breeze prompt and runs that prompt in HubSpot.

A Claude Teams project for every client, with instructions and the client's context, lets a whole team hold its conversations about one portal in one place.

For portal audits, George pairs the Claude connector with an API key that has read access only and the Claude extension for Chrome.

Before adding a lifecycle stage, have AI find every workflow that touches lifecycle stages and build a plan a human checks before it runs step by step.

Starting over in a new portal rarely pays, because the history is hard to get back: clean up, restructure and rebuild inside the portal, and remove the hacks and workarounds that are now default functionality.

George's case for AI is speed to insight: an audit that took three weeks to a month can be done in a day when the client answers his questions.

Questions answered

  1. 00:00Open floor: no set topic, and George loves real questionsTopic
  2. 00:19How do you bring documentation for a big, complicated portal down to what matters?Question
  3. 01:46Simplify the complex: be succinct, make nothing up, link to the article and the toolTopic
  4. 03:06Is there a way in Claude to connect multiple portals?Question
  5. 04:19Asking Claude for a Breeze promptTopic
  6. 05:10A Claude Teams project for every clientTopic
  7. 06:52The audit system: Claude connector, a read-only API key and the Chrome extensionTopic
  8. 07:53Inheriting a portal, and what makes one complicatedTopic
  9. 09:32Should you start fresh with a new portal?Question
  10. 11:38Adding a lifecycle stage with Claude: find every workflow, then a plan a human checksTopic
  11. 12:35Rebuild on top of the history instead of starting overTopic
  12. 14:23Remove the hacks that are now default functionalityTopic
  13. 15:02Step one is the connector, and AI as speed to insightTopic
  14. 15:55An audit that took a month, done in a dayTopic