Show recap — Tuesday, September 8, 2026

Another Orange Morning Recap: September 8, 2026

Tuesday landed one week out from Partner Day at UNBOUND 2026, and the board was thin. Monday was a holiday, so there was no show, and the release page came back lighter than a normal weekday. Chris Carolan hosted with Joshua Oakes and Ryan Ginsberg; Casey Hawkins was off for the morning. The working theory in the room was that Wednesday through Friday get packed, or HubSpot is holding volume back for Unbound week, which last year produced a fifty-update day and a seventy-update day.

Here is what we got into: dashboard sections and the trust problem sitting underneath them, co-term line items on contracts, landing pages built by Content Agent and where the credits actually start, an API for activity auto-association rules that drew the sharpest criticism of the morning, and a Will It Breeze attempt at auditing published forms.

Dashboard Sections, and the Trust Problem Underneath Them

Dashboard sections are in private beta, and the first question in the room was whether this was a rename of something that already existed. It is not. Users can create, rename, delete and reorder sections, and move widgets within or across them, right on the dashboard canvas.

What makes that worth a segment is the workaround it retires. The most common use of the full-width image-or-text widget on a dashboard has been to fake a section header: stretch it across the canvas, put the headline in the body as big bold text, and phrase that headline as the question the section is there to answer rather than as a metric name. Under the headline goes the fine print, the definition of the metric, whether the data is a cohort or a snapshot, the caveat somebody will otherwise ask about in Slack.

Sections cover roughly ninety percent of that job. They do not cover the rest, because a section carries a name and no description field, so the help text still has nowhere to live. The text widget survives for that, and for a clickable-controls trick the show wants to come back to on its own day.

Then the segment widened. Sections are an organizing tool, and organizing a dashboard is only half the problem; the other half is who the dashboard is for. There is a real distance between a director who is elbow deep in the data and knows exactly why a number is messy this week, and an executive one level up who needs a yes or a no plus what is being done about it. The further from the data, the more the whole thing runs on trust, and the more an executive question arrives the way a marble does after hitting four other marbles: something they read, something a colleague said, and out comes a question about fastest-growing geography that is on nobody's priority list.

Two useful distinctions came out of that. The first is asking whether a request is a report or an analysis project, because an analysis project is not a dashboard and does not need to be turned around before next week's standup. The second is a rule of thumb worth stealing: do not measure faster than you can move. If it takes a week to act on a piece of data, measuring it daily is theater. A companion idea landed alongside it, separating visibility from attribution, because almost every request starts with "I want to see" and the follow-up question is whether that is an FYI kind of seeing or an I-am-going-to-act kind.

The handoff went to Ryan Ginsberg for the structural read, and it was about timing. Dashboards are gaining structure and API surface in the same stretch, which means a dashboard layout becomes something you can describe rather than something you stitch together widget by widget.

Why it matters: a section is a small feature. Being able to say what a dashboard should contain, in a sentence, and have the tooling build it, is a different job than clicking. Sections are the part of that shift you can see this week. The rest of it is the reason to pay attention. Full detail on the release is in the Dashboard Sections update.

Co-term Line Items: Plumbing That Lands as a Relationship Feature

Also private beta, and narrow on purpose: sellers can now add a new line item to an existing contract and have that line item's end date align with the contract's end date. Before this, adding something mid-contract pushed the contract's end date out, because terms could only be expressed in whole months or years.

On paper this is a data-model detail. In practice it is the kind of detail that becomes a billing complaint, and billing complaints travel. A large customer's finance team tells their own CEO that re-executing contracts over small add-ons is painful, that CEO mentions it to your CEO over lunch, and by the afternoon the head of RevOps is answering for it. Contracts are one of the few places in HubSpot that sit directly on top of a customer relationship, which is why a fractional-date problem gets executive attention that a reporting gap never would.

It is also why every CFO keeps a spreadsheet exported out of every system, so the dates the platform will not hold cleanly can be reconciled by hand: promised, delivered, invoiced, and when anyone thought about selling it.

