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
Companies, people and deals sit linked with custom fields, correspondence, tasks and notes on each profile — a record I can audit. The hygiene tooling is real: duplicate matching on tax ID, Regon and contact details, merges of up to ten contacts with a default-source rule, and record-level permissions, though the duplicate finder requires the Automation plan and admin rights. We found no public information on custom objects, field validation or field-level permissions that would push this further. 2 3 11