If you are pricing out HubSpot Service Hub for a B2B SaaS support team, you are about to wade through one of the more confusing pricing pages in the SaaS category. The headline tier numbers are simple. The actual bill at the end of the month rarely is, because Service Hub pricing interacts with the broader HubSpot suite in ways the pricing page does not advertise.
This guide breaks the pricing down honestly. What each tier actually costs, what you get, the hidden costs that catch teams by surprise, and how to budget for a working support stack rather than just the line item on the invoice.
In this article
1.
2.
3.
4.
5.
6.
7.
The Quick Version
Four tiers. Two are usable on their own, two require sales conversations and onboarding contracts.
The Free tier gives you up to two seats, basic ticketing, a shared inbox, and reporting. It is genuinely useful for very small teams and a no-brainer way to evaluate Service Hub. It runs out of room fast.
The Starter tier moves you to paid territory. You get more seats, ticket automation, SLAs, a simple knowledge base, and the integrations the Free tier locks out. Most early-stage B2B SaaS teams land here.
The Professional tier is where Service Hub starts looking like a real helpdesk. Custom reporting, advanced automation, customer portals, the survey suite, and team management features. It also adds a mandatory paid onboarding fee that catches a lot of teams off guard.
The Enterprise tier is custom-priced. You get hierarchical teams, advanced permissions, single sign-on, sandbox environments, and a dedicated account manager. The contract is usually annual, often multi-year, and rarely cheap.
The actual numbers shift each year as HubSpot adjusts pricing. The shape of the tier ladder has stayed consistent.
What You Actually Get at Each Tier
The headline features on the pricing page are real. What matters more is what each tier locks you out of.
The Free tier is usable end to end for a one-person or two-person team handling a small ticket queue. The lockouts are seats, automation, SLA tracking, knowledge base, and most of the reporting. If your team is two people, this tier works. If it grows to three people next quarter, you are upgrading.
The Starter tier adds automation, SLAs, the basic knowledge base, ticket routing rules, and the standard integrations. The lockouts that matter most are custom reporting, advanced workflow logic, the survey suite, and the customer portal. A team of five to ten support reps usually has enough room here for a year or two.
The Professional tier opens up the custom reporting and advanced workflows. The lockouts are the enterprise-grade features: hierarchical teams, advanced permissions, sandbox, partitioned content. The mandatory onboarding fee that comes with this tier is the part most teams underestimate.
The Enterprise tier is the everything tier, with a contract to match. The features that justify the price are the permission model, the SSO, the sandbox for testing changes safely, and the account manager who handles the day-to-day questions. For teams under fifty seats, Enterprise is rarely the right call.
The Hidden Costs Nobody Mentions
The pricing page lists three numbers. The actual bill includes three more.
The marketing-contacts tier. HubSpot meters your entire CRM by how many "marketing contacts" you have, even on Service Hub. Cross a threshold (typically 1000, 5000, 10000) and the next tier kicks in across your whole bundle, not just Service Hub. Teams that grow their email list aggressively often see the Service Hub bill climb because of a Marketing Hub-related tier change. Budget for this from day one.
The onboarding fee. Professional and Enterprise tiers come with a mandatory paid onboarding package. It is non-negotiable on standard contracts and runs into four or five figures depending on tier. Some implementation partners offer cheaper alternatives, but HubSpot will still charge their fee. Account for it in year-one budgeting.
The per-seat scaling. Service Hub charges per seat without meaningful volume discounts until Enterprise. A team that doubles from five to ten seats roughly doubles the Service Hub line item. Plan budget against your hiring plan, not against today's headcount.
A few smaller costs add up. Premium integrations through the HubSpot Marketplace sometimes carry their own subscription fees. Some advanced features (custom objects, certain workflow actions) are paywalled behind add-ons. Contact data enrichment and AI features are billed separately on most tiers.
Real-World Pricing Scenarios
The headline numbers do not match the bill most teams pay. A few realistic scenarios, in current-year approximations.
A two-person support team on the Free tier. Bill: zero, plus whatever HubSpot CRM tier you are on. Use case: very early stage. Limit: you outgrow it within a quarter once volume picks up.
A five-rep support team on Starter. Bill: roughly the low hundreds of dollars per month for the Service Hub line, plus whatever Marketing Hub tier you are on. Use case: most B2B SaaS startups for the first year or two. Watch for: the upgrade to Professional once you need custom reporting or advanced workflows.
A fifteen-rep support team on Professional. Bill: low to mid four figures per month for Service Hub, plus the one-time onboarding fee in the first year. Use case: scaling B2B SaaS at the mid-market stage. Watch for: the temptation to add Enterprise features by negotiating mid-cycle, which rarely produces a clean contract.
A fifty-seat Enterprise contract. Bill: custom-quoted, almost always five figures per month, often six figures annually when combined with other Hubs. Use case: established enterprise B2B SaaS with compliance or permission requirements that Starter and Professional cannot meet. Watch for: multi-year contracts that lock in pricing during periods when feature parity with competitors might shift.
The numbers above are illustrative, not quotes. HubSpot adjusts pricing regularly, and any quote you receive will reflect bundle discounts, contract length, and current promotions. The point is the shape of the bill, not the exact dollar amount.
What Service Hub Pricing Does Not Include
The pricing page lists what is in Service Hub. The piece worth understanding before you commit is what is not in Service Hub.
Service Hub is the customer-facing support workflow. Tickets, inbox, SLAs, knowledge base, surveys, and the data that flows from them. Once a ticket needs engineering work, Service Hub does not continue the workflow into your engineering tracker. There is no native Linear integration, no native Jira integration on the standard plans, and the workflow rules that fire on ticket events do not push to engineering systems out of the box.
For teams running engineering in Linear, this is where the budget needs an extra line. A purpose-built sync between HubSpot tickets and Linear issues is a small monthly cost compared to Service Hub itself, but it is genuinely required if you want bug reports to land in engineering with full context and customer-facing replies to ship the moment a fix lands. The Linear HubSpot integration guide covers the four integration approaches and where each fits. The honest read is that this is a real budget item, not an optional add-on, once volume passes a few engineering escalations per week.
The other commonly-missed dependencies. Phone support integrations (Aircall, Talkdesk, others) are extra. Some advanced reporting requires the Operations Hub on Professional or higher. AI features beyond the included Breeze are billed separately on some plans.
Budgeting for Service Hub? Add the engineering handoff line.
If support runs on HubSpot Service Hub and engineering runs on Linear, IssueLinker is the bridge that closes the loop on customer-reported bugs. Predictable monthly cost, no per-seat scaling, and a fifteen-minute setup.
How to Decide Which Tier
The framework most teams settle on after a few months.
Start on Free if your team is one or two people and you want to try Service Hub without committing. Treat it as a working evaluation, not a long-term home.
Move to Starter when you hit the seat cap or when the missing automation starts costing you real time. Most B2B SaaS teams hit this within three to six months of starting on Free.
Move to Professional when custom reporting becomes a real need, the survey suite would change a decision someone makes, or workflow logic outgrows what Starter supports. Resist moving sooner; the price jump is meaningful and the included features only earn their keep if you use them.
Enterprise is rarely the right call for teams under fifty seats. The features that justify the contract value are the enterprise-grade permission models, SSO, sandboxes, and the dedicated support relationship. If you cannot name three specific Enterprise-only features you would use within the first month, the tier is probably overkill.
The mistake to avoid is over-budgeting. The Service Hub feature surface is wide enough that teams talk themselves into Professional or Enterprise on the strength of features they have not actually used. Start at the tier you genuinely need today and upgrade when a missing feature is costing you something concrete. The full setup pattern for a new Service Hub instance is covered in the HubSpot Service Hub onboarding guide.
The Honest Total-Cost Math
If you are budgeting Service Hub for a fifteen-person B2B SaaS company, the realistic year-one total looks something like:
The Service Hub Starter or Professional line itself. The marketing-contacts tier change if your list grows. The mandatory onboarding fee if you go Professional. The engineering-handoff cost if you sync to Linear or another tracker. A small budget for premium integrations and add-ons that turn out to matter.
For most mid-stage B2B SaaS teams, the realistic year-one total is meaningfully higher than the headline Service Hub number on the pricing page. Two to three times higher is not unusual once all the line items are accounted for.
The point is not that Service Hub is overpriced. It is competitive in the category. The point is that the headline number is one piece of a larger budget, and going in with eyes open prevents the awkward conversation in month three when the bill is bigger than what was approved.
The post worth reading next is the support ticket system guide, which compares Service Hub to the alternatives across the three categories (dedicated helpdesk, CRM-bundled, developer-friendly) and helps you decide whether Service Hub is the right pick in the first place.