Monday, October 19, 2026, with Casey Hawkins, Chris Carolan, and Joshua Oakes

Another Orange Morning Recap: Monday, October 19, 2026

Monday opened with a birthday. Chris Carolan wished his stepfather, Craig Everett, a happy one, and then it was the three of them: Chris, Casey Hawkins, and the Monday Friend, Joshua Oakes, who answers to Oaks and had a very different update list in his portals than the hosts had in theirs. That turned out to be the shape of the morning. Three people, three lists, and a viewer question that pulled the show nine minutes deep into SQL.

Here is what we got into: the Hubsessed newsletter landing today on what comes before lead, Breeze in quote templates, a dashboard header cleanup that opened into a rule about which metrics belong at the top, HubSQL and the limits of left joins, bulk delete and restore for index views, Breeze Assistant doing real work from Slack, and a Will It Breeze under the Finance lens that asked Stripe and Orders for the update your boss will ask for.

What Comes Before Lead

Chris had spent the weekend helping Nico Lafakis with the prep and post-production for Hubsessed Office Hours, AI-Native Edition, which Nico and Trisha Merriam host Mondays at 11 a.m. Central. It is free for free Hubsessed subscribers through the end of October and moves into the paid subscription after that. Recaps run on the site and in the Hubsessed newsletter, which the team is now trying to send weekly.

Casey's newsletter goes out today, and it is about a conversation she, Chris and George B. Thomas had on Friday's Super Admin session: lifecycle stages, and specifically what comes before the stage everyone calls lead. She was careful with her words so as not to set Chris off on redoing every stage, and she credited Oaks as the first person who opened her eyes to the idea that before there is a lead, there are people in your CRM who have never interacted with your business and may not know it exists. Whether that is best practice or not does not matter; it is a thing that happens.

Chris, for the record, loved the article, and called it baby steps in the right direction. His read is that the space before lead is usually just not well defined. Subscriber does not make sense in most cases, and yet those people need to be in the CRM, so what are they called? The key is not calling them lead if they do not fit the definition of lead, and getting that definition on paper is often the way a team agrees on what a person who just landed in the system actually is. Oaks had missed Friday's session and planned to read the recap and see who he agrees with, and his practical add before the show moved on: the default setting creates new records at lifecycle stage lead. Go change it, in your portal today or on any new portal, to whatever stage you decide comes before lead, so you stop skipping people ahead without realizing it.

Casey called the newsletter one of her prouder pieces of writing, then wondered whether she should wait to say that until she saw the open rate. The reminder from the room was that opens by themselves do not tell us anything. If you subscribe to Hubsessed now, it lands in your inbox in a couple of hours.

Breeze in Quote Templates

Chris's first pick was Breeze in Quote Templates, a public beta for Revenue Hub Professional and Enterprise. Breeze already worked inside the quote editor; now it works in the quote template editor too, with the same chat-driven editing on the template a quote came from. Casey's immediate question was whether this means legacy quotes or the new quotes, and she answered it herself: Revenue Hub Professional and Enterprise means the new quotes, which had been her guess.

Chris's take was the workflow. If you have been doing fun things on specific quotes because Breeze was in the quote editor, and you catch yourself doing the same thing ten times, you no longer have to take a pile of instructions from Breeze and recreate them by hand in the template editor. Make a brief with Breeze Assistant while you are in the quote you like, then pick that brief up when you go over to the template editor and start from there.

Why it matters: The gap between a good one-off quote and a good template is where most teams leave consistency on the table. Closing it with the same assistant on both sides is a small update with an obvious habit attached. For more details, see the Breeze in Quote Templates page.

The Dashboard Header, and What Belongs at the Top

Oaks picked Friday's Reporting Dashboard header simplification, a minor one by his own description, but he loves seeing these because making work and performance visible is a priority for every business, and it is what the Wednesday Reporting and Dashboards Office Hours is about. The update compresses everything above the filter row. Casey pulled up a dashboard so the show could do a side by side with the new look, and the two legacy top actions, create dashboard and manage dashboard, are out of the header where they no longer need to be. The piece Chris picked out is the link you can click without digging it out of a dropdown, and Oaks noted the share button now has things like share via Slack behind it.

He also pointed at the persistent metrics across the top of the dashboard, a recent update the show had not covered, which lets you pin the same top-line numbers across every dashboard the way you can on index views. That led Chris to the better question: does Oaks have tried and true metrics he puts in that top bar? He thinks about it team by team, carrying over what he already does with clients in index views. A sales team or an individual rep gets whatever the organization calls its gating metrics, MQLs, SQLs, total pipeline, a handful of numbers that cover most of the data questions anyone gets asked in a week. His one firm rule is to never put an activity count up there, because number of outbound calls made is a false metric. We want to move outcomes, not actions. Casey liked it as a simple rule to follow.

