← Back to guides
Finance & Procurement5 minUpdated 2026-04-30

How to handle SaaS license rightsizing

Every CFO knows their company is paying for SaaS seats nobody uses, and every CFO knows the audit to find them costs more than it saves at the typical mid-market spend level. The agent flips the math because the audit costs nothing per cycle, which means it can run monthly instead of quarterly.

What the agent reads

SSO sign-in data per app per user (Okta, Workspace, Microsoft 365). Finance ledger for seat counts billed per app. The mismatch is the rightsizing target. Plus the secondary signals: tools where seats are billed but the user has not signed in for sixty days, tools where the licensed tier exceeds the actual usage pattern, and tools where the customer is billed for premium features the team is not using.

What the agent does about it

Drafts the cancel or downgrade email to the vendor's CSM in the procurement lead's voice. Includes the usage data. Cites the renewal date. Suggests the right number of seats. The procurement lead reviews, edits, and ships.

Why monthly beats quarterly

On a quarterly cadence, the next audit lands halfway through the renewal window, which means the renewal cycle compounds three months of unnoticed seat creep before the audit catches it. On a monthly cadence, the audit catches the creep within thirty days. The savings compound across the renewal cycle rather than waiting for the quarterly review.

Frequently asked

Does this require Okta or Workspace?

An SSO source is the cleanest signal. Without one, the agent reads from the per-app admin console where the API supports it. Coverage is broader with SSO.

Keep reading

Try it on your stack.

Start free