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
Contacts and companies are linked records with a customizable field set spanning number, currency, file and contact-link types, plus a timeline of notes, meetings, follow-ups and synced emails on each record. Duplicate hygiene is real: red warnings on manual entry, a bulk merge page that detects duplicates by shared email or phone, and merge undo. We found no public information on required fields, field-level permissions or custom objects, which is what I would need before enforcing a data standard across 40 seats. 4 5 1 4