Draft — in editorial review, not yet published. Content has not been approved by a human reviewer.
Lesson 27 / 50 · Version 2.2.0
HubSpot CRM Fundamentals
- Level
- Beginner
- Duration
- 15 min learn + 15 min apply
- Prerequisites:
- None
Why it matters: A CRM is only valuable if the data is trustworthy. Choosing the right object, associating records, and agreeing on stages keeps reports and follow-ups reliable.
By the end you can:
- Choose between contacts, companies, deals, and tickets
- Use properties and associations
- Define lifecycle stages and pipelines with owners
- Enforce basic data quality
Learn (15 min)
1. CRM objects (5 min)
| Object | Represents | Example |
|---|---|---|
| Contact | A person | Ana Ruiz |
| Company | An organization | Ruiz & Partners LLP |
| Deal | A potential transaction | 12-person headshot day |
| Ticket | A service issue | "Missing retouched files" |
| Choose the object by what the record is, not by which screen is convenient. Properties hold the fields. |
2. Associations and lifecycle (5 min)
Associations link records (contact ↔ company ↔ deal) so context lives in one place. Lifecycle stage describes a person's relationship (subscriber, lead, opportunity, customer...), while a deal pipeline tracks a transaction's stages (New → Quoted → Booked → Delivered). Decide what moves a record between stages and who owns the move.
3. Data quality and ownership (5 min)
Define required fields, duplicate rules (email for contacts, domain for companies), owner assignment, and which system is the source of truth for synced fields. Agree on definitions across teams, or reports will argue with each other.
Apply (15 min)
Worked example (3 min). New inquiry from ana@ruizlaw.com at an existing client company. Plan: search by email (not found) → create contact → associate to Ruiz & Partners (existing company, matched by domain) → create a deal "Team headshots" in the Corporate pipeline → set source = Google Ads, owner = rotation → lifecycle: lead → opportunity when quote is sent.
Lab (7 min): Map the records.
- Take three inquiries (one new person/new company, one new person/existing company, one returning customer).
- For each, list the records to create or update and the associations.
- State the duplicate check used.
- Define one lifecycle transition rule and its owner.
Deliverable: A three-row record-mapping table. You're done when: No inquiry creates a duplicate company or contact.
Check yourself (5 min)
- What does a deal represent?
- Why associate a contact with a company?
- Who defines stage changes?
- Scenario: Reports show two "Ruiz Law" companies. What process failed?
- Why check duplicates at creation?
Reference
Common mistakes
| Symptom | Likely cause | Fix |
|---|---|---|
| Inflated pipeline | Every contact becomes a deal | Create deals only for real opportunities |
| Reporting arguments | Vague stage definitions | Written stage criteria |
| Duplicates | No dedupe rule | Match on email/domain |
Cheat sheet: Choose object → properties → associate → lifecycle/pipeline rules → dedupe + owner.
Key terms: object, property, association, lifecycle stage, pipeline.
Interview prompts: Contact, company, and deal: how do they relate? How do you clean a messy CRM?
Go deeper: HubSpot contacts API guide · Deals API guide · Lifecycle stages · Associate records
Next: Lesson 28 — funnels and workflows in GoHighLevel.