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
Leads, contacts and opportunities are linked records with custom fields across all of them — twelve field types up to a 250-field cap, hidden API-only fields and role-restricted editing — and every call, text and email is documented as part of the record. Duplicate detection runs at import and the importer merges contacts sharing an email or phone number, but a native bulk merge tool is not documented, with deduplication handled through the Dedupely integration, and custom objects sit behind the top tier. That is a strong core model that stops short of a fully modelable system of record. 4 5 6 13 1 2