Experience management¶
Part of: ClientVerse Core (every client).
What it is¶
Experience is the firm's described, reusable record of work it has done — the deals, cases, and engagements cited in pitches, proposals, league-table submissions, and directory rankings. It is the richest object in ClientVerse and the reason much of the rest exists.
The distinction that matters:
| What it is | Where it comes from | Editable here? | |
|---|---|---|---|
Matter (Matter__c) |
The work the firm performed | The practice management system | No — the PMS is the system of record |
Experience (Experience__c) |
The story of that work, written for reuse | Authored in ClientVerse | Yes |
A Matter is what happened. An Experience is what you can say about it. One Matter may yield several Experiences — a single transaction described one way for a private-equity pitch and another for a directory submission.
Who it's for¶
- Attorneys capture what they worked on and maintain their own experience profile.
- BD searches it when assembling a pitch or proposal — "have we done something like this before?"
- Marketing draws on it for directory submissions and league-table entries.
How it works¶
Experience (Experience__c)¶
The narrative record: what the work was, for whom, its value and outcome, and the classifications that make it findable. Because it is authored rather than synced, its quality is a function of the intake process the firm puts around it — see the business-process library.
Experience Holders (Experience_Holder__c)¶
The join between an Experience and the people who did the work, carrying the role each played. This is the mechanism that assembles an individual's experience profile: a lawyer's profile is the set of Experiences they hold, and their role on each is what makes "led the deal" distinguishable from "supported on tax".
Supporting objects: Experience_Narrative__c (alternative narrative variants for different
audiences) and Experience_Party__c (the other parties involved).
Classification is what makes it findable¶
An Experience with no classifications is invisible to the searches that matter. The whole value chain runs Experience → classification → search → pitch, and a break at the classification step makes the rest inert. This is the single highest-leverage thing to get right when rolling out experience management.
How to use it¶
Capture experience
- Open
CV_Experience. - Create an
Experience__cand write the narrative. - Apply classifications — practice area, industry, region, and anything else the firm segments on.
- Add the lawyers involved as Experience Holders, each with their role.
- Link the originating Matter.
Find experience to reuse
- In
CV_Experience, filter by practice area, industry, or classification. - Open candidates and check the narrative and the people involved.
- Pull the strong ones into a pitch or proposal.
See an individual's experience
Open the lawyer's profile and review the Experiences they hold — assembled through Experience Holders, so a lawyer added to an Experience appears there automatically.
Search and configuration¶
Experience search is configuration-driven rather than hardcoded, through
Experience_Search_Object_Config__mdt, Experience_Search_Objects__mdt, and
Experience_Search_Object_Field_Facet__mdt. Which objects are searched and which fields become
facets is therefore an admin decision — see the
Configuration Reference.
Related¶
- Classification — what makes experience findable.
- Pitch / Proposal Builder — where experience gets consumed.
- Contact review — QA coverage for this area (
EXM). - Data Dictionary — field-level reference.