Skip to content

Glossary

Domain terms used across ClientVerse docs. One-to-two-sentence definitions; pointers to canonical docs where the term is fully specified.

Product / domain entities

  • Experience — A ClientVerse-specific entity capturing a person's work history or qualification (e.g., a partner's prior matters at a law firm, expertise areas, judicial clerkships). Not standard Salesforce. Canonical: data-model/ (Experience object).
  • Experience Holder — Junction between Experience and Contact. The same Experience can be linked to multiple Contacts (e.g., a deal where several attorneys worked together). Distinct from Experience.Owner.
  • Matter — Core legal-domain entity representing a single piece of legal work for a client (a litigation, transaction, advisory engagement). Always linked to an Account and one or more Timekeepers.
  • Opportunity — Salesforce-native object, used in ClientVerse for pre-engagement business development (pitches, RFP responses). Naming convention: PITCH-<Client> - <Description>.
  • Account vs Contact — Standard Salesforce: Account = organization (client firm, peer firm, vendor), Contact = person. ClientVerse uses Account Record Types to distinguish Client / Prospect / Peer Firm / Vendor / etc.
  • Connection — ClientVerse-specific entity capturing a relationship between two Contacts (e.g., "Partner A worked with Partner B at Firm X from 2010–2015"). Directional.
  • Relationship — ClientVerse-specific entity capturing an organizational relationship between two Accounts (e.g., parent / subsidiary, joint venture).
  • Classification — Taxonomy entity. Categories like Practice Area, Industry, Geography. Attached to Matters, Opportunities, Experiences via Classification Assignment.
  • Classification Assignment — Junction object linking a Classification to a target record (Matter, Opportunity, etc.). Allows many-to-many.
  • Record Type — Salesforce feature. ClientVerse uses Record Types extensively on Account, Contact, Opportunity to drive page layouts and picklist values per business context.
  • Timekeeper — Legal-billing term for an attorney or paraprofessional whose time can be billed. Modeled as a Contact with a Timekeeper record type (or a related Timekeeper Summary object).

External systems / acronyms

  • PMS (Practice Management System) — Category of external system that is the firm's system-of-record for matters, time, billing. Examples: 3E (Thomson Reuters Elite), Aderant, ProLaw.
  • ERM (Enterprise Relationship Management) — Category of external system for relationship intelligence and signature mining. Examples: Introhive, SigParser. Integrated with ClientVerse to enrich Connections.
  • InterAction — A specific legacy CRM (LexisNexis InterAction) that many law firms are migrating from to ClientVerse.
  • MINT — A specific legacy intake / opportunity management system (Foundation). Has its own migration plan in migrations/.
  • Vuture — Specific marketing automation platform used by some firms; integrated for event registration and email engagement.

Cross-cutting fields

  • Production_ID — Administrative SF ID field present across objects; used for cross-environment record matching during deployment.
  • Legacy_ID — Field present on migrated objects pointing back to the source system's primary key (e.g., the InterAction CONTACT_ID). Critical for re-migration and audit.

Schema variants

  • Client-Facing schema — A simplified projection of the internal schema with fewer columns, exposed to customer admins. Lives in data-model/ as files with "Client_Facing" in the name.
  • Internal schema — The full canonical schema; lives in data-model/ as files with version markers (v2.6, v3.0).

Organization

  • ClientVerse Inc — The product company.
  • Mount Insights — The services firm that implements ClientVerse for customers. Customer-specific delivery work lives in ~/local-projects/mount-insights/cv-delivery/, not in this repo.
  • Customer / client firm — A law firm running ClientVerse. Customer names and customer-specific content do not appear in this repo by convention; that material lives in the per-customer delivery repo.