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
Companies and people are separate, linked lists with deals, correspondence, tasks and notes on every profile, and admins can add custom form fields that import maps across persons, companies and deals. Duplicate handling is real — matching by Tax ID or name-plus-contact-details, a duplicate search with dismissable suggestions, and merging up to 10 contacts at once with tasks, deals, wall posts and files carried over — though it requires admin permissions and the Automation plan or higher. We found no public information on custom objects, field-level permissions, or field-level change history. 2 3 11