Brian Halligan Returns to HubSpot, Breeze Research Earns Its Keep, and Will It Breeze Works Without the Connection

Another Orange Morning Recap: Thursday, November 12, 2026

Thursday was just Chris and me, with no Friend of the show this time, and we opened with news neither of us had planned around. Brian Halligan is coming back to HubSpot as CEO, and I spent the first stretch of the morning working out how I felt about that.

Here is what we got into. First the leadership news and the word "harness," then where your data is coming from when you inherit a portal. After that, two updates in depth, Breeze Research and CRM views, a quick pass over three more, and Will It Breeze on the Admin lens.

Brian Halligan Comes Back, and Harness Becomes the Word to Watch

Chris put Dharmesh Shah's LinkedIn post on screen and read it aloud. Dharmesh wrote that he and Brian founded HubSpot twenty years ago and are now re-founding it, that Brian Halligan is returning as CEO, and that Duncan Lennox has been promoted to President of Product. He thanked Yamini Rangan, and said the plan is to create "the world's first customer relationship harness" and to accelerate a vision of "headless HubSpot."

Chris added that a date next week, the eighteenth if he has it right, had been mentioned for some announcements. His guess was that the announcement is starting early, and that the customer relationship harness may be what it is about.

I had seen Brian's own post before the show, and it read to me like the template LinkedIn new-job post. On the show I said, "Personally, I'm going to need a little more information than this templated LinkedIn post." Dharmesh's post gave me that, so thank you, Dharmesh. It also came with a photo of the two of them in a small office, in what I guessed was 2006, with an empty chair in the middle of it. I am a little obsessed with that picture.

The other thing that stood out to me is that the twenty-year anniversary never came up at UNBOUND. This was the first time I had seen anyone official acknowledge it, and I think it is a monumental thing.

Then there is the word itself. "Harness is still a word I'm not as confident in," I said, and Chris took it from there. To him, a harness is the environment around you that you need to be successful, and HubSpot was the harness for getting work done and managing customer relationships even before it had AI. A tool is something you assume will magically do things. A harness is different, because "you still have to move yourself, if you're going to create value."

Chris also made the point that the harness is really for the AI more than for the humans, so that Breeze can be a great work partner. His own preference: "I think customer value platform is the right way to think about it. Doesn't matter what the other words are really." Still, he thinks agentic and harness are worth understanding, because they help you follow the changes being made to HubSpot and they help us explain them.

I went looking for context too. The average CEO tenure is seven to eight years, a little shorter in tech, and Yamini's five years is about average for tech, it sounds like. For anyone wondering, she stays on until December 1.

Where Is All This Data Coming From?

Chris plugged "You Inherited a HubSpot Portal" later today with Trisha Merriam and me, and the topic that day is where all the data comes from. When you inherit a portal, the integrations, the imports and the enrichment are some of the most confusing parts. They may be creating good data or bad data, and it is hard to even know which if you can't say where it is coming from.

Chris sees that question as an easy place to build trust in a new role. Very few people in the company can answer it, and answering it quickly chips away at the reasons people give for not trusting HubSpot. He pairs that visibility with Breeze conversations, because you need to be confident enough to say there is no uncertainty about it.

I hear a version of this regularly. Who have we reached out to recently, and who haven't we? Whether the answer is accurate depends on the integrations and on whether you are logging the activity, and that alone can decide whether people believe HubSpot's data is reliable.

Chris shared a story from a HubSpot Admins HUG, where someone in the chat was weighing a move away from Marketing Hub because of bad data they could not control. Right after that, they mentioned that data was flowing in automatically from ZoomInfo. His read is that whether HubSpot really deserves the blame usually becomes clear in a moment like that.

That is what my latest Hubsessed newsletter gets into. When the answer feels like starting over, keep in mind that you can't just start over if you're just moving that data around. Chris went to the same place from the other direction, with intentional data first. It is rare that data is clean, complete and trusted all the time, and ZoomInfo is usually not marketing's call, so the first job is creating enough visibility to have the conversation.

Chris also pointed everyone to the events page at Another Orange Morning, where the HubSpot community calendar lives in one place. He also plugged Hubsessed Office Hours with Ryan Ginsberg, Thursdays at 11 AM Central, which is about getting to a unified revenue view once your data and context are correct across the full life cycle.

Before the updates I read out a comment someone named Brian had left at the start of the show: "Can't imagine what you'll be discussing today." Chris's answer was that it is good to feel seen.

Two Updates Worth Pulling Forward

Breeze Research: From Question to Action Plan

Breeze Research is a deeper investigation capability in Breeze Assistant. Instead of answering a question in one shot, Breeze builds a plan, works through the relevant data step by step, and returns a structured report with findings and recommended next actions. I called it the most interesting update for me.

Part of that is where I have been this week. I hit my Claude weekly limit doing normal work, and I built a HubSpot app for a client, planning it with Breeze Research along the way. I am more comfortable using Breeze than I was even a week ago, and I am asking it to help me plan things.

Chris came at it from the data side. Because the work happens inside your portal, he says the answers about HubSpot process, context and data are getting night and day better, with clearer, more confident answers and links to the research. He connected that to the ZoomInfo conversation. An unimaginable amount of infrastructure has gone into moving purchased data into the system of record in a trusted way, and he now thinks of it as a huge workaround, because we did not have access to understanding the humans we wanted to work with.

