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
Contacts carry tags, custom fields and complete history, each linked to its company with a 360 view across emails, tasks, opportunities and meetings, and the hygiene tooling is real: duplicate detection with smart merging plus bulk merge-and-edit. I found no public information on field validation, required fields or permissioned field access, and the automatic enrichment that fills in company, position and LinkedIn draws on sources the pages never name — provenance a data controller must be able to justify. 2 3