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
The record model is deep and partly self-policing: custom fields across leads/deals, people, organizations, products and projects, with required fields, formula fields and read-only user specification on higher tiers, and a contact detail view carrying notes, calls, emails, files and a filterable history whose changelog names which user changed what and when. Deleting a custom field is at least documented as deleting its data with it — honest about a destructive act. We found no public information on duplicate detection or merging, which is the hygiene gap I look for first in a database of other people's personal data. 6 7 6