Contact & data model
How this is scored
Depth and hygiene of the core records: contacts, companies and deals linked to each other, custom fields, activity history on the record, import hygiene and deduplication.
0 — Not a CRM data model; the product is an address book or mailing list with no companies or deals.
3 — Contacts, companies and deals linked to each other, with a few custom fields and notes on the record.
5 — Custom fields on contacts, companies and deals, an activity timeline (emails, calls, meetings, notes) on each record, and duplicate detection or merging of records.
8 — Custom objects or relationships beyond the standard model, field types with validation and required fields, bulk merge and deduplication tooling, and field-level permissions.
10 — A modelable system of record: custom objects with their own relations, pipelines and permissions, field-level change history, data-quality tooling (enrichment, bulk cleanup, rules) documented, and the model exposed completely through the API.
The Data Protection Officer
Contacts, deals and projects sit linked in a consolidated 360-degree account view with every interaction synced, and timestamped audit logs track activity across the application. Data hygiene such as phone and email validation is documented through marketplace extensions, and lead enrichment via Clearbit and Leadfeeder imports contact profiles from the open web — a lawful-basis question for any controller loading this database. We found no public information on native duplicate detection, merging or custom-field validation in the captured pages. 5 6 10