CRM operations anchor — HubSpot, Salesforce, and Attio selection, contacts vs leads object model, platform blueprints, enrichment integration, implementation partners, pipeline design, and data hygiene. Use when choosing a CRM, setting up Attio/HubSpot/Salesforce, resolving Lead vs Contact architecture, or hiring CRM implementation help. Triggers on: "CRM setup", "HubSpot vs Salesforce", "Attio vs HubSpot", "contacts vs leads", "Salesforce leads", "CRM migration", "CRM implementation partner", "CRM blueprint".
CRM operations anchor — HubSpot, Salesforce, and Attio selection, contacts vs leads object model, platform blueprints, enrichment integration, implementation partners, pipeline design, and data hygiene. Use when choosing a CRM, setting up Attio/HubSpot/Salesforce, resolving Lead vs Contact architecture, or hiring CRM implementation help. Triggers on: "CRM setup", "HubSpot vs Salesforce", "Attio vs HubSpot", "contacts vs leads", "Salesforce leads", "CRM migration", "CRM implementation partner", "CRM blueprint".
license
MIT
compatibility
Claude Code, Jesse, Codex, Hermes, Windsurf, OpenCode, Gemini CLI, Copilot, Zed, VS Code, Goose
Most CRM failures are architecture mistakes, not missing features: wrong platform
for stage, Lead/Contact confusion, enrichment synced both ways, or fifteen pipeline
stages nobody inspects. This skill is the for CRM work in gtm-skills —
selection, object model, platform blueprints, partners, and hygiene — with
rollout delegated to , , and .
anchor
hubspot-setup
salesforce-setup
attio-setup
Tool vs process:tools/crm-toolkit = config reference and blueprints.
automation/crm-integration + platform setup skills = operating model and rollout.
Marc Benioff (Salesforce). V2MOM alignment, trust-based enterprise selling,
land-and-expand in CRM, customer success as revenue function — references/benioff-enterprise-playbook.md.
Attio. Flat objects; qualification via attributes and lists as queues.
Step-by-Step Process
Phase 1 — Operating Model (before software)
Load crm-integration if not done. Minimum:
GTM motion defined (inbound, outbound, PLG, hybrid)
5–7 deal stages with Goal + Exit Criteria (pipeline-management)
Owner per stage (SDR vs AE vs CS)
Dedupe key: email (people), domain (companies)
Phase 2 — Platform Selection
Use references/crm-selection.md scorecard.
ARR / team
Default recommendation
<$1M ARR, founder-led
Attio or HubSpot Starter
$1–10M ARR, sales-led
HubSpot Pro
$10M+ ARR, territories
HubSpot Enterprise or Salesforce
Enterprise procurement
Salesforce
Phase 3 — Contacts vs Leads
Mandatory read:references/contacts-vs-leads.md
Platform
Model
Salesforce
Lead object optional but default for SDR + inbound quarantine
HubSpot
Lifecycle stages on Contact — never duplicate "lead" records
Attio
status on People + dynamic lists — no conversion ceremony