Why it matters: The header cleanup arrives on its own and asks nothing of you. The top bar does ask something: pick the three or four numbers a team is actually accountable for and leave the activity counts off. For more details, see the Reporting Dashboard header simplification page and the Reusable Metrics on Dashboards page.

Has Anyone Tried HubSQL Yet?

A viewer asked, and the answer on the show was no, not yet. Oaks requested HubSQL on one portal and was denied, which is how private betas go, so he parked it until it goes public. The hosts were fairly sure the show had covered it back in early September, and Chris's framing today was the same as for datasets, Data Hub and Data Studio: unless this is where you live, in databases and data science, it is not something you can wander into and have it make sense. If the words joining data mean something to you, this is for you. For most HubSpot users he knows, they do not.

Oaks sharpened it: if you have heard of anything besides a left join, this is definitely for you. He is wrestling with a couple of multi-headed reporting problems right now that Data Studio cannot solve because it only supports left and inner joins, for clients with no external warehouse or BI tool, where HubSpot data needs to sit next to data that is natively not HubSpot and then be visualized in ways HubSpot reports do not support. What he does not want is vibe-coded dashboards living on external systems that everyone has to remember a link to and nobody checks on in six months. HubSQL is a potential path for that, with the last-mile visualization question still open.

Chris's read is that this is HubSpot accepting what people are already doing. Data scientists have wanted SQL access to the tables for a long time, and people are building sophisticated dashboards with Claude on top of a connector or an API key that still does not reach everything HubSQL does. The update page says it outright: paired with AI, HubSQL makes self-service analytics a reality. Oaks' caution is the other half of that sentence. With unfettered access, the biggest problem becomes not knowing which properties you should be looking at. He keeps running into the enthusiastic stakeholder who has connected Claude or ChatGPT to HubSpot and built a really cool dashboard that tells a story and is fundamentally wrong, counting everyone who ever became a customer instead of everyone whose subscription is still active, so the company appears to have fifteen times as many customers as it does. The more powerful the tool, the more dangerous it is to use incorrectly, and that is not solved yet in any of these tools.

Then the fine print. Chris pulled up a post from someone who has been testing it, and the current beta only gives you left joins, and they have to follow existing HubSpot associations. Oaks was relieved he did not get the beta access, since that is time saved, and it looks like the same constraints Data Studio already has, minus inner joins. Baby steps, which the hosts assumed was the right read because it is how HubSpot usually does things, with nobody claiming enough SQL to go deeper.

Why it matters: HubSQL is the right direction and not yet the tool the question imagines. If you need joins beyond left and associations beyond the ones HubSpot already knows about, you are still waiting. For more details, see the HubSQL page.

Bulk Delete and Restore for CRM Index Views

Chris asked for a less nerdy one and shared his screen for Bulk Delete and Restore for CRM Index Views, which is live for every hub and tier, although the portal on screen did not have it yet, so, as Oaks said, it is on a slow rollout. You can now see when each index view was last used, delete views in bulk, and restore deleted views yourself from a new Recently deleted page, with a ninety-day window to recover anything removed by mistake.

Casey said hallelujah. Oaks had gone straight to the portal with his most egregious example: two hundred and change views on the deal object, in a company that still uses deals as projects from the pre-pipeline days. His guess is about twenty of them are used. The rest are things like All deals dash one through dash five, created by different users and sometimes by the same person twice, and copies of somebody's this week view and somebody's project view. Casey's version is baggage. Views have changed a lot over the last few years, and people have moved to board views and other things that were not possible before, so a lot of the portals she works in carry old views nobody opens anymore. This is a clean way to clear some of that out.

Chris's adoption point: if you let people treat index views like an Excel spreadsheet in the beginning, they will clone whatever view they are given because changing someone else's view is not how spreadsheets work. Now you can get adoption first and clean up after, instead of a ten-checkpoint approval process for every view that nobody was going to follow anyway. Oaks' admin fantasy was select all, delete, and then when somebody complains, go restore their most viewed view. Chris loves that kind of admin. The Slack message that would follow, all my records are gone, got a laugh and a reminder that we love HubSpot users.

Why it matters: Usage tracking only started in March, so a view showing no data is not the same as a view nobody uses. Sort by last used, delete in bulk, and keep the restore page in your back pocket. For more details, see the Bulk Delete and Restore for CRM Index Views page.

