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 and companies are nearly identical records with customizable fields across typed options (number, currency, file, contact link, text area), a history timeline of notes, follow-ups, meetings and emails, and duplicate warnings on manual entry plus bulk merge based on shared email or phone. Company-to-company relationship tracking and custom contact link fields go a bit past the standard model. We found no public information on custom objects, field validation or required fields, or field-level permissions, which caps the model at the middle of the range. 1 4 5 4