Breeze vs Custom Claude Agents: Where Each One Wins

If you run HubSpot and you are weighing up where to invest in AI, the question usually lands as a choice between two things. You can lean into Breeze, HubSpot's own AI brand, which is built into the platform you already pay for. Or you can commission a custom AI agent built on Claude, wired into HubSpot and the rest of your stack. The temptation is to treat this as a contest with one winner. It is not. The two approaches solve different problems, and the smartest teams use both.

This guide explains what Breeze actually is, where it genuinely shines, how to get real value from it rather than leaving it switched on and underused, and where a custom Claude agent goes further. It is written for business decision-makers who want a fair, accurate read rather than a sales pitch. If you want the wider context first, our pillar on AI for HubSpot sets out the full landscape. For a deeper look at HubSpot's autonomous agents, read the Breeze agents explained.

What Breeze is

Breeze is HubSpot's AI brand, and it has three pillars. The first is Breeze Assistant, the conversational AI built into HubSpot, your browser and mobile. It answers questions, summarises records, generates content and runs custom assistants, all grounded in your CRM data and aware of your role. The Assistant responds to you. It does not act on its own.

The second pillar is autonomous Breeze Agents. These do run on their own within guardrails. HubSpot's own product page puts it plainly: the agents "run on their own, but you'll always stay in control with clear guardrails, approvals, and visibility every step of the way". So the human in the loop is native, not bolted on. The Customer Agent resolves support enquiries by training on your website, blog, knowledge base and uploaded documents, then hands off to a human on escalation. Per HubSpot's knowledge base it now covers nine channels, including website chat, email, WhatsApp, SMS, Instagram, Telegram, LINE, Slack and Facebook Messenger, with voice and calling in beta. The Prospecting Agent surfaces in market accounts from buying signals such as job postings, funding and technology adoption, builds and enriches contact lists, and drafts personalised outreach for a rep to review and send. It does not send on the rep's behalf. Newer agents, including Closing, Customer Health and Company Research, are in beta and currently run free of HubSpot credits, with notice before they start consuming them.

The third pillar is Breeze Intelligence, which handles data enrichment and buyer intent. Across all three, the defining trait is that Breeze is native to HubSpot. The agents are grounded in your CRM, conversations, knowledge base and documents with no integration to build, and they inherit HubSpot's permissions, approvals and reporting.

Where Breeze shines

Breeze is strong precisely because it lives inside HubSpot. If the work you want to automate is grounded in CRM data and customer conversations, there is very little reason to build something bespoke. The Customer Agent is the clearest example. HubSpot reports that across more than 8,000 customers who have activated it, the Customer Agent resolves 65% of conversations on average and cuts resolution time by 39%. That is an average rather than a guarantee, and top performing teams are reported to reach 90% or higher, but it shows what well grounded native AI can do on support volume.

The commercial model is also worth taking seriously. In April 2026, HubSpot moved the Customer Agent and Prospecting Agent to outcome based pricing. You pay only when the agent produces a result, a resolved conversation or a lead recommended for outreach. HubSpot's Chief Customer Officer Jon Dick framed it as "You pay when it works, full stop". The Customer Agent moved to $0.50 per resolved conversation and the Prospecting Agent to $1.00 per lead recommended for outreach, both for Pro and Enterprise customers and both with a free trial. HubSpot also reported Prospecting Agent activations up 57% quarter over quarter. For a finance team, paying on results rather than on a flat licence is an easy model to defend.

Add to this the breadth of the agent line up, the ability to install pre built specialised agents from the Breeze marketplace or customise them in Breeze Studio, and the fact that everything inherits the governance and reporting you already trust in HubSpot. For native, in CRM jobs, Breeze is the right starting point, and we say that as a HubSpot Diamond Partner.

Getting real value from Breeze

The honest truth is that most teams underuse Breeze. They switch on an agent, leave the defaults in place and judge it on a weak first impression. The value sits in the configuration, and that is where careful implementation pays back.

Start with the knowledge base. The Customer Agent is only as good as the content it trains on, so your help articles, website pages and uploaded documents need to be accurate, current and well structured. Thin or contradictory content produces thin or contradictory answers. Next, set your escalation and handoff rules deliberately. Decide which channels the agent covers, when it is active and exactly when it hands a conversation to a human, rather than accepting the defaults. Then use the guardrails and approvals that HubSpot builds in, so the agent operates inside boundaries your team has agreed.

Data quality matters just as much for the Prospecting Agent. The signals it surfaces and the lists it builds depend on clean, well segmented CRM data underneath. There is also a quiet but useful capability worth planning for. The Run Agent workflow action, in private beta since January 2026, lets you trigger a Breeze Agent from inside a HubSpot workflow, for example when a deal stage changes, then feed the agent's output back into records and follow up automation. During beta it is capped at 500 executions per day, does not consume HubSpot credits, and needs Pro or Enterprise editions. Configured well, these pieces turn Breeze from a novelty into a dependable part of how your team works.

