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 contact record carries name, company, email and phone with an activity feed surfacing calls, texts, tasks and overdue invoices, plus up to 150 custom fields — a real data model, not a mailing list. We found no public information on duplicate detection, merging, custom objects or field-level permissions, which keeps this at mid-scale. Credit where due: the import flow asks how the email addresses were obtained and gates broadcast use on the answer — consent hygiene I rarely see at import. 3 4 12