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
Leads, contacts, deals and projects exist with emails and calls rolled onto the record, but the evidence evidences no custom fields, validation, dedupe or merge tooling — anchor-3 territory where duplicates accumulate unchecked. For what is fundamentally a database of other people's personal data, the total absence of consent or purpose-limitation fields is the more worrying silence. 1 2