The short version: On July 23, 2026, HubSpot put its AI agents behind one console — Agent Hub to build, run, monitor, and audit them, and Agent Builder, a low-code canvas that assembles a custom agent from plain English and your CRM data. It's in public beta for Professional and Enterprise customers. That's the launch. But the detail a founder should actually underline isn't the console — it's the price: HubSpot now charges for its agents by result. The Prospecting Agent costs $1 per recommended lead; the Customer Agent bills only when it resolves the ticket. Both come with a 28-day free trial.

That pricing model is the story, so let's take it in order.

What it is#

Agent Hub is a management surface. It gathers HubSpot's prebuilt agents — a Customer Agent for support and a Prospecting Agent for sales outreach — alongside any custom agents, and gives you one place to configure, activate, monitor, and audit them. Agent Builder is the make-your-own half: a low-code, natural-language canvas where a non-engineer describes what the agent should do, points it at knowledge sources, and lets it pull live context from HubSpot's Smart CRM. No separate SKU, no new platform to stand up — if you're already on HubSpot, it's there.

Mechanically, this is HubSpot doing what every incumbent SaaS with a data moat is doing this year: wrapping its own CRM context in an agent and selling the loop back to you. The CRM data is the point. An Agent Builder agent is only as sharp as the Smart CRM records behind it.

The part that matters: the meter changed#

Here's what separates this from a press release. HubSpot moved its Breeze agents to outcome-based pricing (CMSWire). The Prospecting Agent charges $1 per recommended lead, effective April 14, 2026. The Customer Agent bills when the task is complete — you pay on resolution, not per seat and not per token. Both agents run on HubSpot Credits, with a 28-day trial to test the economics before you commit.

Seat pricing charges you for access. Token pricing charges you for compute. Outcome pricing charges you for a result — and when the market leader flips to it, "cost per completed task" stops being an analyst's phrase and becomes the line on your invoice.

We've been circling this number for weeks. It's the same lens the wire keeps returning to — stop pricing models by their per-token rate, measure cost per completed task — and it's the discipline behind cutting your Opus 5 bill with the effort parameter. HubSpot just made it the default contract. That's a bigger tell than any benchmark: when a vendor is willing to only get paid when its agent produces a result, it's betting the agent works often enough to make outcome pricing profitable — and it's handing the "does this thing actually do anything" risk back to itself.

The catch, because there's always one#

Outcome pricing is a bargain only if you can measure the outcome, and only on the vendor's definition of it. A "recommended lead" is whatever HubSpot's Prospecting Agent decides to surface — and $1 a lead across a high-volume top of funnel is still a real bill, just an itemized one. A "resolved" support ticket counts as resolved by the agent's own account, which is exactly the gap our reporting on why self-reports lie keeps flagging. Before you flip it on:

Bottom line: Agent Hub is a convenient console if you already live in HubSpot, and irrelevant if you don't. But the pricing move is a signal for every founder, HubSpot customer or not — the incumbents are now willing to charge by the result, and that means the number to run your own agent economics against is the one HubSpot just put on the price tag: cost per completed task.