Show recap — Friday, May 22, 2026

Another Orange Morning Recap: May 22, 2026

Friday show. Casey and Chris were joined by Madelyn Donovan. Chris opened by bragging about the perfect weather in Texas. The release list from Thursday was long enough that Casey called herself overwhelmed in the cold open, which is the right energy for a twelve-update day. Memorial Day weekend is on deck, and the show closed with a Madelyn-driven analogy that may be the cleanest framing yet for what is about to change in the workflows tool.

Here is what we got into: a centralized data model finally arriving in one place, custom-coded modules for quotes going live, a one-line dashboard PDF update that did not need any explanation, Breeze stepping into accounts receivable, a HubSpot product update that is barely a product update, the rename of AI Data Sources to Context Home, Will It Workflow on notes, and the agentic automation builder framed as Mercury in retrograde.

Centralized Data Model Management

This is the kind of update Chris has been quietly hoping for. A unified table and graph view for managing objects, properties, associations, and conditional logic from one place. This is in private beta across all hubs and tiers, and Chris is still waiting to be unlocked.

Before clicking in, Chris quizzed Madelyn on what she thought the update would be. She nailed it: there is a lot of data-model work that used to live in settings and a lot that still lives there, so the bet is that this is the merge. That is essentially right. The view ships with a table icon, a flow-chart icon, and an expansion view in the upper left, and the early read on it is that it looks easier to navigate than the current setup, especially when you are on a client call and trying to find your way back to a property group without making it obvious you do not remember where the link lives.

Why it matters: The data model in HubSpot has been a real pain point for years. The "where am I, objects or associations, and which screen has the thing I need" loop is something even people who work in many portals deal with. Chris has been building data-model visualizations outside HubSpot with Claude Code apps just to get a static reference he can trust. The team has been heads-down on this for a while because it has been on the request list since the data model started expanding. The bigger thing this signals is that auditing complex configurations is becoming a first-class workflow inside the platform, not a workaround. Next on the wishlist: stop calling credit memos sales objects.

For more details: Centralized data model management private beta.

Custom-Coded Modules for Quotes Goes Live

This one moved from public beta to live, which is the news. The capability itself has been covered: developers, admins, and HubSpot solutions partners can now embed custom-coded, interactive, data-rich modules directly into quote templates or individual quotes. Modules can access CRM data, pull from external sources, capture inputs and push them back to the CRM, and present interfaces to quote creators while they build, which is the CPQ piece HubSpot has been telegraphing since Inbound last year.

Most of the Why It Matters bullets HubSpot published read like a direct response to feedback from Partner Day. Replace the line items table, render product services and totals however you want, swap terms and conditions language based on company properties, pull in architectural drawings from an external database, capture onboarding or billing info during quote acceptance. As HubSpot's release note put it, the possibilities are endless. Chris's read: that line is not the marketing flourish, it is closer to accurate this time.

Why it matters: The bigger thing this signals is the CMS-CPQ collision. CMS and CPQ have traditionally been completely separate sides of the business, and you needed CMS architecture to customize quotes the way teams have always wanted. By landing these modules on CMS architecture, HubSpot is making "different data that needs to come together" the actual design principle, not "different sides of the business." If you have an AI coding tool you are comfortable with, the developer platform is also more reachable than it was. Chris built one in a couple of hours without prior setup. Worth flagging that, as he noted in the past, custom modules are only as good as the data model behind them. CPQ implementations get burned when the build ships before the data is ready.

For more details: Custom-coded modules for quotes now live.

Dashboard PDF Exports Look Like Dashboards

The title was the whole segment. Casey asked if she could just read the title, Chris said yes, and that was the right call. PDF exports of dashboards now retain the full dashboard layout, including charts, tables, titles, dates, and filter context, including for scheduled report exports sent via email. This is in public beta across all hubs and tiers.

Why it matters: This is one of the updates where the name says "now does what you always thought it did." Madelyn loves these. Worth flagging because exported dashboards are the version of HubSpot data most leaders actually see, and the formatting gap has been a quiet drag on how much teams trust the platform as a reporting surface.

For more details: Dashboard PDF exports look like dashboards public beta.

Prioritize Invoices with Breeze

You can now use Breeze to prioritize open invoices by revenue impact and send personalized collection emails. The aim is to focus accounts receivable work on the invoices that matter most and accelerate cash flow. This is in private beta. The tier list reads as all hubs and tiers, Commerce Hub Professional, Commerce Hub Enterprise, which Casey called weird because that combination does not usually show up that way. Chris's read is that invoices in general do not require Commerce Hub, but some specific invoicing capabilities, especially around billing structures, are starting to. Casey was able to request the beta in her starter portal, so the gating may be lighter than the tier list reads.

Why it matters: Collections work is a real pain that nobody else is solving. QuickBooks and most ERPs hand the team a screen of open balances and leave them to do the discovery, the prioritization, and the customer outreach. None of those steps happen near the customer data, which means the team is either jumping between systems or calling people who do have context. Bringing the prioritization, the personalized message, and the customer record into one place is where Breeze actually earns the AR use case. When you can communicate better, people pay, and they pay faster.

