What HubSpot's new sales agents read before they act

Every sales leader we talked to at UNBOUND asked the same question in different words: will the Fall 2026 agents HubSpot announced on stage work on my pipeline as it is? The answer for most portals is no, and the reason is boring. Deal Progression reads emails and calls. Prospecting Agent scores against an ICP. Revenue Agent chases invoices. If the emails aren't logged, the ICP isn't written down, and the invoices live in QuickBooks, the agents have nothing to read.

This is for the sales leader or RevOps owner who already runs Sales Hub. HubSpot's survey found its top performers run five AI use cases to win deals, five of 18, and that prioritizing pipeline was one of the three highest-impact use cases across all 50. We used the same five. The argument for why context is the Kernel lives in Growth Context is your Kernel; this is the part you can run this month.

One number to hold onto. RevenueWell sells patient engagement software to more than 11,000 dental practices, and HubSpot's published case study puts its meeting booking rate at 22% with sequences and 40% with Prospecting Agent. On the UNBOUND panel, Kim Cormier, its chief sales and marketing officer, put the year-over-year jump at 11% to 43%. Not with more SDRs. With intent signals, a custom engagement score her team built from meaningful interactions, and Prospecting Agent writing the outreach. Her caveat was as useful as the result: early on they targeted the wrong companies and found stale content in their own knowledge base, and SDRs reviewed every email the agent wrote until it earned the reins. Low impact is low context, and she fixed the context first.

Five use cases, and what each one reads first

1. Prioritize pipeline

Kernel and Agents layers. L3. Prerequisite: amounts, stages, and close dates current on every open deal; activity logged.

Ask Breeze Assistant for your open deals ranked by value and stage, and it builds the table. Ask again and it turns the table into the artifact your manager wants for the Monday one-on-one, formatted her way. Deal Progression adds the next action per deal. The rep in the keynote demo did the whole sequence in a few prompts, and the point wasn't the report. It was the hour she didn't spend exporting and reformatting.

The ranking is only as honest as the fields. A deal with a placeholder amount and a close date from March ranks wherever the placeholder puts it. Sales Process Optimization is where we write exit criteria for each stage, so a stage means something an agent can check.

2. Prospecting Agent, fed by signals

Agents layer. L3. Prerequisite: ICP in Context Home; a target account list; one scoring property; brand voice.

Prospecting Agent watches target accounts for buying signals, scores them against your ICP, sources contacts, and drafts the outreach. This release widens the signals it can read: Bombora company surge, UserGems job changes, an expanded Buyer Intent set, and custom signals you define from your own data.

RevenueWell's result came from the custom signal. Her team scored prospects on interactions that mattered to them, plugged the score into Prospecting Agent, and let the agent decide who got outreach and when. That score is process-as-code, and RevOps builds it. Keep a human on every send until the agent's drafts stop needing edits. Her team loosened the reins in weeks, and never all the way.

3. Deal Progression and Notetaker

Agents layer. L3. Prerequisite: email and calendar connected for every rep; recording consent; stages with exit criteria.

This is the self-updating CRM as a rep experiences it. Notetaker captures the meeting. The mobile version takes dictation in the car afterward. Deal Progression, in public beta as of this writing, reads the meeting, the emails, and the calls, then suggests next actions and CRM updates the rep approves with a click. When a buyer mentions a competitor in an email, Deal Progression flags it the same day.

Every rep we've met hates updating the CRM, and every RevOps leader knows a meeting detail has a half-life of about an hour. Deal Progression removes the excuse. It cannot remove a rep who never connected their inbox. HubSpot implementation done as Kernel work starts with every inbox and calendar connected, logging on by default.

4. Buying groups

Kernel layer. L3. Prerequisite: contacts associated to deals with role labels; team notes logged.

Type "help me break into" and an account name, and Breeze Assistant pulls deal history, existing contacts, emails, and your team's notes, then assembles the buying group and asks who you want to reach first. The drafts read like the rep wrote them because Context Home holds the rep's tone. Buying groups in Breeze is a public beta feature.

