Show recap — Tuesday, August 18, 2026

Another Orange Morning Recap: August 18, 2026

Tuesday opened with a hat. Ryan Ginsberg is in Brazil right now, where Father's Day lands on a different day than it does here, and his daughter's school had all the kids make hats for their dads. That is the hat he wore on the show, and it is now his favorite hat to wear. Somehow that turned into a bit about selling limited editions on the floor at Unbound, which turned into the actual thing Chris wanted to say about the emails already piling up from vendors he has never met.

Then the updates page, and a morning that kept circling one idea: the silos are the reason most of this is harder than it needs to be. Revenue reporting showing up in a workspace built for customer success. A knowledge base agent that only works if marketing and service stop pretending they are different content teams. A campaign object that people cannot use because they have decided what the word campaign means. Four updates, one argument.

Revenue Reporting Lands in the Customer Success Workspace

Customer success managers and leaders can now pull out-of-the-box revenue reports and summary cards directly inside the customer success workspace. Gross and net revenue retention, ARR, MRR, what is up for renewal, and an MRR waterfall report. The pitch is that CS teams get measured on retention and have never had a consistent structured view of their own book of business.

The first read was skepticism about the prerequisites, and it turned out to be right. Your account needs Revenue Hub, or to be ungated on the contracts direct create and edit beta that came up on the show last week. Subscriptions alone will not get you here, and deals definitely will not. So the honest version of this feature is: add a brand new and fairly load-bearing object to your data model that you are probably not prepared to add, and then go look at all your revenue.

Chris signed up for the beta to test it on the VFT side. He also mentioned talking to the Revenue Hub team early on specifically to make sure they knew the customer success workspace existed, because for industrial manufacturing teams the customer success workspace makes far more sense as a home than the sales workspace does. Sales workspace is built to go get net new. Customer success workspace has been able to hold the whole picture of a relationship for about two years now, which is exactly why revenue reporting should land here first.

Why it matters: This is Service Hub Professional and Enterprise, so it is still tied to a hub, and that is the part worth watching. The direction is right and the gate is the same gate as always. As Chris put it, he is looking forward to the day the silos of sales, service and revenue are gone. Finance is apparently next. The real question before you get excited is smaller and more practical: how many teams are actually working in the customer success workspace, do they care about ARR and MRR, and is the data model set up to answer that well. If the answer to any of those is no, this is a reason to fix that, not a reason to turn something on.

Breeze Assistant Makes PowerPoint Decks Now

Breeze Assistant can generate a fully formatted downloadable .pptx when you ask it for a slide deck or a presentation, alongside the HTML and Markdown artifacts it already produced. You open the file directly in PowerPoint, Keynote or Google Slides. The reasoning is that customer-facing reps spend real time copying CRM information into decks for prospect meetings, proposals and business reviews.

Casey made the case for why this is more useful than it first sounds, and it came from actually living it. She is building a sales presentation right now that runs through an HTML artifact, and every time she needs to change one phrase or update a price, she has to go back to Breeze, run a prompt, download a new version, and re-upload it to the drive her team references. With a PowerPoint file she could just fix the text herself. That editability, the moment of correcting the last little thing, is exactly where the HTML version gets frustrating.

Chris agreed on the value and flagged the tradeoff. AI-native tooling transferring output into fairly strict Microsoft file frameworks often requires a level of editing you were not expecting to do. The line worth keeping from that exchange: because AI can do this for you, it does not remove your responsibility of making sure it looks good and reads right for whoever you are giving it to.

Why it matters: They tested it live at the end of the show and it produced a clean deck. If your team is already sending Breeze-generated collateral out and losing time to small edits, this is a straightforward win. If you are choosing between HTML and PowerPoint from scratch, the HTML artifact is still the better experience for the person receiving it. Use the deck when the deck is genuinely what the room expects.

The Knowledge Base Agent, and the Rant It Set Off

Ryan pulled this one forward. The Breeze Knowledge Base Agent analyzes and extracts topics from your tickets, compares them to your existing knowledge articles, and surfaces suggestions for new articles plus edits to existing ones where content is unclear, outdated, incomplete or off brand. You review, accept or reject each suggestion from the suggestions tab.

The pricing note is worth reading twice. Starting September 16, the agent begins consuming credits. Two dollars, or two hundred credits, per new knowledge base article generated. Edit suggestions to existing articles are included in the Service Hub seat. Chris's read on the packaging was dry: thank you so much, HubSpot, for putting the two dollars right next to the two hundred credits, so very helpful for us.

Then the actual argument. Two hundred credits for a knowledge base article compares to roughly a thousand credits to create a blog on the AEO side, where marketing sits. Meanwhile all the subject matter expertise lives on the front lines in service, where people are writing magnificent novellas inside individual emails to answer the same question for the tenth time that day. Some of them have private Word docs full of answers. If you are using tickets in HubSpot, you almost certainly bought Service Hub to get them, which means the knowledge base agent is an immediate win sitting in nearly every portal. The reason nobody gets here is not technical. Marketing is over here and service is over there, and that is the only reason.

Ryan's customer success background pushed it somewhere better. He described being a little lazy on knowledge base articles back in SaaS, keeping up with an ever-growing feature list while engineering built the things sales had already sold. What he liked most was the continuous update side, because the minute an article goes live it starts going stale. Move a button, change a page, update text, and every screenshot and video recording goes out the window. Then he asked the sharper question: is this only fed by the email and ticket loop, or can it hook into other sources? You cannot wait for support emails to tell you a feature shipped. Product needs to feed this too.

