HubSpot’s CRM is built on a handful of default objects—Contacts, Companies, Deals, and Tickets—plus several supporting or specialized objects. Each record type is stored separately but can be associated with the others to form a complete picture of your relationships, workflows, and data.
1. Contacts
Definition: A Contact record represents an individual person.
Key Attributes:
- Usually identified by an email address.
- Stores personal information such as name, phone number, job title, and any custom properties you create.
- Tracks interactions (emails, calls, form submissions, website activity, LinkedIn messages if logged, etc.).
Use Cases in Consulting:
- Every client stakeholder, lead, referral partner, or personal connection you maintain in HubSpot should be a Contact.
- You can track outreach, calls, and meeting notes at the Contact level.
Associations:
- Contacts can be associated with Companies (for B2B relationships).
- They can also be associated with Deals (opportunities or projects) and Tickets (service/support issues).
2. Companies
Definition: A Company record represents an organization or business.
Key Attributes:
- Typically identified by a domain (e.g., “company.com”).
- Stores address, industry, size, and custom properties relevant to that organization.
Use Cases in Consulting:
- When consulting for B2B clients, you’ll often have multiple stakeholder Contacts at a single client Company.
- Great for capturing company-wide notes, such as a summary of the organization’s challenges or strategy, and for rolling up certain data from the associated Contacts.
Associations:
- A Company can be associated with many Contacts, and multiple Deals or Tickets.
- Helps track the overall relationship with each business you serve.
3. Deals
Definition: A Deal represents a potential revenue opportunity or project in your pipeline.
Key Attributes:
- Typically has a Deal Stage (e.g., “Proposal Sent,” “Closed Won,” “Closed Lost”), an Amount, and a Close Date.
- Organized into Pipelines (e.g., “Sales Pipeline,” “Consulting Pipeline,” or “Nurture Pipeline”).
Use Cases in Consulting:
- Tracking potential engagements or projects.
- Monitoring the progress from lead to signed contract.
- Logging all relevant activities (emails, calls, notes) related to winning that project.
Associations:
- Usually associated with Contacts (the main stakeholders) and optionally a Company if it’s a B2B deal.
- Can also be associated with Tickets, if post-sale support is needed.
4. Tickets
Definition: A Ticket represents a customer service or support request (often used by support teams).
Key Attributes:
- Has a Ticket Status (e.g., “New,” “Open,” “Closed”).
- Organized in a Ticket Pipeline with various stages, similar to a Deal pipeline.
Use Cases in Consulting:
- Handling post-engagement questions, ongoing client support, or internal requests.
- For example, if a client needs follow-up work or has an issue with deliverables.
Associations:
Commonly associated with a Contact (the person who reported the issue) and possibly a Company.
Could also associate with a Deal, especially if service issues arise during or soon after a consulting engagement.
Other HubSpot Objects
Below are additional objects/features you’ll see in HubSpot, which can be useful in certain consulting scenarios but may or may not be core to your setup.
5. Products & Line Items (Sales Hub)
Definition: In HubSpot, Products are items or services you sell. Line Items are specific instances of Products added to a Deal.
Use Cases in Consulting:
- If you have set packages or standard service offerings, you could create them as Products.
- This helps when you want to track revenue by service type or standardize proposals.
- Line Items appear on Quotes for a more detailed breakdown (e.g., “Workshop,” “Training Session,” “Hourly Consulting Blocks”).
6. Quotes
Definition: A Quote is a record that can be generated from a Deal, showing pricing and terms.
Use Cases in Consulting:
- If you provide a formal quote or proposal for your services, you can generate a Quote from the Deal.
- The client can view and even electronically sign it (if you have e-signature functionality).
Associations: Typically tied to a specific Deal, with Contact and Company associations pulled in automatically.
7. Conversations / Inbox
Definition: A shared Inbox that logs email, chat, and form submissions as “Conversations.”
Use Cases in Consulting:
- If you have a shared or generic email address (like “[email protected]”), incoming emails can become Conversations in the HubSpot Inbox.
- Great for small teams that need to track and assign inbound inquiries.
Associations: Each Conversation can be associated with a Contact, Company, Deal, or Ticket.
8. Custom Objects
Definition: A powerful feature (available in certain Enterprise tiers) allowing you to create entirely new record types. Examples: “Consulting Engagement,” “Project Phase,” “Event Registrations,” etc.
Use Cases in Consulting: If your process requires an object not covered by default (for instance, a multi-phase project structure), you can build a Custom Object to manage it in HubSpot.
Associations: Can be associated with Contacts, Companies, Deals, or Tickets just like any other object.
9. Tasks (and Notes, Calls, Meetings)
While not always referred to as objects in the same sense as Contacts/Companies, “Tasks,” “Notes,” “Calls,” and “Meetings” are engagements that live on the timeline of a record. They aren’t full “records” but rather activities:
- Tasks: Reminders for follow-ups or to-do items.
- Notes: Quick text entries about a conversation or detail you want to remember.
- Calls: Logged phone calls with timestamps and outcomes.
- Meetings: Logged or scheduled appointments associated with a Contact or Deal.
Best Practices for Independent Consultants
- Keep it Simple
- For many small consulting practices, you’ll primarily live in Contacts and Deals. Use Companies if you’re B2B with multiple stakeholders at the same company.
- Tickets can be optional if you do a lot of post-project support.
- Use Pipelines
- You can create separate pipelines for your Deals (sales process) and Tickets (support process).
- Customize stage names to match your consulting flow (e.g., “Proposal Sent,” “Contract Signed,” “Engagement Complete”).
- Make the Most of Associations
- Always associate Contacts with the correct Company. For each Deal, make sure you link relevant Contacts.
- This ensures emails, calls, tasks, and notes show up in the correct place, giving you a 360-degree view of every relationship.
- Leverage Products/Line Items (If Relevant)
- If you have recurring, standardized offerings (e.g., “Discovery Session,” “Retainer,” etc.), consider setting them up as Products for consistent quoting and reporting.
- Explore Custom Objects (Enterprise Tier)
- If you find yourself needing to capture a specialized data structure (like “Projects” that have multiple phases and sub-records), a Custom Object can be a game-changer.
Lessons:
PART 1: OVERVIEW OF HUBSPOT
PART 2: INTRODUCTION TO CONTACTS
- Introduction to Contacts
- Who Should be a Contact?
- Understanding HubSpot Property Types
- Most Commonly Used Default Properties for Contacts
- How to Create a Custom Property
- Create a Custom Property for LinkedIn Connect Request Status
- Create a Custom Property for Nickname
- Custom Property for Educational Institutions Attended
- Create a Custom Property for Former Firm
- Create a Custom Property for Industry
- Create a Custom Property for Metro Area
- Create a Custom Property for Continent
- Customizing the Contact Record View
PART 3: EXPORTING AND IMPORTING CONTACTS
PART 4: MANAGING CONTACTS
- Adding Attachments Manually to Contact Records
- Adding a Manual Note to Contact Records
- Using the Call Engagement in HubSpot
- Using the Meeting Engagement Type
- Using Lists (Active vs. Static)
- Creating a Static List
- Creating an Active List
- Understanding the Default Lifecycle Stages
- Recommended Custom Names for Lifecycle Stages
- Understanding Lead Status – Default Options
- Recommendations for Custom Lead Statuses
- Adding an Association Between Two Contacts
- Merging Two Contacts
PART 5: COMPANIES
PART 6: DEALS
- Introduction to the Deal Record Type
- Introduction to the Default Pipeline
- Recommendation for Custom Deal Stages
- Customizing Deal Stages for Projects Through Staffing Firms
- How and Why to Create Multiple Pipelines
- Create a Custom Deal Property: “Source of Deal”
- Customizing the “Closed Lost Reason” Property
- Adding Attachments to the Deal Record
- Importing Previous Deals from a Spreadsheet
PART 7: EMAIL
PART 8: OTHER COMMUNICATIONS
PART 9: TASKS
PART 10: WORKFLOWS
PART 11: REPORTING
PART 12: TICKETS
PART 13: PRODUCTS
PART 14: CONTENT MARKETING
PART 15: INTEGRATIONS