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.
In this article
1.
2.
3.
4.
5.
6.
7.
8.
The Quick Version
Four tiers. Two are usable on their own, two require sales conversations and onboarding contracts.
| Tier | What you get | Best for |
|---|---|---|
| Free | Up to two seats, basic ticketing, shared inbox, reporting | Very small teams evaluating Service Hub |
| Starter | More seats, ticket automation, SLAs, simple knowledge base, integrations | Early-stage B2B SaaS teams |
| Professional | Custom reporting, advanced automation, customer portals, survey suite, team management | Scaling teams that need a real helpdesk |
| Enterprise | Hierarchical teams, advanced permissions, SSO, sandbox, dedicated account manager | Established enterprise with compliance needs |
The Free tier is genuinely useful for very small teams and a no-brainer way to evaluate Service Hub, but it runs out of room fast. Starter moves you to paid territory and is where most early-stage B2B SaaS teams land. Professional is where Service Hub starts looking like a real helpdesk, and it adds a mandatory paid onboarding fee that catches a lot of teams off guard. Enterprise is custom-priced, usually annual, often multi-year, and rarely cheap. The actual numbers shift each year as HubSpot adjusts pricing, but 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.
Free
Usable end to end for a one- or two-person team handling a small queue. Lockouts: seats, automation, SLA tracking, knowledge base, and most reporting. Works at two people. Grow to three next quarter and you are upgrading.
Starter
Adds automation, SLAs, a basic knowledge base, ticket routing rules, and standard integrations. Lockouts that matter most: custom reporting, advanced workflow logic, the survey suite, and the customer portal. A team of five to ten reps usually has room here for a year or two.
Professional
Opens custom reporting and advanced workflows. Lockouts are the enterprise-grade features: hierarchical teams, advanced permissions, sandbox, partitioned content. The mandatory onboarding fee is the part most teams underestimate.
Enterprise
The everything tier, with a contract to match. What justifies the price: the permission model, SSO, the sandbox for testing changes safely, and the account manager. For teams under fifty seats, 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. Aggressive list growth often pushes the Service Hub bill up because of a Marketing Hub tier change. Budget for this from day one.
The onboarding fee
Professional and Enterprise 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 still charges their fee. Account for it in year-one budgeting.
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. Plan budget against your hiring plan, not today's headcount.
A few smaller costs add up too. Premium Marketplace integrations 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.
| Team | Tier | Approximate bill | Watch for |
|---|---|---|---|
| Two-person support | Free | Zero, plus your HubSpot CRM tier | Outgrowing it within a quarter once volume picks up |
| Five reps | Starter | Low hundreds/mo for Service Hub, plus Marketing Hub tier | The upgrade to Professional for custom reporting or workflows |
| Fifteen reps | Professional | Low to mid four figures/mo, plus year-one onboarding | Negotiating Enterprise features mid-cycle, which rarely produces a clean contract |
| Fifty seats | Enterprise | Custom-quoted, often five figures/mo, six figures annually with other Hubs | Multi-year lock-in during periods when feature parity may shift |
The numbers above are illustrative, not quotes. HubSpot adjusts pricing regularly, and any quote you receive reflects 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.
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.
A bridge like this is what gets bug reports into engineering with full context and lets customer-facing replies ship the moment a fix lands. The Linear HubSpot integration guide covers the four integration approaches and where each fits. The other commonly-missed dependencies: phone support integrations (Aircall, Talkdesk, others) are extra, some advanced reporting requires the Operations Hub on Professional or higher, and 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.
- 1
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.
- 2
Move to Starter
When you hit the seat cap or the missing automation starts costing real time. Most B2B SaaS teams hit this within three to six months.
- 3
Move to Professional
When custom reporting becomes a real need, the survey suite would change a decision, or workflow logic outgrows Starter. Resist moving sooner; the price jump is meaningful.
- 4
Consider Enterprise only over fifty seats
If you cannot name three specific Enterprise-only features you would use in 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 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 stacks up from several line items.
What goes into the real year-one number
- 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.
Two to three times the headline number is not unusual once every line item is 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 and helps you decide whether Service Hub is the right pick in the first place.
