Glossary
Plain-language definitions for the HubSpot, RevOps, SaaS, and AI terms INSIDEA uses with customers every day. Built so founders, RevOps leaders, and marketers can move faster on a shared vocabulary.
9 terms
Hubs, tiers, partner program, and the configurable surface of HubSpot itself.
HubSpot CMS Hub is HubSpot's content management system, designed for marketing teams who want their website, landing pages, blog, and forms living on the same database as the rest of the CRM. Pages can pull live CRM data, personalize for the visitor's lifecycle stage, and convert form submissions directly to Contact records without an integration step.
HubSpot CRM is the contact and account database that sits underneath every HubSpot Hub. It stores Contacts, Companies, Deals, Tickets, and the relationships between them. It is free at the base tier, and every paid Hub (Sales, Marketing, Service, CMS, Operations) extends the same CRM with workflow tools, reporting, and channel-specific features.
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.
A HubSpot Elite Partner is the highest tier in the HubSpot Solutions Partner Program, awarded to agencies that prove the broadest combination of sold MRR, customer retention, and product certification. INSIDEA is one of a small number of Elite partners globally and the world's #1 rated, with a 4.99 / 5 score in the HubSpot Solutions Directory across 1,500+ businesses delivered for.
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 Operations Hub is the part of the HubSpot CRM suite built for RevOps: data sync, programmable automation, data quality tools, and advanced workflow actions. It is the hub that turns HubSpot from an opinionated CRM into a platform you can shape around your business logic, with custom-coded workflow actions, data formatting transforms, and bi-directional sync to systems like Salesforce, NetSuite, and Snowflake.
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 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.
HubSpot Workflows are the automation engine inside HubSpot. A workflow is a trigger plus a sequence of actions: when a contact does X, do Y. Triggers can be form submissions, property changes, list memberships, dates, custom events, or workflow chains. Actions can update properties, send emails, create tasks, change owners, set lifecycle stages, or notify Slack.
7 terms
Lifecycle, lead scoring, pipeline, forecasting, and the operating concepts that run revenue.
An Ideal Customer Profile (ICP) is the written definition of the customer type a company is set up to serve best: industry, company size, geography, tech stack, buying trigger, and value driver. Unlike a buyer persona, which describes individual humans, an ICP describes the account. It is the targeting filter sales and marketing both work against, and it lives as data on the Company record in HubSpot.
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.
A Marketing Qualified Lead (MQL) is a contact whose marketing engagement (form fills, content downloads, email opens, page visits) has crossed a threshold that marketing has agreed represents real intent. MQL is the lifecycle stage that says: this person is more than a name in the database, sales should consider working them.
A Product Qualified Lead (PQL) score is a numerical signal HubSpot or another CRM uses to identify product users who have shown behaviour that historically correlates with conversion to a paid customer. Unlike an MQL score, which weighs marketing engagement, a PQL score weighs in-product actions: feature adoption depth, usage frequency, team activation, and intent signals like pricing page visits while logged in.
RevOps, short for revenue operations, is the function that aligns sales, marketing, and customer success around a single revenue motion. It owns the CRM, the data model, the lifecycle stages, the forecasting cadence, and the systems that connect them. Done well, RevOps is the operating system that lets a leadership team see, predict, and improve revenue without guesswork.
A Sales Qualified Lead (SQL) is a lead that has been vetted by sales and confirmed to meet the criteria worth pursuing as a sales opportunity. Where an MQL is qualified by marketing engagement, an SQL is qualified by an actual sales conversation, discovery, or fit check. SQL is usually the lifecycle stage just before the lead converts to an open opportunity.
Sales Velocity is a composite metric that measures how fast a sales team turns pipeline into revenue. The standard formula is: (number of opportunities × average deal size × win rate) ÷ sales cycle length. The output is revenue per day, and it is one of the few metrics that captures all four levers of a sales motion in a single number.
6 terms
MRR, ARR, churn, LTV, CAC, and the numbers that define a healthy software business.
Annual Recurring Revenue (ARR) is the normalized annualized revenue a subscription business expects from its active contracts. It is calculated by taking MRR × 12 or by summing each subscription's annualized fee. ARR is the headline number SaaS investors and operators track because it represents the durable, predictable revenue base of the business stripped of one-off variability.
Customer Acquisition Cost (CAC) is the total sales and marketing spend required to win a new customer, divided by the number of new customers acquired in the period. It is the cleanest single measure of acquisition efficiency: are you spending more or less than the next dollar of customer revenue is worth.
Churn Rate is the percentage of customers (or revenue) lost over a period, expressed monthly or annually. Logo Churn measures customers lost. Revenue Churn measures ARR lost. Both matter, and they often tell different stories: a business can have low logo churn but high revenue churn if it loses one big customer, or the opposite if it loses many small ones.
Customer Lifetime Value (LTV) is the total gross profit a customer is expected to deliver over the length of the relationship. For subscription businesses, the standard formula is: (average revenue per customer × gross margin) ÷ customer churn rate. LTV is the value side of the LTV-to-CAC ratio, which is the single most-cited measure of subscription business health.
Monthly Recurring Revenue (MRR) is the predictable, normalised revenue a SaaS business expects each month from its subscription customers. It is calculated by summing each active subscription's monthly fee, with annual contracts divided by 12. MRR is the single most important metric in subscription-software finance because it predicts ARR, growth rate, and runway without requiring the volatility of one-off bookings to interpret.
Net Revenue Retention (NRR) measures how much revenue a SaaS business retains from a cohort of customers over a period, including expansion, contraction, and churn. NRR is calculated as: (Starting ARR + Expansion - Contraction - Churn) ÷ Starting ARR. NRR over 100% means the cohort grew without new logos. Public SaaS leaders run 110-130% NRR and it is one of the strongest predictors of long-term value.
3 terms
Nurture, lifecycle marketing, segmentation, and the triggered messaging stack.
A conversion path is the specific sequence of steps a visitor takes from anonymous traffic to identified contact to qualified lead. Classic conversion path: visit a blog post, click a call-to-action, land on a landing page, submit a form, receive a thank-you page, get added to a nurture. The conversion path is the unit of measurement for a marketing program's effectiveness.
A drip campaign is a sequence of pre-scheduled marketing emails sent to a contact over time, triggered by an event (form submission, content download, lifecycle stage change). The emails are paced (one every few days), often educational, and designed to build relationship and qualification signal without overwhelming the recipient. Drip campaigns are the basic unit of email-driven lead nurturing.
Lead nurturing is the practice of building relationship with prospects over time through relevant content and personalized communication so they are ready to engage with sales when they are ready to buy. It covers the long middle of the funnel between the first touch and the qualified sales conversation, and it is usually automated through email workflows, content programs, and behavioral retargeting.
3 terms
Agents, LLMs, RAG, MCP, and the AI vocabulary that now matters inside a CRM.
An AI Agent is an autonomous software workflow powered by a large language model that can take a goal, plan a series of steps, call tools, and act without step-by-step human direction. Inside HubSpot, Breeze Agents are the pre-built version: Prospecting Agent, Content Agent, Customer Agent, Social Agent. Each is scoped to a specific function and operates against the customer's CRM and data.
A Breeze AI Assistant is a customer-configured AI assistant built on HubSpot Breeze that answers natural-language questions against the customer's own CRM and data sources. INSIDEA's Lagan Aviation build is a working example: the Lagan Executive Pipeline AI Assistant turned 3 to 5 hours of board reporting prep into a 30-second query against live HubSpot data.
HubSpot Breeze is HubSpot's umbrella for native AI features built into the CRM. It covers AI assistants for content writing and editing, AI agents that handle specific operational tasks (prospecting, customer success), Breeze Intelligence for data enrichment, and the embedded AI on records (Breeze Record Summaries, suggested next steps). Breeze runs against the customer's CRM data, so the AI has context the team has been building for years.
2 terms
Stripe, Segment, Salesforce, NetSuite, and the systems HubSpot most often connects to.
A HubSpot integration is any tool or system that exchanges data with the HubSpot CRM: native integrations from the HubSpot App Marketplace, custom integrations built against the HubSpot API, or data sync via Operations Hub. The integration layer is what lets HubSpot live inside a real enterprise stack, not as a silo.
A webhook is a way for one system to notify another that an event has happened, by sending an HTTP POST request with the event data to a URL the receiver chose in advance. In HubSpot, webhooks fire from workflows: a deal stage change, a form submission, a property update, anything you can trigger a workflow on can send a webhook. They are the primary way HubSpot pushes data to external systems in real time.
Book a demo and discovery call to get a look at:

Book a Call With Us