Contact & data model
How this is scored
Depth and hygiene of the core records — contacts, companies, deals, custom fields, deduplication.
0 — A flat address book; no relations between people, companies and deals.
3 — The standard three objects exist but customization is cosmetic: few field types, no required fields, duplicates accumulate unchecked.
5 — Custom fields across objects, basic dedupe on create, activity history on the record; complex models still need workarounds.
8 — Rich field types with validation, merge and dedupe tooling, relationships beyond the standard model, permissioned field access.
10 — A genuinely modelable system: custom objects or equivalent, bulk hygiene tooling, field-level history — the data model bends to the business, not the reverse.
The Data Protection Officer
Merge and duplicate handling are documented in unusual depth — Advanced Mode field-by-field retention, ownership and delete-rights rules, and API merge endpoints described as working the same as in the application — with custom entity records and a broad field-type set also evidenced. Duplicate detection fires only on an exact name match, and I found no public information on field validation or field-level permissioning. 2 3 9 11