Show recap — Monday, May 4, 2026

Another Orange Morning Recap: May 4, 2026

The first Monday back after a month off the daily show, and HubSpot greeted us with a redesigned product updates page. Of course it did. Casey opened her portal, got what she described as a jump scare, and the show found its first segment before anyone had finished their coffee.

Here is what we got into: a tour of the new updates experience, two updates worth pulling forward from Friday, a Will It Workflow that started as a stretch and ended somewhere genuinely useful, and Payments as the Object of the Day.

The Product Updates Page Got Rebuilt

If you have not seen it yet, your portal might still be on the old version. The rollout is gradual. But once you have it, the difference is immediate.

The old experience dropped you into a wall of every recent update. The new one opens on a "For You" tab, which is similar in spirit to the old Recommended view but now sits front and center. Updates are grouped by how your team uses HubSpot, your goals, and feedback you have shared. The nine tabs you used to navigate have been replaced with three: For You, Your Betas, and All Updates. Search works from any tab and falls back to All Updates if your current view comes up empty.

The honest take from the show: this is a step in the right direction, especially for people who are not opening the updates page every day. Big updates used to get buried within a week. The For You tab keeps the things that matter to your portal in the foreground for longer. The search is not quite semantic yet, you still need to know roughly what an update is called, but the filters for favorites, major updates, and beta status make the page feel more like a tool than a feed.

The bigger thing this signals is HubSpot moving away from configuration-based recommendations and toward behavior-based ones. The old logic could only know what you marketed yourself as when you set up the portal five years ago. The new direction will eventually know what your team actually does. Not there yet. Going there.

If you want to see if you have it: Personalized Product Updates private beta.

Two Updates Worth Pulling Forward

Generate LinkedIn Articles and Posts from AEO Recommendations

HubSpot's AEO tool already tracks how AI engines like ChatGPT, Gemini, and Perplexity respond to questions about your brand, and it already recommends LinkedIn content topics when LinkedIn is being cited and your brand is not. The new piece is that you can now generate the draft directly inside AEO, and if you have Brand Voice set up, the draft will reflect it.

For LinkedIn posts, the draft lands inside HubSpot's social tool where you can edit, schedule, or publish. For LinkedIn articles, it generates a title, body, and companion post with copy buttons for each, and you take it over to LinkedIn's article editor to publish. There is no direct article publishing from HubSpot yet, which is the small letdown in an otherwise interesting feature.

Why it matters: Buyers are increasingly asking AI engines for recommendations instead of searching the web, and LinkedIn is one of the most commonly cited sources in those answers. The gap between "AEO told me what to write" and "I published the thing" is a real bottleneck, and this closes most of it. The fact that HubSpot is treating LinkedIn as a strategic surface for AI visibility is itself worth noting.

For more details: AEO LinkedIn article and post generation private beta.

Customer Success Rooms

This one was easy to skim past on a first read. It is a shared workspace where customers and CSMs can track project tasks, forms, documents, and status updates inside one portal. The clarification in this update was about scope: the beta currently supports task sharing and form submission. Document sharing and status updates are coming.

The setup is tied to the projects object. Tasks assigned to a customer on a project where Project Type equals Service - Onboarding will surface in the room. Rooms are created automatically based on triggers like deal close or project creation, typically through a workflow. By default, all contacts associated with the project get access.

Why it matters: The "shared Google sheet of who is doing what during onboarding" pattern has been overdue for replacement for years. The opportunity here is bigger than onboarding tasks though. Customers want an Amazon-style experience, one place to see everything they have ever done with you. Customer Success Rooms is one piece. The billing portal that opened up for private beta last week is another. The eventual unified customer experience is where this is heading.

For more details: Customer Success Rooms private beta.

Will It Workflow: Subscription, Knowledge Base, Cleanup

The wheel landed on Subscription as the object, Knowledge Base as the app, and Cleanup as the use case. Casey called her own first idea a stretch. By the end of the segment, the answer was yes, it workflows, and probably should.

The use case landed on commerce subscription cancellation as the trigger, with two paths worth considering. The first is a custom Cleanup Check property that flags accounts when a subscription cancels, paired with the Knowledge Base Agent to handle things like removing the customer from a member-facing knowledge base list or article. The second path uses an associated tickets rollup on the subscription, so any time a ticket comes in tied to a canceled subscription, the workflow knows. The marketing-brain extension that came up at the end: when a subscription cancels, you could send an email pointing the former customer toward your free-tier knowledge base resources, in case they want to come back.

The real takeaway is the one Chris named at the close. The question is not whether you can workflow it. With everything HubSpot has connected now, you can workflow almost anything. The question is whether you should. In this case, yes. If you have an active customer experience that depends on subscription status, automating the cleanup beats catching it on a Friday afternoon.

The agent involved in the segment: Knowledge Base Agent private beta. Watch the episode for the full build.

Object of the Day: Payments

If you set up HubSpot more than a year ago and have not looked at Payments since, here is the headline: payments are not just for HubSpot Payments and Stripe users anymore. You can create payment records standalone, including importing your historical payments, and you can associate them to most objects in the platform.

Payments now show up in the data model builder, which is the clearest signal that this is a real first-class object. You can associate payments to deals, contacts, companies, marketing events, courses, and more. The use case Casey flagged: tracking payments that are not tied to invoices, quotes, or payment links. Marketing event registrations, course purchases, anything that happens outside the standard sales motion.

One opinion that came out of the segment: payments probably do not need a full record view. They want to live in context, as a card or a side panel, next to the contact, deal, or other record they relate to. The current sidebar preview is the right call.

The bigger reframe: HubSpot is not trying to replace your accounting system or ERP. It is making space for the data so your unified customer view actually includes whether someone paid you. For most teams, that gap is real. You are calling accounts to figure out a discrepancy that should be visible in the CRM.

For more details: Payment Object enhancements and Multiple Stored Payment Methods public beta.

The Rest of Friday's Updates

Two more updates shipped Friday that did not get the deep-dive treatment on the show but are worth a look: multiple permission sets per user (public beta) and the Sandboxes Roadmap (live). Full breakdowns of all four updates from Friday are on the updates blog: HubSpot Updates: May 1, 2026.

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.