crm-integrationlisted

# CRM Integration ## Overview Most CRM problems are process problems disguised as software problems. Teams add fields, automations, and sync rules before deciding what the CRM is supposed to be the source of truth for. This skill designs a CRM integration that supports GTM execution without turning into rep admin theater: clear lifecycle stages, field ownership, enrichment sync, dedupe, and stage-gate rules. ## When to Use Use this skill when the user asks to "set up our CRM for sales", "configure HubSpot", "configure Salesforce", "set up Attio", "design deal stages", "integrate enrichment with CRM", "clean up CRM data", "define lifecycle stages", or "build CRM reporting". Use platform-specific skills (`hubspot-setup`, `salesforce-setup`, `attio-setup`) after this skill defines the operating model. ## Authoritative Foundations ### Winning by Design — Bowtie Model CRM design should cover the full bowtie: acquisition, conversion, retention, expansion, and advocacy. Most teams only model pipeline and ignore post-sale stages. ### HubSpot — Lifecycle Stage Model HubSpot's lifecycle model is useful for SMB and mid-market teams because it connects marketing, sales, and CS handoffs with clear stage definitions. ### Salesforce — Opportunity and Object Architecture Salesforce works best when object relationships, required fields, and automation rules are designed before admins start customizing pages. ### Attio — Programmable CRM Model Attio's flexible object model works wel