Platform · Licenses

Every seat on a key,
every key on one ring.

Adobe seats, GitHub Enterprise, the Bloomberg terminal, the licences you administer for clients — accounted for, allocated, watched, and ready when the audit arrives at 16:42 on a Friday.

Join the waitlistSee the allocation

Twelve SaaS bills, four reseller portals, three spreadsheets — gathered onto a single ring you can read in a glance.

LicenceCreative CloudEnterprise · ENT-0412 of 20 seats live
EV
JR
HM
PA
TW
—
MC
RB
DK
LO
Auto-renew60d leadCounselpre-clearedAudit47 sources
Allocation, in motion

Each seat belongs to someone.

Not a spreadsheet of counts — a map of currents. Every licence flows to a person, every flow carries a usage tone, and the slack lights up on its own.

Plate IIWorkspace · Northbridge & Co · Apr 2026
Adobe · Creative CloudENT-04
8/12seats live
GitHub · EnterpriseGH-22
9/10seats live
Microsoft 365 · E5MS-E5
7/8seats live
Figma · OrganizationFIG-08
5/6seats live
Bloomberg · TerminalBBG-02
2/3seats live
EV
JR
HM
PA
ASidle 47dreclaim?
TW
MC
RB
DK
LO
NS
OCrenewedseat 12 · re-plan
TG
WK
BS
ZP
Active · used in 14dIdle · 30d quietReclaimable3 reclaimable seats could fund the next two onboardings without a renegotiation.
The renewal horizon

Sixty days of foresight, on every key.

Twelve months on one band. Each renewal arrives with its own quiet sixty-day lead — long enough to renegotiate, never short enough to surprise the partner.

May 2026 → Apr 2027 · scheduled renewals7 renewals · 0 lapses last 18 months
GH-22GitHub · EnterpriseDrafted · in counsel review
BBG-02Bloomberg · TerminalRe-tier proposed · −1 seat
MS-E5Microsoft 365 · E5Auto-renew armed · 90d
FIG-08Figma · OrganizationNegotiation pack ready
ENT-04Adobe · Creative CloudRenews Q3 · seats trimmed −2
BBG-ABloomberg · API addendumAuto-renews unless cancelled
DS-12DocuSign · Business ProDraft due in 12 days
The faint trail behind each pin is the sixty-day lead — the time window during which Clientia drafts the paperwork, pre-clears it with counsel, and pings the partner if anything is worth renegotiating.
When the letter arrives

The audit response
composes itself.

Microsoft Volume Licensing on a Friday at 16:42, the BSA on a Tuesday morning. Whatever the prompt, the answer is already assembled — sources cited, counsel-cleared, seal at the foot.

Northbridge & Co · Counsel of RecordRe: Volume Licensing audit response · Q1 2026
Ref · MS-AUD-2026-Q1
Sealed · 2026-04-22

In response to your inquiry of 2026-04-19, the firm submits the following statement of allocation, retention and seat lineage, compiled from source records held under per-tenant key isolation in the workspace registry.

  1. i.20 perpetual seats deployed across 12 active and 8 reserved holders. Allocation last reconciled 2026-04-14.
  2. ii.Seat #15 reassigned 2026-03-02 from O. Côte to W. Kim with continuous coverage; no seat overlap recorded.
  3. iii.Usage telemetry retained 18 months in EU-Frankfurt, exportable on request, no third-party processors involved.

The firm holds itself accountable to the foregoing and stands ready to produce, on twenty-four hours' notice, the underlying records, hashes and counter-signatures.

For the partnershipR. Northbridge · Managing partner
Composed12 minfrom first prompt to signed PDF
Cited47source records, hash-anchored
Missing0unaccounted seats this period
Questions

Quiet answers to the loud questions.

Which licences can Clientia track?
Two distinct use cases, both from the same workspace. First: licence keys you issue to your own software customers — seat-based activation keys, hardware-bound tokens, and API-validated licences for any product you sell. Second: licences you have purchased or administer on behalf of clients — SaaS subscriptions, perpetual licences with maintenance, API quota tokens, and terminal seats. Both live in one record, tied to the client they belong to.
How does Clientia know whether a seat is being used?
Two paths, depending on the licence type. For keys you issue from Clientia: every activation calls the Validation API endpoint, and Clientia logs the device fingerprint, timestamp, and activation state in real time — billing-linked suspension is instant. For third-party SaaS subscriptions you administer on behalf of clients: native connectors pull last-active and feature-usage signals from major vendors. For vendors without an API, CSV upload or an export endpoint is supported.
What happens at renewal?
Sixty days before the term, Clientia drafts the renewal paperwork using the licence's actual usage posture — which seats are stale, what the negotiated discount surface looks like, and whether the tier could step down. The draft is pre-cleared with counsel; the partner signs.
Can the audit response really compose itself?
Yes — for any licence whose source records (purchase order, allocation log, usage history, retention policy) Clientia holds. The response is composed from those records with hash-anchored citations, reviewed by the partner of record, and counter-signed before it leaves the workspace. We don't fabricate; we assemble.
Where do the licence records live?
Per-tenant, encrypted at rest with envelope keys you can rotate, in your choice of region (EU-Frankfurt or US-Virginia). Vendor credentials are held in HSM-backed isolation. Full posture on the Security page.
What about licences I administer on behalf of a client?
Each administered licence is linked to the client record on the Clients page, and the seat lineage is reflected in both views. Audit responses can be scoped per-client, per-tenant, or per-licence, and exported on the client's letterhead if you've configured one.
For partners & counsel

Bring every key
onto one ring.

We're bringing in a small number of firms to start. Migration from your spreadsheets and reseller portals takes two business days; the first reconciled allocation lands the morning after; an audit prompt could come on a Friday and you'd be home by six.

Join the waitlistBrief our counsel

Switching from HubSpot, Salesforce, Monday, or Zoho? See how we compare.