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
Companies, people and deals are linked by documented two-way relationships, custom attribute slugs work through the API, and custom objects exist with per-plan caps (three on Free, five on Plus, twelve on Pro, unlimited on the top tier). Duplicate prevention is real but thin: companies auto-match on a person's email domain and the API's upsert merges on a matching attribute, with domains the only unique company attribute and no custom unique constraints allowed, while enriched values cannot be overridden at all. We found no public information on an activity timeline on the record, in-product duplicate merging, or field-level permissions. 6 7 14 2