If you've used Breeze AI on HubSpot, you've probably used Breeze Copilot.
You’ve likely asked it to summarize a contact, draft a follow-up, maybe pull a deal update. It worked. You moved on.
That's the version of Breeze AI most teams on HubSpot know. It's also the smallest part of what's actually there.
HubSpot Breeze AI is a more comprehensive platform for GTM and RevOps teams — connected components that sit across your entire CRM.
Each component works differently. Each one requires different things from your team to actually deliver.
The gap between "we have Breeze" and "Breeze is doing something meaningful for our pipeline" almost always comes down to understanding which layer maps to which GTM and RevOps problem and objective.
There's a version of HubSpot most teams run on for years without questioning. Workflows fire when conditions are met. Sequences send emails on a schedule. Deals move when someone updates a stage. It works. It's reliable. And it has a hard ceiling.
Breeze AI sits above that ceiling. Standard HubSpot automation is rule-based — you define the conditions, HubSpot executes them.
But Breeze AI is judgment-based. It can read a contact record and decide what matters. It can analyze a set of closed-lost deals and surface a pattern. It can research a prospect, write a personalized email, and queue it for review — without you defining every step in a workflow builder.
That's a different category of tool. Not a replacement for your regular Workflows or Sequences — those still handle what they're built for — but a layer above them that adds reasoning, generation, and autonomous execution to your CRM.
Quick history: Breeze AI didn't appear from nowhere. HubSpot's earlier AI experiments — Content Assistant and ChatSpot — were the groundwork. At INBOUND 2024, HubSpot unified everything under the Breeze rebrand, and that’s when AI stopped being a feature sitting next to HubSpot and became native to how the platform works.
Breeze AI isn't one thing you turn on. It's multiple AI and agentic components that work together — each with a distinct role, each sitting in a different part of your CRM.
Some you'll use daily. Some you'll configure once and let run. Some you'll only need when you're ready to build something custom.
Breeze Assistant is the conversational AI embedded across your HubSpot; it's the persistent sidebar you can open on any record, in any hub.
If you've used HubSpot Breeze Copilot, this is the same thing. Copilot was the earlier name. Breeze Assistant is what HubSpot calls it now.
What it actually does depends on what's in front of it.
Open it on a contact record and it can summarize that contact's full engagement history, draft a follow-up email in context, flag overdue tasks, or prep you for a call — pulling from everything HubSpot has on that person.
Open it on a deal and it can surface where things stand, what's stalled, what the last interaction was. Open it in your pipeline view and you can ask it direct questions about your numbers.
A few things worth understanding about how it works:
For sales reps, AEs, and CSMs doing high-volume daily work — call prep, follow-up drafting, record updates — Breeze Assistant is the most immediately accessible part of HubSpot Breeze AI.
Low setup friction, available today, delivers time savings from the first use.
But also, it’s important to know the limit: Breeze AI is a productivity tool, not a magic bullet workflow transformation. The real leverage comes when Breeze Assistant is working alongside configured agents — not as a standalone.
Breeze Agents are where the platform shifts from assistive to autonomous.
Where Breeze Assistant responds to what you ask, agents run multi-step workflows on their own — researching, generating, acting, and updating your CRM without a human decision at each step.
You configure them, define their inputs and goals, and let them run. They can be triggered manually, scheduled, or automated through Breeze Studio or HubSpot Workflows.
A few things that apply across all agents before getting into the specifics:
The HubSpot Prospecting Agent researches target companies, builds contact lists, and personalizes outreach — pulling from Breeze Intelligence and public web data.
For now, it's the most GTM-relevant of the pre-built agents for outbound-heavy teams.
💡 Actual use case: A B2B SaaS company RevX worked with used the Prospecting Agent as part of a connected outbound pipeline — pairing it with Breeze Intelligence, NeverBounce for contact verification, and Zapier for sequencing.
The result was an outbound pipeline that could research, enrich, verify, and queue contacts with minimal manual intervention.
That kind of stack doesn't come out of the box — it takes configuration — but the Prospecting Agent is the engine at the center of it.
The Breeze Data Agent enriches contact and company records at scale.
It lives within the Breeze Intelligence tier (more on this in a bit) but operationally it functions like the other agents: configurable, schedulable, and capable of updating CRM records without manual intervention.
Closed-lost deals are one of the most underused data assets in any CRM.
The Deal Loss Agent reviews them systematically — surfacing patterns in why deals were lost and feeding those insights back to sales and marketing.
For RevOps leads trying to close the loop between pipeline performance and GTM strategy, this is one of the higher-signal agents available natively in HubSpot Breeze AI.
For sales teams in proposal-heavy cycles, the RFP Agent drafts RFP responses by pulling from CRM data and configured knowledge vaults.
The quality of the output depends heavily on how well those knowledge vaults are stocked — generic knowledge bases produce generic responses.
From what we’ve seen for our clients and experiments we’ve run for ourselves, teams that have invested in structured product and competitive documentation get meaningfully more usable drafts.
One of the more underrated agents for GTM alignment, the Sales-to-Marketing Feedback Agent analyzes sales interaction data and surfaces themes — objections, questions, patterns — that marketing can act on.
Essentially, its job is to close the feedback loop between what sales is hearing in the field and what marketing is producing, without requiring anyone to manually compile call notes or run a quarterly review.
The HubSpot Customer Agent handles support queries autonomously — answering questions, retrieving information, performing supported actions, and escalating to a human agent when it hits something outside its scope.
What’s neat is that it works across messaging, email, calling, workflows, and bots, and draws on your knowledge base and approved CRM data to resolve tickets.
For support and service operations teams dealing with high ticket volume, it's the most direct path to deflection without sacrificing resolution quality.
HubSpot Breeze’s Content Agents research and generate blog posts, create landing pages, case studies, and social copy from brand voice input.
Output quality scales with how specifically you've configured your brand voice and the instructions you've given agents.
Ideally, if you treat these as a first-draft engine — with a human editing pass built into the workflow — you can get significantly more than simply expecting a publish-ready copy straight out of an agent.
The Social Post Agent generates and schedules social posts based on content themes.
Useful as a distribution layer sitting downstream of the Content Agent — once content is produced, Social Agent handles the formatting and scheduling across channels.
Breeze Studio is where the pre-built ends and the custom begins.
Every agent and assistant covered so far comes with default configurations — useful starting points, but built for general patterns. Breeze Studio is the build environment where you take those defaults apart and configure something specific to how your team actually works.
That last point matters more than it sounds.
Execution history gives RevOps leads visibility into what agents are actually doing — not just whether they're running, but what they're outputting and where they're hitting limits. It's the difference between deploying something and managing it.
The reason Breeze Studio is worth understanding early — even if you're not ready to build anything custom yet — is that it changes the ceiling of what HubSpot Breeze AI can do for your team.
Pre-built agents cover common GTM patterns. Most teams have at least one workflow that doesn't fit a common pattern:
💡 Actual use case: That last example is real. One luxury travel company RevX worked with had rich contact data in HubSpot and reps who were starting every day from scratch — manually triaging who to follow up with, what was said last, which channel to use.
We built them a Breeze Studio assistant structured around seven operational questions their reps needed answered daily. The CRM data was already there. Breeze Studio was the layer that turned it into something a rep could act on in minutes.
The configuration investment is real, for sure. But so is the delta between a default Breeze AI deployment and one that's been built to fit a specific workflow.
Breeze Intelligence is the data layer underneath everything else.
While Breeze Assistant and Breeze Agents work with the data already in your HubSpot, Breeze Intelligence is what improves that data — enriching records, filling gaps, and surfacing companies that are actively in-market for what you sell.
It does two distinct things: enriching data, and tracking buyer intent.
Breeze Intelligence pulls from HubSpot's commercial dataset to populate contact and company records with job title, company size, industry, tech stack, and buying signals.
It runs in four modes:
Smart properties sit on top of this — AI-populated fields that update dynamically based on enrichment data and existing CRM activity. For RevOps teams managing data hygiene at scale, smart properties reduce the manual work of keeping records accurate as contacts change roles, companies grow, or deals progress.
This is the part of Breeze Intelligence that's most directly GTM-relevant.
It tracks which companies are actively researching your category — based on content consumption, search behavior, and third-party intent signals — and surfaces them inside HubSpot.
For outbound teams, it turns HubSpot buyer intent data into a prioritization layer: instead of working a static list, reps can focus on accounts showing active in-market behavior right now.
A few things worth knowing before you run at scale:
Where you may feel limited: Enrichment quality scales with the cleanliness of your base data. Enriching a database full of duplicates, stale contacts, and incomplete records doesn't fix those problems — it layers data on top of them. Clean first, enrich second.
For teams with reasonably clean HubSpot data and an outbound motion that depends on accurate contact information and timely intent signals, Breeze Intelligence has a clear ROI case. For teams whose CRM is still a mess, it's the wrong place to start.
Two other useful components worth knowing about — especially if you're managing Breeze AI adoption across a team rather than just using it yourself.
The Breeze Dashboard is a centralized view of how Breeze AI is being used across your organization. It tracks:
For individual contributors, the dashboard is background noise. For RevOps leads managing a HubSpot Breeze AI rollout across sales, marketing, and CS, it's the operational layer that tells you whether activation is actually translating into usage — and where the gaps are.
The Breeze Marketplace is where you discover and install pre-built agents without building anything from scratch.
Think of it as the starting point before Breeze Studio — browse what's available, install what's relevant, open it for configuration.
For teams that are early in their Breeze AI activation and not yet ready to build custom, the Marketplace is the fastest way to get something running.
Featured agents — HubSpot's recommended pre-builts — are surfaced prominently and can be downloaded, configured, and modified to fit your specific needs.
The practical value: you're not starting from zero. E.g. a pre-built Prospecting Agent or Customer Agent from the Marketplace gives you a working foundation to configure from, rather than a blank canvas in Breeze Studio.
Not every Breeze AI capability is equally relevant to every team.
E.g. Content Agent and Social Agent are built for marketing. Customer Agent is built for support.
But specifically for GTM and RevOps teams specifically — since you’re managing pipeline, outbound, deal velocity, and revenue operations — the highest-leverage tools are the Prospecting Agent, Deal Loss Analysis Agent, and Sales-to-Marketing Feedback Agent.
🧠Pro tip: As HubSpot rolls out more pre-built agents and assistants, it’s helpful to keep an eye out for Breeze Studio tools that’re free, i.e., need no credits. You’ll be surprised at how many powerful agents HubSpot’s literally giving away for free.
From what we’ve seen so far at RevX, there's a pattern that separates teams getting good value from HubSpot Breeze AI vs. teams that turned it on, got mediocre output, and quietly stopped using it:
It's not about technical sophistication but about sequencing, i.e., doing a few specific things before touching any settings.
The teams that configure well start outside HubSpot.
They pick one workflow that's costing the team measurable time or producing inconsistent output — a daily lead triage process, a closed-lost review that never happens, an outbound research task that takes an SDR two hours a day — and they describe it in plain English first. Who does this? What triggers it? What does good output look like? What should the agent never do?
That plain-English description becomes the foundation for AI instructions in Breeze Studio. Skip this step and go straight to configuration, and you end up writing vague instructions that produce crap.
Breeze Agents are only as good as the context you give them.
E.g. a Prospecting Agent with no knowledge vault runs on public web data and whatever's in your CRM. But a Prospecting Agent with a detailed ICP definition, a product positioning document, and a list of disqualifying signals runs on all of that — and produces meaningfully more targeted output.
This one is straightforward but consistently skipped.
HubSpot Breeze Intelligence enriches what's already there; it doesn't audit or deduplicate for you.
Before running enrichment at scale, the teams that get clean output from Breeze Intelligence have already dealt with their duplicate contacts, updated their lifecycle stages, and removed or suppressed records that shouldn't be in active segments.
The enrichment then lands on a foundation worth building on.
Every Breeze Agent can be tested before it goes live.
That doesn’t mean just running a test and checking whether the output looks plausible — it means running tests against a benchmark.
You’re looking for answers to questions like, “What would a senior rep or ops lead have produced for this same input manually?” or “Does the agent output match that standard? Where does it fall short and why?” and so on.
That benchmark also becomes the basis for ongoing maintenance.
Agent performance drifts when the underlying data changes, when ICP definitions shift, or when knowledge vaults go stale.
Set a standard upfront and have something to measure against when you run monthly reviews.
Full disclosure: we’re HubSpot Gold Tier partners, so HubSpot is our bread and butter.
But from months of experimentation and real-world deployments for companies across industries, here’s our honest take:
HubSpot Breeze AI is genuinely useful. It's also genuinely easy to underuse — or to activate in ways that produce underwhelming results and lead teams to conclude it isn't worth the effort.
Breeze Assistant is the lowest-friction entry point into HubSpot Breeze AI and worth using from day one.
For reps doing high-volume daily work — call prep, follow-up drafting, record summarization — it saves real time. The ceiling is clear though: it's a productivity tool. It makes individual tasks faster. It doesn't reinvent workflows, doesn't surface patterns across your CRM, and doesn't act without being asked.
The value it delivers compounds when it's working alongside configured agents — on its own, it's a faster way to do things you were already doing.
This is where the real workflow leverage lives — and where a lot of GTM teams get tripped up.
HubSpot Breeze’s Prospecting Agent can meaningfully change how an outbound team builds pipeline. Deal Loss Analysis Agent can surface patterns that a quarterly sales review never would. Sales-to-Marketing Feedback Agent can close a GTM alignment gap that usually requires a dedicated ops resource to manage manually.
If you can't describe the workflow you want to automate in plain English before you open Breeze Studio, the agent output will show it.
What we’ve noticed is that GTM folks that get ROI from agents almost always do one thing first: they define what good output looks like before they configure anything.
Skip this and you end up with agents running on vague instructions and producing output nobody trusts. In other words: clarity ensures that AI (in any shape or form, really) doesn’t take you in the wrong direction, fast.
Agents work on what's in your CRM. A Prospecting Agent built on a poorly defined ICP and a contact database full of bad data will research and personalize outreach to the wrong people, efficiently.
🦊Pro tip: Need to exactly how broken your HubSpot data is? Run a 20-minute audit on Audit Fox (we built this!) and get an incredibly detailed report.
HubSpot Breeze Intelligence has a clear ROI case for outbound-heavy teams — accurate contact data, tech stack signals, and HubSpot buyer intent data surfacing in-market accounts directly in your CRM is genuinely useful.
The condition: your base data needs to be reasonably clean first. Enriching a database full of duplicates, stale contacts, and incomplete records doesn't fix those problems. It adds accurate job titles to contacts your team hasn't touched in three years. Clean first, enrich second.
The credit system also warrants attention before running at scale.
Breeze Intelligence and agents draw from the same HubSpot Credits pool. A heavy enrichment run can quietly consume credits budgeted for the Customer Agent or Prospecting Agent. Model your expected usage before turning on continuous enrichment across your full database.
That's not how teams get ROI from Breeze AI.
Pick the layer that maps to your sharpest operational bottleneck — the workflow that's costing your team the most time, producing the most inconsistency, or creating the most downstream noise — and go deep there first.
One well-configured agent running on clean data and clear instructions will deliver more than five half-configured ones running in parallel.