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
The data model has genuine depth: companies with native firmographic fields linked to people, group-scoped custom fields in eight types including contact, user and object links to deals and custom objects, all reachable through the API. We found no public information on dedupe or merge tooling or field-level history, and removing a person from a group removes the custom field values with it — a hygiene landmine for a shared revenue database. 4 5 13 2