What Actually Changed in HubSpot's CRM for 2026
Three real product changes shipped inside HubSpot this year, and two Australian rules that now apply to any CRM making decisions on its own.
Most CRM trends pieces for 2026 could have been written in 2023. AI is important, data quality matters, personalisation is good. True, and none of it tells you what to change on Tuesday.
So here is the other version: three things that genuinely changed inside HubSpot this year, two Australian rules that now apply to any CRM making decisions on its own, and what each one asks of you.
Commerce Hub became Revenue Hub, and the scope got wider
HubSpot renamed and expanded Commerce Hub into Revenue Hub in June 2026. If you were already using it, nothing broke. Quotes, invoices, payment links, subscriptions and integrations carried over, with no migration and no cutover date.
Read the rename as a direction. Native payments arrived in 2021, billing and subscriptions in 2023, AI-assisted CPQ in 2025, and in June 2026 contracts plus a connected quote-to-cash flow. HubSpot is building the billing layer of your CRM.
What to do about it: decide on purpose whether quoting and invoicing move into HubSpot or stay in Xero or your ERP, and write down which system holds the number when the two disagree. The detail is in what changed for existing Commerce Hub users.
Is your CRM still mostly a contact list?
Most were set up for one job and quietly given three more.
Agent Hub and Agent Builder launched on 23 July 2026
HubSpot put Agent Hub and Agent Builder into public beta for Professional and Enterprise customers on 23 July 2026. Agent Hub is the evolution of what used to be called Breeze Agents: one console where every agent in your account works from the same customer record, grouped by the outcome it is driving.
The problem it fixes is worth stating plainly, because HubSpot's own example is the one that actually happens. A Prospecting Agent emails a contact the same week a Customer Agent is handling an open complaint from that same account, and neither knows the other exists.
What to do about it: list every agent running in your portal, who turned it on, and what it is allowed to send or change. Most portals with more than one agent have never had that list written down.
Breeze pricing moved to outcomes, and it bills in US dollars
HubSpot's Breeze agents moved to outcome-based pricing in 2026, with a credit pool underneath for the agents that still charge per action. Content Agent, Social Media Agent and Data Agent run on credits per action. A resolved Customer Agent conversation consumes credits equivalent to its per-resolution price.
For an Australian business the sting is the currency. HubSpot publishes agent pricing in US dollars and typically bills Australian accounts in USD unless local currency invoicing has been set up, so your AI line moves with the exchange rate. What the agents cost to run has the numbers in AUD.
What to do about it: give the credit pool an owner with a budget, before finance meets the invoice.
Rule one: there is now an Australian framework to check your CRM's AI against
The National AI Centre published its Guidance for AI Adoption in October 2025, an update to the 2024 Voluntary AI Safety Standard. It runs on six essential practices: decide who is accountable, understand the impacts and plan for them, measure and manage the risk, share the essential information, test and monitor, and keep meaningful human control. There is a foundations version for low risk use and a longer implementation one for the harder cases.
It is voluntary. It is also the document an Australian customer, insurer or tender panel will reach for when they ask how you govern the AI in your CRM. Run your agent list against those six practices and the gaps show up fast, usually on accountability and on monitoring.
Rule two: automated decision transparency, from 10 December 2026
From 10 December 2026, where personal information is used in automated decision making of the relevant kind, your privacy policy has to set out two things: the kinds of personal information used in those decisions, and the kinds of decisions being made that way. The OAIC's APP 1 guidelines are the source, and the regulator is consulting on transparency guidance ahead of commencement.
The obligation says "a computer program", so read it wider than chatbots. If your CRM scores a lead, routes it to a rep, or decides who gets a call and who gets a nurture email, that is a decision made by a computer program using personal information. A scoring model built in 2019 counts. We wrote up the whole obligation in the Privacy Act change due on 10 December 2026.
What to do about it: write down every place your CRM decides something without a person. That one list feeds both the privacy policy update and the governance conversation above.
None of it survives dirty data
Here is the unglamorous part. Every change above assumes the record underneath is right, and an agent inherits whatever confusion your properties already carry. If lifecycle stage means three different things to three teams, the agent will pick one of them and act on it a thousand times before anyone notices.
Which puts the 2026 work in an order most teams do not like:
- Definitions first. One written meaning per lifecycle stage, one owner per property, and a rule about who can create new ones.
- Then the pipeline. Deals without an amount, a close date or an owner break every forecast built on top of them. Here is fixing what you can see inside your CRM.
- Then ownership of the system itself. Somebody has to approve a new property, review the workflows, and say no. See who should actually own the CRM.
- Then the handovers. The gap between a closed deal and a supported customer is where the churn hides, and closing the sales to service gap is usually a workflow and an agreement, not a new tool.
- Then automation, measured. HubSpot's own guide to automating your processes is the map. Judge each one on conversion rate and cycle time, and turn off anything you cannot explain.
Reporting comes last, because a HubSpot dashboard built on unclear definitions is a confident wrong answer delivered weekly.
What this adds up to for 2026
Three product changes, all of them real, dated and already live in your portal. Two Australian rules, one voluntary and one with a commencement date. And the same fundamentals underneath: clear definitions, a pipeline you believe, someone who owns the thing.
One question for your next leadership meeting. Of the agents and automations running in your portal right now, which ones would you be comfortable explaining to the customer they act on?
Reading a trends list and wondering where to start?
Every trend on that list assumes your data is already clean.
If you want a hand with the definitions, the pipeline and the governance, that is our RevOps and HubSpot work. Talk to us.