The prerequisite is association labels. A contact attached to a deal with no role is a name. A contact labeled champion, economic buyer, or blocker is a buying group. Most portals we open in a Diagnostic have the first and lack the second.

5. Revenue Agent

Agents layer. L3. Prerequisite: invoices in HubSpot; a written AR policy for tone, cadence, and escalation.

Revenue Agent, new and in public beta, follows up on overdue invoices with messages written for each customer, and it adapts as the thread unfolds. Duncan Lennox called it his personal favorite. It's also the one most Sales Hub customers can't switch on, because their invoices live in an accounting system HubSpot can't see.

The prerequisite is Revenue Hub with invoices, contracts, and payments in it. The AR policy is a prompt: how firm at 30 days, how firm at 60, who gets looped in and when. Write it once and the agent runs it. Our Revenue Hub onboarding is the setup that makes the agent possible.

Switch-on order, 30 days

Week 1. Connect every rep's email and calendar. Turn on Notetaker. Write exit criteria for each stage. Confirm amounts and close dates on every open deal.

Week 2. Breeze pipeline report, ranked by value and stage, every Monday. Deal Progression on one pipeline. Track the share of suggestions reps accept.

Week 3. ICP into Context Home. Intent signals on. One engagement-score property. One Prospecting Agent play against 50 target accounts, every send reviewed.

Week 4. If invoices live in HubSpot, Revenue Agent on everything past 30 days. If they don't, scope the Revenue Hub migration.

Other HubSpot features shipped for sales

• Deal Plans (public beta). A shared plan with milestones and owners the buyer can see. It's a buyer-facing surface, and it looks a lot like the deal room we run before a contract.
• Buyer Billing Portal. Customers see and pay invoices without emailing you.
• Buy Now, Pay Later. Klarna and Affirm on HubSpot Payments, US and Canada.
• Price books and quote rules. Segment pricing and discount guardrails a rep can't talk their way past.
• Contract management (public beta) and billing migration. Contracts as a native object, and a path to move them in.
• Breeze revenue context (public beta). Ask Breeze about MRR, renewals, and contract revenue and get the reporting answer.
• Customer Agent payment links and invoice support. The service agent can find an invoice and take a payment mid-conversation.
  
  

FAQ

What is HubSpot Deal Progression?

Deal Progression is a Sales Hub feature that reads the emails, calls, and meetings on a deal, then recommends next actions, drafts follow-ups, and proposes CRM updates for the rep to approve. It's the sales-facing part of what HubSpot calls the self-updating CRM, and it's in public beta as of September 2026. It needs logged activity to read, so email and calendar connection is the prerequisite.

What does Prospecting Agent need to work?

An ICP it can score against, a target account list, buying signals to watch, and a brand voice for the drafts. Teams that see results usually add a custom score built from their own engagement data. Without an ICP in Context Home, the agent targets the wrong companies, which is the mistake RevenueWell's Kim Cormier described making first.

What is HubSpot Revenue Agent?

Revenue Agent automates invoice follow-up. It sends personalized reminders on overdue invoices and adapts its messages as customers reply. It requires invoices to live in HubSpot's Revenue Hub, it's in public beta as of September 2026, and it works best with a written accounts-receivable policy that sets tone and escalation.

Does the self-updating CRM replace manual deal updates?

For activity, yes. Calls, emails, and meetings log themselves, and Deal Progression proposes stage changes and next steps from them. Reps still approve the updates, and fields that never appear in a conversation, like a closed-lost reason, still need a required property.

What are buying groups in HubSpot?

A buying group is the set of contacts involved in a deal, each with a role. Breeze Assistant can assemble one from deal history and notes, then draft outreach per stakeholder. The feature depends on contacts being associated to deals with role labels.

See where this lives in your intelligence layer. Or find your level first: book the Diagnostic.