Hubspot Architecture
The CRM object model
HubSpot is built on four core objects:
Contacts: individual people. Every person you interact with is a contact record. Properties: email, name, job title, lifecycle stage, lead score, and any custom properties you define.
Companies: organizations. Contacts are associated to companies. Properties: industry, size, revenue, domain. HubSpot auto-enriches company records from email domains.
Deals: revenue opportunities. Live in a pipeline with stages you define. Associated to contacts and companies.
Tickets: support requests. If you're using HubSpot Service Hub.
Custom objects (Enterprise tier) let you model any other concept: subscriptions, products, events, locations. Without custom objects, you're shoehorning everything into these four types.
Lifecycle stages
HubSpot's default lifecycle stage model:
Subscriber → Lead → Marketing Qualified Lead (MQL) → Sales Qualified Lead (SQL) → Opportunity → Customer → Evangelist
These map to where a contact is in your revenue process. The transition from MQL to SQL is the handoff from marketing to sales — arguably the most important moment in the funnel.
Define your lifecycle stage criteria clearly before you build anything:
- What makes someone an MQL? (Downloaded 2+ resources AND visited pricing page)
- What makes someone an SQL? (Sales rep reviewed and accepted the lead)
- How does a lead become a customer? (Deal moved to Closed Won)
Sloppy lifecycle stage definitions create the classic marketing-sales conflict: marketing says "we sent 500 MQLs," sales says "those weren't qualified."
Lead scoring
HubSpot's lead scoring combines demographic fit and behavioral engagement:
Fit criteria (who they are):
- Job title contains "Director" or "VP": +15 points
- Company size 51-200: +10 points
- Industry is SaaS: +10 points
- Personal email address (gmail, yahoo): −20 points
Engagement criteria (what they've done):
- Visited pricing page: +20 points
- Opened last 5 emails: +10 points
- Downloaded a case study: +15 points
- No email opens in 90 days: −10 points
Score threshold to become MQL: typically 50–80 points. Set this based on your sales team's feedback on actual lead quality.
Review and recalibrate scores quarterly. Compare MQL conversion rates — if MQLs at score 60 convert at the same rate as score 100, your scoring model is wrong.
Workflows: HubSpot's automation engine
Workflows are HubSpot's trigger-based automation. They run when an enrollment trigger fires, then execute a sequence of actions.
Types of workflows:
- Contact-based: most common. Triggered by contact property changes, form submissions, page views, list membership.
- Deal-based: triggered by deal stage changes. Auto-create tasks, send notifications, update properties.
- Company-based: triggered by company property changes.
Example nurture workflow:
1. Trigger: Contact downloads "GA4 Migration Guide"
2. Action: Set lifecycle stage to Lead
3. Wait: 2 days
4. Condition: Did they visit the pricing page? Yes → send high-intent email. No → send nurture email 1.
5. Wait: 5 days
6. Action: If lead score > 50, notify assigned sales rep
Warning: workflow spaghetti. HubSpot portals that have been running for 2+ years often have hundreds of overlapping workflows with unclear logic. Document every workflow. Pause (don't delete) obsolete ones.
HubSpot as the source of truth
The decision of whether HubSpot or Salesforce is the system of record matters. In HubSpot-only setups, HubSpot is clearly the source of truth. In HubSpot + Salesforce setups, you need to define:
- Which system owns contact records?
- Which field wins on conflict (HubSpot or Salesforce)?
- How are duplicates handled at the sync layer?
HubSpot's native Salesforce sync is solid for standard objects. For complex custom object sync, you need middleware (Zapier, Make.com, or a dedicated rev ops platform like Crossbeam or Revenue Grid).
I build these systems professionally.
Whether it's a RAG pipeline, analytics migration, or AI workflow — let's talk.