Records / Stages / Privacy / Brief
Pick the right CRM shape
Define what the CRM must remember before picking the app
Start with the job: people, companies, deals, tasks, stages, privacy, and the weekly question the CRM must answer. You leave with a CRM brief Claude can use for the build.
Worth knowing:The tool is not the CRM. The CRM is the operating memory for customer work.
Solo operatorsFreelancersConsultantsSmall sales teams
Start Module 1Sheets / Fields / Views / Stale checks
Build the starter system
Prove the fields and review habit before moving into heavier tools
Build the first contact table, add owner and next-action fields, create a pipeline view, clean messy contacts, add stale-lead checks, and test the system with ten records.
Worth knowing:A small CRM with the right fields beats a full app that nobody updates.
Founders with scattered contactsTeams moving out of notesOwners who need follow-up discipline
Start Module 2Imports / IDs / Lifecycle / Exports
Move into HubSpot or Airtable
Use the online tools when the work needs shared structure
Prepare HubSpot import files, map required fields, prevent duplicates, add companies and deals, use lifecycle stage correctly, export backups, and decide when Airtable is the better fit.
Worth knowing:Most import problems are preventable before the upload begins.
Teams preparing HubSpotAirtable base ownersPeople cleaning old contact lists
Start Module 3Review / Drafts / Automations / Handoff
Run the CRM every week
Turn the CRM into a repeatable operating habit
Run the Friday review, draft follow-ups from verified facts, build one safe Airtable automation, use Airtable MCP for read-safe review, fix stuck deals, hand off ownership, and maintain the system.
Worth knowing:The weekly review is where the CRM proves whether it is worth keeping.
Account ownersSales managersOperators maintaining customer data
Start Module 4