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 Sales Ops Lead
People, companies and deals are properly linked, custom objects and deals sit in Premium, and there are eight documented field types including selects, contact references and object links, with auto-merge on contacts and an interaction timeline exposed both on the record and through the API. I found no public information on required fields with validation, field-level permissions or field-level change history — permissions are stated at group and workspace level — so the model is real but I cannot run field governance for a 40-seat team on it. 4 5 13 2