01
Tiered dossiers
Founding, private, and standard tiers — each with its own service standard, escalation path, and visibility rules.
All features
Client intelligence
Every detail your principals expect you to remember.
A living dossier for every relationship — tiered, codenamed, and audited on every read. The intelligence that lets a junior coordinator sound like they've known the principal for years.
The cost of forgetting
One misremembered name, one forgotten allergy — and a relationship worth millions is gone. And it lived in someone's head, not your system.
Knowledge walks out the door
The coordinator who knew the principal leaves, and a decade of preference, history, and hard-won discretion leaves with them.
Spreadsheets can't keep a secret
Sensitive identities and financials sit in shared sheets and inboxes — readable by anyone, logged by no one, discreet to none.
The new hire sounds new
A junior fumbles a detail the principal assumes everyone already knows, and the illusion of effortless, familiar service breaks in an instant.
312Active relationships
Audit-on-readEvery record access
Capabilities
What client intelligence gives you.
02
Codenames & redaction
Reference principals by codename and redact sensitive fields per role. Discretion is the default, not a setting.
03
Preferences & allergies
Dietary needs, seat preferences, no-fly vendors — captured once, surfaced everywhere a request is built.
04
Relationship history
Every prior request, complaint, and resolution on one timeline. Context that survives staff turnover.
How it works
Three moves, end to end.
01
Capture
Intake forms and inbound email populate the dossier automatically — no double entry.
02
Surface
The right facts appear inline as a coordinator builds a request, not three clicks away.
03
Protect
Field-level redaction and audit-on-read mean access is always least-privilege and always logged.
Questions
Client intelligence, answered.
Can we hide a principal's identity from junior staff?
Yes — codenames plus role-based field redaction let coordinators work a request without ever seeing the underlying identity.
Is record access logged?
Every read is a signed audit event with actor, timestamp, and the exact fields viewed.
Does context survive staff changes?
The dossier is the system of record — history, preferences, and prior requests stay put when people move on.