Show recap — Monday, August 10, 2026

Another Orange Morning Recap: Monday, August 10, 2026

Monday opened with Joshua Oakes back in the room, a screen share that would not cooperate, and a countdown clock reading thirty six days to Unbound. It also opened with a promise coming due. Friday's show closed by saying Will It Breeze would be back this week with a focus on AI ROI, and this was the morning that had to make good on it.

Here is what we got into: the Road to Unbound page and the format change behind it, scheduled prompts arriving in Breeze Assistant, product usage tracking landing in Service Hub, manual meeting syncing showing up in the Google Calendar sales extension, and a live run at Will It Breeze that asked Breeze to report on the ROI of the AI already running in the portal.

The Road to Unbound Opens Its Door

Casey walked through an updated Road to Unbound, including a new be-a-guest page for anyone who wants a seat on the show. It is built with HubSpot Unbound insiders in mind, though the position taken on air was that nobody with something to say about Unbound is getting turned away.

The more interesting change is underneath the page. These conversations have been recorded on demand as podcasts for the past couple of months. With Kyle Jepson out for a month on sabbatical, the Thursday sessions are shifting toward something closer to open office hours, which is a deliberate move to widen the number of voices in the room rather than book them one at a time.

There is also an Unbound 2026 channel up in Slack for the Value-First team and collective, where the hot topic has been the least glamorous part of any conference, which is finding somewhere to sleep. One useful scheduling note surfaced in that conversation and is worth repeating outside it. Unlike the last couple of years, Labor Day does not fall inside the Unbound window this time, so the Monday is a working day for most attendees. If you are planning meetups around the assumption that everyone has a holiday, that assumption does not hold this year.

Three Updates Worth Pulling Forward

Scheduled Prompts in Breeze Assistant

Breeze Assistant can now run a saved prompt on a recurring schedule, daily, weekly, monthly or annually, and drop the answer into your chat list when it finishes. Until now those chats have been reactive, running only when you opened Breeze and asked for something. A Monday morning pipeline check or a weekly account health summary can now be waiting for you instead.

The conversation on air moved quickly past the capability and onto the interface, which is where the real argument lives. If a feature is proactive, the output should not be something you have to go looking for, and right now it is. The answer lands in your Breeze chat list, which means opening Breeze, finding the three dot menu, and clicking through to chats. The version of this that changes how anyone works is the one where the result meets you on the HubSpot homepage, on the page you were already going to open.

Why it matters: This is a necessary step rather than the destination, and it is worth building in this order. But do not expect a scheduled prompt to change your behavior on its own. If you set one up, point it at something concrete you will actually look at, a pipeline number or a call prep brief, rather than the vague daily summary that demos well and gets ignored by Wednesday. Skip the annual cadence for now. Enough will change about these tools in twelve months that a once a year prompt is the definition of set and forget.

For more details: Scheduled Prompts in Breeze Assistant.

Product Usage Tracking

This one came back around after showing up on Friday, and it took a second look to place it. Service Hub customers can now define product activation and usage benchmarks using custom events and an expected frequency, up to ten events per portal. Customer success teams get a read on feature adoption and, more to the point, on adoption falling off.

The capability underneath is not new. You have been able to track product usage through custom events for years. What is new is that HubSpot has given the use case a name and a setup path, which sounds like packaging until you remember that event management is a bridge most portals never cross. The conversation went somewhere sharper from there, into how this data normally lives in a warehouse and never makes it back into the customer record. You end up with the numbers in one system, the relationship in another, and two teams who each own half the picture. That is the friction a unified customer view is supposed to remove, and product usage is one of the places it most often survives.

Why it matters: If you run HubSpot for a software or digital product company, go look at your events before you do anything else here. There is a good chance data is already flowing in that nobody has done anything intentional with. The honest caveat is that instrumenting this properly means real work on the product side, and doing it twice, once for your analytics stack and once for HubSpot, is the trap to avoid.

