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 Sales Ops Lead
The merge and duplicate story is unusually solid — a similar-accounts warning at creation, a full merge flow with master selection and field-by-field retention, and the same merge exposed through the API with identical behavior. Field variety is real (text, currency, autonumber, multiselect and more all appear in the export documentation) and custom entities are reachable through the API, but we found no public information on required-field validation, field-level permissions or field-level history. 2 3 5 9 11