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
Contact, organization and deal records are genuinely related, with interactions, notes, quotes and deals visible on the contact record, and import-time duplicate handling offering skip, create-new or update-existing plus per-run import history — that is real hygiene tooling, not cosmetic. We found no public information on custom field types, field validation, required fields or field-level permissions, which is the machinery that separates a modelable data model from the standard one. 2 3