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
Contacts, companies and deals are linked, custom fields exist on all three, and the Contact Page puts calls, emails, deals and activity on one timeline; duplicate merging, bulk edit and a merge import that updates thousands of records in one pass are documented, plus one-click enrichment from a third-party partner. We found no public information on required fields with validation, field-level permissions, or custom objects, which is where a 40-seat team enforces hygiene. 6 13 7 10