Why it matters: The suggestion is not the deliverable. Do not take it at face value and ship the article. The value is making the suggestion visible to everyone across the customer-facing team so they can put input on it, because that is what gets you to content people are actually proud of and willing to share. And once you look at it across the full lifecycle, the line between a blog post and a knowledge base article mostly stops mattering. HubSpot sales reps pull up knowledge base articles to sell the product. What still differs is tone and the experience someone expects when they click something labeled a knowledge base article. Knowledge base content usually clears fewer marketing gates, which is a feature, not a shortcut.

Campaign Automations, and the Word Nobody Agrees On

A set of new triggers, actions and reporting features is now available in campaign automations for private beta portals. The gaps it closes are real ones: no trigger for a contact entering a campaign, no visibility into where contacts dropped out, no native A/B testing. Before this you stitched it together with separate workflows or accepted a flow that fell short.

The setup for this one was a story from last week. On a client call someone said you cannot use HubSpot campaigns the way you use Salesforce campaigns and attach leads or contacts to them. Nobody corrected it in the moment, because the Salesforce integration itself has demonstrably improved and the conversation was going somewhere else. But an update had dropped about a month earlier saying you can. That is the whole problem with campaigns in one exchange. People are working from an understanding they formed a year or two ago, and the tool has moved.

Chris has been arguing for a while that campaign is not a great word for what this object actually is. You can manage an entire marketing strategy inside Marketing Studio, map a real journey, and set up triggers against it. But most people hear campaign and think email send, and that gap makes it very hard to see what the object is capable of. His example was Unbound. The campaign for Unbound is the entire strategy of going to an event, and that usually lives in a spreadsheet somewhere, or in an expensive marketing budget management platform, because it has been hard to track in any system. That is what the object is designed to support, along with the Q1 goals and the 2026 and 2027 budget conversations that currently happen nowhere findable.

Ryan reframed it usefully. There are two things to teach here and they are separate: what a campaign actually is, as a parent container holding all the assets and representing a strategy rather than an email, and then the data model, meaning which objects can associate to it. He also named the tension honestly, which is that HubSpot has followed marketing teams' requests as their needs grew digitally, so this is an ever-evolving tool set and most teams have never stepped back to ask whether what they are doing now still works.

Attribution came up and did not get a clean answer, which was the right outcome. Ryan asked whether this addresses the attribution needs teams have. The response: it definitely gets you the unified visibility everyone wants, and visibility is step one. True attribution is step two and involves a lot of variables, most of them conversations with the rest of the team who are all touching the thing you want to attribute. If you are attributing a closed-won deal and not talking to sales, you have set yourself up to believe marketing had far more influence than it did. Casey has three attribution projects running right now, each set up differently, one using campaigns and two not, because every organization looks at attribution a little differently and there is no single solve.

Why it matters: One practical gate to know before you plan around this. Attribution reports using campaigns depend on your subscription, so unless you have Sales Enterprise and Marketing Enterprise it is genuinely hard to use campaign-based attribution reports. That is why Casey is not using campaigns for all her clients today. Also worth knowing: the influenced-by-campaign trigger fires on any interaction with a campaign asset, and there are around twenty-eight asset types now, including sales and service ones. That is powerful and it can also dirty up influence reporting fast. And if your team uses the word campaign to mean the email you sent last week, that is fine. Nobody is asking you to rethink your vocabulary or build an elaborate data model you do not need.

Will It Breeze: What Are We Missing?

The wheel landed on the customer base and CTAs, and the prompt was: using CTAs, can you tell me what we are missing across the customer base? The honest prediction going in was that this would not go well.

Breeze did something better than answering. It asked what was meant by missing, and offered four readings: CTA assets not yet built for key customer segments, customers or companies with little to no CTA engagement, which CTAs are underperforming or missing clicks, and content topics or offers the CTAs are not covering. Option three got picked, but the point had already landed. Just being asked to pick makes you think, and this is normally a question an admin has to answer for leadership or marketing management with no good way to frame it.

The answer came back that nearly half the CTA inventory has no click value at all. Which is accurate and, in this portal, completely expected, because VFT has largely moved off HubSpot CTAs. That is the useful part. A report showing a dramatic drop in CTA clicks looks like a crisis if you do not know the team intentionally stopped using them. A leader who catches that number without the context calls an emergency meeting about nothing.

Why it matters: This is the case for asking a tool for business context instead of a chart. The chart was right and the chart was misleading. Worth noting alongside it: with event management and raw events carrying so much more of the picture now, there is a lot less need to get granular about routing everything through HubSpot CTAs just to preserve reporting. Then Breeze was asked for a PowerPoint deck about attribution in HubSpot, which tested Tuesday's own update live. It produced a clean deck, and defined attribution as a decision system for understanding which interactions contribute to contacts, deals and won revenue. Not bad.

The Rest of Tuesday's Updates

Two more shipped on Tuesday that we did not get to. Super admins and primary contacts are getting a consolidated view of subscription usage in the Other Limits page under Account and Billing, which replaces piecing entitlement numbers together from scattered corners of the product. And workflow enrollments now preserve the record you keep when you merge duplicates, so cleaning up your data stops quietly pulling contacts out of in-flight nurturing. That one is genuinely nice.

Monday also carried a heavy list, most of which we covered on yesterday's show. Everything 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.