← Vendor directoryVendor profile

PeoplePath

A capable directory of the previous generation whose enterprise base has been visibly draining toward the category leaders.

Legacy enterprise platformAI tier 1 · Keyword box5.2assessed 2026-10-01

Positioning

A previous-generation enterprise alumni platform with a long North American installed base — the directory-era product many current alumni teams learned the category on. That installed base is real, and so is the documented erosion of it at the demanding end of the market.

The record substrate

Enterprise-managed alumni records with directory and chapter tooling from the prior architecture generation: functional, but limited effective-dated history and verification pipelines compared with the record-centric leaders. Adequate for a list-and-events program; thin as a graph substrate.

AI capability, per the claim ladder

Tier 1. AI features appear in marketing; we can find no pilot-verified query-over-graph delivery, no published eval practice, and the substrate constraints above cap any tier-3 claim. Per the claim ladder, treat the AI language as vocabulary.

Integrations

Legacy connector estate; SSO and HRIS feeds exist in the classic pattern. The change/drift question — whose problem a broken connector is — deserves particular scrutiny on an aging platform.

Pricing analysis

Legacy enterprise licensing, frequently renewed on inertia. The incumbent play is switching-cost defence; per our migration coverage, answer it with a three-year cost-of-staying model, not acceptance.

Compliance posture

Long-standing vendor with baseline enterprise terms; the modern AI-layer questions (embedding deletion, model-training boundaries) may find the machinery unbuilt because the AI layer is largely unbuilt.

Migration assessment

Documented outflow: Oliver Wyman and K&L Gates moved programs off PeoplePath onto EnterpriseAlumni. Partnership announcements positioned as the answer to competitive pressure read, on our viability sheet, as borrowed roadmaps rather than product answers — the intermediate-step pattern buyers should treat as an evaluation deadline.

Viability sheet

Five signals, 0–2 each, per our published scoring framework. The overall score weighs these plus judgment.

Migration inflowNamed documented outflow; no enterprise inflow we can verify.
Roadmap spendOutput skews to maintenance and partnerships; frontier capability absent from shipped releases.
Reference patternDeep legacy base — but reference depth decays as the base erodes.
Structure & hiringPublic signals point to consolidation-side dynamics; watch engineering hiring.
Failure clausesEstablished contract machinery; export terms vary by vintage of agreement.

Best for

  • Incumbent customers with stable list-and-events needs and no AI roadmap appetite — for now

Avoid if

  • You are starting fresh — this is buying the market of five years ago
  • Your incumbent is using migration cost to defend renewal: run the three-year model before accepting

Questions to ask this vendor

  1. Quantify our cost of staying against a three-year model: roadmap, integration drift, and AI capability gaps included.
  2. What shipped to all customers in the last four quarters that is not maintenance?
  3. What exactly does the partnership deliver that your product roadmap does not?