Show recap — Monday, July 20, 2026

Another Orange Morning Recap: July 20, 2026

Monday morning, a new show time, and the first real proof that the new time was the right call. Joshua Oakes was in the Friend chair, and the episode opened where a lot of Mondays open lately, with Chris Carolan promising to sing the theme song one of these days and pushing the date out to Unbound.

Here is what we got into: forms that can finally be unpublished, the meetings calendar arriving in the main navigation, filtering straight from a column header plus news from a HubSpot filters team most people do not know exists, webhooks landing inside custom agents, and the conversation that ate the back half of the show, which is what happens to the ROI question when everything in your portal starts costing credits.

The New Time Is Already Earning Its Keep

At the top of the hour there were no updates on the page from Friday. By the time the show pulled the page up again, eight updates from Monday were sitting there. That is the whole argument for moving the show, in one refresh.

The 9am Eastern slot works like a moment of release. The old pattern was going a little long, looking back, and realizing an update had dropped mid-show, then watching LinkedIn fill up with posts about it for the rest of the day. That particular flavor of missing it is gone now.

On the theme song, Oakes noted that he lives in Nashville, where the neo-country stomp folk singer-songwriter thing follows you to the mailbox. Chris, who built the song with AI after a lot of work on strategy, themes, and tones, admitted that anybody who knows him would not call it his usual thing. He does practice it daily, to himself, so Unbound karaoke is not off the table.

Forms Can Finally Be Turned Off

Unpublish a form

You can now unpublish a HubSpot form. Until now, a published form stayed live after the campaign ended, the event filled up, or the offer expired, which meant manual work, messy data, and reaching for third-party tools to solve something the platform should have handled.

Oakes called it a sleeper, and he is right about why. This solves a class of problem teams have been trying to fix with process, rules, and reinforcement instead of software. The legacy-to-new form editor transition leaves lingering forms scattered around. Someone names a form "webinar form" when it was built for one specific webinar, it gets embedded somewhere, and six months later a team is staring at click data wondering why there are no registrations. You cannot fix that with a please-do-not-use-the-old-form instruction.

Casey has lived the workaround. Renaming a form's internal name to "archive" or "legacy" just to signal to colleagues that it is outdated is not a system, it is a sticky note. The gap Oakes still wants closed is non-HubSpot forms. The forms tool does a good job surfacing and mapping them, but there is no way to differentiate them by ID or CSS and mark them inactive when they are gone. The nine-year-old Gravity form still sitting in a client portal, the one nobody can explain, does not get swept out by this. Baby steps, and maybe this is the foundation that gets there.

Why it matters: form sprawl is one of those problems that never makes the priority list because it never breaks anything loudly. It just quietly corrupts your data and wastes an afternoon every quarter. Being able to pause a form is a small feature that removes a recurring tax.

For more details: Unpublish a form.

The Meetings Calendar Moves Into the Nav

Meetings calendar in the main navigation

Chris had too many things he wanted to click on and handed the pick to Oakes, who went to the meetings calendar. You can now view and act on past and upcoming meetings from a calendar in the main navigation. It was previously only available in the sales workspace and the customer success space, so anyone working outside those two never saw it.

The room read it as a quality-of-life change and a minor nav shuffle, the kind of thing that arguably could have shipped without a beta. The upside is that it is bookmarkable now, which prompted the standing wish that views were bookmarkable and not just pages.

The more interesting part is what it signals. If you are not living in the workspaces, stumbling into this view is a small revelation. You can launch a Google Meet from it, you get your Breeze assistant summaries, and you can work an entire day's schedule without leaving the page. It fits the work platform direction HubSpot has been pushing with projects and adjacent tooling. The next ask is unification for non-calendar events, but the direction is right.

Why it matters: features buried inside a workspace are invisible to everyone who does not work there. Moving this into the main nav is less about the calendar and more about HubSpot deciding the workspace is not the only way in.

For more details: Meetings calendar in the main navigation.

Filter Straight From the Column Header

Column-Level Filtering

Casey's pick, and one both hosts had flagged before the show. You can now filter records by clicking directly on column headers inside CRM tables, using the spreadsheet-style interaction people already have muscle memory for, instead of opening a separate menu and searching for the property you want.

This portal was already enrolled in the beta, and the move looks like private to public rather than a brand new capability, which surfaced a fair complaint. The update cards do not tell you what actually changed when something like this moves stages, so you are left guessing whether you are looking at a new feature or a wider rollout.

