HubSpot has been adding AI features across its platform since 2023, under the Breeze brand. For most of that period, the honest assessment was that the features were promising but not yet changing how RevOps teams actually work. In 2026, that has changed. Several Breeze features have matured to the point where teams that have configured them correctly report real productivity gains, and the gap between teams using HubSpot AI and teams not using it is becoming visible in how fast they can run their revenue operations.
This post covers what the main HubSpot AI features are, what they actually do in practice, and how they are changing the day-to-day work of RevOps and go-to-market teams.
What Breeze AI Actually Is
Breeze is HubSpot's name for its AI layer. It is not a single feature. It is a set of capabilities embedded throughout the HubSpot platform. The main components are:
- Breeze Copilot: A conversational AI assistant available throughout the HubSpot UI. Ask it to summarize a contact record, draft a follow-up email, explain why a workflow is not enrolling contacts, or pull data from your CRM. It has context about your specific HubSpot data, not just general knowledge.
- Breeze Agents: Specialized AI agents for content creation, social media management, and prospecting. Each agent can be given a goal and runs toward it autonomously within defined parameters.
- Breeze Intelligence: AI-powered data enrichment that scans public sources to fill in missing contact and company data: job titles, company size, industry, LinkedIn profiles, phone numbers. Available via credits separate from the base subscription.
Breeze Copilot: What It Does in a RevOps Context
The most immediately useful Breeze feature for RevOps teams is Copilot. It is accessible via the side panel in HubSpot and understands your data. Practical examples of what it can do today:
- Summarize a contact's full interaction history before a sales call. Instead of scrolling through 90 days of email threads, meeting notes, and deal activity, ask Copilot to summarize the relationship and it returns a readable brief.
- Draft a follow-up email after a meeting, using the meeting notes and the contact's company context to personalize it beyond a standard template.
- Build a workflow enrollment criteria list. Describe what you want to automate in plain language and Copilot generates the filter conditions, which you then verify and apply.
- Answer RevOps questions about your data. "Which deals created in Q2 have not had any activity in the last 30 days?" returns a filtered list rather than requiring a manual report build.
The caveat: Copilot is only as useful as the quality of data in your HubSpot. If contact records are incomplete, if deal stages are not maintained, if meeting notes are sparse, Copilot has nothing to work with. Teams that have invested in data hygiene are getting more value from AI than teams that have not.
Predictive Lead Scoring: AI vs Rule-Based
HubSpot has offered rule-based lead scoring for years. You define criteria (job title, company size, page visits, form submissions) and assign points. A contact's score goes up or down based on whether they match those criteria. This works, but it requires the RevOps team to define what good looks like upfront and update the criteria as patterns change.
HubSpot's AI-powered lead scoring, available on Enterprise, takes a different approach. Instead of manually defined rules, it analyzes your historical deal data to identify which contact and company attributes actually correlate with closed revenue. It then weights those signals automatically and updates the model as new data comes in.
The practical difference: rule-based scoring rewards contacts who match your ICP on paper. AI-based scoring rewards contacts whose pattern of behavior and attributes looks like your historical best customers. For most B2B teams, the AI score surfaces different contacts than the rule-based score would, and the AI-surfaced contacts tend to convert at higher rates once teams start prioritizing them.
Breeze Intelligence: Fixing the Dirty Data Problem
One of the most persistent RevOps problems is incomplete contact data. Sales reps do not fill in fields. Inbound forms collect email and first name only. Over time, the CRM accumulates thousands of records with missing industry, company size, job title, and phone data.
Breeze Intelligence addresses this by scanning public sources and enriching contact and company records automatically. The enrichment runs on demand or on a scheduled basis, and you see the source of each data point added. It is not perfect but it meaningfully reduces the gap between what your CRM should know about a contact and what it actually has on file.
For RevOps, this matters for segmentation, lead scoring, and workflow enrollment. A workflow that enrolls contacts with a specific job title at companies with more than 50 employees only works if that data is in the record. Breeze Intelligence increases the percentage of records that match your segmentation criteria, which increases workflow enrollment rates and improves marketing targeting accuracy.
HubSpot AI Setup
Ready to put HubSpot AI to work?
We configure Breeze AI, predictive lead scoring, and data enrichment as part of our HubSpot implementations. Book a call to see what is possible for your team.
Book a Free CallAI-Assisted Email and Sequence Writing
Writing outreach sequences is one of the most time-consuming tasks in a RevOps or sales enablement workflow. A well-structured 5-step prospecting sequence takes a skilled writer 2 to 4 hours to produce. With HubSpot's AI writing tools, the first draft takes 15 to 20 minutes.
The AI does not produce final copy. It produces a working draft that addresses the right topic, uses an appropriate tone, and is long enough to be useful. The RevOps or sales enablement manager edits the draft, checks the logic, and refines the personalization tokens. The total time to a publish-ready sequence is 40 to 60 minutes instead of 3 hours. Across a team creating sequences regularly, this is a meaningful time saving.
What Changes in a RevOps Workflow with AI Enabled
The teams getting the most value from HubSpot AI are not using it to replace judgment. They are using it to replace the low-leverage execution tasks that previously consumed the most time. Specifically:
- Data review before calls shifts from 10 minutes of manual research to 2 minutes of reading a Copilot-generated summary
- Workflow building shifts from writing every enrollment criteria from scratch to describing what you want and refining the output
- Lead prioritization shifts from a static scored list to a dynamic model that updates as your deal data changes
- Contact data quality shifts from a manual data project (quarterly at best) to continuous enrichment
The work that does not change: defining the revenue process, setting pipeline definitions, analyzing what the data means, managing the exceptions, and making the judgment calls about which contacts to pursue and how. RevOps professionals who position themselves as the people who configure, govern, and interpret the AI are more valuable than they were before it existed. The ones at risk are those doing high-volume, low-judgment execution work that AI handles well.
The Prerequisite for AI to Work: Clean Data
Every HubSpot AI feature performs better with clean, complete data. Copilot's summaries are only as good as the notes and activities logged against a record. Predictive lead scoring only learns from deals that were accurately tracked from stage to stage. Breeze Intelligence can enrich incomplete records but cannot invent contact history that was never captured.
If your team is evaluating HubSpot AI and wondering why the results are not impressive, the answer is almost always in the data. The AI layer is working correctly; it simply does not have enough good inputs to produce good outputs. A data audit and cleanup project typically unlocks more value from the AI features than any additional AI configuration.