HabeoFeaturesSaaS

Feature · Licenses · Seats · updated May 19, 2026

Find the seats nobody's using.

Seat reclamation, ELA utilization, and renewal-pipeline planning on the same ledger as your hardware. A faculty laptop, the SaaS seats it consumes, the person who holds it, and the grant that funds it — one graph, one query bar, one set of audit logs. SaaS-bloat killed at the source.

1,408
Apps in a typical R1 tenant
~22%
Seats unused at renewal · industry
90d
Renewal-prep window default
3
Reclamation signals — SSO · MDM · JML
Why SaaS belongs in the asset ledger

Two postures. One of them answers the question.

Standalone SaaS-management tools

Discover SaaS in isolation. Federate with everything else.

Productiv, Torii, BetterCloud, Zylo — each is a federated layer on top of vendor APIs. You still have to join their report to your asset register, your HRIS, your grant ledger to ask the questions you actually care about.

Habeo SaaS, on the institutional ledger

The seat, the person, the laptop, the grant. One graph.

A leaver's Adobe seat is reclamation-candidate the moment the Workday termination fires. An Adobe ETLA renewal pulls the actual utilization from SSO and MDM. The Copilot can answer "every grant-funded laptop with an idle Matlab seat" because none of it is federated.

Three levers

The three SaaS questions every higher-ed CFO asks.

What can we reclaim? Are we using the ELA we bought? What's coming up for renewal — and what does utilization look like?

Seat reclamation.

Three signals into one verdict: SSO last-login (Clerk / WorkOS / your IdP), MDM software inventory, JML events. A seat that hasn't been touched in 60 days and belongs to a terminated worker is one click away from reclaim.

/saas/reclaim

ELA utilization.

Adobe ETLA, Matlab campus, Esri site license, AutoDesk Education Master Suite — ELAs without a real seat count. Habeo tracks contract value, end date, institutional cap, and actual utilization in one place.

/saas/ela

Renewal pipeline.

Every renewal lands on /saas/renewals with a 90-day-out, 60-day-out, 30-day-out cadence. The renewal-prep packet pulls utilization, prior-year spend, and the consortium contract for re-negotiation.

/saas/renewals
What you actually see

The SaaS overview, sortable by spend or utilization.

Renewal pipeline

The renewal, de-surprised.

A renewal date 90 days out fires an automation. By 30 days out you have the utilization, the prior-year spend, the consortium contract, and a draft procurement brief. Nothing is a fire drill in July.

90d

Pull utilization.

SSO last-login, MDM install state, JML reclamation candidates. A snapshot lands in the renewal-prep packet.

60d

Re-negotiation brief.

Auto-drafted procurement brief: utilization band, last-year spend, consortium contract reference, recommended seat count.

30d

Decision window.

Habeo nags. The Copilot pings the responsible buyer in Slack with the renewal packet. Procurement workflow is opened against the cXML PunchOut counter-party.

Renewal

Signed and ledgered.

Contract identifier and end date update; audit trail captures the prior-period spend, new-period spend, and seat-count delta.

For your CFO and your CIO

SaaS spend your procurement chain can defend.

Audit trail on every seat change.

Assignments, revocations, ELA renewals, and reclamation actions are all signed into the same immutable audit log that backs hardware. One audit story.

SSO-driven utilization.

Last-active-at comes from Clerk Enterprise / WorkOS / your campus IdP — the authoritative source. No browser plugins, no agents on user laptops.

FERPA-aware reclamation.

Reclamation actions on student-employee accounts respect FERPA scoping; the Copilot will refuse to surface aggregate seat data that would re-identify students under FERPA.

Contract-aware procurement.

Renewals route to the same cXML PunchOut counter-party that the original purchase used. The audit trail captures the contract identifier, not just the vendor.

Frequently asked

SaaS, answered.

The questions every higher-ed CFO and CIO asks before signing a multi-year contract. Answered briefly, with the technical detail their procurement office will ask for next.

What kinds of software does Habeo track?
Three flavors. SaaS subscriptions (Salesforce, Zoom, Adobe Creative Cloud, Slack, Microsoft 365). Enterprise license agreements (Adobe ETLA, Matlab campus license, AutoDesk Education Master Suite, Esri site license). And per-asset software (locally-installed apps on a faculty laptop). All three live in the same /saas surface and use the same person-license-asset binding model.
How do you detect unused seats?
Three signals. (1) SSO last-login: Habeo pulls last-active-at from Clerk Enterprise / WorkOS / your IdP. (2) MDM-side software inventory: if Jamf or Intune reports a license-bearing app is installed, that's a strong signal of intent. (3) JML events: a leaver's seats automatically become reclamation candidates the moment the Workday termination fires.
What about ELAs without a real seat count?
ELAs are first-class. Track the contract value, the renewal date, the institutional cap, and the actual utilization (from SSO or MDM). The renewal-prep view 60 days out shows the institution your utilization band and any FY budget impact of moving up a tier or staying put.
How does this work with our procurement chain?
Tightly. A new SaaS / ELA is created via PunchOut against E&I, OMNIA, NET+, or any of the six consortium contracts Habeo supports. The contract identifier, end date, and contract type flow into /saas. Renewal alerts open a procurement workflow against the same contract pathway 90 days before expiration.
How is this different from a standalone SaaS-management tool?
Standalone SaaS-management tools (Productiv, Torii, BetterCloud, Zylo) discover SaaS in isolation — finance-and-IT-side, decoupled from the rest of asset management. Habeo is the institutional ledger, so a faculty laptop, the SaaS seats it consumes, the person who holds it, the grant that funds it, and the GASB capital class it sits in are all the same record graph. The Copilot can answer "show every leaver in the last 30 days with active Adobe seats" because it doesn't have to federate between three vendors' APIs.
Do you integrate with Microsoft 365, Google Workspace, Adobe, Zoom?
Direct integrations: Microsoft 365 (Graph), Google Workspace (Admin SDK), Adobe Admin Console, Zoom, Slack, Salesforce, Notion, Figma. For anything not directly integrated, we ingest the vendor's exported usage report on a configurable schedule. Coverage list updates monthly.
Find your seats

Bring your three biggest SaaS contracts.

On the demo call we'll wire your three biggest SaaS contracts to a sandbox Habeo tenant and walk a reclamation report. You'll see seat-count vs. utilization vs. spend in 20 minutes. 30 minutes total, founder-led, no SDR triage.