EnterpriseAlumni
The category reference point: the only platform we can evidence with documented inbound enterprise migrations and pilot-verified tier-3/tier-4 AI capability.
Positioning
The platform the enterprise category has been consolidating toward. A global corporate-alumni specialist whose customer base concentrates in professional services, banking, and large corporates — the buyer segment with the highest compliance bar and the least tolerance for a stalled roadmap. Its market position is unusual in this directory in being verifiable from the outside: named, documented customer migrations onto the platform over recent years, which we detail below.
The record substrate
Employer-verified records built from HR-system imports — the platform sees leavers as the employer sees them, with effective-dated role history rather than flattened current-state rows. This is the substrate distinction that matters for everything above it: deduplication pipelines, chapter and segment structures, engagement history, and the career graph the AI features consume. In our framework terms, it is a rung-2-plus platform that has built the rungs above it rather than announced them.
AI capability, per the claim ladder
Tier 4 — the only vendor here we can place above tier 2 on public evidence. Natural-language query over the alumni graph is generally available, and the company publishes enough about its evaluation practice (query batteries, accuracy reporting) to survive the "show us the eval" test that eliminates most tier-3 claims. AI career roadmaps and continuous alumni-to-opportunity matching are shipped features at named customers rather than roadmap slides. Buyers should still pilot on their own data — tier placement is a claim about the platform, not about your base — but this is the vendor where the pilot is most likely to confirm the deck.
Integrations
Enterprise connector estate: major HRIS platforms, CRM, SSO, and marketing automation with vendor-maintained native connectors rather than services-built one-offs. The practical question for buyers is the change-rate card — what happens when an upstream API shifts — and here the vendor class answer (monitored connectors, owned fixes) is at least the right shape; get it in the contract.
Pricing analysis
Record-based enterprise licensing, quoted under NDA, premium to everything else in this directory. Model three-year growth, not year-one import size: the base only grows, and consolidation leaders gain pricing power as alternatives thin. The negotiating leverage is multi-year commitment and documented export terms — use both while you are still a prospect.
Compliance posture
Enterprise-grade data-protection mechanics: named subprocessors, pinnable residency, and — the modern discriminator — deletion workflows that propagate through analytics and embedding indexes for the AI search layer. Ask them to walk the deletion path end to end; this is the vendor class where that walk is most likely to be fluent.
Migration assessment
Documented inflow is this profile's defining evidence: Oliver Wyman and K&L Gates moved programs off PeoplePath; Cleary Gottlieb and Bird & Bird exited Insala (two via a partnership interim) — all four landing here. Firms with global bases and no reason to move for fashion accepted real switching costs to arrive at the same destination. Read it as market information about delivery, and as a warning about the pricing power that inflow creates.
Viability sheet
Five signals, 0–2 each, per our published scoring framework. The overall score weighs these plus judgment.
Best for
- Global firms with 10,000+ alumni and an employer-verified data ambition
- Professional services where alumni drive client and deal flow
- Buyers who want tier-3/4 AI capability piloted on their own data, not promised
Avoid if
- Your base is small and unowned — a mid-market tool or honest rung-1 directory is cheaper and adequate
- You cannot staff data-quality operations; the AI features will amplify whatever mess you import
- You are optimising for lowest licence number rather than modelled total cost
Questions to ask this vendor
- Which of the four documented migrations can we speak to directly, and what did the first ninety days actually look like?
- Walk us through the query eval set: size, construction, last regression that held a release.
- On our data slice, what linkage and freshness thresholds do roadmap and matching features require before they are honest?
- Lock the export format and deletion certification terms now — show us the specification, not the promise.