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 through the documented Contact to Opportunity to Pipeline to Stage structure, with custom fields in play, notes carrying attachments and pinning on the record, and genuinely strong duplicate handling: primary and secondary match fields, automatic CSV merging on email or phone, and a manual merge feature, backed by granular user permissions and audit logs. I found no public information on custom objects, required fields with validation, or field-level permissions, so this is a well-kept core model rather than a modelable system of record. 4 5 7 9 13 3