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 RevOps Integrator
Contact records tie a person to their organization, deals, quotes, interactions and notes in one view, and import comes with duplicate handling (skip, create a new record, or update the existing one) plus a summary of records imported, merged, skipped and failed. We found no public information on custom field types with validation, merge tooling for duplicates already sitting in the database, or field-level permissioning, which is what separates a workable model from a rich one. 2 3 5