Tool
HubSpot Breeze
Use HubSpot Breeze when AI should work inside an existing HubSpot CRM. Review Agent Hub, Assistant, 2026 credit rates, limits, privacy, and fit.
Verdict
Choose HubSpot Breeze when HubSpot already holds the customer record, engagement history, content, and team permissions that should ground AI work. Its advantage is context and action inside the CRM, not a uniquely capable standalone model. Do not migrate to HubSpot for Breeze alone: the useful agents sit behind hub entitlements, seats, setup work, and a second usage bill in HubSpot Credits. Pilot one bounded workflow, cap its credits, and compare accepted outputs per dollar with the deterministic workflow or specialist tool it would replace.
HubSpot still uses Breeze for its AI layer and Breeze Assistant for the conversational helper. The former Breeze Agents product is now Agent Hub, where teams activate HubSpot agents and build custom ones. That naming matters when comparing prices: there is no single “Breeze plan.” Access is assembled from a HubSpot subscription, the right edition and seat, enabled data permissions, and credits for metered actions.
Start with the best AI sales tools if the CRM decision is still open. For prospect data and outreach without a full HubSpot commitment, compare Apollo and the AI sales prospecting shortlist. For multi-provider research and enrichment logic, compare Clay.
Decide from the CRM outward
| Buying question | Breeze is a fit when | What to validate |
|---|---|---|
| Where context lives | HubSpot contains reliable contact, company, deal, activity, content, and support data | Check missing associations, duplicate records, property authority, and permission boundaries before asking an agent to act |
| What the job requires | Summarization, research, drafting, routing, or a bounded agent action benefits from CRM context | Keep exact field insertion, suppression, billing, and other deterministic rules outside generative judgment |
| Which product is needed | The required Assistant or agent is in the edition the team already buys | Verify the live catalog, seat type, beta status, connected accounts, and AI data switches in the actual portal |
| How usage scales | A defined credit event maps to an outcome worth its published rate | Replay representative volume; budget recommendations, resolutions, prompts, recurrences, telephony, and adjacent hub fees separately |
| How work is reviewed | Owners can inspect drafts, cap spend, monitor exceptions, and take over conversations | Start with manual enrollment and approval before autonomous sending or property updates |
| Why it beats the current stack | Keeping context and action in HubSpot removes meaningful exports, syncs, or admin work | Compare accepted outputs and operator time against existing workflows, not a generic chatbot demo |
What the current product includes
Breeze Assistant is available across HubSpot products and plans. It can draft and refine content, summarize CRM information, prepare for meetings, use saved prompts and projects, and work with connected apps subject to the user's permissions. HubSpot documents a generation limit of 30 requests per minute and 1,000 per day. Connected-app search has tool-specific syntax limits; Gmail searches, for example, do not accept every natural-language filter.
Agent Hub is the operating layer for prebuilt and custom agents. The live catalog includes customer, data, prospecting, content, nurture, revenue, knowledge-base, and custom agents, with several still labeled beta. Availability differs by agent. The catalog currently lists Data Agent and Prospecting Agent with any Starter, Professional, or Enterprise edition, Customer Agent with specified Professional or Enterprise hubs, and custom agents with paid editions. “Agent Hub included” therefore does not mean every agent is unlocked on every plan.
For sales, the prospecting agent monitors selected company and engagement signals, researches accounts, and follows a user-defined play for outreach. Its context can include associated form submissions, page views, calls, meetings, notes, and email opens from the previous year. Setup requires the relevant AI data switches plus Super Admin or prospecting-agent permission. Credit-consuming actions cannot run in sandbox accounts, so evaluation needs a tightly limited production sample.
This CRM-native loop is the real advantage. The agent can start from HubSpot signals and return drafts and activity to the same operating system. It is weaker as a reason to adopt HubSpot from scratch, or when the source of truth remains Salesforce and the team already has separate data and engagement products.
Pricing has three layers
Breeze Assistant has no separate add-on fee, but that does not make the agent system free. Model the hub subscription, paid seats and onboarding, then HubSpot Credits.
The live Sales Hub page shows Free at $0 for up to two users. Its current Starter card displays a promotional $7 per seat/month annual-commit starting price beside $20; verify renewal terms rather than treating the promotion as permanent. Professional shows $90 per seat/month when billed annually or $100 with monthly billing and an annual commitment, plus required $1,500 onboarding. Enterprise starts at $150 per seat/month with required $3,500 onboarding. Other hubs and the Customer Platform have different totals, contact tiers, seats, and entitlements.
Included monthly credits follow the highest qualifying subscription and are not added together across products:
| Subscription family | Starter | Professional | Enterprise |
|---|---|---|---|
| Smart CRM, Marketing, Sales, Service, Content, or Revenue Hub | 500 | 3,000 | 5,000 |
| Data Hub or bundled Customer Platform | 500 | 5,000 | 10,000 |
Additional credits cost $0.010 each: either $10 capacity packs of 1,000 monthly credits for the remaining commitment term or pay-as-you-go overages, invoiced in ten-credit increments. Credits reset monthly and unused units do not roll over. Capacity packs can automatically raise the committed monthly limit; pay-as-you-go returns to the prior limit after reset. Set account, feature, and action limits before enabling volume.
The rate sheet checked October 9 makes the spend event concrete:
| Agent action | Credits | List-price equivalent |
|---|---|---|
| Customer Agent resolves one text conversation without human help | 50 | $0.50 |
| Data Agent answers one prompt for one record | 10 | $0.10 |
| Prospecting Agent recommends outreach for one lead | 100 | $1.00 |
| Content Agent generates one piece of content (beta) | 1,000 | $10.00 |
| Custom agent uses one action unit (beta) | 1 | $0.01 per unit; an execution can require multiple units |
The rate sheet also charges some recurring monitoring and automation work. A published per-action price is not the complete workflow cost: telephony, SMS, hub seats, contact tiers, external data providers, and human review may sit beside it. “Outcome based” means the defined billable event, such as recommending outreach—not a reply, meeting, opportunity, or sale.
Where Breeze earns its place
Breeze is most defensible when the team has already standardized on HubSpot. An account brief can draw on records, emails, calls, meetings, website activity, and approved business context without copying them into another agent. Permissions follow the surrounding account, and administrators can limit credit use by feature.
The assistant is also a low-friction way to test whether CRM-grounded generation helps. Meeting preparation, record summaries, first drafts, and questions about a known account are easier to review than autonomous outreach or record mutation. If those assisted tasks do not save measurable time, moving to custom agents will add configuration and billing without fixing the value case.
For outbound work, use the agent after ICP and routing rules are already sound. The prospecting agent can watch signals and prepare personalized outreach, while the surrounding HubSpot workflow handles ownership and activity. Use account research to define evidence requirements, lead scoring to separate fit from activity, and controlled prospecting for approval and suppression gates.
Limits that change the decision
HubSpot's product family is broad enough to hide dependencies. A compelling demo may combine features from different hubs, editions, betas, seats, and credit meters. Build an entitlement sheet from the live catalog and order form. Do not infer that an agent is included merely because Agent Hub appears in the account.
Generative output is also the wrong tool for exactness. HubSpot's own Product Specific Terms say AI output may be inaccurate or unreliable and require independent review. Keep consent, opt-out, sender identity, exact prices, contract terms, and protected CRM fields deterministic. Draft into review queues or proposed fields before allowing autonomous sends or writes.
The prospecting agent cannot complete metered actions in a sandbox. That makes credit caps and a production pilot essential. Start with a small manually enrolled segment, inspect the research and message for each contact, and measure accepted drafts, corrections, replies, handoffs, and credit cost. The catalog names an outreach recommendation as the 100-credit event; the setup documentation describes credit use when personalized outreach is generated for recommended or manually enrolled leads. Confirm the trigger in the current portal before forecasting rejected suggestions or manual enrollments.
Breeze does not replace source coverage testing. Data Agent and enrichment features can research or populate CRM data, but more fields do not make an irrelevant lead relevant. For conventional contact coverage, compare Apollo. For source selection and waterfall logic, compare Clay. Use the CRM enrichment guide before allowing either path to change production records.
Privacy requires two separate answers
HubSpot says third-party AI service providers it hires, including providers such as OpenAI, cannot use customer data for model training. It says it minimizes retention and enforces zero-day retention where possible; the exact provider, processing location, and retention boundary belong in the current subprocessor list and model card.
HubSpot's own model training is a different setting. Its September 2026 documentation says the account-level training toggle is on by default and HubSpot may use eligible customer data to train models across customer accounts. A Super Admin can opt out without losing AI feature access. Sensitive Data accounts are opted out by default and cannot opt in. The opt-out applies going forward and cannot remove data already used in a trained model. Enrichment and model-training controls are separate.
For the prospecting agent, administrators must separately enable access to CRM data, customer conversations, and files. Treat those switches as data-scope decisions rather than onboarding chores. Map which records, communications, files, connected apps, external providers, and users each agent can reach; then review regional processing, subprocessors, retention, DPA terms, and required disclosures for automated outreach or support.
What operators report
In an r/hubspot implementation thread, u/B2BMktg reported that deployment required more operational work than expected: seat and permission checks, connected sender mailboxes, a fallback sender, sender-field decisions, enough credits, and monitoring. They recommended manual enrollment and human review at first, plus a credit limit.
In a July 2026 account of a long-cycle, high-value funnel, u/Forsaken-Talk-4779 reported that the prospecting agent was useful for tone, contextual synthesis, and re-engaging cold inbound leads, but not for exact form-field recall. They kept a human handoff at the first real reply and described the lack of sandbox execution as a reason to budget a controlled live sample.
These are attributed individual reports, not evidence of average accuracy, cost, reply rate, or implementation effort. We did not create a HubSpot account, enable an agent, connect CRM or mailbox data, spend credits, send outreach, compare generated copy, or test data accuracy for this profile.
Choose Breeze when its work can stay close to a well-governed HubSpot record and remove a real handoff. Keep the current workflow when it is deterministic, low-volume, or already reliable. Choose a specialist when the task's core advantage comes from external data coverage, multi-provider control, or execution outside HubSpot.
For adjacent decisions, use personalized cold email workflow, post-meeting follow-up controls, and the broader sales-tool comparison.
Sources & further reading
- HubSpot Agent Hub overview and agent pricing
- HubSpot Credits pricing and controls
- HubSpot Product and Services Catalog credit rate sheet
- Sales Hub plans, seats, onboarding, and included credits
- Breeze Assistant requirements and limits
- Prospecting agent behavior and limitations
- HubSpot AI model training controls
- HubSpot AI service-provider data handling
- HubSpot Customer Terms
- HubSpot Product Specific Terms
- Reddit report on prospecting-agent deployment
- Reddit report on high-touch prospecting fit
