Show recap — Tuesday, August 11, 2026

Another Orange Morning Recap: Tuesday, August 11, 2026

Tuesday opened with all three of us in the room, Ryan Ginsberg back in the co-host chair, and a running bit finally getting somewhere. Casey has been talking with Aaron Wiggers and Trisha Merriam about commissioning someone to play the show's AI generated theme song live, and Aaron has apparently raised her hand with some banjo talent nobody knew she had. Seven updates were on the board by the time the show got moving, and the morning worked through most of them with real depth.

Here is what we got into: a buyer intent signal called Company Surge that stumped two of us before HubSpot explained it, a faster and more accurate transcription experience for Notetaker, a hands-on look at the rebuilt property history table and the one-click revert that comes with it, quick takes on access requests for Users and Teams permissions and embedding live HubSpot pages on dashboards, and a Will It Breeze segment that turned into real Bombora topic picks for the Value First portal.

A Guessing Game Nobody Won: Company Surge, Powered by Bombora

Before HubSpot explained anything, Chris put Ryan on the hot seat and asked him to guess what a new signal called Company Surge might mean. He guessed hiring growth or revenue earnings, reasonable enough, and wrong. Chris admitted he would have guessed the same thing, and that turned out to be the more interesting confession, because the actual feature has nothing to do with a company's own performance. Casey had worked with Bombora before, so she took it from there.

Company Surge signals, powered by Bombora, are now in beta and native to HubSpot as a new intent signal. They surface which accounts are actively researching your category right now, pulled from Bombora's B2B research co-op across thousands of publishers and business sites, not from anything happening on your own website. Every signal is tagged high, medium or low research level plus category and top metro data, and it rides inside the intent signal tracking portals are already paying for. No separate Bombora account required.

Why it matters: This is the first time HubSpot has folded a named third party's data straight into an existing signal category rather than launching it as its own bolt on product, and we read that as a pattern to watch rather than a one off. The advice that came out of the segment held up well. Start tracking topics you care about now, because the value compounds the earlier you start, and HubSpot has already shown with custom signals last month that this list keeps growing.

For more details: Company Surge, Powered by Bombora.

The Fifty Task Problem: Enhanced Meeting Transcription for Notetaker

Ryan picked this one, and it came from a real pain point. HubSpot's new transcription experience for Notetaker promises transcripts up to four times faster than the current experience, plus better handling of non-English and multilingual conversations where speakers switch languages mid meeting.

Ryan's case for why speed matters was personal. He uses Fathom for some meetings and gets a transcript almost the moment the call ends, and Google Meet's native transcription for others, where the wait can stretch past an hour. By the time that slower transcript lands, he has usually forgotten the detail he would have caught and corrected on the spot. The update is scoped tightly though. It only applies to meetings recorded with HubSpot's own native Notetaker, not calls captured through a Zoom, Teams or Meet integration.

Why it matters: The more interesting thread came after the transcript itself. Ryan raised something he has actually run into, handing a transcript to an agent for next steps and getting back fifty tasks that clearly are not fifty real tasks. A faster transcript does not fix that on its own. It just means whatever is broken about the step after transcription shows up sooner.

For more details: Enhanced Meeting Transcription for Notetaker.

The Deep Dive: Property History Gets a Restore Button

This was the day's on screen segment, and Casey pulled up a real portal to walk through it. Two updates landed together: a rebuilt property history table with a cleaner layout, filtering by source and date range, and search, plus a new single property revert that restores one value directly from that table without running a full restore workflow.

They clicked into a contact's lifecycle stage history to test it live. One thing HubSpot has not spelled out is what a revert actually does to the record of what came after it. Our hunch is that it brings the old value back up as a new entry rather than erasing the changes in between, because the whole reason the history exists is compliance and quietly deleting it would work against everything HubSpot has built there. That is a hunch, not a confirmed spec, so check it against your own portal before you lean on it for a compliance answer. There is a real limit worth knowing. Changes older than two weeks cannot be restored through this shortcut, which reads as a governance guardrail more than an oversight.

The bigger thread of the segment was not the button, it was who gets to use it. The case we kept circling back to is letting the rep who owns a small set of properties fix their own mistakes without needing an admin to intervene or a Slack thread to untangle what happened. Casey brought up a real example, a client asking why a record had switched to customer status, which traced back to a sync lifecycle stage setting rather than a workflow. Having that source visible right in the history table would have cut that investigation down considerably. It also came up that HubSpot used to require third party apps to do exactly this kind of property recovery, and this update folds that capability in natively.

For more details: Property History Table Updates and Revert Single Properties in History Table.

Two Smaller Updates Worth a Look

Access Requests for Users and Teams

Casey raised this one. If someone tries to open the Users and Teams settings without the right permissions, they can now request access directly in HubSpot instead of pinging an admin cold. The modal captures what they are trying to do and notifies an admin with a link straight to the edit permissions page, context already attached. Her honest reaction was mild disappointment that it is scoped to just this one settings page for now, though the read from the segment is that starting narrow, on a page people rarely request by accident, makes sense before expanding it further. Kyle Jepson had raised a related idea a few weeks earlier about using Breeze to help people navigate permission requests, and this update reads like a step in that direction even without saying so directly.

For more details: Access Requests for Users and Teams.

Live HubSpot Pages on Dashboards

You can now embed live HubSpot pages, deal boards, contact lists and ticket boards, directly on a dashboard, instead of grabbing a URL and stuffing it into an embed card. Casey had assumed it meant embedding a website or landing page and was pleasantly surprised it meant real CRM views instead. The bigger point that came out of it is that dashboards have always been for looking, index pages have gotten steadily more actionable, and this is one more step toward closing the gap between seeing something in HubSpot and being able to act on it without leaving the screen.

For more details: Embed Internal HubSpot Pages on Dashboards.

Will It Breeze: Picking Bombora Topics for Our Own Portal

The segment turned Breeze loose on the Company Surge update from earlier in the show. Breeze confirmed the Value First portal is eligible, credits are provisioned, and buyer intent is already live in the nav, but it could not confirm from its current view whether the Company Surge row and its select topics button were actually visible in the signals panel yet. From there it recommended twelve Bombora topics for the portal, things like revenue operations, customer relationship management, marketing automation and sales enablement.

Someone asked why the recommended topics were so broad rather than specific. Casey's answer, drawing on past experience working with Bombora, is that it is intentional. Narrow topics can return nothing to work with, while a wider bucket gives you a real pool of companies to filter down by location, size or whatever matters next. The conversation also covered what not to do with a high intent signal. Reaching out to say you noticed a company surging on a topic reads as strange and a little invasive. The better move is widening touchpoints, connecting with more people at the account, especially if you are already publishing on that topic, and layering in other signals like event attendance before making contact.

Why it matters: Chris's closing point was aimed at anyone still saying they cannot keep up with HubSpot's release pace. He brought up a conversation with a product marketing manager a month into the job asking exactly that question, and the answer was simple: ask Breeze directly, and half the time it will set the thing up rather than just explaining it. Stop treating the update firehose as something to keep up with manually when the tool sitting in the portal will do the reading for you.

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

The Rest of Tuesday's Updates

We worked through six updates in depth this morning — five of Tuesday's seven releases, plus one from Monday we had not gotten to yet. Everything else that shipped on the tenth and eleventh is in the HubSpot updates feed, including the ones we did not talk about: local time campaign sends changing on August 19, portal-level billing settings, marketing contact limits, line-item view permissions, sandboxes copying website and landing pages, the Eventbrite attendee-question sync, and the Chatflows Node 24 deadline at the end of the month.

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.