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
Leads stand in for companies with contacts and opportunities attached, custom fields run to twelve types and 250 fields with editing restrictable by role, every call, text and email is logged on the record, and the importer both detects duplicates and merges contacts sharing an email or phone number. Bulk find-and-merge of duplicates arrives through a third-party connection rather than a native tool, and we found no public information on required fields or field-level change history. 4 5 13 11 2