Show recap — Thursday, September 10, 2026

Another Orange Morning Recap: September 10, 2026

Thursday morning, six days out from Unbound, and Casey Hawkins joined from a car in Maine. She had been up since three to drive two hours to the easternmost point in the United States for the first sunrise in the country, and she saved the story for the recording so Trisha Merriam could react to it live. Chris Carolan put the sunrise photo on screen, Trisha admitted her February trip to Ireland has TikTok showing her the Cliffs of Moher daily ever since, and then the three of them looked at a board with twelve updates on it.

Here is what we got into: a major email update that made Trisha nervous before it explained itself, a payments API that Chris read as the arrival of something bigger, a second day on the Microsoft app with a consultant who has migrated people off SharePoint, column suggestions for the index table, Breeze coaching the customer agent, brand fonts in email, and a closing Breeze prompt that came back with a blunt read of our own portal.

Email Variants, or Is This Dynamic Content Again

Email Variants

Nobody on the show had seen the word variant in the email editor before, and it arrived flagged as a major update, so it went first. The idea is one email asset that carries several variants, each tailored to an audience segment, instead of a cloned email per group. HubSpot's own examples are variants per customer tier, language, industry, lifecycle stage, region and persona, and the tier example reads like it was written for HubSpot itself. It is a private beta for Marketing Hub Professional and Enterprise.

Trisha's first feeling was worried, and the how-it-works section did not settle it. You create the email, add a variant, edit each variant's content, configure each variant's audience, then send and analyze. Every step of that is still configuration you do by hand, with discrete snippets and discrete images per variant. Trisha's question was how this differs from dynamic content, and the honest answer from the announcement is that it is hard to tell. Casey, who is not a fan of dynamic content and knows it is a hot take, named the risk: the other variants are hidden while you edit, so a change requested in approval gets made on the primary and missed everywhere else. She would rather each email be its own email, tied together with a custom email property when the performance needs rolling up.

There is a real use case in it. Casey has a client whose webinar follow-up needs an attended version and a did-not-attend version, and that is tidier as one asset than as two more emails in a list that already runs four deep per webinar. The open question is reporting. Trisha remembered building list-based performance reports with Casey years ago, spotted a new property holding the variant name, and could not say whether those existing reports will see it.

Why it matters: Chris's read is that this is a stepping stone for AI more than a feature for humans, and the announcement would land better if it said so. Humans loved HubSpot's clone-and-tweak email flow. That flow is a bad way to ask AI to run a campaign, because ten generated emails nobody reviews is how AI becomes unhelpful. One asset with variables in specific spots is inspectable and cheaper in tokens. The place HubSpot is asking you to configure today is where Breeze is going to put its work tomorrow.

For more details: the full update on email variants.

ERP Lite Is Here

New Revenue Payments API

Chris picked this one and the room knew he would. A set of new public endpoints lets customers, partners and third-party agents create payment records, retry failed payments and configure checkout page settings. Every one of those was UI-only until now. It is a public beta across all hubs and tiers.

The conversation started with the daily emails. Casey gets one nearly every day now about new API permissions, and Trisha put the count at eleven a day, because the notice comes for every portal. For an average HubSpot user that is confusing at best. Casey's plain reading is that HubSpot is opening its public API surface as fast as it can so people can do more work out of Claude than ever before, and Chris agreed: if the API is available, AI can access it, and so can Breeze.

Then Chris got to the qualifier. This is a revenue payments API, and revenue payments are the ones you receive. Trisha asked the question everyone was thinking, and the answer is accounts receivable versus accounts payable. Which raises the next one: is a bill payments API coming someday, the way an ERP would have it? HubSpot has no purchase order system out of the box, though the team has built approximations for clients.

Why it matters: Between contracts, orders, subscriptions and now payments and checkout settings by API, ERP Lite is here, and Chris sees no reason an entire e-commerce experience cannot be built inside HubSpot. He also mentioned last week's contracts unboxing with Ryan Ginsberg and a Revenue Hub product manager, working from a real subscriptions use case, and said to expect more of that at Unbound.

For more details: the full update on the revenue payments API.

SharePoint, Day Two

Microsoft SharePoint and OneDrive App

Trisha asked if she was allowed to pick from yesterday's board, was told it is her world, and went straight to the Microsoft app. The show covered it Wednesday with Zach, and Chris pointed out the full segment is already on the update's page, six minutes and fifty seconds of it. Since then the announcement has gained a link to the app listing in the Marketplace, and the line about a beta starting September ninth is gone, because it is here.

Trisha's reason for picking it is that a lot of her clients run on Microsoft, and getting at their files from anywhere else has always been a whole extra thing. Casey remembered that the first place the two of them worked together ran on SharePoint, and Trisha confirmed it. One client had their entire CRM on SharePoint before she migrated them to HubSpot, and they still have a huge amount of content there. Knowledge base material, onboarding documents and contracts are the obvious first things to link to records.

Why it matters: Chris asked why there was no official Microsoft app until September 2026, and Trisha's answer, that Microsoft is locked down, is now the majority answer from the four people who have been asked on the show. The more useful question is how to help everyone who believed that understand it is no longer true. The clunky way, copying a link into a note and hoping you were signed in when someone clicked it, is over.

The Index Table Learns Your Habits

Index Table Column Suggestions

When you add a column to a CRM index table, HubSpot now suggests a personalized list of properties, and hovering any suggestion tells you why it was recommended. It is a private beta across all hubs and tiers, and it belongs to a family of updates the show likes: AI suggesting and coaching on your behalf inside the tool.