His picture of the alternative runs through intent signals and buying groups, and we talked about buying groups yesterday. You choose an account, intent signals bring in contacts, and Breeze offers to research who is real at that account instead of buying data that has to be vetted and doesn't care about your business. That is the difference between building for just in case and building for just in time. In his words, "We don't have to buy data from other places anymore. We just don't." He called it a dramatic shift, and none of it works if we can't get users talking to Breeze.

I am pointing more of my clients here first, with a caveat. I am not promising it will be perfect in its first shot, but I often find it a really good first step. A client recently asked me to build some reports and wanted to know the cost, and I told them, "I think you should ask Breeze before we start…" Chris put it more bluntly: "Stop paying people to build reports in HubSpot for the love of all things holy." The question changes by the next day, he said, and AI can change with you. He would also build the report with a narrative, because the most frustrating part for an admin is putting in the effort when you can't see all the context behind the question.

Why it matters: The update only pays off if people start the conversation. A good first answer from Breeze in the portal, with the research linked, is a better starting point than a report request that sits in someone's queue. Admins can help by pointing people there first, and by being honest that the first shot won't be perfect.

For more details: Breeze Research: From Question to Action Plan.

CRM Views: Auto-Save and Collaborative Sharing

CRM views now autosave your changes and persist them across sections, and they come with new roles and a sharing system so teams can collaborate on views without overriding each other's work. Saving on the index pages where you work with contacts, companies, deals and tickets has been unpredictable for a long time, which meant lost work and a pile of duplicate and stale views.

I almost went to this update first, because it was my favorite one. I have lost count of how many times I have coached someone through building a view and said, wait, wait, click save. Chris described the other side of it. One of the most frustrating things in HubSpot has been doing the work to get a view the way you want it, then clicking into a record you are interested in and losing it.

The roles decide who can do what. Owners have full control and can publish changes to all users, manage sharing and assign roles. Collaborators can customize filters, sorting, columns and visualization settings in their own personal working layer, and a restricted role covers a limited set of settings, such as sorting. Chris noted how far the CRM has come, with visualization settings in there now if you haven't looked lately.

That personal working layer is where I got nervous, as someone who works in an admin role a lot. Changes a user makes there autosave for their profile only and don't affect anyone else's views. We see the same thing with CRM cards, where an admin sets a view, users customize it, and later a new field gets added that those users never see because they have already customized theirs. I think the update makes sense. "It's just something that you can and should be aware of if you're adminning a portal."

Chris agreed. Earlier he had pointed to the balance underneath it, which is empowering people to create their own views while still keeping specific default admin views. His advice was short: "Have some intention. Understand how views work." He added that it is very powerful.

Why it matters: Autosave takes away friction that nearly everyone has felt. The new work for admins is deciding which views are the published defaults, and noticing when someone's personal layer is hiding something you just added.

For more details: CRM Views Auto-Save and Collaborative Sharing.

Three More, for the Record

I had a hard stop, so rather than a third deep dive we noted three updates and moved on. New workflow builder now supported in Sandboxes is in development, with a date of November 19, which Chris pointed out is next week, and he figured a lot of people would be rejoicing. Chris also flagged Post-Restore Summary as probably an interesting one.

The third was Run a workflow on demand for a set of records, in the new builder. I don't know if we have seen it yet, but we have talked about the new builder reaching parity, so I was happy to see it.

Will It Breeze: The Admin Lens and a Shopify Breeze Could Not See

I picked the Admin lens, since I felt like I had just been talking about adminning. The wheel gave us a scope of every integration we run and a business outcome of showing the work behind the number. The question for Breeze was whether, as the portal's admin, it could show the work behind a number across every integration the portal runs. I got the name of the app wrong on the way in, and Chris says he does the same thing.

Breeze came back right away asking which number we meant, and it flagged that Shopify isn't a connected app. I had an idea for a twist. What if we wanted to start using Shopify, so how would we get the integrations there, and how would that affect revenue? I said I didn't know how to tie the number in, and Chris's advice for anyone in that spot is to say exactly that to Breeze, and to mention that finance asked for it.

Chris pointed out that the real-world version of this is not unusual. People assume things are integrated when they are not, and a whole business might run on a Shopify commerce setup while the data reaches HubSpot through exports, or through an iPaaS tool, because the Shopify integration got much better and nobody has taken the time to move it over. That ties straight into the topic Trisha and I were taking on later in the day.

Breeze suggested net sales, refunds, profit and cash as the numbers to consider, and it helped define what showing the work should mean. Then it asked what accounting system finance uses, because that determines the next connection plan and where the reconciliation should happen. It saved to memories, which Chris called the not great part of this demo. I was worried the memory would say I don't know what I'm doing. What Chris read back was that the user needs guidance on which metrics to prioritize.

Chris called it one of the best Will It Breezes we have done, and I agreed. His lesson line for the segment: "And so will it breeze? It will. Even when you don't have the data connected to HubSpot."

The Rest of Thursday's Updates

We did not get to these on air, and they are in the feed now: Updated refund process for HubSpot payments, Reusable Metrics on Dashboards, Revenue Reporting from Contracts, and Turn on Supervised Mode for Customer Agent. Everything else that shipped is in the HubSpot updates feed.

The Sign-Off

You probably already own the value you are looking for in HubSpot. You just need to wake up to it. We will see you tomorrow morning.