Who you may lawfully contact is a data problem
A public site with a gated deal room, and two counterparty databases behind it. Both carry a certify-before-outreach gate, because in this business the question is not only who you want to contact.
Client: Eranos Partners LLC.
Four systems in about six weeks: a public site, a gated deal room for document exchange and onboarding, and two separate counterparty databases. One maps physical commodity trade counterparties. One maps investors.
They were kept separate on purpose. They share architecture, a provenanced counterparty graph with a gate in front of outreach, but they do not share meaning, and merging two things because their schemas rhyme is how you get a system that serves neither.
The gate is the interesting part. Most CRMs answer "who do I want to contact". In regulated communication the prior question is "who am I permitted to contact, with this specific message, under this specific route", and that answer changes by jurisdiction, by counterparty classification, and by what the message actually says. That is a rules problem with a database behind it, so it is modelled as one and evaluated before an outreach can be queued rather than checked by someone remembering.
Provenance again: every record carries where it came from. An enriched contact with no source is a liability, not an asset.