For more details: Prioritize invoices with Breeze private beta.

HubSpot Capital Financing for Commerce Hub Payments Customers

This is the update that made everyone on the show stop and ask whether it was a product update at all. Commerce Hub customers using HubSpot payments or Stripe payment processing in the US and UK can now access capital financing directly within HubSpot, based on their payment history. This is in public beta. There is no beta button to smash because it is an org-level rollout, not a tool to enroll in.

The cool piece is the mechanical one. Stripe Capital underwrites businesses based on processing history. HubSpot is so deeply integrated with Stripe that it can surface that financing offer right inside the platform, which is a real reason to stay on HubSpot payments instead of switching processors. Chris's read: this is one of the levers HubSpot is pulling to get more businesses using Commerce Hub, period.

Why it matters: It is a business update more than a software update, and that is the interesting part. Platforms with payments data have a real wedge into financing, and HubSpot has decided to use it. For SMBs running on Commerce Hub, the option to pull capital from inside the tool you already use, based on data the platform already has, is a meaningful shortcut compared to a separate application. The careful part: how this shows up to leadership matters. "Hey, come get more money from this part of your HubSpot platform" lands differently depending on who is reading the message.

For more details: HubSpot Capital financing for Commerce Hub payments customers public beta.

Context Home Replaces AI Data Sources

Madelyn spotted this one while the hosts were trying to find another setting and noticed her portal URL said "/context-home." Context Home is the new centralized place for context, replacing what used to be called AI Data Sources under AI Settings. Customers can now view and manage all the context HubSpot holds on their business, including business information, customer information, and team and process context, in one location. This is live across all hubs and tiers.

Why it matters: The brand identity, brand overview, AI data settings, and knowledge faults have been scattered across the portal for as long as anyone has been using them. Consolidating them under one Context Home page is the same move the data-model team is making with centralized data model management: take a sprawl of settings pages and give it a single, scannable home. The reason it matters specifically for AI is that the context layer is what powers everything Breeze does. If teams cannot find or maintain it, the AI gets worse. Worth a walkthrough next time you are in your portal.

For more details: Context Home live.

Will It Workflow: Note, Companies, Send to External System

The wheel landed on the note object as the object, companies as the app, and "send to external system" as the use case. Casey called it weird, and then immediately realized she had built something like this for a client. Madelyn had too. First time on the segment that both hosts had the exact use case already shipped.

The build Casey walked through: a property on the company called Latest Note, populated by a workflow triggered when a note is created today (the filter had to be set in a segment, not the workflow itself), with the most recent note body associated through the note object and run through a small bit of formatting code to strip the HTML. The reason that specific design wins is the sales meeting use case. The team runs a table report that lists companies with their latest note, and if you use the association directly, the report shows every note on the record, which defeats the point.

Chris widened the lens on it. The whole conversation is the kind of thing teams used to push into more and more structured properties because the alternative was building reports they could not control. Now that notes are a real first-class object with workflow support, associations, and threaded conversations, you can move a lot of that work out of properties and onto the note object itself, especially if you adopt a naming convention so the note body becomes searchable. The trade-off is the trade-off you always make in HubSpot. Structured data is easier to report on. Unstructured data is easier to capture and easier to ask AI to read. Where you land depends on whether the team is going to be looking at the report or asking Breeze about it.

Will it workflow? Yes, both versions of it have shipped. Watch the episode for Casey's actual build, including the formatting code that cleans up the HTML.

The Close: Mercury Is in Retrograde for the Linear Workflow Builder

Madelyn closed the show with an analogy that landed harder than expected. Workflows are the nervous system of the platform. The linear workflow builder, the one-object, one-direction tree we have all been using for years, is officially going into retrograde. The new agentic automation canvas, currently in private beta from last week's announcement, is drag-and-drop, starts from any trigger including a Google Sheet row, requires branches before you can publish, and treats every workflow as a non-deterministic flow that the old builder was never built to handle.

Mercury gives and Mercury takes. It took the straight line, and finally, finally gave us a canvas. Chris and Rylee were going to unbox this update yesterday and held off so they could align first, which says everything about how big the change is. The reassurance Madelyn added matters: flexible does not have to mean complicated. The simplest workflows will still build the simplest way. The expectation management for the rest of us is that the new builder is closer to "current workflow tools on a canvas" than "rebuild your brain," and HubSpot will move the platform in baby steps so people get comfortable. They have to, because if teams do not feel comfortable with this kind of agility, they will not use it.

The Rest of May 21's Updates

Several updates from May 21 did not get pulled forward on the show, including Run Agent Workflows Action (public beta, the new way to orchestrate Breeze agents inside the Workflows app), Content Recommendations for Emails (private beta), Create/Edit/Analyze Products in Breeze Assistant (live), Manage Stage Calculated Properties by Pipeline (public beta), Playbooks in Sandboxes (private beta), and Sandbox Support for Multi-Brand Assets (private beta). Full breakdowns of all twelve updates from May 21 are on the updates blog: HubSpot Updates: May 21, 2026.

The Sign-Off

You probably already own the value you are looking for in HubSpot. You just need to wake up to it. Have a great Memorial Day weekend.