I'm implementing it · 4 min read

What to decide before you configure Sales Hub's 2026 features

The decision to turn on a Sales Hub feature is made, or nearly, and you need the order things go in and what each step actually costs before anyone opens a settings screen.

If you have five minutes

  • Each of these features writes to or reads from a CRM object other teams already rely on — a deal, a contact's job title, a call record, a meeting.
  • The order below follows the operators' own words on the record, not a generic rollout checklist.
1 of 3

Decide before you configure

Each of these features writes to or reads from a CRM object other teams already rely on — a deal, a contact's job title, a call record, a meeting. The order below follows the operators' own words on the record, not a generic rollout checklist.

Each decision, what it costs to skip, and the operator on record for it.
DecisionWhat it costs to skipSource
Define your sales handoff threshold before reviewing suggested scoring pointsYou accept HubSpot's numbers with no anchor, then own the cleanup when a suggestion turns out to be offCasey, Discover and Score High-Impact Events with AI-Powered Insights
Decide which buying signals actually matter to your business before switching on the prospecting agentThe agent automates generic cold outreach at higher volume instead of targeted outreachChris, Prospecting Agent Gets Smarter: Buying Signals and Contact Sourcing
Confirm you hold a Sales Hub Pro or Enterprise seat, not just prospecting-agent credits, before enabling itChris: "this needs a Sales Hub Pro or Enterprise seat, not just credits" — teams "buy agent credits assuming that is the whole cost, then discover they need seats too"Chris, Prospecting Agent Gets Smarter
Audit which job titles actually populate your CRM before trusting an auto-built buying committeeThe Account Map inherits "the least reliable field in the CRM"Chris, Buying Groups
Decide per-team recording defaults (opt-in vs. opt-out) before rolling out Call Recording SettingsGetting it wrong either suppresses adoption (opt-in, unused) or surprises a prospect (opt-out, no warning)Rylee, Call Recording Settings per User and Team
Check whether your calls and meetings run through HubSpot's native Notetaker before promising faster transcriptionEnhanced transcription "doesn't touch you yet" if you record through an integration like Fathom or GongRyan, Enhanced Meeting & Call Transcription for Notetaker
2 of 3

What each beta actually costs you today

  • Recorded Meetings No Longer Create Duplicate Call Records (recorded-meetings-no-duplicate-call-records, public beta) — During the beta, adding meetings to a playlist, deal insights derived from meetings, and asking Breeze Assistant about meeting transcripts are unavailable until rollout completes. If you use call properties in any workflow, or report on calls, plan for the change ahead of it landing — reports built on the old dual-write pattern will read differently once it does.
  • Sequence Task Associations (sequence-task-associations, public beta) — The settings live under Settings, Objects, Activities, not where most admins look first, and the feature inherits whatever activity-association rules are already configured — audit those before enabling it.
  • Sales Templates Public API and Sequences Public API (sales-templates-public-api, sequences-public-api, both public beta) — Released to beta together, and read together they answer one practical question: what an AI connector can now do on your behalf inside a sales sequence. Check your token scopes before building against either.
  • AI Email Editing in Gmail (ai-email-editing-in-gmail, private beta) — Not broadly available yet; the win when it lands is the CRM context riding into the window where the rep already works, not the rewriting itself.
  • Your conversation history searchable in Breeze Assistant (conversation-history-searchable-in-breeze-assistant, in development) — Nothing to configure yet. Worth tracking if your team is stuck asking what a customer said months ago, once it moves toward beta.
3 of 3

The order

  • Set your sales handoff threshold and your buying-signal definitions in a room with sales and marketing, before any scoring or prospecting-agent feature goes live — Rule Insights for Building Scores and Discover and Score High-Impact Events both assume that number already exists.
  • Audit job-title data quality before turning on Buying Groups' automatic account mapping.
  • Confirm your seat tier (Sales Hub Pro or Enterprise) before licensing credits for the prospecting agent — the show flags these as billed separately, and teams keep discovering that after the fact.
  • Decide recording defaults per team before enabling Call Recording Settings, so the call is made once rather than argued call by call.
  • Confirm your notetaker path — native or integration — before promising faster transcription to a team that records through Fathom or Gong.

One honest gap

Nothing above resolves forecasting. The pipeline number and deal-stage math that "anything related to deals and forecasting" points toward has not shipped as its own Sales Hub feature the show has taken a position on. The archive that does exist — deal tags and buying-committee detection on The Value Path, forecast intelligence and deal-stall detection on Value-First Data's Unified Revenue View series — argues for the same discipline named above: define the thresholds and the stages before you configure anything against them. Treat it as the groundwork a forecasting build will need, not as a stand-in for one.

Status and dates from the HubSpot Updates object; implementation notes from the show's own Take pages, quoted verbatim above — Another Orange Morning HubSpot Updates.

Where to next

Where this comes from

  • The HubSpot Updates object on Another Orange Morning. the status and first-covered date on every feature named here
  • The show's own Take pages. the implementation notes, quoted verbatim on this page

What we do not know yet

  • The pipeline number and deal-stage math that "anything related to deals and forecasting" points toward has not shipped as its own Sales Hub feature the show has taken a position on.
  • AI Email Editing in Gmail is in private beta — not broadly available yet; the win when it lands is the CRM context riding into the window where the rep already works, not the rewriting itself.
  • Your conversation history searchable in Breeze Assistant is in development — nothing to configure yet, and worth tracking if your team is stuck asking what a customer said months ago, once it moves toward beta.