Hey folks,
Office Hours started on October 1. An hour, every weekday, a different lane and different hosts each day. You bring a real question from your own portal. You leave able to take the next step yourself. That's the point. We'd rather you leave knowing how to do the thing than needing us to do it for you.
In week one, here's what I noticed. Each day below links to the session page with the takeaways, the questions we answered and the clips.
New: Sign in at hubsessed.io/sign-in and your member page is waiting: Office Hours replays and transcripts, this newsletter, and your Academy courses if you're a member.
Thursday, Oct 1: Unified Revenue View
Hosts: Ryan Ginsberg and me
Ryan built the page and walked it. I tagged myself in as Coach Chris about eight minutes in. We followed one demo customer through four revenue numbers in HubSpot: booked, billed, earned and collected.
They're statuses, not a timeline. Seeing these as time-based activities is why this is so hard for so many people. They happen in different orders for different products and sales types, and sometimes all at once. Somebody signs the contract and pays in the same click. A view that stops at the signature only ever sees the first one.
The four numbers are allowed to disagree. What changes is that they live on one record and every gap has an owner: sales, accounts receivable or finance. Put those four groups in a room today and each one can only know their own truth.
Start with the people. Before you build, ask finance for the fiscal calendar and how each number is defined at the line-item level, by business unit and product line. They are already doing this somewhere. It's not a new financial practice. And if AI is helping you set it up, watch anything time-based. Calendars, time zones and fiscal years are arbitrary, and that's the part you check by hand.
If I could call it the Unified Value View, I would. The relationship value at the front end, the stuff that's not dollars, is never going to be found in the ERP. That's what this view is for. And I haven't met an organization where it still makes sense to live in Deal Closed Won alone.
Friday, Oct 2: HubSpot Super Admin
Hosts: George B. Thomas and me
George asked me what the biggest change for super admins has been in the last six months. My answer: getting help from Breeze, whether they want it or not. Six months ago I wouldn't have used it. We weren't suggesting it to anybody. Now it's real help, if you know what to ask.
Breeze does the work, once you know what to ask. George had Breeze capture an original amount and original date that were getting overwritten, then backfill a new property. He didn't enter a thing. He still had to understand the data model and the basics to ask for it.
Your data model is more than three objects. We don't live in a world of just contacts, companies and deals anymore, and AI doesn't always know that either. George's habit for every new client: download every property and hand them to the AI project, so it knows the organization before you ask about duplicates or a new object.
Go look at the data model page. With Breeze on, the sidebar opens there on its own, and the first thing it offers is to map your data model. One click. It's already on every admin's list, so start there.
For everything else, George's habit is to ask "is it possible?" and go test it. A failed test still teaches you something. And before anything AI wrote goes to an executive, one more pass to simplify the complex.
Monday, Oct 5: AI-Native
Hosts: Nico Lafakis and Trisha Merriam
Nico and Trisha spent most of the session on one question: how do you get a HubSpot agent to follow a template the same way every time?
One job per agent. If two jobs would ever be used apart, give each its own agent and run them one after the other. Long runs make an agent lose its starting instructions.
If it has to be one agent, work the instructions. Use markdown headings to show what matters most, put the role before the goal, and keep a rule set that grows every time testing shows something you don't want.
Trisha also runs a writer agent and a checker agent for content. Nico suggested adding a reviewer as a workflow action, and testing what each run costs in credits.
Tuesday, Oct 6: Loop Marketing and AEO
Hosts: Casey Hawkins and me
Casey and I took questions and kept landing on Breeze and the data model. I'm fine with that. Data and context have to be right, or AEO, Marketing Studio and all the other new things don't work. AI can't do what it needs to do to help us.
Rename before you buy. Somebody asked whether to pay for custom objects or rename Projects. You don't need custom objects right out of the gate. Projects, Services, Listings, Courses and Appointments are all there to rename, and each comes with superpowers built into other parts of HubSpot. Where I'd start: what process is the object supporting, and who owns that process?
Rename in the right direction. It's easy to rename the wrong way. A school renames Contacts to Students, and now where do the parents go? The test is whether the words on the screen match how your team already talks, because that's where adoption comes from. I renamed Contacts to Humans, and that's how it looks in George's portal too. Mind you, AI still sees "contacts" inside HubSpot, so it's not without effort.
Don't one-shot it. Get into a conversation with Breeze. Ask for its definition before you report numbers against it. As Casey put it, "one of the biggest mistakes people make with AI is not questioning it back." You'll get where you need to go, even if that's Breeze telling you it doesn't have the context to answer. That's a powerful place to be.
If something worked for someone else and not for you, this is usually why. Your portal is different. Your humans are different. Your AI is different. You don't have the part of HubSpot that person had.
Wednesday, Oct 7: Reporting and Dashboards
Hosts: Joshua Oakes and Madelyn Donovan
Joshua and Madelyn opened the reporting lane by starting before the build.
Settle the denominator first. Agree on definitions with the people asking before you build. As Joshua put it, "misleading reports are more dangerous than no data."
Put reports where they belong. Reports about one record go on that record. Reports about all your data go on a dashboard. For quick questions, the report view on index pages works from the table's own filters, with no saved report needed.
Name reports so you can find them. Joshua's pattern is Intent, Breakdown, Timescale, with short codes like LW, TM or T90. And use color on purpose, so people can connect a summary with its detail.
Watch: Same words, different languages, and the denominator first and Intent, Breakdown, Timescale: naming saved reports
What came up in every lane
Five lanes, five pairs of hosts, and the data model came up every single day. Revenue statuses on one record. Renamed native objects. Reports on the records they describe. Properties handed to your AI project. Almost every answer started with how your data is shaped.
The other thread was people before tools. Ask finance. Ask the stakeholders. Ask who owns the process.
And the thing I keep seeing: the most powerful part of any unified view isn't making everything look the same. It's giving teams permission to not be the same. You can watch the relief on people's faces. Our numbers are different, our processes are different, my auditor wants this, your KPI is that. We get it. Build around your business and your customers, not around the tool.
This week, I want to see more of you in the sessions with us. I know you have questions!
Join us live
Office Hours runs every weekday, noon to 1:00 PM ET, on Google Meet. Monday is AI-Native, Tuesday is Loop Marketing and AEO, Wednesday is Reporting and Dashboards, Thursday is Unified Revenue View, and Friday is HubSpot Super Admin. Right now it's open to all active subscribers.
Each lane has its own room. Pick the lanes you want and add each one to your calendar at hubsessed.io/office-hours. Bring the question you're stuck on. You don't have to show your most embarrassing report to ask. Questions between sessions can go to community@hubsessed.io.
See you in the room,
Chris
The Hubsessed team
 Chris Carolan |  Casey Hawkins |  Ryan Ginsberg |
 Madelyn Donovan |  Joshua Oakes |  Zach Hussion |
