Show recap — Wednesday, May 13, 2026

Another Orange Morning Recap: May 13, 2026

Casey Hawkins, Chris Carolan, and special guest Maggie Philbin opened the show on a Wednesday, which is when the team wears orange. Maggie did not get the memo, which led to a quick aside about how many HubSpotters and former HubSpotters do not actually own much orange. The show then turned to four updates that landed Tuesday, two of which carried the episode and one of which produced a surprise guest.

Here is what we got into: the Marketing Research Agent and an unannounced drop-in from the product manager, Breeze Assistant gaining access to campaign data, a Will It Workflow run on Contact, Data Studio, and notify on change, and a meta-conversation about how product updates get written and how the “major change” tag actually works.

The Marketing Research Agent (with a Drop-In from the PM)

The Marketing Research Agent is in very limited private beta and the team is intentionally gating access. Anyone who requests it gets a mandatory onboarding call with the product team. Betas are for learning, and a forcing function to actually talk to customers is the kind of structural choice that produces better feedback loops than a self-serve toggle ever does.

The agent reads all of your reporting data, reasons through it, and proposes next-best actions as tasks. Casey opened the segment with a real critique: the example tasks in the rollout screenshot looked like sales tasks, not marketing ones. She had expected something more traditional, like “this webinar from two months ago did well, you have not done another one since then, do more of that.” Instead the examples were re-engage a stalled deal, capture a lost reason, follow up after months of inactivity.

Chris pushed the other direction. This is what marketing should look like now. The line between marketing and sales has been blurring for a while, and a customer platform built around the campaign as the unit of work is going to surface tasks that do not respect the old team boundaries. If the marketing team has an asset that could unblock a stalled deal, that is a marketing task whether or not the deal owner happens to sit on the sales side of the org chart. Maggie's read sharpened it further: maybe the line between marketing and sales is becoming less useful as a category, and what looks like a sales task is actually a marketing prompt about which asset would unblock the conversation.

That is when Maggie messaged the product manager, Ankur Gupta, and asked if he wanted to join. He did. Ankur clarified the framing: the agent is not exclusive to marketing. Anything that runs through reporting is fair game, and the agent intrinsically understands the relationship between assets. If a landing page is linked in an email, the agent treats those two things as related. The marketing-specific behavior shows up when it reaches a blog post or an email, where the agent reasons through asset context to suggest the next best action.

Before Ankur joined, Maggie ran what she called a classic product manager grilling on Casey: why did it feel surprising that the agent lives inside the campaigns app? Casey's first instinct was that it would live in some kind of AI category. Pushed on it, she landed somewhere more useful. Campaigns are not just email blasts anymore. With 28 different asset types you can associate to a campaign across every hub, Marketing Studio has become closer to a communication strategy canvas than a campaign builder. If that is what a campaign actually is, then the marketing research agent belongs there. That reframe carried into the next segment.

Paul dropped a question in the chat about whether the agent would work with buyer groups, suggesting asset X to help blocker Y for a specific champion. Ankur offered to add him to the beta to find out. The honest answer from the segment: this is a very early, very private beta, and the team is building it with the people who show up.

Why it matters: The bigger thing the agent is signaling is the merging of canvases. Marketing Studio, Breeze Assistant, and the agent itself all sit on top of the same data and increasingly share the same conversational entry point. The campaign is the unit of work, not the email or the form, and the AI sees the relationships between assets natively. The path from idea to action keeps getting shorter, but only for teams that have actually populated the data model the agent needs.

For more details: Marketing Research Agent private beta

Breeze Assistant Can Now Access Campaign Data

Breeze Assistant now answers questions about a campaign's goals, performance metrics, assets, and budget without making you tab between reports. This is live for Marketing Hub Professional and Enterprise.

Why it matters: This update lines up with the campaigns reframe from the prior segment. If the campaign is the place where teams coordinate across hubs, then asking conversational questions about that campaign needs to live there too. The piggyback into this update from the Marketing Research Agent conversation was natural, because both updates point in the same direction: the conversational layer is becoming the primary surface for getting answers out of HubSpot. Anywhere you see the Breeze sparkle, you can ask the question without leaving the page.

For more details: Breeze Assistant campaign data access

A Meta-Conversation: How Updates Get Written and What the “Major” Tag Means

Having a product manager live on the show meant the conversation pulled toward the kind of inside-baseball questions HubSpot users always wonder about. Chris led the detour, and two questions stuck.

The first: how does a product update actually get from a PM to the Product Updates page? Ankur walked through it. PMs answer a set of standardized questions about their feature, the draft goes through approval with go-to-market and product marketing, and once both the copy is approved and the code is rolled out, the update lands on the page. The stylistic differences across updates come from different PMs with different voices. Maggie added that the right tone depends on the surface. A salesy pitch for a data governance update would be wrong. A flat description of a marketer-facing feature would also be wrong.

The second: how is the “major update” tag decided? Ankur named the formula. It is not a value statement. It is a projected disruption rating. Something can be incredibly valuable to one business and still not be tagged as major, because major signals “this is going to require change from a lot of customers.” Custom events updates are never tagged major. A change to operator language that migrates filters cleanly is not major. A change that forces customers to rethink how they filter their data probably is. The tag is a signal about disruption, not a signal about importance.

This was the kind of segment that does not show up in the updates list. Worth keeping in mind the next time a feature you care about deeply ships without a “major” tag. It is not a snub. It is a different question being answered.

Will It Workflow: Contact, Data Studio, Notify on Change

The wheel landed on Contact, Data Studio, and notify on change. Casey's first read was honest: notify on change is a workflow problem first, not a Data Studio problem. If you just want to know when something changes, go to workflows.

Chris pushed back, gently. The point of the segment is to put two things together you would not normally combine. If the answer is “just use workflows,” the segment ends. The pitch Maggie landed on for Data Studio was sharper. Use property change events as the trigger, run the change through Data Studio with a smart property, and generate a contextual message the salesperson can send. The change is the data. Data Studio is where you transform it into something usable. Workflows are where you act on it.

Casey picked up the thread with a sales-side use case: tracking lead score changes to surface what pushed someone over the threshold. The reasoning landed on the broader purpose of Data Studio in HubSpot. It is the only tool that lets you do data transformation before the workflow runs. The real value shows up when external data is involved, when you need to curate and clean before automating.

Maggie also flagged a small but useful pattern. From the events page, the “use in workflows” button launches a workflow with the property change event pre-populated as the trigger. Most people set property change tracking up from the property settings panel, but you can do it from event management, and it connects more naturally to automation when you start there.

The Should It Workflow answer: yes, but only for the right reasons. Data Studio's job is curation and transformation, and the more complexity you add to the integration layer, the harder it gets to troubleshoot. Maggie's close was the one to keep: figure out what you actually want to happen before you start building workflows. Watch the episode for the full segment.

The Rest of Tuesday's Updates

Full breakdowns of all four updates from Tuesday are on the updates blog.

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.