On 23 July, HubSpot's Agent Hub and Agent Builder entered public beta. From that date, all agents consume HubSpot Credits from your plan's balance.
That is a small pricing note and a large strategic change, and almost nobody is treating it as the second one.
Here is why it matters. For years, bad CRM data cost you hours. Someone worked a duplicate. A report didn't reconcile. A lead sat unrouted. The cost was real but invisible — absorbed by the team, argued about once a quarter, never on a bill. Metered agents move that cost somewhere it can be counted. The agent reads the broken record, spends the credit, returns a confident wrong answer, and a human still has to fix it. You now pay cash for the mess, and then pay salary to clean up after the thing you paid cash for.
Data quality just stopped being hygiene and started being unit economics.
Two releases matter here, and they're five weeks apart. Most of the coverage has merged them, which makes the timeline confusing — so here they are separately. We track these month by month in our monthly HubSpot product update.
23 July 2026 — the pricing switch. Agent Hub and Agent Builder went to public beta on Professional and Enterprise, across Marketing, Sales, Service, Data and Content Hub and the Smart CRM. HubSpot Credits are a prerequisite, not an optional add-on. The controls shipped alongside: a per-agent monthly run limit, cost previews in the agent inbox and on CRM record cards, and a test run that estimates the credit cost of a task without consuming credits. Separately, credit settings hold an account-level monthly credit limit.
Five templated agents were sunset the same day and can no longer be installed: Social Post, ABM Landing Page, RFP, Cross-sell/Upsell, and Sales to Marketing Feedback. Existing installations were left in place.
30 June 2026 — the surface got much wider. This is the release most teams half-noticed on the way into July:
Read that second list again as an operator rather than a reader. Several of those items don't just add capability — they hand an automated system the authority to act on your existing configuration, at volume, whether or not that configuration was ever finished. And since 23 July, that activity draws credits.
Because an agent charges per run, not per correct answer. Every structural flaw in your CRM becomes a multiplier on a number that now appears on your bill.
Three that bite immediately:
Duplicates multiply runs. Two records for the same company is not one problem, it's two agent executions, two credit draws, and two outputs a human has to reconcile into one truth. You are paying twice to learn something once.
Broken associations misdirect the work. Agents act through associations — contact to company, company to deal. A contact hanging off the wrong parent doesn't produce a smaller result. It produces a confident, wrong, fully-billed one.
Enforced configuration executes whatever it finds. This is the sharpest one. Help Desk routing now enforces one primary assignment method per channel, so whichever skills map exists is the one tickets follow. Lead Qualification Triggers fire on the instructions an admin wrote, against whatever definition of "qualified" already lives in your portal. If your skills map was aspirational, or marketing and sales never actually agreed what an MQL is, that disagreement is no longer a debate in a meeting. It is a rule, running at machine speed, on real tickets and real inbound leads.
Take the Prospecting Agent at its published price: 100 credits, about $1.00, per recommended lead.
Say it surfaces 500 leads in a month, and 20% of them are people already sitting in your CRM under a duplicate or a mis-associated record. That's 100 leads × $1.00 = $100 a month, $1,200 a year, spent rediscovering contacts you already own — before a single rep wastes a minute working one.
Be clear about what that number is. The $1.00 is HubSpot's published price at the overage rate. The 20% is an assumption I picked to show the shape of the maths, not a measured benchmark — your real rate might be 5% or 35%, and the only way to know is to look. That is exactly the point: most teams have never measured it, because until 23 July there was no invoice forcing the question.
Now scale it. Prospecting is one agent. Add agents built in Agent Builder on Professional and Enterprise, a Customer Agent qualifying inbound, and Breeze firing across five new surfaces, and the multiplier stops being a rounding error.
Five checks. None of them are glamorous, all of them are cheaper than the alternative.
That is a fortnight of work for most mid-market portals. It runs ahead of the spend, not behind it.
This is the unglamorous half of the agent era, and it's the half we do.
We're a HubSpot Solutions Partner and the first Asana Solution Partner in Israel, and the integrations we take on are the ones most partners route around — HubSpot to ERP, to billing, to the routing layer — because that is where coherence actually lives. HubSpot's 2026 State of Ecosystems Report puts it better than we could: "Intelligence is abundant. Coherence is not." The same report sizes the partner opportunity at $42B by 2030, growing at a 21.8% CAGR, with AI-first engagement revenue growing at 28.4% — and names the upmarket win condition as connected solutions plus partner expertise, with upmarket customers using an average of 16 or more applications.
Metering doesn't weaken that argument. It puts a price on it.
Agents are no longer a capability question, they're a cost question. The bill is a function of your data model — how many duplicate records you run against, how many associations point somewhere wrong, and how much of your configuration was aspirational rather than true. Fix that upstream and metering rewards you. Skip it and you've bought a subscription to your own technical debt.
If you want a specific read on your own portal before you scale agent runs, book the silent lead loss audit. We'll look at where inbound leads die between the form and the rep, which records your agents are paying to rediscover, and the one thing to fix first. We'll look at your HubSpot together and tell you straight whether we're the right fit. No deck. No pitch.
Yes. Since 23 July 2026, all HubSpot agents consume HubSpot Credits from your plan's balance, following the public beta launch of Agent Hub and Agent Builder on Professional and Enterprise. The Prospecting Agent has billed separately since 14 April 2026, at 100 credits per recommended lead.
100 HubSpot Credits per recommended lead — about $1.00 at HubSpot's published overage rate of $0.010 per credit, invoiced in increments of 10 credits. Credits are consumed when a lead is enrolled for prospecting. Since 30 June 2026 the agent has been available to every paid HubSpot customer, controlled through standard user permissions, and it came with a free 28-day trial.
Set a per-agent monthly run limit, use the test run to see the estimated credit cost of a task before it goes live (testing doesn't consume credits), read the cost previews in the agent inbox and on CRM record cards, and check the account-level monthly credit limit in your credit settings. Do all of that before rollout rather than after the first surprising invoice.
Because agents bill per run, not per correct answer. Two records for one company means two runs, two credit draws, and two outputs someone has to reconcile — you pay twice for one piece of information, then pay a person to merge it.
Revenue leaking through gaps nobody is watching — inbound leads that die between the form and the rep because of routing rules, ownership gaps, duplicates or broken associations. It's silent because nothing errors; the lead simply never gets worked. Metered agents make it louder, because now you're also paying credits to process records that shouldn't exist.
Deduplicate records, repair contact-company-deal associations, write down one shared definition of a qualified lead, reconcile your skill-based routing map with who actually does what, and set run limits plus test-run cost estimates before the first production run.