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 Skeptic
The contact record shows name, company, email and phone up top with action buttons for calls, texts, emails and payments, and an activity feed that pushes overdue invoices, tasks and missed calls to the top; custom fields were raised to 150, though that announcement is dated July 2020 — the freshest word on the data model in these captures. We found no public information on duplicate detection or merging, on custom fields split out across companies and deals, or on field-level permissions. Solid records, unproven hygiene. 3 4 7