Definition
Last reviewed June 7, 2026
The CRM model in HubSpot is built around four standard objects: Contact (a person), Company (an organization), Deal (a sales opportunity), and Ticket (a support case). Each object has a default property set and you can add custom properties. Enterprise tiers also unlock custom objects, which let you model things like Subscriptions, Projects, or Vehicles natively.
Associations are how the CRM connects records: a Contact belongs to a Company, a Deal has multiple Contacts, a Ticket sits on a Company. The Labels API lets you describe the nature of each link, so 'primary buyer' versus 'champion' versus 'decision maker' is data, not a note in the bio field.
The most common mistake teams make is treating HubSpot CRM as a contact database. The database is the smallest part. The workflow and reporting layers built on top of the CRM are where the real leverage lives. A well-configured HubSpot CRM enforces the company's data model: which fields are required at each pipeline stage, which lifecycle transitions are automated, and what every Hub reports against.
FAQs
The base HubSpot CRM is free, including Contacts, Companies, Deals, Tickets, basic email, basic chat, and basic reporting. The Hubs (Sales, Marketing, Service, CMS, Operations) are paid add-ons that extend the same CRM with workflows, advanced reporting, and channel-specific features. The free tier is enough to start; teams add Hubs as they scale.
Contact (a person), Company (an organization), Deal (a sales opportunity), and Ticket (a support case). Each has a default property set and customizable properties. Enterprise tiers also unlock custom objects, which let you model business-specific entities like Subscriptions, Projects, or Vehicles natively without forcing them into one of the standard four.
HubSpot CRM is built around an opinionated workflow model with a strong UX, and the marketing, sales, and service tools share the same database. Salesforce is a more customizable platform with a deeper enterprise ecosystem but typically requires more configuration and integration. For most companies under one to two hundred reps, HubSpot delivers more value per implementation hour.
The property model and the lifecycle stage automation. Properties decide what data the team can act on. Lifecycle stages decide who owns the record at every transition. Get those two right and the rest of the build, pipelines, dashboards, workflows, follows naturally. Get them wrong and you spend the next year patching reports.
Related terms
HubSpot Sales Hub is the part of the HubSpot CRM suite built around the sales motion: deal pipelines, contact and company records, meeting links, sequences, quotes, forecasts, and reporting. It runs on the same CRM core as Marketing Hub and Service Hub, so the sales team works against a single record of truth instead of a siloed sales database.
HubSpot Marketing Hub is the part of the HubSpot CRM suite that handles inbound and outbound marketing on the same database the sales team uses: forms, landing pages, blog and SEO, email sending, workflows, campaigns, lists, ads, and attribution. The CRM record is the single source of truth, so a lead's marketing history and sales history live on one timeline.
HubSpot Service Hub is the part of the HubSpot CRM suite designed for post-sale customer experience: ticketing, knowledge base, customer portal, surveys (NPS, CSAT, CES), inbox and chat, and now SLA management. It runs on the same contact and company records as Sales Hub and Marketing Hub, so support sees the full customer history without an integration layer.
A lifecycle stage is a fixed property on a contact or account record that describes where that record is in the relationship with the business: subscriber, lead, MQL, SQL, opportunity, customer, evangelist, or other. Lifecycle stages let RevOps measure conversion at every transition, automate routing, and report a clean funnel without inventing one in a spreadsheet.
HubSpot Custom Properties are user-defined fields you add to Contacts, Companies, Deals, Tickets, or Custom Objects beyond the default property set. They store the business-specific data the standard properties cannot: lead source, ICP segment, contract end date, renewal owner, ARR, integration partner, anything that needs to live on the record and be queryable by lists, workflows, and reports.
Book a demo and discovery call to get a look at:
Book a Call With Us
How INSIDEA works