The use case Chris walked through is the one that makes this feature earn its place. A stakeholder says they think there was a data problem with leads last week. You go to contacts or deals, filter down, pull in create date, lifecycle stage, lead status, a couple of attribution fields, and eyeball it to decide whether there is a real problem or one bad record skewing the read. That is a scope-the-question workflow, and the old path made you go through the gear, then edit columns, then the modal, before you could even start.

The honest caveat is that column management in views is still the slow part. The right rail is great for adding one column. If you are removing six and adding seven, you are clicking one at a time, and the column modal is the faster path even though nobody loves it. There is also a keyboard shortcut for table settings that works for Chris and does not fire for Casey or Oakes, which is its own small mystery.

The real news came at the end of the segment. There is a filters team inside HubSpot now, and Chris spent time with Charlene Yang from that team on Friday. They are heading into a sprint and expect to have work out before Unbound, including association filtering on associated records, which has been at the top of a lot of wish lists. Sorting by association columns is a separate team and a separate conversation.

What stuck from that meeting was how much complexity sits under a request that looks obvious from the outside. Once associations enter the picture, you have to decide whether the user picks the property or the association first, whether a property like create date should appear once or once per associated record, and how labels multiply every version of it. It is easy to show up asking why this is not done yet. It is harder to look at the layers and still think that.

Why it matters: the pattern underneath all of it is that the hard work is designing the data model layer so that no user ever has to think about it, and then handing the whole thing to Breeze. Data, metadata, and UI is the entire stack, and metadata is just data. Wire it up properly and an admin can ask for every contact whose company was created before 2025 via an import, in a sentence.

For more details: Column-Level Filtering.

Webhooks Land Inside Custom Agents

Use Webhooks in custom agents

Custom agents can now send and receive data from external systems over HTTP webhooks, using post or get actions configured in the agent builder. The stated reason is workflow parity, giving agents a way to reach external systems without a custom integration and enriching what an agent can do with real-time outside data.

You still build the agent the same way. Instructions, data, context, and the tools it can reach. What is new is that the list of what HubSpot is now calling utilities includes sending a webhook. The screenshots make it look like agentic automation, and the agent builder and agent automation experiences do appear to be converging, but this is still the agent build itself.

Why it matters: this is the update that quietly raises the stakes on everything else, because on Thursday, July 23, custom agents stop being free and start consuming credits. A capability expansion and a pricing change landing in the same week is not a coincidence, and it is why the rest of the show went where it went.

For more details: Use Webhooks in custom agents.

The Credits Question Nobody Has Answered Yet

This is AI ROI week on the show, and the webhooks update opened the door early. Thursday's change to custom agent billing has already produced the questions you would expect. How many credits will this use, what happened to them, what did we get, and the favorite, what is the ROI. None of those have clean answers yet.

The structural problem is that credits and usage are showing up all over the portal at once, which is hard enough when one team owns the portal and much harder when several teams do, each with its own budget to defend, approve, and report on. Credits currently cover things like customer agent, prospecting agent, data agent, and Data Studio syncs, and the knowledge article listing them has a draft queued for what looks like Thursday, presumably to bring the rest of Breeze Studio into scope.

One clarification worth writing down, because Casey got it wrong with a client just last week. AEO prompts are not credits. A client who wanted more than the twenty-five prompts included asked whether credits could cover the gap, and the answer is no. More prompts is an old-school add-on, not a credit spend and not a seat. They are not tokens at Chuck E. Cheese.

The math that is available is uneven in a way that makes planning hard. An enterprise portal includes five thousand credits a month. One AI-generated blog post through content agent runs a thousand credits, and it is not clear whether a rerun after a bad draft costs another thousand. Signal monitoring runs fifty credits per signal per month per company, so a hundred target accounts on a single signal consumes the entire enterprise allotment. Deciding between one blog post and five percent of your account monitoring is not a comparison anyone has a framework for.

