A CRM nobody has to fill in.
Every client, counterparty, expert and insurer lives beside the cases they appear in — and agents keep the record current from the work itself. Open any relationship and see the whole history: exposure, behaviour, last contact, next step.
CRMs fail because people feed them. This one feeds itself.
The relationship record is a by-product of the casework — which means it's actually complete, actually current, and actually trusted.
Clients, counterparties, experts and insurers — every relationship lives beside the cases it appears in, not in a separate system.
Agents keep it current — every email, call note and case event updates the relationship record without anyone typing.
The CRM knows the work. Exposure across matters, history of positions taken, response times — context no standalone CRM has.
Open the card, know the history.
A counterparty insurer, profiled from seven years of matters — the numbers on the left, the living timeline on the right.
What a case-aware CRM can do.
Clients, opponents, experts, insurers — profiled across every case they touch.
Correspondence and case events maintain the record; nobody fills in fields.
How they negotiate, when they settle, how fast they respond — recalled on every new case.
New case intake checks every party against the relationship graph automatically.
Every client touchpoint drafted with the full case picture behind it.
Exposure, activity and history rolled up by client, sector or opponent.
Questions teams ask about the CRM.
Does this replace our CRM?
For case-driven relationships, most teams stop needing one. If you keep Salesforce or similar, the connector keeps both in sync.
Who fills in the records?
Agents do. Emails, call notes, case events and outcomes update the relationship automatically — humans only add what machines can’t know.
What makes it different from a standalone CRM?
It knows the casework. Exposure, positions taken, settlement behaviour and response times are computed from real matters, not typed into fields.
Can we see relationships across offices and teams?
Yes — the graph is workspace-wide with role-based visibility, so conflicts and shared relationships surface wherever they matter.
How is sensitive relationship data protected?
The same governance as everything in Hendl: role-based access, field-level permissions, and every view and export on the audit trail.
Does it work for business development?
Yes — referral sources, dormant clients and growing exposure patterns feed opportunity capture directly.