Breeze Goes First, Serverless Functions Reach the Quote, and a Calendar View Worth Showing Your Clients

Another Orange Morning Recap: Tuesday, November 10, 2026

Chris was back on Tuesday, and Ryan Ginsberg joined us as our Friend of the show. We started with a flip. Will It Breeze normally closes the hour, and Chris decided on the spot that it should go first, so the show opened with the wheel and the updates came after.

Here is what we got into: a quick look back at yesterday's Will It Breeze, today's Will It Breeze on the Finance lens, and then five updates. Serverless functions arriving in Revenue Hub Enterprise, the Properties Schemas API, the new run settings in Agent Hub workflows (which we had already read yesterday), the audit log redesign, and the CRM calendar view. We ended at the hour, a little surprised how fast it went.

Will It Breeze, Moved to the Front

Yesterday's Leadership prompt was still on my mind. When I tried it in our test account and again in a real client portal, Breeze came back in both cases asking which number we meant, so the first job was working out what number we were asking about. Chris liked that this is exactly the kind of thing the clips are for, and it led into what I have been doing lately: sending the Will It Breeze page to clients. "I've been sending this page to some clients who I think could and should use Breeze."  One of them emailed me that morning saying they could not get the answers they were looking for in HubSpot and thought they needed new reports. My reply was to ask whether they had asked Breeze.

Chris put the point to listeners plainly. Start anywhere, because the request matters less than the habit: "no matter how great it has worked for somebody else, you are at a different portal. You're talking to Breeze at a different time. And it's going to go differently."  He also described what he runs into when he asks another AI to write a prompt for Breeze: the other AI tries to protect the data with a list of warnings, and "Breeze is like, stop. I know what I'm doing. I know HubSpot better than you know HubSpot."  That is a learning curve worth knowing about before you hand Breeze a prompt somebody else wrote.

Chris called the spin, we landed on the Finance lens, and the three reels were the whole pipeline, customer success, and write the update my boss will ask for. I read the prompt, as our finance lead using customer success, write the update my boss will ask for across the whole pipeline, and ran it on my screen in the Demo Account. Chris asked for it in the private chat to run on his side too. His first read was the one a lot of HubSpot users hit: "customer success the team or customer success the app in HubSpot."  Finance outside HubSpot probably means the team, and Breeze has to pick one.

The output was a pipeline update shaped for a finance reader. It asked sales and customer success to validate the open close dates and delivery commitments, and asked finance to reconcile the open opportunity to the signed agreement, the billing schedule and the accounting treatment. Chris's verdict: "So again, will it Breeze? The answer is yes."  I came back to why this is where I tell people to start. When a client says they lack visibility, my first move is to ask what visibility, and I will have more questions after they answer. "Being able to have this conversation and correct in real time, I think is really strong."

Ryan asked whether admins can see Breeze usage across a portal, to improve context at the portal level. Chris said a beta is starting to address that, and I pointed out that for now you can ask Breeze Assistant about your team's usage. It will not show the specific questions people asked, but it will answer. Chris loved that the only way to get this is by talking to Breeze, with no setup and no report to find.

The part Ryan picked out was the end of the output, the paragraph on what Breeze could not yet substantiate. "The fact that it's clearly telling you what it can't do is a trust-building exercise. And I appreciate that a lot."  He treats the output as a starting point and would validate it before taking it to a boss, which is the right instinct. Chris added that a paragraph like that makes the case for connecting the ERP or the customer success system without turning it into a fight over buying more tools. Ryan was left curious about what happens behind the scenes: "I'm just always so intrigued what's happening behind the scenes for it to write that line."  Chris's answer was to stop trying to reverse-engineer it. Many of the chats in the sidebar are, in his words, "a lot of them are coming from a slot machine."  A general question to Breeze also lets it draw on its own memory of how users in the portal behave. Someday we may get a clear view of that memory architecture, "But for most humans, just start talking to Breeze."

Ryan caught a word on the way out. "I could have sworn I heard you say slop machine, but it was slot machine."  Chris confirmed it was slot, and we moved on to the updates.

See the prompt and more: Will It Breeze: Finance.

Five Updates

Serverless Functions in Revenue Hub Enterprise

Chris read the title and Revenue Hub Enterprise was the headline: serverless functions are now available there, for building a more dynamic quoting experience. I read the why. Serverless functions run custom backend logic behind your HubSpot tools without servers to set up or maintain, and for quotes the use is capturing what a buyer enters on a custom field and writing it back into the associated CRM record, so the deal and quote data stay current without extra steps for your sales team. Before this, serverless functions were not available in Revenue Hub and needed another hub subscription. Chris skipped the what's-new text as largely unhelpful, then turned to Ryan.

Ryan builds serverless functions with the developer projects framework and UI extensions, so his first question was whether this is the same thing or something different. His interest is a gap he has noticed for a long time. A quote and a deal can disagree, with a deal amount that differs from its line items and several quotes at different stages hanging off one deal. What he wants is simple: "whatever they sign on the quote should actually update the deal."  The new capability looks like it lines up with that, with a caveat: "But it needs to be intentionally designed…"  He plans to dig in right away. "I'm going to play with it probably this week because I think this is an incredible opportunity."  Chris said he would expect a report on Thursday at the Unified Revenue View office hours, and Ryan agreed he would have something to talk about.

Why it matters: if you run Revenue Hub Enterprise and care about the buyer's quoting experience, what a buyer enters on the quote no longer has to stop at the quote. Whether you build it yourself or have someone build it for you, plan the design first.

