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
Records build themselves out of the inbox: contact and organization pages aggregate every team pipeline appearance with a full email timeline and auto-enrichment, contacts and companies link automatically or manually, and pipelines take custom columns of several types with importer-side duplicate-row cleanup. We found no public information on field validation, merge tooling, or permissioned field access, so demanding models still need workarounds. 3 4 6 12