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
Custom objects and custom fields are unlimited on every plan, and the whole data model is exposed through the API: REST and GraphQL endpoints for every object including custom ones, plus a metadata API that creates, modifies and deletes objects, fields and relations. Field- and row-level permissions arrive on the Organization plan, but I found no public information on duplicate merging, field validation or required fields, or field-level change history, which keeps this short of the top level. 11 11 6 2 7