For many organizations, user licences are the largest line in the cloud CRM bill, and they tend to creep. People change roles, contractors come and go, a pilot group expands, and nobody removes the seats that are no longer needed. A licence audit is the most direct, lowest-risk way to recover money, and it is also a good reason for IT and finance to sit in the same room.

Set the Scope Before You Pull Reports

Decide what the audit covers. At minimum:

• Named user licences by type and edition
• Add-on products and feature packs
• Sandbox or development environment charges
• Metered items, such as storage or API usage, where applicable
• Connected apps and marketplace subscriptions that bill separately

Pricing structures differ across vendors and change over time, so start by reading your own contract and the vendor’s current documentation for exactly how each item is metered and renewed. Do not assume your agreement works like anyone else’s.

Step One: Build the Licence Inventory

Export a list of every user with their licence type, role, status, last login date and team. Cross-check against the HR or identity system to find accounts belonging to departed staff. This reconciliation often turns up the cheapest wins, such as accounts for people who left long ago that were never deactivated.

Next, list every paid add-on and who uses it. Ask the add-on’s business owner to confirm it is still needed.

Step Two: Classify Usage

Activity-based review works better than login-based review alone, since someone can log in weekly just to glance at a dashboard. Create categories.

• Active creators: users who create or update records regularly.
• Light users: users who mostly view data or run reports.
• Dormant users: users with no meaningful activity for an agreed period.
• Special accounts: integration accounts, shared admin accounts and executives with infrequent but important access.

Choose the dormancy threshold with the business, based on real work rhythms. A seasonal team may legitimately be quiet for months.

Step Three: Match Users to the Right Licence Type

Many platforms offer different user tiers, such as full, limited or read-only types, at different price points. Check the vendor’s current documentation for what each type allows. Where a user only needs to view dashboards or approve records, a lighter option may suffice, if one exists in your plan. Equally, make sure you are not under-licensing, since using features outside your entitlement can create compliance and true-up issues at renewal. The aim is the right licence for each person, not simply the cheapest.

The Audit Table

Finding	Typical Action	Check Before Acting
Account of a departed employee	Deactivate and reassign records	Data ownership and retention rules
Dormant user, no activity	Contact manager, then reclaim	Seasonal or on-call role
Light user on a full licence	Move to a lighter type if available	Features the user truly needs
Unused add-on	Remove at next renewal point	Contract notice period
Duplicate user accounts	Merge or deactivate extras	Audit trail and integrations
Idle sandbox environments	Delete or consolidate	Any tests still depending on them

Step Four: Understand Contract Mechanics

Savings are only real if the contract allows them. Look for:

• Minimum commitments or term-length seat counts that limit mid-term reductions
• Notice periods for changing quantities or cancelling add-ons
• Co-terming, which aligns the end dates of different purchases
• Price protection or caps on renewal increases
• Terms on true-ups, where extra usage is billed later

Some agreements allow reductions only at renewal, which makes timing critical. Put renewal dates and notice deadlines on a shared calendar, with a reminder well before each. Many organizations miss savings by learning about a deadline after it passes.

Step Five: Act With the Business, Not Against It

Before reclaiming licences, notify managers with a clear list and a response deadline. Offer a straightforward way to reinstate a user quickly if someone objects. This turns the audit into a service rather than a raid, and it protects relationships with teams who depend on the tool.

For anything involving personal data in deactivated accounts, follow your retention and offboarding policies, and consult your compliance or legal advisers where requirements are unclear.

A Short Hypothetical

Imagine a company with a few hundred CRM users. An audit finds a handful of accounts for people who left, a group of managers who only open dashboards, and an add-on purchased for a campaign that ended. After checking with owners, the company deactivates the former staff accounts immediately, asks the vendor which lighter licence type suits the dashboard-only managers, and flags the add-on for removal at renewal. None of this requires a conflict with any team, but together the savings recur every renewal cycle. Round numbers here are purely illustrative.

Make It a Routine

A one-off audit decays quickly. Make licence hygiene part of normal operations.

• Tie user provisioning and deprovisioning to HR joiner-mover-leaver events.
• Review usage quarterly, with a larger review before each renewal.
• Require a business justification for new full-licence requests.
• Keep a single owner accountable for the CRM contract.

Keep Quality of Work in View

Savings that damage productivity are false economies. If sales reps lose access during a critical quarter, the cost to the business may dwarf the licence fee. Make changes with warnings, avoid peak periods, and monitor support tickets for access issues after each round.

Frequently Asked Questions

How often should we audit CRM licences? Quarterly light reviews and a thorough review ahead of each renewal is a sensible rhythm for most organizations.

Can we get refunds for unused seats? That depends on your contract. Many agreements do not refund mid-term, so the benefit comes at renewal. Confirm with your vendor in writing.

Who should own the audit? A joint effort works best: IT supplies the usage data, finance understands the contract and cost, and business managers confirm who needs access.

What about shared logins? Shared accounts usually violate vendor terms and weaken your audit trail. Replace them with named users or proper integration accounts.

Should we negotiate based on audit results? Yes. Accurate usage data strengthens your position at renewal and helps you right-size commitments rather than defaulting to last year’s count.

Next Step

Export your user list with last activity dates, compare it with the HR leaver list, and deactivate any accounts that clearly belong to departed staff. That alone is a safe, quick first win.