Hubsessed Office Hours Recap: Loop Marketing and AEO, October 6, 2026

This week's Office Hours for Loop Marketing and AEO turned into a session on Breeze and the HubSpot data model: ask Breeze before you build, rename a native object before you buy a custom one, document your process, and treat Breeze as a conversation. This is the written recap of the session.

Ask Breeze before you build

Chris Carolan asked how many questions could have been put to Breeze before anyone brought them to the admin HUG (HubSpot User Group). When time tracking came up there, he asked a beta he calls Breeze Builder for a time tracking app tied into his HubSpot. By his account he had one in about ten minutes. In his words: "It's just, are you willing to ask AI?"

Casey Hawkins asked where he started it. The beta has its own address, and App Builder, reached from the HubSpot Marketplace storefront, may be the way in now.

Rename before you buy a custom object

The first question from the room asked whether HubSpot onboarding is enough, and whether to rename Projects instead of buying custom objects. Chris started with the data model: "You don't need custom objects right out of the gate." Projects, Services, Listings, Courses and Appointments can be renamed, with care, because each has superpowers built into other parts of HubSpot. Start with what process the object supports and who owns it. As Chris put it, "HubSpot functionality is not in the way."

Casey answered the onboarding part with "it depends," on things like how familiar you are with Marketing Hub and how comfortable you are asking Breeze. "I'm a little more cautious with Breeze than Chris is," she said. She would still have a client start with custom reports to understand where the data comes from.

A later question asked whether to build groups, with participants and leaders, as a custom object or by renaming Projects. Chris leans toward Courses, or Appointments if the group is close to a calendar item. His advice: pick the object, pick a name that makes sense, and put the effort into associations and association labels rather than more objects.

Let Breeze read your data model

Chris says the ability to model data and document it is one of the weakest places in the ecosystem. Clicking Data model under data management now opens Breeze, and asking for data model recommendations walks you through the same questions we ask, starting with which process and who owns it.

His portal uses every object and about ten custom objects. Breeze's top recommendation there: "Your biggest opportunity is to simplify and clarify the model you already have, not add more objects."

If you don't have that muscle yet, talk the process out loud and bring the transcript into Breeze, so AI can help turn it into recommendations or documentation.

Words on the screen, pictures people read

For a team, common language is everything, and object names can get in the way, as with deal versus opportunity. Each object in Chris's HubSpot has a documented profile. AI doesn't take over the responsibility, but it gets you to where you can ask specific questions. Casey added: "I think one of the biggest mistakes people make with AI is not questioning it back."

Then turn the documentation into visuals, and ask Breeze for versions that speak to sales, to operations and to finance. As Chris put it: "But the time it has taken to do it in the past means we just don't do it. And then we send big documents to people that they're never going to read."

Chris's test for renaming: "Do the words on the screen match the way your team thinks, talks about the object, because that's where you get adoption faster." He renamed Contacts to Humans, then to Friends. When you work with AI, it still sees the object as Contacts.

Don't one-shot it

On the last question, favorite Breeze use cases with clients, especially in Marketing Hub, Chris named the one he had just shown: document your data model, and let Breeze help if you have never done it. Casey has talked with a newer team member at a client about working through campaign performance with Breeze.

We closed on not overthinking it. Get into a conversation with Breeze, even if it ends up saying it doesn't have the data context to answer, because, in Chris's words, "your portal is different. Your situation is different. Your humans are different. Your AI is different. Everything's different."

Send your questions between sessions to community@hubsessed.io.