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
The core model is genuinely linked — leads, contacts, companies, deals and activities as distinct objects — and Smart Process Automation lets you create custom CRM entities on top of it, with role-based control over who edits forecast-driving fields and required fields at stage transitions. We found no public information on bulk merge or deduplication tooling as a native capability, so I stop below the top of the scale. 9 7 5 6