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
Contacts, opportunities and companies are linked in a Contact → Opportunity → Pipeline → Stage model with notes, attachments and pinning on the records, and duplicate handling is genuinely configurable — primary and secondary match fields, automatic merge on CSV import by email or phone, messenger auto-merge and a manual merge feature. Custom fields are documented on contacts and companies and granular user permissions with audit logs appear on the security page, but we found no public information on custom objects, field validation or field-level permissions. 4 5 7 13 3