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
Custom fields attach to any object, standard or custom, with unlimited custom objects, fields and records advertised on every tier, custom fields creatable in Settings, and permissions on the Organization plan reaching down to fields and rows. The importer pushes hygiene onto the buyer: files must stay under 10,000 records with no duplicate email addresses, and we found no public information on in-product duplicate detection or bulk merging. Activity history is claimed in one marketing line — 'Emails and meetings log themselves', 'Calls recorded, leads enriched' — with no documented record-level timeline. 6 2 6 5