Contact & data model
How this is scored
Depth and hygiene of the core records — contacts, companies, deals, custom fields, deduplication.
0 — A flat address book; no relations between people, companies and deals.
3 — The standard three objects exist but customization is cosmetic: few field types, no required fields, duplicates accumulate unchecked.
5 — Custom fields across objects, basic dedupe on create, activity history on the record; complex models still need workarounds.
8 — Rich field types with validation, merge and dedupe tooling, relationships beyond the standard model, permissioned field access.
10 — A genuinely modelable system: custom objects or equivalent, bulk hygiene tooling, field-level history — the data model bends to the business, not the reverse.
The Skeptic
Contacts and companies are the evidenced core: Gmail creates both from an email, matches a contact to its company, and stores conversations on the card, backed by a database of European company data. For the things that decide whether records survive scale — custom field types, required fields, dedupe and merge tooling, permissioned field access — we found no public information. I credit the standard objects and their relations, and stop there. 1 3