The best remedy here is already free.
View-Only access can suit users who need visibility without making changes. Check its feature limits against each workflow and confirm whether the paid subscription can be reduced.
Paid seats doing work a free seat already covers
The typical HubSpot estate accumulates paid seats for people who need visibility rather than capability. They were provisioned at onboarding because a paid seat was the default, the requirement was never re-examined, and the seat renews indefinitely. Validate required access and permitted subscription changes before choosing the remedy.
Provisioning defaults, not decisions
New users get the standard seat because that is the standard. Whether they need selling capability or only visibility is a question that gets asked once, at onboarding, if at all.
Seat types that outlive the role
Roles change while specialised seat assignments can remain. Review the needed capabilities before deciding whether a Core or View-Only seat is appropriate.
Archived users, live seats
Seat release is a separate action from archiving a user, so a departure that was handled correctly in every other respect can still leave a paid seat billing.
Reclassification is easy to execute and easy to get wrong
Moving a user to a free seat is a small administrative action. Deciding which users can move without breaking their work requires knowing what they actually do, not what their job title suggests — and getting it wrong is visible immediately.
- 01
View-Only seats grant reading without editing, so a user who updates even one field occasionally is not a candidate, and the exception is invisible in aggregate activity.
- 02
Dashboard and forecast users author nothing while being entirely active, so authorship alone cannot identify candidates.
- 03
Free seat classes have their own entitlement limits that must be checked against what each candidate genuinely needs.
- 04
Reclassification that removes needed capability generates support load and reverses quickly, which costs more credibility than the saving was worth.
- 05
Changing user access and reducing a purchased subscription have different effects. Verify the contractual renewal date and notice requirements.
- 06
Contract minimums still cap what is recoverable, and they are customer-confirmed rather than inferable from the portal.
What the plan is built from
The optimisation plan starts from the seat analysis and adds the entitlement and contract facts that determine which changes can actually execute.
- 01Classified seat ledger: keep, reclassify to free, or release
- 02Per-user activity pattern: read-only, light-write, or full
- 03Free seat class entitlements against each candidate's genuine requirements
- 04Specialised seat capabilities compared with actual user requirements
- 05Archived and deactivated users still holding seat assignments
- 06Contract minimums and billing period, customer-confirmed
- 07Hub tier and what it already includes at no additional cost
- 08Renewal date alongside the next billing period date
- 09Users whose needs exceed a free seat but fall short of a full one
- 10Seats where implied and actual billing status disagree
- 11Headcount plans that will change seat requirements inside the term
- 12Access-change dates and confirmed subscription-reduction dates
Four steps, from review to negotiation
Release seats held by archived users
Confirm that the user no longer needs access, unassign the seat, and separately schedule any permitted reduction in purchased quantities.
Reclassify read-and-report users to free seats
Pilot the target workflows before reclassification. Any reduction in billed quantities depends on the subscription terms and effective date.
Review specialised seat assignments
Where specialised functionality is unnecessary, assess a Core or View-Only seat against the actual workflow.
Then negotiate what remains
Only once the estate reflects actual requirements is a rate conversation worth having — and by then it is backed by evidence rather than by an opening position.
Sequence the access changes, user checks and contractual reductions separately. Record when each change is permitted and when it will affect an invoice.
- Which users move to free View-Only seats without losing any visibility
- Which departed-user seats to unassign and remove from renewal
- Which specialised seat assignments can change to Core or View-Only
- Which users genuinely need full seats and should be left alone
- Which light users would be better served by a portal than by any seat class
- What is recoverable now versus what waits for the renewal conversation
What you receive
Reclassification plan
Every candidate named, with the activity evidence supporting the move and the entitlement check confirming nothing they use is lost.
Execution sequence
Access changes, acceptance checks and confirmed commercial effective dates, in a sequence your team can review.
The dated number
Potential recoverable value with free seats excluded, unknown prices flagged and each reduction tied to a confirmed contractual date.
Reclassify before you renegotiate
Stage 00 is a 30-minute qualifying call at no cost. If the timing or the estate does not justify an engagement, we say so on that call.