Where a custom Claude agent goes further

Breeze is grounded primarily in HubSpot and the web. That is its strength and also its boundary. When the work spans systems that do not all live inside HubSpot, or needs logic HubSpot does not model, a custom Claude agent goes further.

Custom Claude agents are built on the Claude Agent SDK and the open Model Context Protocol, a standard for connecting an agent to external tools and data sources without writing bespoke integrations for each one. A single agent can connect to several systems at once. HubSpot can be one connection among many, alongside a Postgres data warehouse, a billing system or an internal API, so the agent can reason across systems that do not all sit in the CRM. If you need to answer a question that pulls from HubSpot, your finance platform and a product database in one go, that is custom territory.

There are three further levers. The first is governance. With a custom agent you grant tool access explicitly in code, so the agent can only call the systems and operations you allow, a control you configure rather than inherit. The second is model choice. Breeze abstracts the underlying model away from you. With a custom Claude agent you choose the model per task. Anthropic's 2026 lineup runs Haiku for fast simple work, Sonnet for most production workloads and Opus for complex multi step reasoning, and you can route between them. One trade analysis from claudeimplementation.com estimates that routing in this way can reduce API cost by 40 to 70% versus sending everything to Sonnet. The third is deployment and compliance. The Claude API is available via Anthropic direct, Amazon Bedrock and Google Cloud Vertex AI, and Enterprise plans offer single sign on, spend controls, HIPAA readiness and data residency options, which matters when rules dictate where your data is processed.

The honest caveats apply too. A custom Claude agent needs engineering to build and run. There is no marketplace to install from, you must connect HubSpot yourself to get the CRM grounding Breeze has by default, and cost is tied to token usage rather than outcomes, so it has to be controlled with model routing and spend limits. That is real work, which is exactly why the choice between the two should be made on the job in front of you, not on a preference.

How SpotDev helps

SpotDev sits on both sides of this. We are a HubSpot Diamond Partner, so we implement, configure and optimise the Breeze Assistant and agents to get genuine value out of HubSpot's own AI, the knowledge base, the guardrails, the escalation rules and the data underneath. We are also a Claude specialist with in house engineers who build custom Claude agents for the work Breeze cannot reach, wired straight into HubSpot. Nothing is subcontracted, and we have delivered 300 plus technology projects.

Because we do both, our advice is honest. We will tell you when Breeze is enough and when a custom build pays back, rather than steering you toward whichever pays us more. Often the answer is both running side by side, with Breeze handling native, outcome priced, in CRM jobs and a custom Claude agent orchestrating across your wider stack. HubSpot's own Run Agent workflow action means the two can sit together rather than compete. Our packages are fixed, from a £5,000 Readiness Assessment through delivery from £8,000 to £45,000, with a first rollout live in two to three weeks. If you want a frank assessment, talk to a Claude-specialist engineer.

Work with a Claude specialist

SpotDev designs, builds and deploys custom Claude agents and enterprise Claude rollouts for UK businesses, with fixed packages from £8,000 to £45,000 and a first rollout live in two to three weeks. Explore our Claude implementation packages or talk to one of our engineers.

Frequently asked questions

Is Breeze included in my HubSpot subscription?

Breeze Assistant is built into HubSpot, and the autonomous agents are available on Pro and Enterprise editions. In April 2026 HubSpot moved the Customer Agent and Prospecting Agent to outcome based pricing, so you pay only when the agent produces a result, such as a resolved conversation or a lead recommended for outreach, and both include a free trial. Several newer agents are in beta and currently run free of HubSpot credits, with notice before they start consuming them.

Can Breeze and a custom Claude agent work together?

Yes, and that is often the best setup. Breeze handles native, CRM grounded work inside HubSpot, while a custom Claude agent orchestrates across systems that do not live in HubSpot, such as a data warehouse or a billing platform. HubSpot's Run Agent workflow action, in beta, even lets you trigger a Breeze Agent from within a HubSpot workflow, so the two approaches complement each other rather than compete.

When is a custom Claude agent the better choice over Breeze?

Choose a custom Claude agent when the work spans systems beyond HubSpot, needs bespoke logic HubSpot does not model, requires you to pick or route between models per task, or sits under stricter governance and data residency rules. Breeze is grounded primarily in HubSpot and the web, so cross system reasoning across non HubSpot systems is where a custom build earns its keep.

Do I need engineers to build a custom Claude agent?

Building and running a custom Claude agent needs engineering, including the Agent SDK, connections to your systems, permissions and monitoring. There is no marketplace to install from. SpotDev's in house engineers handle that work for you, wiring the agent into HubSpot and the rest of your stack, with fixed packages from £8,000 to £45,000 and a first rollout live in two to three weeks.