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 Solo Seller
Contacts link to companies (via External ID on import) and custom fields on contacts are confirmed, with incoming email landing on the pipeline and group-based record visibility — but the captured help threads describe a three-part import procedure with admin toggles and technical settings, and I found no public information on duplicate detection or merging records. As someone who sets up in an afternoon, that import dance worries me more than the model itself. 1 4 5 6