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
Contacts, companies, leads and deals are linked, with custom fields in several types across five objects, required fields per stage, and an audit trail plus stage history on each record — that clears the middle bar with room to spare. What holds it down: duplicate handling matches on phone and email at import and the API refuses known duplicates, but we found no public information on record merging or bulk cleanup tooling, custom objects, or field-level permissions. 2 4 5 8