One Salesforce Audit. 90 Inactive Licenses Found. Here's What Happened Next.

The company described here is a composite of patterns commonly observed across mid-market Salesforce organizations. The name is fictional.

When the procurement team at Lakewood Industrial was preparing for their annual Salesforce renewal, nobody expected to find a problem.

They had 580 contracted seats. They had been on Salesforce for six years. The platform was central to sales and service operations across four regional offices. The renewal had always been a formality — a number arrived from the vendor, someone approved it, and the process moved on.

This time, someone thought to ask a question before signing.

The Discovery

The IT operations analyst pulled a last-login report — something Salesforce makes available through its standard admin tools. The report showed every active user account alongside the date of their most recent login.

Ninety-three users had zero logins in the past 90 days.

On a 580-seat org with a negotiated Enterprise rate of approximately $130 per seat per month, those 93 inactive licenses represented $12,090 per month. $145,080 per year.

The analyst's first assumption was that the data was wrong. A platform this central to the business, running for six years — 93 people with no activity?

The data was not wrong.

The Breakdown

Over the following two weeks, the team cross-referenced the inactive account list against three sources: the current HR employee roster, the Active Directory, and the active contractor engagement records. What they found broke down into four distinct categories.

41 former employees. Users who had left the company at various points over the previous two years. In every case, their corporate email accounts had been closed and their building access revoked. Salesforce — managed separately by the IT operations team under a different offboarding checklist — had not been updated. Their accounts remained active. Their licenses continued billing.

28 role-change ghosts. Current employees who had transitioned into roles that no longer required Salesforce access. Sales reps promoted into management. Service agents transferred to internal operations functions. Each transition had been managed at the HR and organizational level, but not at the license level. Nobody had flagged the change to IT. Nobody in IT had a process to check.

17 contractor accounts. Temporary staff from four projects, all of which had concluded. The contractors were no longer engaged, but their accounts had never been deprovisioned. There had been no expiry date set at provisioning, and no standard process for closing out contractor access when engagements ended.

7 department migrations. A service team that had moved to a different platform six months earlier. Seven users with active Salesforce licenses who had not logged in since the migration was completed. The team's manager had considered it handled at the workflow level. Nobody had communicated the license cleanup to IT.

The Remediation

Of the 93 flagged accounts, 11 were placed on a protected list — users whose licenses needed to remain active for administrative access, historical data review, or pending system transitions. The remaining 82 were deprovisioned over a three-week remediation period, following verification with each account's former manager or department head.

At renewal, Lakewood negotiated the contracted seat count down from 580 to 500 — supported by documented usage data. The vendor accepted the reduction. The annual savings: $127,920.

What Happened Next

This is the part the success stories usually leave out.

Twelve weeks after the remediation, the same analyst ran the last-login report again as a routine check.

Fourteen new inactive accounts had appeared.

Not because the process had been ignored. Because of the normal motion of the business in the intervening months. Two employees had left. Three had changed roles. A new project had brought in outside contributors, run to completion, and closed — leaving their accounts active. The pattern that had taken two years to accumulate was rebuilding in weeks.

Why a One-Time Audit Is Not a Solution

The insight from Lakewood's experience is consistent with what emerges across organizations that run license audits: the audit successfully identifies what has accumulated, but it does not address the mechanism that caused the accumulation.

That mechanism is structural. Every departure, every role change, every contractor engagement, every tool migration creates a moment at which a license could go idle and stay idle — unless something is watching usage continuously and acting on inactivity automatically.

Without that continuous layer, the audit's results begin deteriorating the day the audit closes. Three months later, the organization runs another audit. Six months after that, another one. Meanwhile, the cost continues accumulating between each cycle.

Gartner's projection that organizations without centralized SaaS license management will overspend by 25 percent through 2028 is not a forecast about what might happen. It is a description of what is currently happening at organizations that rely on periodic reviews to manage a process that is inherently continuous.

The audit is not the solution. The audit is evidence that a solution is needed.

---

The final article in this series looks at what it actually looks like when this problem is solved — not with a better audit process, but with a system built around the continuous nature of the problem.

If this mirrors what you have seen in your own organization, drop a comment. Follow along for the final post.