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 opportunities are linked — with a one-contact-field-to-one-company-field link mechanism that even enforces matching data types and lengths — and custom fields can be created before importing into them. A History tab collects email and SMS results on the record, and import-time duplicate checking across up to three matching fields with merge, overwrite or skip gives basic hygiene. I found no public information on custom objects, bulk merge tooling or field-level permissions, so I cannot take the model beyond solid core records. 1 2 5 9