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 RevOps Integrator
The model holds together for stack work: companies linked to people, group-scoped custom fields in eight documented types including relationship fields to contacts, users and objects, custom objects and deals, auto-merge for duplicates, and an interaction history synced from email and calendar. The API exposes the whole model — people, companies, deals, custom objects, notes, tasks, interactions — which is what I build against. We found no public information on field validation, required fields, or field-level change history, and permissions are documented at group level only on the top tier. 4 5 13 2 2