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
Leads carry custom fields (four on Starter, unlimited above), with emails auto-attached to the deal record and calls and meetings logged with outcomes, plus prospects and client folders alongside the lead. We found no public information on duplicate detection or record merging, required fields with validation, or field-level permissions — the hygiene layer a 40-seat forecast depends on. That sits above basic records with fields and notes, short of a validated system of record. 8 2 3 4