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
Contacts split into companies and people, custom form fields set by an admin, and profiles that carry correspondence, tasks, notes and deals — the clean afternoon-setup model I want. Duplicate matching is genuinely smart (tax ID and Regon for companies, name-plus-contact-details for people) and merging carries over deals, files and wall posts, though the duplicate finder sits behind the Automation plan and bulk merges cap at 10 contacts. I found no public information on custom objects or field-level permissions, so I'd stop short of calling it a modelable system of record. 2 3 11