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
The standard objects are there and extensible — leads, contacts/companies, deals and activity history — plus custom CRM entities you can create and automate, which is what I need for a 40-seat model. Stage-level required fields and role-based edit control over forecast-critical fields give me the hygiene levers I look for. What I could not find is bulk deduplication or merge tooling on the records themselves; the only dedupe reference sits inside an integration workflow. 7 8 9 5 6