HubSpot Cut Breeze Customer Agent to $0.50 a Resolved Conversation. Here's the Break-Even Math and the Vendor-Defined-Metric Trap.

On April 14, 2026, HubSpot cut Breeze Customer Agent from $1.00 per conversation to $0.50 per resolved conversation, and moved Breeze Prospecting Agent from a recurring per-contact-enrolled charge to $1 per qualified lead. The headline reads like a price drop. Run the funnel math and it is a repricing of risk, and the part that decides whether it lands in your favor is a number HubSpot defines and you cannot independently audit.

What actually changed, in numbers

Two Breeze agents moved to outcome billing. Customer Agent (the support deflection agent) went from a flat $1.00 per conversation to $0.50 per resolved conversation. Prospecting Agent (the outbound enrollment agent) dropped its recurring monthly per-contact-enrolled fee in favor of $1 per qualified lead handed to your team. The change took effect April 14, 2026, announced the day before (HubSpot company news; CMSWire).

HubSpot's supporting claim: Customer Agent resolves 65% of conversations and cuts resolution time 39% across 8,000 customers (MarTech). For context on the market it is pricing into, Intercom's Fin charges $0.99 per resolution with a mandatory 50-resolution monthly minimum (Fin AI pricing). At $0.50 per resolved conversation HubSpot is landing at roughly half the closest outcome-priced competitor, which is the real reason this move matters, not the move from "per use" to "per result" on its own.

I have not pushed $5,000 of real volume through the new Breeze model. This is the break-even model I built before deciding whether to, because the pricing change does not tell you whether your account gets cheaper. Your resolution rate does.

The break-even math the coverage skipped

Every writeup repeated the $1.00 to $0.50 line. None of them ran the only equation that matters to a P&L: at what resolution rate does $0.50 per resolved beat $1.00 per attempted?

Old model cost per 1,000 inbound conversations: 1,000 attempts × $1.00 = $1,000, flat, regardless of how many the agent actually closed.

New model cost per 1,000 inbound conversations: 1,000 × resolution rate × $0.50.

Set them equal and the break-even resolution rate is 100%. Below a 100% resolution rate the new model is strictly cheaper than the old flat per-conversation fee. At HubSpot's quoted 65% resolution rate the math is concrete.

That looks like a clean win, and for Customer Agent against the old flat fee it usually is. The trap is not in this table. It is in the word "resolved" and in the fact that the same logic does not transfer to Prospecting Agent, where the old model had no per-attempt floor at all.

Prospecting Agent is the harder case. The old per-contact-enrolled fee was a known, cappable number: you enrolled N contacts, you paid for N contacts, your CAC contribution was fixed before a single reply came back. The new $1-per-qualified-lead model converts a fixed cost into a variable one indexed to a conversion event HubSpot scores. If your enrolled-to-qualified rate is high, $1 per qualified lead can cost more than the old flat enrollment fee, not less. Outcome pricing is not a discount. It is a bet that your conversion rates are bad, priced by the side that measures them.

The credit-pool catch nobody priced in

"Pay when the task is complete" implies pay-as-you-go. It is not. Breeze outcome charges draw down HubSpot Credits, a prepaid pool, with a conversion schedule (100 Breeze Credits map to 3,000 HubSpot Credits in the published table) (HubSpot Credits and billing).

That changes the unit economics in two ways the coverage missed. First, unused credits at the end of a period are sunk cost, so your effective cost per resolved conversation is not $0.50, it is $0.50 plus your credit breakage rate. A team that prepays for 10,000 resolutions and uses 7,000 is paying an effective $0.71 per resolved, not $0.50, until the breakage is worked out of the forecast. Second, prepayment removes the cleanest property outcome pricing is sold on, that you only pay for results. You pay for a forecast of results in advance, then reconcile against actuals, which is the same cash-flow shape as a seat license with extra steps.

The vendor-defined-metric trap

Here is the part that makes this a /growth/ problem and not a procurement footnote. In outcome pricing, the vendor invoices you on a metric the vendor defines, measures, and reports. You are paying a CAC line item that you cannot independently audit.

What counts as a "resolved" conversation? If a user gets an answer, closes the chat, and reopens a new conversation 20 minutes later with the same problem, is that one unresolved issue or two billable conversations, one of them "resolved"? What counts as a "qualified" lead handed to your team? HubSpot's model decides, using HubSpot's scoring. SaaStr's read on the broader shift was blunt about exactly this incentive: per-resolution pricing only changes customer economics if the definition of resolution is honest, and the vendor sets the definition (SaaStr). Constellation Research flagged the same structural point, that outcome-based AI pricing shifts measurement power to the platform (Constellation Research).

