data-model-and-synclisted

# Data Model and Sync Define what an account is before building anything that counts accounts. This is the first artifact in any engagement and the one most often skipped. ## When to use - Before the first list build - Before connecting any enrichment or agent write access to a system of record - When account-level reporting is incoherent - After an acquisition, a merge, or a CRM migration ## Inputs - Needs from user: CRM object list and custom fields, a sample export of 200 account records, the list of systems that write to the CRM, and the intended segmentation - Reads: `workspace/audit/systems-audit.md` if it exists ## Workflow ### 1. Answer the four definitional questions In writing, with a named decision maker. These are one-way doors and reversing them later means a migration. **What is an account?** The buying entity. Options are legal entity, operating company, division or business unit, or domain. There is no universally right answer, and the right one depends on how you sell. If you sell to divisions independently, the division is the account and the parent is a relationship, not a record. **What is the account key?** The field that makes a record unique. Normalized primary domain is usually the best available answer. Company name is never acceptable as a key. **How do parents and children relate?** Explicit hierarchy field, or flat with a group label. Pick one. Reporting rolls up differently under each and the choice cannot be silently changed later. **Wh