You get a practical way to determine which HubSpot seats your team actually needs, and where you can save money without disrupting the workflow. We distinguish between Core Seat, View-Only Seat and front-office seats like Sales Hub Seat and Service Hub Seat.
If a user is only going to read, check reports or follow along, they usually don't need a paid seat.
That's the quick way to save money in HubSpot: Separate people who need to do work in the system from people who just need to see what's going on. It sounds trite. It's also where many people pay too much. It's a bit like buying a company car for everyone who occasionally looks out of the window. Read all about it in the Full guide on HubSpot's new pricing model
Use this model first:
The important thing is that "HubSpot user" does not mean "expensive seat". A general manager reading dashboards doesn't need the same access as a marketing manager building workflows. A salesperson using sequences doesn't need the same seat as an external advisor who only needs to see the pipeline.
If you're already using HubSpot, this should be part of a regular CRM cleanup. It is closely linked to the HubSpot CRM structure, HubSpot onboarding and how you have set up ownership, teams, pipeline and reporting.
Always start with the lowest possible access. Give more access when someone can explain what specific job they can't do without it. "Nice to have" is not a license basis. It's a cost leak with a tie.
In HubSpot, seats are about what access a user has to features in the portal. It's not just a question of logging in. It's a question of what the user can do, change and own.
A Core Seat is for users who need editorial access to HubSpot features that come with their subscription. Typical users are marketing managers, CRM managers, operations people, content producers, campaign managers and administrators.
They often need to do things like:
If the person is actually building, modifying or operating HubSpot, Core Seat is often the right choice. If the person is just going to see the result, it's probably too much.
When people say "front-office seat", they often mean paid seats for the teams that work directly with customers: sales and service. In HubSpot, this typically means Sales Hub Seat or Service Hub Seat, depending on which Hubs you've purchased.
The Sales Hub Seat is suitable for salespeople and sales managers who need specific sales functions. Examples include sequences, playbooks, forecasting, advanced sales reports, meeting tools or other paid Sales Hub features.
Service Hub Seat is suitable for support, customer success and account managers who work with tickets, help desk, SLA, knowledge base, customer portal or service processes.
A person may need both a Core Seat and a Hub-specific seat, depending on their subscription, features and tasks. But don't start there. Start with the task at hand. Ask: "What is this person going to do in HubSpot that they can't do without this seat?" If the answer is unclear, the cost is probably clearer than the need.
| The role | Typical need | Recommended seat |
|---|---|---|
| General manager | View pipeline, reports and activity | View-Only Seat |
| Marketing manager | Build campaigns, lists, emails and workflows | Core Seat |
| Salesperson | Work with deals, sequences, meetings and sales activity | Sales Hub Seat, possibly Core Seat as needed |
| Support employee | Handle tickets, help desk and customer inquiries | Service Hub Seat |
| Finance | Check customers, agreements, reports and invoice basis | View-Only Seat or limited Core Seat with active editing |
| External advisor | See structure, give advice, maybe build layouts | View-Only Seat or Core Seat for a limited period |
This should be linked to rights and team structure, not just invoice. A good seat structure without good permissions is like an access card that opens all doors because "it was easiest". It's rarely easiest when someone deletes the wrong workflow.
If you need help setting this up correctly, it should be considered together with HubSpot implementation and RevOps. Seat selection is not just purchasing. It affects data quality, process, reporting and who can change what.
HubSpot costs often slip because access is granted when the need arises, but rarely removed when the need disappears.
It often happens like this: A new campaign is going out. A salesperson needs access. A manager wants to see reports. A consultant is going to help for two weeks. Everyone gets a little more access than they need because it's quick. Then it gets left behind. Not because anyone is lazy, but because no one owns the license hygiene. Very human. Also quite expensive.
Create a simple overview of all users in HubSpot. For each user, ask four questions:
This doesn't take long, but it requires someone to dare to ask the boring question: "Why are we paying for this?" Boring questions are often the most profitable ones.
Let's say you have 18 users in HubSpot:
It's tempting to give many of these paid seats. But in practice, management and finance can often get by with View-Only. The external partner may have time-limited access. Sales managers may need Sales Hub features if they work actively with forecasting and coaching, but not if they only read dashboards. Marketing and CRM managers often need the Core Seat. Customer success needs the Service Hub Seat if they work in tickets and service tools.
The point is not to cut everything. The point is to pay for work, not for "possibly one day".
If your processes are unclear, your seat choices will be unclear. That's when you buy access to compensate for a poor division of labor. It's more expensive than cleaning up the process.
That's why a seat review should happen alongside CRM work: pipeline, lifecycle stages, lead routing, dashboards, permissions and automation. In particular, look at HubSpot marketing automation if multiple users are building workflows, and sales process and CRM if the sales organization uses HubSpot daily.
Start by downgrading read-only users and keep paid HubSpot seats for people who actually do work in the system.
That's the most practical order:
Use this when someone asks for access:
If the answer is "I'm not sure yet", start low. It's much easier to upgrade the right user than to explain why everyone has had overpriced access for a year.
At least four times:
For help, a quick review of your portal, seats, permissions and processes can often reveal both direct cost savings and improved workflows. Start with HubSpot CRM if the problem is structure, or RevOps if the problem is the interaction between sales, marketing and service.
The right seat is not about being stingy. It's about buying access where it creates value. The rest is just subscriptions with a clear conscience and poor ROI.
Need help choosing? We help Nordic B2B companies with HubSpot setup, license selection and implementation.