HubSpot UNBOUND 2026 Of everything HubSpot announced at UNBOUND in Boston last week, Breeze Assistant is the change most HubSpot users will notice first. We run AIMG on HubSpot too, so this is something we’ll be living with right alongside our clients. I thought it would help to lay out what actually changed, what it means for industrial marketing and sales teams, and where I’d put the guardrails before turning it loose.
The short version: most industrial marketing and sales teams don’t need more AI agents. They need fewer places to click and a clear answer to one question. Who is doing the work, and what CRM information are they relying on?
Breeze Assistant is HubSpot’s answer to that question. It used to be mainly a chat companion that answered questions about your portal. Now you describe an objective, and the Assistant brings in specialized agents to deliver the proposal, report, or campaign plan, grounded in what your CRM knows.
This is one of three posts from UNBOUND. For the big picture, start with HubSpot UNBOUND 2026: What Industrial and B2B Marketers Should Actually Care About. For the data side, see Why Messy CRM Data Kills AI Agents.
From Copilot to Coordinator
The path is short, and HubSpot’s own announcements trace it:
| When | What HubSpot shipped |
|---|---|
| September 2024 | Breeze launched at UNBOUND, including Breeze Copilot, a chat companion inside HubSpot |
| September 2025 | Breeze Assistant introduced as the AI that “works alongside you in HubSpot, your browser, and all-new mobile app,” next to a growing library of agents |
| July 2026 | Agent Hub and Agent Builder released in public beta for Professional and Enterprise customers |
| September 2026 | At UNBOUND, Breeze Assistant repositioned to take action: it coordinates agents against a goal, on top of HubSpot’s new Growth Context foundation |
In two years it went from answering questions to assigning work. That’s the change to plan around.
What “Coordinator” Means in Practice
Instead of picking an agent from a list, you state an outcome and the Assistant decides which agents to involve. HubSpot’s Spotlight page describes it coordinating the demand agents in Marketing Studio, so you can ask it to kick off a campaign plan, draft a nurture email, or build a landing page using your business context.
HubSpot says customers using Breeze Assistant generate 2.2× more leads. That’s a vendor figure, and SiliconANGLE noted the announcement didn’t explain how HubSpot’s comparisons were calculated. For an industrial company, a win will look different anyway: better RFQ follow-up, nurture sequences that match your product families, and campaign briefs that don’t make things up.
Here are the kinds of requests that fit the new model. A person should review every output.
- “Build a 60-day nurture for contacts who downloaded the hydraulic filter sizing guide but haven’t requested a quote. Use only our existing blog and video content. Write for engineering buyers.”
- “Summarize open deals over $100,000 where the last meeting was more than 21 days ago. Flag missing next steps and missing buying-committee roles.”
- “Draft a trade-show follow-up sequence for our booth scans that ties each lead to the product family they asked about. Don’t send anything automatically.”
Notice what each of those assumes: product families exist as data, meeting notes are logged, and lead source and content history are tracked. The Assistant is only as good as that foundation.
The Slide That Explains the Guardrails
The featured image at the top is a slide I photographed at UNBOUND. HubSpot framed the future of automation as agents (“autonomous power”) plus workflows (“deterministic control”), connected by an intelligence layer.
I think that’s the right way for industrial teams to think about it. Let agents do the flexible work: summarizing, drafting, pulling context together. Keep the things that must happen the same way every time inside workflows, such as lead routing, approval steps, quote rules, and who gets notified. The more a mistake would cost you with a customer, the more it belongs on the workflow side.
Connectors: Your HubSpot Data in Other AI Tools, and Other Tools’ Data in HubSpot
Connectors now run both directions, and this may be the most practical change for mid-sized companies that already use several tools.
HubSpot into outside AI tools. HubSpot offers connectors for Claude, ChatGPT, Gemini, and Microsoft Copilot. You can ask one of those assistants to summarize your top open deals using real CRM data instead of pasting screenshots into a chat window. HubSpot’s own descriptions show these connectors can do more than read: depending on the tool, they can create and update records and log activity. That’s useful, and it’s also exactly why you need a policy before you turn them on.
Other tools into HubSpot. HubSpot’s Fall ’26 Spotlight lists connectors that bring context from Gong, G2, and Asana, plus new Marketplace apps for Google Drive, Microsoft SharePoint, and OneDrive. That matters for industrial companies whose real product knowledge still lives in shared drives.
Keeping track of it all. HubSpot added a connected apps digest (in public beta), a monthly email summary of what changed across your connected apps. It’s a small thing, but someone on your team should own reading it.
The slide above is HubSpot’s pitch: your data is connected, your agents are running, and you got there “without building a second stack.” I agree with the direction. Connect the tools you actually use, retire the ones you don’t, and put one person in charge of what’s connected. It’s the same modular approach we described in An Industrial Marketing AI Stack That Earns Its Keep.
Before you promise any connector to your sales team, confirm it’s live in your portal and on your subscription tier.
Agent Hub: Build Agents When You Can Name the Owner
Agent Hub and Agent Builder let you manage HubSpot’s agents and build your own. HubSpot released them in public beta for Professional and Enterprise customers in July, and the Fall ’26 Spotlight still labels Agent Builder as beta.
For industrial teams, the custom agents worth considering are practical ones: RFQ triage, dealer and distributor handoffs, and answering spec questions from your own documentation. My rule of thumb is simple. If you can’t name the person who owns the process and the number that tells you it’s working, don’t build the agent yet.
Two related updates are worth a look:
- Quote Rules. Spotlight describes rules that protect quote accuracy for products, pricing, discounts, and quantities. For industrial companies where discount logic has lived in someone’s head, this is a good prompt to finally write it down.
- Prospecting Agent. Spotlight says it can now source contacts on demand and enroll them right away, with outreach that improves as reps edit it. For industrial outreach, I’d keep a person approving messages before anything reaches a plant manager’s inbox.
Guardrails to Write Down Before You Scale
- Fix context before adding agents. Use Context Home to see what HubSpot knows about your buyers, product lines, dealer terms, and RFQ rules, and close the biggest gaps first. The messy CRM post covers how.
- Keep a person on anything that leaves the building. Emails, ads, nurture sequences, and quotes. One-click approval is fine. Automatically sending to a buying committee is not.
- Give the AI your voice and your limits. Industrial buyers spot generic copy immediately. Put your writing guidelines, product terminology, and claims you never make somewhere the agents can read them.
- Document the sales and marketing handoff. Lead routing, response times, who owns a lead when, and what “qualified” means for capital equipment versus parts. Agents will invent definitions you didn’t write.
- Set connector permissions deliberately. Decide what customer data can go into Claude, ChatGPT, Gemini, or Copilot, which of those tools can write back to your CRM, and who owns the monthly digest.
- Run one outcome at a time. Get one use case working reliably before adding the next. The number of agents you run is not a success metric.
A 30-Day Breeze Pilot
Week 1: Check your context. Review Context Home and clean up CRM data for one product family in one region. Hold off on new agents.
Week 2: Connect with a policy. Turn on only the AI connectors and file sources you’ve written rules for.
Week 3: One marketing outcome. For example, turn existing case studies into a nurture draft for one segment. A person edits it, and nothing is enrolled until two reviewers sign off.
Week 4: One sales outcome. For example, a deal-risk summary for opportunities that stalled after plant visits. Reps correct the CRM where the summary is wrong. Measure whether follow-up actually improved, not whether the Assistant sounded smart.
If week 4 output still invents contacts, plants, or specs, the problem isn’t Breeze. It’s the data underneath it, and that’s the place to spend your next month.
Bottom Line
The Breeze Assistant rebuild is HubSpot acknowledging that a long menu of agents doesn’t work for real sales and marketing teams. The Assistant’s job is to assign the work. Your job is to make sure the information it works from is trustworthy, and to keep people in the loop where your reputation is on the line.
The 2.2× lead figure is HubSpot’s. Your wins will look like fewer invented briefs, faster reuse of your technical content, and sales summaries that match what actually happened on the plant floor. Start with context, connect only what you’ll govern, and get one outcome right before you widen the Assistant’s job.
If you’d like help planning a Breeze pilot around how your manufacturing or distribution team actually sells, we’re happy to talk it through.
Ready to secure your digital presence?
About Amplify Industrial Marketing + Guidance
For over 30 years, Amplify has helped industrial companies turn marketing into measurable growth. Our integrated approach combines strategic guidance with tactical execution-including visibility optimization across search and AI platforms. Request a consultation to discuss your visibility strategy for 2026.