Casey's angle came from Wednesday's conversation about sales teams still living in segments. She knows plenty of reps who do, mostly out of habit, and the index table getting steadily better is what makes it possible to move them. What has slowed that move is that the rep has to know which columns to ask for, which turns into a stream of requests to the admin: can you add this, can you change that. Being empowered to do it yourself is what makes the change stick. Trisha went from rarely opening an index view to spending nearly all her time there once she realized you can build a board out of a single property, and she likes setting them up for people who are still running on the default segment columns.

Why it matters: Chris told the story of a mutual client whose whole job is in HubSpot seeing an index page for the first time last month. When you have a job to do and a procedure to follow, you do not explore, so the people who most need these features are the least likely to find them. Never assume any knowledge about HubSpot exists until you have talked about it or shown it on screen. A suggestion with a why attached is some of that teaching moving inside the product.

For more details: the full update on index table column suggestions.

Breeze Coaches the Customer Agent

Customer Agent Reporting and Coaching in Breeze

Breeze Assistant can now report on the customer agent, recommend improvements tied to your coaching opportunities, and make configuration changes to the agent, all from one conversation. It is a public beta for Professional and Enterprise across Marketing, Sales, Service, Content, Data Hub and Smart CRM.

Casey liked the shape of it as much as the substance. Recommendations broken into discrete pieces you can work through one at a time are far easier for a human brain to act on than a wall of flags in a feed, which is the same reason she has trained her own Claude to ask her structured questions instead of burying them in prose. Trisha connected it to something the show talks about often: one of the real blockers to AI adoption is visibility, and knowing there is one place to get every answer about how the agent is doing builds trust.

Why it matters: Chris thinks HubSpot buried the lede. The announcement leads with reporting, but the line that matters is make configuration changes. If you can set up and tune a customer agent by talking to Breeze, a lot of people who were never going to open the agent settings will set one up. And if you are not comfortable with AI yourself, coaching an agent is not something you know how to do; putting the how, the why and the what-to-change in one conversation is what creates safety.

For more details: the full update on customer agent reporting and coaching.

Fonts, Finally, With a Catch

Brand Fonts in the Marketing Email Editor

Casey called this one out on purpose as bigger than it looks. Brand Kit fonts, including Google fonts and custom uploads, now appear in the drag-and-drop email editor's font picker with automatic fallback handling. Public beta, Marketing Hub Free through Enterprise.

Fonts have been limited in the email editor for years, and the reason was never HubSpot being lazy. Not every email client renders every font, so most companies got three or four choices and picked a backup. Now the brand font goes in and a fallback goes beside it. The catch is that Gmail, Outlook and most mobile web clients show the fallback, and Casey remembered a client from many moons ago who was consistently frustrated that the emails they approved never looked the same when they arrived. Trisha's advice is the preview tool, which shows you what each client will render.

Why it matters: Chris said this was always the most painful conversation when he worked internally with people who cared deeply about how a marketing email looked, knowing the entire industrial manufacturing audience was reading it in Outlook. Use the preview tool, choose the fallback deliberately, and set the expectation before the send. The reason this can ship now is that AI can transform content on the way out and absorb the variation, which makes options like this safe for the product team to add.

For more details: the full update on brand fonts in email.

Unbound Unboxed

Chris slipped in a cross-promotion: Wednesday, September 23, the week after Unbound, a few of the Hubsessed team will be unboxing the event, with details going out today. Trisha told him he is killing it on cross-promotion for someone stirring so many pots at once and saying so little about them, and Chris mentioned the page, the campaign in HubSpot and the email with every link came together in about an hour on his morning walk.

Will It Breeze: What Are We Missing

The closing prompt was custom objects plus Data Studio, tell me what we are missing, aimed at the show's own portal. Chris noted that HubSQL also landed this week, and that he is trying to match Ryan Ginsberg's excitement about it without a database background, because it points at the same place: it needs to be easier to get at the data and do whatever you want with it.

Breeze came back with an inventory first. Nine custom objects, four event records, two hundred seventy-seven value entries and deliverables, plus documentation, investment, series, interest and, as Chris noted with thanks to Casey, HubSpot updates. Six months ago Breeze routinely missed custom objects and the outer parts of a portal. It sees everything now. Then it gave what it called a blunt read: the biggest gaps across the custom objects are adoption, consistent business-level unique IDs, normalization across objects, coverage of every content pillar, and a cleaner primary relationship design for delivery and value tracking.

Chris called it a do-as-I-say moment and then gave himself and everyone else permission, because no portal the team encounters is perfect. The bigger point stands: that unintentional prompt produced a data model roadmap you might once have paid for or waited weeks to get, from an assistant that already knows your portal better than the consultant coming in to tell you the same thing. Start talking to Breeze now, before it gets more overpowered after Unbound.

The Rest of Thursday's Updates

Also on the board and not pulled forward: two requests for feedback on product revenue reporting and revenue forecast reporting, the customer agent tester now reachable from every configuration page, automatic brand voice setup, manual voicemail drops for outbound calls, and WhatsApp voice notes. Still carrying from Wednesday's board: the Shopify discount sync for marketing emails, HubSpot Work ahead of its move to public beta and credits next week, campaign goals through the Goals API, associating a form to multiple campaigns, and using Breeze to enroll contacts in the prospecting agent and build buying groups. 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 next time.