Free comparison Vendor-neutral
HubSpot Breeze vs. custom Claude agent: which should you build?
CS Written by Charles Summers, founder of Hacking Demand (12+ years in B2B SaaS demand gen) · Updated July 2026
If your customer agent lives inside HubSpot’s CRM and knowledge base, HubSpot’s native Breeze Customer Agent wins on speed, cost, and proven results: 65% average resolution across 8,000+ customers, at $0.50 per resolved conversation. If the work reaches outside HubSpot — other systems, custom logic, model routing — a custom Claude agent earns its complexity. Most teams don’t know which one they actually need until someone scopes it. That’s what this page, and the free call below, are for.
The two options, side by side
Both are real ways to automate customer conversations. They are not competing on quality so much as on where the work lives. Here is the full breakdown, dimension by dimension.
| Dimension | HubSpot Breeze Customer Agent | Custom Claude Agent |
|---|---|---|
| What it is | Native HubSpot AI agent, found in the nav under Service › Customer Agent regardless of which Hub's Pro/Enterprise license unlocked it | Bespoke agent built on the Claude Agent SDK/API, wired into HubSpot via MCP or custom integrations |
| Subscription required | Professional or Enterprise on any one of: Marketing Hub, Sales Hub, Service Hub, Data Hub, Content Hub, Smart CRM, or Commerce Hub, plus HubSpot Credits for usage | No HubSpot subscription tier requirement; cost is Claude API/Bedrock/Vertex usage plus engineering to build the HubSpot connection |
| Setup effort | No-code, live in about 15 minutes; real value depends on knowledge base and escalation config | Engineering build; benchmark is 2 to 3 weeks minimum, $8K to $45K typical partner cost |
| Channels | 9+ native: web chat, email, WhatsApp, SMS, Instagram, Telegram, LINE, Slack, Facebook Messenger, voice (beta) | Whatever you build connectors for; no pre-built marketplace |
| Knowledge grounding | HubSpot knowledge base articles, website/landing pages, blogs, uploaded files (.docx, .pdf, .csv, etc.), public URLs | Anything you connect: HubSpot, data warehouse, billing, internal APIs, docs |
| Governance | Seat- and permission-gated (Customer agent editor permission); CRM read/write access toggled per agent, with approval gates on write actions | You grant tool access explicitly in code, more granular, more DIY |
| Pricing model | Outcome-based since April 14, 2026: $0.50 per resolved conversation, credits consumed only on resolution, free 28-day trial | Token-based usage, cost tied to consumption not outcomes; Enterprise tiers add SSO, spend controls, HIPAA readiness, data residency |
| Model control | Abstracted away, no visibility or choice | You pick and route per task (Haiku/Sonnet/Opus); routing can cut cost 40 to 70% vs. all-Sonnet |
| Cross-system reach | HubSpot + public web, plus live one-off API calls to outside systems (order status, pricing, inventory) via no-code Actions | Core strength — can reason across CRM + finance + product DB + anything else in one agent, multi-step |
| Maintenance | HubSpot-managed, updates automatically | Owned by you or a partner, ongoing engineering required |
| Track record | 8,000+ activated customers, 65% avg resolution, 90%+ for top performers, 39% faster resolution | No standardized benchmark; performance is entirely build-quality-dependent |
| Best fit | Support/service resolution grounded in CRM + knowledge base, prospect already on Pro/Enterprise for any Hub, fast time-to-value | Work spanning multiple systems, bespoke multi-step logic, strict compliance/data residency needs |
| Weak spot | Actions are scoped, single-endpoint lookups, not full multi-step orchestration across systems; no native backtesting against historical tickets | No marketplace; needs sustained engineering investment, less predictable cost |
Two routes to build a customer agent
Rather than argue you into one option, we will scope your actual requirements and tell you honestly which path fits. Both routes start the same conversation.
The fast path if your agent lives inside HubSpot’s CRM, knowledge base, and conversations. No engineering team required, live in days.
Scope my Breeze build →The right path if the agent needs to reach outside HubSpot: other systems, bespoke logic, model routing, or strict data controls.
Scope my custom build →How to tell which one you need
Start with where the data lives. If everything the agent needs to answer a question already sits in your HubSpot CRM, knowledge base, help desk, and public site, Breeze gets you live in days at a price your finance team will approve without a fight. That covers the large majority of "customer agent" requests we see.
The custom Claude route earns its cost when the agent has to reach past HubSpot: a billing system, a product database, a warehouse, bespoke approval logic, or a requirement to route between models for cost or compliance reasons. Building that inside HubSpot alone is not possible today; building it outside HubSpot means owning the engineering.
The honest failure mode on both sides: buying a custom build for a problem Breeze already solves, or trying to force a cross-system workflow into a tool that was not built to leave HubSpot. Scoping the actual requirement first avoids both.
FAQ
Does the HubSpot Breeze Customer Agent require Service Hub specifically?
No. It requires a Professional or Enterprise subscription on any one of Marketing Hub, Sales Hub, Service Hub, Data Hub, Content Hub, Smart CRM, or Commerce Hub, plus HubSpot Credits for usage. Service Hub is simply where the Knowledge Base and Help Desk content sources typically live.
What does the Breeze Customer Agent actually cost?
Since April 14, 2026 it runs on outcome-based pricing: $0.50 per resolved conversation, with a free 28-day trial. You only pay when it resolves something.
When does a custom Claude agent make more sense than Breeze?
When the work reaches outside HubSpot: other systems, bespoke multi-step logic, per-task model routing, or strict data residency and compliance controls Breeze doesn't offer.
Can Breeze pull data from an outside system like an ERP?
Yes, via Actions: a no-code feature where you set a trigger phrase, define required inputs, and point the agent at a live API endpoint (GET or POST, with API key or signed-request authentication). HubSpot's own example is a customer asking "where's my order," with the agent pulling the live answer from an outside system. It is built for scoped lookups like order status, inventory, or pricing, not full multi-step orchestration across many systems.
Can I run HubSpot Breeze and a custom Claude agent together?
Yes. Breeze can handle native, in-HubSpot support resolution while a custom Claude agent orchestrates work that spans your wider stack. The two aren't mutually exclusive.
Do I need an engineering team for a custom Claude agent?
Yes, to build and maintain it: the Claude Agent SDK, connections to your systems, permissions, and monitoring. There's no marketplace to install from the way there is with Breeze.
How do I know which option is right for my use case?
It comes down to scope. Book a free 30-minute call and we'll walk through your actual requirements before you commit engineering budget or a subscription tier to either path.
