SIM Now Manages SaaS and AI Spend, Per User
AI and SaaS have something in common with the software SAM teams have always managed: both are bought per person, and both are paid for whether or not that person uses them. What is different is where the evidence lives. Access sits in an identity provider, AI usage in a separate console for every vendor, and the cost on an invoice.
Today, Software Inventory Manager (SIM) brings that evidence into LICENSEWARE. SIM now manages SaaS and AI spend, per user. SSO connectors for Microsoft Entra ID, Google Workspace and Okta show which SaaS apps your people have access to. Dedicated API connections to Anthropic Console and Enterprise, OpenAI, ChatGPT Enterprise, Cursor, Google Gemini, Microsoft 365 Copilot and GitHub Copilot bring detailed token analysis and usage per user. SaaS spend analysis puts a cost beside each app. All of it is included in the Core plan, with no separate price.
What is new in SIM
| Connection | Type | What it adds in SIM |
|---|---|---|
| Microsoft Entra ID | SSO connector | The SaaS apps your people have access to |
| Google Workspace | SSO connector | The SaaS apps your people have access to |
| Okta | SSO connector | The SaaS apps your people have access to |
| Anthropic Console | API connection | Detailed token analysis and usage per user |
| Anthropic Enterprise | API connection | Claude Enterprise seats and usage per user |
| OpenAI | API connection | Detailed token analysis and usage per user |
| ChatGPT Enterprise | API connection | ChatGPT seats and usage per user |
| Google Gemini | API connection | Detailed token analysis and usage per user |
| Microsoft 365 Copilot | API connection | Usage per user |
| GitHub Copilot | API connection | Usage per user |
| Cursor | API connection | Seats and usage per user |
SaaS: who has access, and what it costs
SaaS spend management starts with two lists that rarely sit together: who has access to each app, and what the app costs. The SSO connectors read the first from the identity provider you already run, and SaaS spend analysis adds the second. With both in SIM, next to the software installed on your devices, a renewal or a license harvest starts from evidence rather than from the vendor's seat count. More on SaaS management.
AI: tokens and seats, per person
AI arrives as a seat plus a meter, bought through several channels at once. The API connections read Anthropic, OpenAI and Google Gemini for detailed token analysis, and Microsoft 365 Copilot and GitHub Copilot for usage per user, plus Claude Enterprise, ChatGPT Enterprise and Cursor for seats and usage per user. The result is AI spend you can put a name to, which is where every budget conversation starts. More on AI cost management, and on why tokens are priced the way they are in Tokens, Explained for the People Who Pay the AI Bill.
Also in this release
- Adobe Deployment Manager (ADM) reads the Adobe Admin Console. A new API connection pulls additional information from the Admin Console and matches it to the installation and usage data LICENSEWARE collects locally, so the console's view of your Adobe seats and the estate's view meet in one license position.
- Roles for every user. Role-based access control (RBAC) gives each user one of two roles, editor or viewer, so you decide who works on the data and who reads the results.
The release notes are on the releases page, and every source LICENSEWARE reads is on the data sources page.
Getting started
If you are a LICENSEWARE customer, talk to your account team about connecting your identity provider and your AI platforms. If you are not a customer yet, or you would like to see your own SaaS and AI spend per user, book a call with our team.