For more details: Product Usage Tracking.

Manual Meeting Syncing in the Sales Extension for Google Calendar

From the HubSpot sales extension inside Google Calendar, you can now manually push a meeting into HubSpot and set its CRM associations at the moment you create it. Previously, if a meeting did not sync on its own, often because the contact did not exist in HubSpot yet, your only route was to go into HubSpot, create the contact, and hope the sync caught up.

Joshua took this one, and spent most of it on the limitations rather than the feature, which turned out to be the right place to spend it. Cancelled meetings, private meetings, and meetings with no association attached still will not sync. And if you manually sync one instance of a recurring meeting, HubSpot logs that single event, not the series. That second limit is the one that matters. Stable weekly meetings are not where calendar sync falls over. It falls over on the orphaned instance, the week somebody dragged the time or split off a separate invite, and that case is not fully solved yet. HubSpot says support for syncing multiple events from a series is coming before this reaches public beta.

Why it matters: What this fixes today is the everyday version of the problem, digging through HubSpot for a meeting that never arrived and rebuilding it by hand. That gap closes, and being able to set associations from the calendar rather than after the fact removes a second step nobody enjoyed. Watch the recurring series handling as it moves toward public beta, because that is where the remaining pain sits.

For more details: Manual Meeting Syncing and Enhanced Meeting Creation in the Sales Extension for Google Calendar.

Will It Breeze: Can It Report on Its Own ROI

Will It Breeze has been part of the show for a while in a loose form, a wheel spin and a question. Today was the version with structure behind it, a scope, an app and a business outcome, and a prompt drawn before air. Chris was candid that the wheel still needs work and that this particular draw was not a good one, which is a reasonable thing to say out loud about something being built in public.

The prompt asked Breeze to report on the ROI of the AI being used in the portal. Chris ran it in his, Joshua ran the same prompt in his, and the two answers were compared live. Breeze made a real attempt, pulling from AI settings, product context and CRM activity, and produced an AI ROI report with charts. It also could not verify a hard number, because it had no clean attribution trail tying AI usage to saved hours, influenced revenue or avoided cost. Pushed further, it had to be told to go and check Agent Hub, which is a strange thing to have to ask when the question was about AI.

The most useful line came out of Joshua's portal, where Breeze reported that the portal was not set up to prove ROI in a finance grade way. The reaction on air was that this is the correct answer for very nearly every portal asking that question right now, and that it is not really a HubSpot failing. You cannot record credits consumed against a specific deal, AI cost is not only credits, and a workflow action doing record hygiene is no more measurable in isolation than any single node in an automation. The question being asked of these tools is one the instrumentation cannot answer yet.

Why it matters: Everyone is getting asked this question, so the value here is not the report. It is that Breeze can hold a conversation about AI ROI with whoever is asking, and that a conversation is the right shape for it. Start with what is actually installed and what is actually being used, treat the first output as a draft, and take the several rounds it needs. What you should not do is show anyone that first report. Anything measured in strictly black and white terms on this topic is missing most of the picture.

You can watch the full segment on the Will It Breeze archive.

The Rest of the Week's Updates

The show pulled three forward, but fourteen releases were on the board across Friday and Monday, and the rest are worth a scan. On the admin side there are view permissions for standard line-item properties, which finally extends field level control to viewing sensitive pricing and margin data, plus two sandbox improvements, one copying website and landing pages from production and one copying permission sets so UAT can start without rebuilding them by hand. Payments picked up the ability to remove a stored payment method directly from a contact or company record.

On the AI side, HubSpot is recruiting testers for a rebuilt Social Content Agent that grounds its drafts in your own CRM data and past performance rather than the calendar, Customer Agent can now be assigned to calling channels for voice, and its performance reporting has been redesigned. Elsewhere there are four new Campaign API endpoints covering cloning and asset types, custom metrics on Global Home, real time table updates across index and record pages, and dashboard caching you can tune from five minutes to seven days.

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.