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 Migrator
People and companies are linked in both directions with typed attributes, custom attribute slugs flow through the API, and creating a person auto-generates or matches the company from the email domain — combined with the upsert endpoint's matching attribute, that is the deduplicated entry I insist on. Custom objects exist up to per-plan limits and notes, comments and tasks ride on the records. We found no public information on bulk merge tooling, field-level permissions, or required-field validation, which is what separates this from a top-tier data model. 6 7 2 14