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 split into Person and Organization with linking between them, history from person records rolled up onto the organization, custom fields, tags, ownership assignable to a user or a team, merging of contacts, and activity logging on each record. The website contact form documents how to record consent, which is what I want to see, and contact lists, filtering and saved reports are documented. Enrichment exists as a feature but we found no public information on the source of the enrichment data, nor on custom objects, field-level permissions or bulk merge tooling. 6 7 7