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, companies and deals are linked through profiles that carry correspondence, tasks and notes, with admin-defined custom form fields and a genuinely documented duplicate workflow — matching by Tax ID for companies, bulk merge of up to ten contacts, and default-contact rules for merged data. Import hygiene is real: four duplicate-handling modes and a full undo of a bad import. I found no public information on custom objects or field-level permissions, which is what would lift this above the midline. 2 3 11