Simplified Pipeline Limits
Friday, August 14, 2026
What it is
Pipeline limits in HubSpot are simpler now: your account gets one pipeline limit, shared across all object types, based on your highest subscription tier, instead of a limit that varied by object type, tier, and hub. Every hub now has access to pipelines for every object type, so you no longer need a specific hub subscription just to get deal or ticket pipelines.
Why it matters
Chris's story on today's show is the exact failure mode this fixes: a client moved seats from Service Hub to Revenue Hub mid-project, had already built six ticket pipelines, and the next time he went to configure them, HubSpot said he was over the limit — because with zero Service Hub seats, the account had quietly dropped to the free Service Hub tier, and free tier only allows one ticket pipeline. His read: "how is that not just like a part of the CRM? Like across the board, you have enterprise over here, but I can only use one pipeline on this object." The old model punished a completely normal thing — reorganizing your team's seats — with a pipeline limit nobody remembered existed.
The Take
Chris Carolan
How is that not just like a part of the CRM? Like across the board, you have enterprise over here, but I can only use one pipeline on this object. Like people don't like that.
Just to make sure I'm reading this right: Starter now gets fifteen pipelines total, and you decide how to split them across deal, contact, ticket, or whatever object you're using. That's the part that actually matters. Before this, if I had Sales Pro and Service Starter, I could run multiple sales pipelines but only one ticket pipeline. Now, because the limit is tied to my highest subscription tier and shared across everything, I could build a hundred ticket pipelines if I wanted to, using the same Sales Pro license.
This is HubSpot breaking the object away from the seat that happens to be attached to it, and I think it's the right call — those billing-shaped limits never made sense to a human trying to reorganize a team, and they make even less sense to AI. Ask Breeze for help and it can burn a whole run only to discover it hit a limit that has nothing to do with the actual work. If HubSpot wants AI working across the CRM the way it's clearly building toward, the data model has to stop caring which hub paid for which object.
Watch Us Discuss This
The full segment from the show, us working through this update start to finish.
FAQ
How many pipelines do I get now?
One shared limit across all object types, based on your account's highest subscription tier — for example, Starter gets fifteen pipelines total, split however you want across deals, tickets, contacts, or any other object.
Do I still need a specific hub subscription to get deal or ticket pipelines?
No. Every hub now includes access to pipelines for every object type, regardless of which specific hub subscription attached to that object in the past.
What was the actual problem with the old limits?
Pipeline limits used to vary by object type, tier, and hub, so reorganizing your team's seats (like moving from Service Hub to Revenue Hub) could silently drop you to a lower pipeline limit on an object you'd already built out, with no warning.
Does this affect how AI tools like Breeze work with pipelines?
Indirectly, yes — Chris's take on today's show is that billing-shaped limits didn't make sense to AI either; a whole agent run could hit a wall on a limit that had nothing to do with the actual task.
Produced by Value-First Media