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 Solo Seller
Leads, deals, contacts and companies are linked, and custom fields come in text, number, date, choice and checkbox types across five record types, with import duplicates matched by phone and email — the API even answers a suspected duplicate with a 409 until you override it. Required fields per stage and stage history exist. What I found no public information on is anything beyond the standard objects: no custom objects, and roles decide record visibility rather than field-level permissions. 2 5 8