The wider debate came off a LinkedIn post from Aja Frost, Senior Director of Global Growth and Paid at HubSpot, arguing that the important argument right now is not between AEO practitioners, it is between AEO and finance teams, and that a CFO will not care about visibility in AI answers unless it connects to pipeline, nor should they. The post makes the case from HubSpot's own program, which started by asking what they needed to prove to get buy-in and built the measurement framework second, and reports qualified leads from AI search growing eighteen hundred and fifty percent and converting at three times the rate of other sources. That framework is written up in the AEO Revenue Playbook. Chris pushed back on the framing. Everyone else in the business is being asked to change because of AI except the CFO, and the old math of hours, effort, and headcount does not describe AI-assisted output at all. Finance teams have to approve this spend across the organization, so they need to help build the measurement frameworks for it rather than defaulting to the numbers that were already easy. Aja's reply, fairly, was that not everyone needs to change but finance teams should be leaning into AI like everyone else, and that this does not let AEO practitioners off the hook for telling their leadership to just trust them.

Oakes put the practical version of it. The ROI question lives with the team using the tool first, because this is not a spend-more-get-more calculation like ad ROAS. Most of the value is indirect, and a CFO cannot work that out on behalf of a content person or an ops person. If a team already takes SEO seriously, they are already paying for a tool, and AEO arguably belongs inside that same budget line.

Casey's counter is where this gets uncomfortable for HubSpot specifically. SEMrush is not lowering anyone's bill, so folding AEO into the SEO budget means the total goes up, not sideways. And HubSpot never charged separately for its SEO tooling. Customers who came in on Marketing Pro were getting that included, so asking them to fund AEO on top is a real increase from their point of view, even if twenty-five prompts covers most businesses that are not running four ICPs against a wide product set. Looking at the recommendations coming out of client portals, the line between AEO and SEO is thinner than the framing suggests. Longer keywords, same concepts, same job of answering a question for a human.

The part that will actually bite is attribution, or more precisely the roll-up. Marketing gets recommendations from the AEO tool, maybe uses content agent to produce the piece, then customer agent receives the visitor, then intent data times the handoff to sales, then a custom agent inside an agentic workflow manages the process. Every one of those steps spends credits, and the question of credits per closed-won customer has no owner. A customer agent conversation that starts as a ticket and ends as an upsell belongs to service, success, and sales at the same time. Dividing that up is going to get in the way of teams working together before it ever produces a useful number, and it perpetuates the old pattern where marketing plays by a stricter set of rules than everyone else.

What would help first is not attribution, it is visibility. A roll-up property on a company or contact showing how many credits touched that record between two lifecycle stages would at least answer where the spend is going and where it is going to dubious value. Knowing where you are wasting money is step one. Getting there is complicated by the credits and usage sitting outside HubSpot in the rest of the AI stack, which starts to feel like attributing electricity.

Oakes ended up being the optimist, which he admitted was an odd casting. His read is that this is a transitional period, that HubSpot is working out how software should be priced when seats stop being the right unit, and that utilization-based pricing can cut cost for lighter users. The reason it feels unclear is that the constraints, the capacity, and the long-term usage patterns are not known yet, by anyone, including HubSpot. He believes the way we think about this in eighteen months will be unrecognizable, and that the harder problem is not technical, it is organizational structure and who owns the question.

Nico Lafakis, watching live, made the call worth ending on. Everybody wants ROI tracking right now, everybody used to providing it is providing it the traditional way, and every one of those numbers is sculpted to make a division look good. In eighteen months the conversation will not be about credits or cost savings. It will be about how much opportunity got created and how much the business grew because everyone is using AI.

Chris is heading to a HubSpot Academy Labs session in person in Houston on Thursday, about forty minutes from home, covering Loop foundations, ICP and audience segmentation, smarter prospecting, enriching sequences at scale with AI, campaign building, and optimizing prospecting agent. All of it spends credits. He will bring back the word on the street on AI ROI for Friday's show. If you work in finance and you have ideas here, the show wants you at the table.

What Else Shipped Monday

Four more updates landed Monday. The Run Agent workflow action came up in passing during the webhooks segment, and it is the one worth circling back to, because it brings agent automation out of Breeze Studio triggers and into any workflow trigger, with multi-agent orchestration and output chaining. The other three did not make the show. Column freezing for pivot tables now defaults to frozen left-side and totals columns while you scroll horizontally. User import gained the ability to update existing users' seat, team, permission set, and manager rather than only creating new ones. And Breeze Assistant learned to create and manage payment links from a plain description, covering the full lifecycle from cloning to activation. Each has its own page in the updates feed with our take.

The Sign-Off

Value First AI Daily comes back online later today at a new time, with builds on these topics every day of the week. 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.