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 standard objects exist with activity on the record — leads, contacts, deals, 'emails & calls' — plus projects and Enterprise-tier pricebooks/quotes, but the evidence is silent on custom fields, dedupe, merge tooling, or field-level permissions. That's the standard model with activity history and no evidenced hygiene layer. 1 2