For more details: Serverless Functions in Revenue Hub Enterprise.

Properties Schemas API

Chris raised this one because everyone gets excited about property schemas, and he read the what. The Properties Schemas API brings rollup and sync properties, field-level permissions, validation rules and richer property metadata to the API. I read the why: until now, building properties through the API meant working around gaps, because many settings in HubSpot's property tools could not be read or written programmatically, and validation rules lived in a separate API from the property they governed. The twenty-plus validation rule types now match what you can set in HubSpot.

I tied it to something from yesterday's show. "APIs just mean, what can your AI connectors do now? But I've gotten blocked on some of these exact things when trying to build properties."  Ryan was the strongest voice on this one. "This is truly a massive upgrade to the properties API."  He has more than once had to undo what he built through the API, when it created plain text properties that needed to be rollups, and he called the timing perfect.

Chris went looking for something the update text did not say, whether it reaches the documentation area in property settings, where data entry instructions live. He asked Breeze and shared his screen. Breeze said the update does not explicitly mention that dedicated area but does explicitly support property descriptions, data entry instructions and option descriptions, which Chris counted as another win. His reason it matters: "you can build instructions for them at the property level of how and when to use the property."  He was talking about agents using the CRM. I added that I have been happy with that section. "And I've been really happy with that documentation section overall."  It goes down to the option level too: "you can even give descriptions to the options."  I have been using that with a client on properties for their sales team, spelling out what makes a deal a particular type of deal.

Why it matters: a property built through the API can now match one built in the property settings, which means your AI connectors and your admins can build to the same standard. If you are building agents, write the property-level instructions as if a new teammate will read them.

For more details: Properties Schemas API.

New Run Settings in Agent Hub Workflows

Chris wanted me to pick the next one, and I chose this, then realized we had read it yesterday. I stayed on it for a moment anyway, because Chris's page says November and I thought it was new. This is the update that adds exclusion criteria and merge settings to the Agent Hub workflow builder. Exclusion criteria is the one Oakes and I talked about at length yesterday, because it was holding me back from building in Agent Hub workflows. "that's something that was a limiting factor that was preventing me from building in my workflows in Agent Hub."  Chris asked whether we are almost at full parity with the old builder, and I do not know enough to say. "I don't know enough to give that answer."  His answer was another question for Breeze.

For the full read, see yesterday's recap and the update page: New Run Settings in Agent Hub Workflows.

Audit Log Redesign

Chris gave me another pick and I took the audit log redesign, which I called a very sexy one. Chris read the what: audit logs now have separate Security activity and CRM data changes tabs, event filters for each tab, and clear attribution of whether a person or an agent made a change. I read the why. Security and CRM data events used to sit in one log, so tracking down a specific change meant sorting through unrelated entries.

I have checked the audit log many times, and it has improved over the years. What I like here is the new labels. "specifically these labels around security activities and CRM data changes that I think is good for if you are trying to figure out what happened when, just having more flexibility there."

Chris carried the rest, and his focus was the actor filter. It replaces the modified by and source filters, and you can use one search to find the person, agent or other source behind a change, including integrations. He had been creating properties in the CRM so that agents could stamp their names on records. "This should create the space to make it easier to see who's doing what, where, when, which is super important right now."  He also pointed at the people side of this. "I'm sure there's a lot of humans that have all of a sudden become very active in their HubSpot portal in ways they never were before because they are using AI to do stuff. And we need to be able to see that."

Why it matters: when a record changes and nobody remembers why, you now have a faster path from the change to the person or agent behind it. If your team has started building with AI, check the log with them before you need it.

For more details: Audit Log Redesign.

CRM Calendar View Enhancements

Chris went to this one next, saying he and Ryan already had a client call that morning that would benefit from it, and tying it back to the Gantt view from last week. He read the what, and the list is long: configure the start and end date properties that power the view, including custom date properties; see multi-day events; reschedule or change an event's duration with drag and drop; schedule events that are missing dates by dragging them from the left panel; create a new record by clicking directly on the calendar; show up to three properties on each event; and collapse the left panel. The view has also been visually modernized. I read the why, which is that the release addresses several of the top feature requests since the calendar view launched.

Ryan reacted first. "This is incredible. The whole drag and drop from the left side into the calendar is just really nice. It's a really cool feature."  He then went to where his own work lives. "I'm thinking about our unified revenue view, also booked, billed, invoiced. You can have four calendars for each of those dates."

Chris connected it to the question he and Ryan had been working through that morning: "how much do you build before you let it go to a team?"  His point was that a calendar used to demand that every date be in place before it was useful, so teams held back from building anything that might not have dates. Now you can capture a record when it makes sense and fill in the dates by dragging, and the context for AI to push the work forward is already in the CRM. He also liked how the calendar sits with Gantt and Kanban, so one dataset can be viewed at the level of detail a role needs.

He closed the segment with a tip for coaches and consultants. "Pro tip for any coaches, consultants, builders out there trying to help folks buy in to HubSpot, show them the calendar view."  His reason: "Everybody knows what a calendar view looks like in Google."  It gives people something familiar to stand on while they learn the rest.

Why it matters: a calendar built on the dates you actually track is an easy first view to hand a team, and the new settings make it possible to build the one that fits.

For more details: CRM Calendar View Enhancements.

The Close

We were at the hour before we knew it. Chris's explanation was that this is what happens when you start with Breeze. Chris and I will be at today's Hubsessed Office Hours on Loop Marketing and AEO in a couple of hours, so come with questions.

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.