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, organizations, deals, leads, products and projects are linked, and the contact record carries notes, activities, calls, emails and files with a filterable history and a changelog of who changed what and when. Custom fields span every core object, with required fields, formula fields, pipeline-specific visibility and read-only per-user field access on the higher plans, and those fields are exposed through the API — though we found no public information on custom objects or on deduplication and bulk merge tooling. 1 6 7 15 6