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
Records sit in customizable folders with user-defined fields, a required Name identifier, and a timeline of comments, call logs and linked Gmail threads, while import offers field mapping, duplicate checking on email or name, and pre-import correction of mismatched formats. The enrichment that 'builds comprehensive customer profiles with verified contact details' is offered with no statement of where those details are sourced, which I record as a consent risk rather than a hygiene credit. We found no public information on bulk merging, field-level permissions, or field-level change history, so the documented hygiene reaches everyday working level, not governed-system level. 1 3 4 9 11