Contact & data model
How this is scored
Depth and hygiene of the core records: contacts, companies and deals linked to each other, custom fields, activity history on the record, import hygiene and deduplication.
0 — Not a CRM data model; the product is an address book or mailing list with no companies or deals.
3 — Contacts, companies and deals linked to each other, with a few custom fields and notes on the record.
5 — Custom fields on contacts, companies and deals, an activity timeline (emails, calls, meetings, notes) on each record, and duplicate detection or merging of records.
8 — Custom objects or relationships beyond the standard model, field types with validation and required fields, bulk merge and deduplication tooling, and field-level permissions.
10 — A modelable system of record: custom objects with their own relations, pipelines and permissions, field-level change history, data-quality tooling (enrichment, bulk cleanup, rules) documented, and the model exposed completely through the API.
The Sales Ops Lead
Accounts and contacts are properly linked — each account holds one or several contacts, a contact can relate to multiple accounts, and every contact record carries the full interaction history. The open-source core documents custom entities, fields and relationships beyond the standard model, alongside security roles and mass update for editing records in bulk. I found no public information on duplicate detection or merging, field validation with required fields, or field-level permissions — the record hygiene a 40-seat team has to enforce. 6 7 16 9