Attribution-honest version: I cannot prove HubSpot inflates resolution counts, and I am not claiming it does. The problem is structural, not accusatory. When the billed event and the success metric are the same number, and one party owns the meter, your finance team is reconciling against a definition it did not write and cannot recompute. That is a different risk class than a seat license, where the unit you pay for (a seat) is one you can count yourself.

The defensible move is to instrument your own resolution and qualification definitions in parallel, in your own data warehouse, from day one. Tag every Breeze-touched conversation, score qualification on your own pipeline-conversion data, and run your number next to the invoice every month. If the two diverge by more than a few points, you have a renegotiation lever. If you never built your own meter, you have a bill.

What didn't hold up when I modeled it

Two things I expected to be true broke under the math.

I expected outcome pricing to be universally cheaper than the old model. It is not. It is cheaper for Customer Agent against a flat per-attempt fee, and it is potentially more expensive for Prospecting Agent against a fixed per-enrollment fee whenever your qualification rate is healthy. The pricing change rewards accounts with weak funnels and penalizes accounts with strong ones. A team converting 8% of enrolled contacts to qualified leads pays less per qualified lead than a team converting 25%, in absolute terms per enrolled contact, the strong-funnel team can end up paying more total under $1-per-qualified than under the old enrollment fee.

I also expected the Fin comparison to be the deciding factor. It is not, for most HubSpot-native teams. If you already run HubSpot CRM, the switching cost and data-model integration dwarf a $0.49-per-resolution rate-card gap with Intercom. The comparison that decides this is not Breeze versus Fin. It is Breeze-outcome versus your own blended cost of human-handled conversations, and that is the number to put on the page in your internal memo.

The decision rule I'd actually run

1. 1

   Pull your real resolution and qualification rates first

   Do not start from HubSpot's 65%. Pull your last 90 days of support conversations and outbound enrollments and compute your own deflection-eligible resolution rate and your enrolled-to-qualified rate. These two numbers, not the rate card, decide the outcome.

2. 2

   Model Customer Agent against your flat-fee baseline

   Cost_new = monthly conversations × your resolution rate × $0.50, divided by your forecast credit utilization. If that is below your old flat per-conversation spend and below your blended human handling cost, Customer Agent outcome pricing is a clear move.

3. 3

   Model Prospecting Agent against the OLD enrollment fee, not against zero

   Cost_new = qualified leads × $1, divided by credit utilization. Compare to what the old per-contact-enrolled fee would have cost at the same volume. If your funnel is strong, this can be the rare case where the old model was cheaper. Keep the option to negotiate enrollment-based terms if so.

4. 4

   Stand up your own meter before you switch

   Instrument resolution and qualification in your warehouse with your own definitions. Reconcile against the HubSpot invoice monthly. Treat any divergence over a few points as a contract conversation, not an accounting rounding error.

5. 5

   Re-decide quarterly, because your funnel moves

   The break-even is a function of your conversion rates, and those drift. A pricing model that wins at a 65% resolution rate can lose at 85%. Put the recompute on the quarterly finance calendar.

This is also a reason to keep your CRM automation portable rather than fully welded to one vendor's billable-event definitions. The teams I have helped instrument WhatsApp and CRM lead-response flows through DVNC.ae keep the qualification scoring in their own pipeline data precisely so a vendor's metric change is a config conversation, not a quarter of margin.

Is HubSpot Breeze outcome pricing actually cheaper than the old model?

For Customer Agent against the old flat $1.00-per-conversation fee, almost always, because any resolution rate below 100% makes $0.50-per-resolved cheaper. For Prospecting Agent against the old per-contact-enrolled fee, not necessarily, a strong enrolled-to-qualified rate can make $1-per-qualified-lead cost more in total. Model them separately.

What counts as a resolved conversation in Breeze?

HubSpot's model determines resolution using HubSpot's scoring, and that definition is not one you can independently recompute from the invoice. Instrument your own resolution definition in parallel and reconcile monthly so you have a renegotiation lever if the numbers diverge.

Does $0.50 per resolved conversation include the HubSpot Credits prepayment?

The rate card is $0.50, but charges draw from a prepaid HubSpot Credits pool. Your effective cost is $0.50 divided by your credit-utilization rate. At 70% utilization that is closer to $0.71, so model breakage before comparing to competitors.

How does Breeze at $0.50 compare to Intercom Fin at $0.99?

On the rate card HubSpot is roughly half. For a HubSpot-native team the rate-card gap is rarely the deciding factor, integration and switching cost dominate. The comparison that decides it is Breeze-outcome cost versus your blended cost of human-handled conversations.