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 Data Protection Officer
Typed custom fields sit on leads, deals, contacts, companies and documents, duplicates are matched by phone and email on import and rejected with a duplicate warning through the API, and records carry a timeline, stage history and a 30-day recycle bin that restores with history and files; the contact model even carries a marketing consent field with granted, denied and unknown values plus a do-not-contact flag, which is the consent hygiene a GDPR buyer looks for. We found no public information on custom objects, bulk merge tooling or field-level permissions, so this is a solid, typed core model rather than a fully modelable system of record. 5 8 2 13