How to Tell Which CRM Users You’re Overpaying For

If your CRM bill climbs every time you hire, you’re almost certainly paying full per-seat prices for people who barely touch the platform. Per-seat pricing is built around the power user — the rep who lives in the CRM all day. Everyone lighter than that is where the overpayment quietly piles up.

The good news: you don’t need to rip out Salesforce or HubSpot to fix it. You just need to know which users are “light,” and what to do with them. Here’s a practical audit you can run this week.

What is a “light” CRM user?

A light user touches the CRM for a narrow slice of work but gets billed the same (or nearly the same) as someone who uses the whole thing. Common examples:

• Field sellers and dealers who check inventory or update an order status a couple of times a day.
• Operations and back-office staff who update records or move a case along, but never build reports or run pipeline.
• Partners and vendors who submit and track requests — external users sitting on internal seats by default.
• Customers who just need to see status or make a request.

In most mid-market organizations, these people outnumber the power users. So the overpayment isn’t a rounding error in the corner of your license count — it’s spread across the majority of it.

The 4-step light-user audit

1. Pull login and feature-usage data

Most CRMs expose last-login dates and, at higher tiers, feature-level usage. Export it. You’re looking for two groups: people who almost never log in (dormant) and people who log in but only ever touch one or two screens (light).

2. Separate “dormant” from “light”

Dormant users — left the company, changed roles, provisioned “just in case” — are the fastest win, because deactivating them changes nothing for anyone active. Light users are trickier: they’re genuinely working, just not using much of what you’re paying for.

3. Map each light user to what they actually do

For each light user or group, write down the handful of tasks they perform. If that list fits on a sticky note, they don’t need a full platform seat — they need a focused tool that does exactly those tasks.

4. Choose the right lever for each group

There are three honest ways to cut the bill, and you’ll usually use more than one:

If the user is…	The right lever	Cost after
Inactive / left the company	Reclaim the seat (audit)	$0 — seat removed
Occasional, still needs native CRM	Right-size to a cheaper tier	Lower per-seat, still per-seat
Light — seller, ops, partner, customer	Move to a flat-fee custom portal	Flat fee, same at any headcount
Power user living in the platform	Keep the full seat	Full seat — and worth it

Why light users are the biggest opportunity

A license audit finds seats you’re not using and reclaims them — useful, but it can’t shrink seats that are being used, just lightly. That second group is where the durable savings sit, because per-seat fees recur and grow with headcount forever, while a purpose-built custom portal costs the same whether 10 light users are on it or 400.

To put rough numbers on it: a full Sales or Service Cloud seat lists around $150–$165/user/month, and even limited-access or login-based tiers still bill per person. (Those are publicly listed ranges, not a quote — confirm your own rates.) Multiply that by dozens of light users and the annual figure gets serious fast.

Cut the bill without switching CRMs

The key point: this isn’t “leave Salesforce.” Your CRM stays the system of record. A custom portal sits alongside it, syncs through its API in real time, and gives light users a clean tool built for their job — on one flat fee instead of a license each. Your power users never notice a thing.

Want to see the whole framework? Read how to cut CRM licensing costs, or plug your own numbers into the savings calculator to see what moving light users off per-seat licenses would save you.

Related reading: 7 ways to cut CRM licensing costs in 2026 and Salesforce Platform license vs. a custom portal.

Frequently asked questions

How do I find light users if I don’t have feature-usage reporting?

Start with login frequency and role. Anyone in a field, ops, partner, or customer-facing role who logs in occasionally is a strong candidate. A short conversation with team leads about what those people actually do in the CRM fills in the rest.

Isn’t moving users to a cheaper license tier enough?

It helps, but cheaper tiers still bill per person and cap what you can build for them. You’re renting a smaller box, not escaping the per-seat model. A flat-fee portal breaks the link between cost and headcount entirely.

Will a portal keep my CRM data accurate?

Yes. It reads and writes the same CRM records in real time, so there’s one source of truth — the portal is a tailored window into the data you already trust, not a second database that drifts out of sync.