Why Salesforce Optimizer Can't Help You at Renewal — and What Can

TL;DR: Salesforce Optimizer and Org Check show you what your org looks like right now. Renewal negotiations require you to prove what your org looked like for the last six months. Those are different questions, and snapshot tools answer the wrong one. The customer who's been tracking weekly usage for 26 weeks walks into the renewal call with a defensible floor; the customer with last week's screenshot is back in “trust me” territory.

The point-in-time problem

If you've ever run Org Check the week before a renewal call, you know the feeling. You get a clean report. 240 active users. 312 purchased seats. 72 seats “unused.”

You take it to the Salesforce rep. The rep nods. Then they ask: “What about your peak usage over the past six months?”

You don't have that number. Because Optimizer didn't track it. Org Check doesn't track it. Your dashboards reset every quarter. The LoginHistory object retains six months of records and then ages them out — and even those six months are episodic logins, not usage you can chart against purchased capacity.

The rep names a number. Maybe they say 287 was your peak. Maybe they say 295. You can't falsify it because you don't have an audit trail. You end up renewing 300 seats “to be safe” — which is the rep's job, not yours.

What renewal negotiations actually require

Salesforce account executives are trained to anchor renewal conversations to peak usage. That makes sense for them. It works against you if you don't have the counter-data.

The data you need to negotiate confidently looks like this:

• Active user count, sampled weekly, for at least 26 weeks. Twenty-six points is enough to see seasonality (Q4 push, January hiring, summer dips) without being so granular that one bad week skews the picture.
• Min, max, and average across that window. Min is your floor. Max is your ceiling. The gap between max and purchased is your negotiating range.
• The exact dates of the min and max. “Our peak was 287 on March 14, when we onboarded the BD team. Before and after that week, we've been running at 248±5.” That sentence wins arguments.
• Inactive-user evidence with login dates. Not “we think these users are inactive” — “these 47 users have not had an interactive login since September 2025, here's the LoginHistory export.”

None of these come from a snapshot. They come from showing up every week and writing down what you saw.

Why 26 weeks is the magic number

A handful of Mondays of data doesn't do it. Here's how the leverage compounds:

Twenty-six weeks is roughly when the rep stops being able to dismiss your data as “a snapshot” and starts having to engage with it as a record.

Why Optimizer can't solve this

Optimizer (now mostly succeeded by Org Check in Hyperforce orgs) is a great tool — for what it does. It tells you what's configured wrong, what permissions are over-broad, and where your org has technical debt. It's an admin's tool.

It doesn't maintain a historical record because Salesforce doesn't want it to. Salesforce's revenue model benefits from customers being unable to prove their actual usage. That's not malicious — it's structural. The vendor that sells you seats has limited incentive to give you the data that helps you buy fewer seats.

This isn't a conspiracy theory. It's why every category eventually has an independent monitoring tool: AppDynamics for performance, Datadog for infra, Splunk for security. The vendor's telemetry serves the vendor. Customers needed someone keeping a separate ledger.

What about Era, License Guard, and the other AppExchange tools?

Several AppExchange tools address slices of this problem. Era (on AppExchange since July 2025) focuses on identifying users who could be downgraded from Enterprise to Platform licenses based on access patterns — useful, but a narrower slice and priced for enterprise (per-user fee + savings share, typically a fit for 500+ seat estates). License Guard (free) automates inactive-user deactivation. Adoption-tracking apps surface real-time presence. Each runs inside your Salesforce org. When the LoginHistory window expires at 6 months, their historical views expire too — same hard ceiling everyone in-org hits. To get a multi-quarter trend, the data has to live somewhere Salesforce doesn't own.

Coefficient and similar data-pipeline tools can also extract LoginHistory beyond 6 months — they'll give you the raw spreadsheet. The difference is what you do with it. SpendReady packages the extraction as a renewal-anchored CFO artifact: findings with dollar figures, severity-sorted recommendations, weekly trend, audit-complete email. Anyone running Coefficient + a smart admin who likes building dashboards can get partway there. SpendReady is built for the buyer who'd rather not.

What the “separate ledger” looks like for licenses

The mechanic is straightforward: a read-only OAuth integration runs once a week, queries the same objects Optimizer reads (User, LoginHistory, PermissionSetLicenseAssign, UserLicense, AuthSession, OAuthToken), and stores the snapshot externally so it doesn't age out.

Over time, you accumulate:

• A weekly time series of active user count (defined as users with at least one interactive login in the past N days, configurable per org)
• A weekly time series of purchased seats vs assigned seats per license type (Enterprise, Unlimited, Platform, etc.)
• A roster of specific users by name who haven't logged in for 90, 120, 180 days — with the actual last-login date attached
• A roster of Permission Set Licenses assigned to users who never activated the underlying feature
• A trend of integration users and OAuth tokens — service accounts holding interactive licenses, tokens that haven't been used in 60+ days

None of this is hard to capture. Salesforce exposes all of it through standard read-only API access. The trick is just capturing it every week without fail. Snapshots that don't get taken don't exist later when you need them.

The compounding-value frame

This is the part most license-optimization conversations miss. A single audit is a tactical artifact — it identifies a fixed list of cleanup actions, you do them, and the report goes stale within a quarter as users change roles, contracts shift, and new licenses get provisioned.

A weekly snapshot record is a strategic asset. Six months in, you have a defensible negotiating position. Twelve months in, you have a full annual cycle. Two years in, you have year-over-year comparisons that let you separate growth from waste. The asset gets more valuable the longer you hold it, and it can't be reconstructed retroactively from a tool you start using a month before renewal.

This is why we built SpendReady's monitoring tier around scheduled weekly audits rather than on-demand reports. The on-demand report is the table stakes. The 26-week record is the actual product.

What this means if your renewal is more than six months out

If your Salesforce renewal is in November, June, or anytime in the back half of 2026 — start tracking now. Don't wait. The most expensive renewal mistake we see isn't paying too much; it's not having the data to argue.

If your renewal is in the next 90 days, start tracking anyway. Even four weeks of data is better than none — it's also a credibility signal in the negotiation (“we've been tracking weekly since May” reads very differently from “we ran a tool this morning”).

What we ship at SpendReady

Read-only OAuth, no AppExchange install, weekly automated audits for monitoring and enterprise tier customers. Every audit feeds a time-series chart visible in your dashboard. By the time you renew, you have the historical record Salesforce can't supply.

Independent benchmark for the same data that the rep is presenting to you — written down weekly, owned by you, not aging out.