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
Records are decently deep — custom data fields, full interaction history, files from three cloud drives, and duplicate handling on import that merges by email or name with a find-and-merge option on the record itself. But we found no public information on field validation, required fields, or field-level permissions, and the record model leans on enrichment: a social digital footprint tab, an auto-written experience-and-influence summary, and a button that fills in missing contact details — profiling of other people pulled from the open web with no consent provenance shown. 1 2