XOPS

The Platform  /  Domains  /  Software

Software Lifecycle.
Request to retirement.

Every request. Every license. Every audit. Coordinated as one continuous lifecycle, from the moment an employee asks for an app to the moment a vendor renewal is signed.

5

Lifecycle phases

5

End-to-end runbooks

Weeks

To first production Outcome

The cost nobody budgets for

The expensive part of SAM isn’t the license.
It’s the people.

Legacy SAM surfaces the same 30,000-row export every month, then relies on analysts, spreadsheet specialists, and outside consultants to make it mean something. That standing human overhead is the real line item, evidence the operation still depends on manual reconciliation. XOPS runs the operation continuously, so staying compliant and right-sized isn’t a headcount.

Legacy SAM

Analysts normalize the export, a council debates it, and reclamation emails get ignored, every month.

+ Consultants

A managed-services retainer keeps the tool useful. And the capability leaves when the contract ends.

XOPS

Evaluates, reconciles, and acts on every license continuously: with evidence, no standing headcount.

From a tool your team operates to a continuously coordinated operation.

The lifecycle, end to end

Five phases.
One coordinated lifecycle.

Every application, every license, every renewal passes through the same five phases. XOPS coordinates each transition, and the events that span them.

1

Request & approval

Catalog routing, security review, manager & budget approval, duplicate-request detection.

2

Procurement & provisioning

License procurement, SCIM/API provisioning, desktop deployment, self-service portal assignment.

3

License & usage

Pool reconciliation, true-up calculation, usage telemetry, patch ring deployment, underutilization detection.

4

Compliance & vendor

Audit evidence, shadow-IT discovery, vendor SLA monitoring, contract renewal, risk assessment.

5

Retirement

Grace-period reclamation, immediate revocation on offboard, automated removal, evidence trail.

Pre-built runbooks

Five runbooks.
Every software transition.

Each runbook coordinates the work across every system involved (HRIS, IDP, SaaS admin consoles, MDM, procurement, vendor portals) and adapts when reality breaks the script. Every transition follows a governed, auditable path. Every action is reversible.

Provisioning

P2

SaaS Application Provisioning

Catalog match, security review, license-pool check, SCIM or API provisioning, role assignment, employee notification, first-use confirmation.

Endpoint deployment

P2

Desktop Software Deployment

Application packaging (MSIX/App-V), Intune/SCCM/Jamf delivery, self-service portal entitlement, install verification, license activation.

Reclaim & rightsize

Continuous

License Harvesting + Reallocation

Inactive-user detection, grace-period reclamation, immediate revocation on offboarding, license return to pool, reassignment to waiting requests.

Patch & compliance

Scheduled rings

Patch Management via Rings

Patch classification, ring assignment (canary → broad), staged deployment, compliance verification, automated rollback on failure.

Discovery & risk

Continuous

Shadow IT Discovery + Remediation

Asset-discovery scan, classification against approved catalog, vendor risk assessment, remediation routing: sanction, replace, or remove.

When systems disagree

The Director left in September.
Her seats kept billing through January.

Workday processed the termination cleanly. Okta deprovisioned within minutes. Nine SaaS admin consoles never got the memo. By Q1 close, finance found 47 active seats billed against an employee who left 90 days ago.

Without coordination

90 days of phantom licenses.

  • Sept 30: Workday processes the termination. Okta deprovisions. The standard offboarding ticket closes.
  • Oct–Dec: Salesforce admin doesn’t see the HR signal. Adobe rotates SSO during a security upgrade. Notion is billed against marketing’s card, invisible to IT.
  • Jan 5: Quarterly finance review. 47 seats across nine SaaS tools still active. $48K already billed. Two-week reclaim project starts.
  • Multiplied across hundreds of departures a year, the reclaim is always behind and the renewal forecast always inflated.

With XOPS

Reclaim before the day ends.

  • 4:12pm Sept 30: Workday termination event fires. The living knowledge graph already maps the Director to every entitlement across the estate.
  • 4:13pm: SCIM-capable apps (Salesforce, Notion, GitHub, Slack, Figma) deprovision automatically. Seats return to the pool.
  • 4:18pm: API-based reclaim fires for Adobe and Asana. Vendor billing locked from next cycle.
  • 4:24pm: The one app without SCIM or API support gets a coordinated ticket to its admin, with full context, not a vague form.
  • Total reclaim time: under 20 minutes. Phantom seats: zero. Procurement renews on real usage, not historical drift.

One departure. Nine SaaS vendors coordinated in real time.
Zero phantom licenses.

Why the graph

Row-based tools record.
A living graph reconciles.

Traditional SAM stores rows. XOPS stores relationships. So one departure automatically reconciles every entitlement, renewal, and audit trail.

A purchase order records line items; a contract defines commercial obligations. XOPS reconciles both against real usage, so commercial terms (renewal floors, bundled entitlements, negotiated exceptions) don’t go invisible between signature and renewal.

Installed Used Entitled Purchased

The Four Truths: held as relationships, not rows, so a change in any one updates the rest. When a renewal arrives, XOPS already knows whether the line item is justified against actual usage.

Real time

License reclaim on offboarding

82%

Auto-provisioning rate (SCIM / API)

~25%

License waste recovered, year one

The new SAM primitive

License management used to be
about seats.

ServiceNow meters Now Assist in assist units. Microsoft meters Copilot in prompts. Salesforce meters Einstein in conversations. Every major SaaS vendor is shipping AI as a consumption line item, a metering primitive that traditional SAM tooling was never designed to track, attribute, or govern.

Consumption units are entitlements too.

XOPS reads consumption telemetry from the same surfaces it reads seat assignments (ServiceNow’s usage logs, Microsoft Graph usage reports, Salesforce platform event logs) and treats them as first-class entitlement state. When the renewal arrives, XOPS already knows whether the consumption-based AI line item is justified against actual usage, not the vendor’s upsell assumption.

What changes in production

Operational impact,
measured where it matters.

Representative outcomes observed across Fortune 500 deployments. Your numbers will vary. And we’ll measure them with you.

Real time

License reclaim on offboarding

82%

Auto-provisioning rate (SCIM / API)

< 1 hr

Request-to-provisioned for new SaaS

~25%

License waste recovered (year one)

100%

Audit-ready evidence posture

Hours

Patch ring deploy (was: weeks)

In production today

Running software lifecycle
across the Fortune 500.

Customer outcome · Cencora

Fortune 15 · Pharmaceutical

From quarterly reclaim to continuous rightsizing.

Cencora’s SaaS estate spans 60+ vendors and 46K employees. Before XOPS, license reclaim ran on quarterly cycles, at best, and lagged the workforce by months. The living knowledge graph now mirrors every entitlement against active employment status in real time. Reclaim happens automatically. Pools rebalance. Renewals price against actual usage, not historical drift.

60+

SaaS vendors continuously reconciled

Real time

Reclaim against workforce changes

Quarterly

True-up surprises, eliminated

“We used to renew on what we were billed. Now we renew on what we use. The vendor conversation is completely different when you walk in with the actual number.”

Director of Software Asset Management · Fortune 100 Financial

1.4M+

Employees under license coordination

$4.8B

Annual SaaS spend reconciled

Weeks

Typical time to first production Outcome

See it coordinate in your estate. In days, not quarters.

Pick one domain. Connect the systems. Run a real Outcome end-to-end before the next steering meeting.