Breeze Assistant Does Real Work From Slack

Two Slack updates went live. The bigger one is Breeze Assistant updating records, enrolling records in workflows, prepping for meetings and logging calls, all started from a Slack thread. The page describes the jobs: duplicate cleanup, reassigning accounts in bulk, enrolling contacts into workflows, the kind of work that today means leaving Slack and taking several steps in HubSpot.

Oaks concluded from historical patterns that all of it will be permission gated even though the page does not say so, because reassign all of Sarah's accounts to Mike is the kind of sentence that becomes a problem fast. Casey's guess is the same: only if Slack is connected and your user already has those permissions. Her larger observation is a recurring one, that people are increasingly using HubSpot without being in HubSpot, and she is curious to see how that evolves.

Oaks' take came from his month. October has turned out to be the month of sales territory and record ownership reassignment across a bunch of his projects, and territory rules are rarely just region; there are specialties and other parameters, and automations and governance behind them. He has been encouraging clients, not terribly successfully by his own admission, to get the things they build documented in Breeze context, whether that is a knowledge vault or the overall AI context, so that when someone tells Breeze in Slack to reassign a batch, it has the same awareness Breeze in HubSpot would and knows not to blanket-reassign deals and companies that rules govern. Chris's framing: this is the moment where agents shine. AI has made it easy to reach systems of data from anywhere, but editing a ticket record from Slack is different from asking the agent to make the updates. He read the hard-to-see screenshot, where a request to build a deal workflow comes back from agent: Breeze with an approve and build step and a publish-or-draft choice, and took the agent label as a hint that other agents could show up in Slack too. The effort you put into granular user permissions on the HubSpot side is what makes bringing Breeze into Slack safe.

The second update is richer responses: tables, record and meeting cards, reports with a link back into HubSpot, instead of plain text. Casey brought it up because it surprised her. She had read richer as deeper, more explanation, and it means formatting. Oaks wanted GIFs.

Why it matters: Bulk changes from a chat thread are only as safe as the permissions and the rules behind them. Before you let Breeze reassign anything from Slack, make sure the rules it should respect are somewhere Breeze can read them. For more details, see the update records from Slack page and the richer responses page.

Will It Breeze: The Update My Boss Will Ask For

Oaks picked Finance, and said nobody ever picks it; Chris pointed out that he picks it about half the time. The wheel landed on Orders, Stripe, and write the update my boss will ask for, and the composed prompt read: as our finance lead, using Stripe, can you write the update my boss will ask for across Orders? Oaks asked whether the portal has its team structure set up so Breeze knows who the boss is, and the answer is that you can, because team management now carries a whole org chart in the user management area, so in theory Breeze could know your manager.

Chris ran it on his screen, in the Value-First Team portal's orders view with Breeze Assistant open. His lesson while it worked was the point of the Finance lens. Nobody really uses or even knows about the finance side of HubSpot, and you could be the RevOps person who has never been in charge of the back-end system or the revenue reporting, with people starting to ask what HubSpot can do here now. You do not need finance experience to facilitate that conversation, and you do not need a two-week course. If you have the most context about how your HubSpot is set up, you are the right person to ask, and asking this outside HubSpot, in Claude or GPT, gets you a much less contextual answer, closer to do not do that in HubSpot, or a list of questions Breeze already has the data to answer.

Breeze came back with a real finance update, and the first line was a hygiene problem: only thirty of one hundred thirty-six orders have a total amount populated. It drafted the orders finance update for leadership covering financial visibility, collection evidence, reconciliation gaps and recommended actions, and flagged that it could not independently verify Stripe's ledger. Chris's close was the pattern he sees with orders. Part of your business integrates a Stripe or a Shopify, that data comes in as a new object type while everything else still runs through deals, people start asking questions, and Shopify is arriving in a very specific way that is probably not how your B2B business works. Those gaps lose trust in the system very quickly, and if you get out in front of them, even if you have never looked at orders before, you have a better chance of the buy-in you need, and a clear place to say that data lives in the other system and here is where it would plug in. NetSuite, looking at you. Watch the episode for the full run.

The Rest of Monday's Updates

Two more shipped that did not get airtime: Updated Report Visualizations, a public beta refreshing every chart type with a new palette, repositioned legends and clearer tooltips, scheduled to reach portals October 20, and the Zoom Connector for Breeze Assistant, a public beta that lets Breeze and HubSpot agents read Zoom meetings, AI Companion summaries, recordings and Zoom Docs on request. Friday's two, Manage Spend between Seats and HubSpot Credits and Customer Agent understanding WhatsApp voice notes, were covered on Friday's show. 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.