The praise in the room was specific. Contracts is a deliberately controlled object with an intentional model behind it, and the reflex when a controlled object meets messy reality is to clamp down harder. HubSpot went the other way and added room to move inside the control, which is what lets a smaller company say yes to a one-off request without breaking the audit trail or the trust between sales and finance. Last week's unboxing on contracts covered the object itself; this is the same theme arriving as a shipped change.

Why it matters: if you use contracts for subscriptions, this closes a gap somebody on your team has been solving with a manual pro-ration every quarter. The beta has limited availability and is aimed at customers who have already named this as a roadblock, and the product manager's contact information sits right in the update, which is a good habit and a fast path if this is you. The release page is Co-term Newly Added Line Items with Contract End Date.

Landing Pages with Content Agent, and Where the Credits Start

A shorter beat, and the practical part is the boundary rather than the feature. You can now chat with HubSpot's content agent inside Breeze Assistant to build a landing page, with your brand kit, brand voice, CRM data and past landing pages used as context from the first message.

The useful thing to carry out of this segment is where the meter starts. Working inside Breeze Assistant does not consume credits. Stepping out into an agent-shaped experience does. That line is the whole cost model right now, and the room's expectation is that it eventually stops mattering, because the destination is a world where you talk to Breeze, a landing page gets built, and whether an agent was called in the background is not your problem.

Getting there is blocked by vocabulary as much as by product. Agents, assistants, Breeze, HubSpot AI: the terms are used interchangeably in the wild and precisely in the docs, and that gap is what stands between a competent admin and actually trying this. It is worth saying plainly that the published guidance on exactly when content agent starts charging has not been consistent across announcements, so confirm the current behavior in your own portal rather than trusting a date you read somewhere. Details are on the Content Agent landing pages update.

The Activity Auto-association API Describes a Race, Not a Business

Public beta, and the sharpest criticism of the morning. Activity auto-association rules control whether an activity logged on one record also logs on associated records, a call on a contact also appearing on that contact's primary company being the standard example. Those rules can now be read and updated through a public API.

The question went to Ryan, and the answer was that everybody deals with this whether they know it or not. It shows up when you work out of Outlook or Gmail with the sidebar open, creating records and expecting the relationships to appear downstream. The settings page governing that behavior exists, it is buried, and most people never find it. Reading it through an API is a real gain on its own.

The problem is what the API exposes. The options are most recently created, five most recently created, most recently updated, five most recently updated. That is a description of a race condition, not a description of a business. Nothing about which record was touched last carries any semantic relationship to the work being done.

The worked example made it concrete. Should a call or a meeting on a contact be associated with the deals that contact is on? The first gate is whether the deal is open or closed. The second is what the association label says, because a sales process that supports third-party contributors has partners, vendor finance relationships and referrers attached to deals on purpose. Neither gate is expressible in the current options, so every email a referrer sends updates every past deal they ever touched. The tools do not describe the business; they describe technical constraints.

Why it matters: the upside is not the configuration, it is the exposure. Once a setting has an API surface, Breeze can reason about it with you, and a conversation about what should associate with what becomes possible where a settings page never allowed one. The eventual version of this has fewer variables, not more. The update is Activity Auto-association Rules API.

Will It Breeze: Auditing Published Forms

The recurring segment closed the show, and it did not go the way it usually does. The ask was an audit of published HubSpot forms: which properties each one contains, and whether those properties are required. Reasonable, bounded, and exactly the sort of thing Breeze usually returns something useful for.

What came back was instructions for checking every form by hand, plus an offer to build a spreadsheet template. The reaction in the room was the one everybody has had at least once, which is asking an assistant for help and being handed the manual.

The segment did not stop there, and the salvage is the takeaway. Do not accept the first answer, because the first answer is usually correct and rarely sufficient. Narrowing the request to published forms only was a real assist. So was asking Breeze for a prompt you can hand to another model that does have the access.

And a spreadsheet template is worth more than it sounds the first few times you do this kind of audit, when the hard part is knowing what the output should even look like. The expectation is still that Breeze should be able to do this, because the APIs to do it exist.

The Rest of Tuesday's Board

Tuesday was a light release day and the four updates above were the ones the show pulled forward. The full set of what 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.