Claude x HubSpot

How Sales Teams Use Claude in HubSpot

Deal reviews, call prep, post-call admin and prospecting: five ways sales teams use Claude in HubSpot, and what IXT's team did with it.

By Rikki Lear, Imagine Growth · 2 November 2026 · 9 min read

How Sales Teams Use Claude in HubSpot

Short answer: Sales teams get the most from Claude in HubSpot on the jobs reps put off: deal reviews, call prep, post-call admin and chasing old quotes. Claude reads the CRM, drafts the work and logs it back. A rep approves anything that goes to a customer.

What can Claude do for a sales team in HubSpot?

It does the prep and admin around selling, so reps spend more time in conversations. Through HubSpot’s connector, Claude can read your CRM and create or update deals, contacts, companies, leads, tasks, notes, calls and meetings, according to HubSpot’s connector guide. It can read quotes too (creating and updating them is in beta).

It only sees what the connected user can see. A rep’s Claude sees that rep’s view of HubSpot.

Every create and update also lands in HubSpot’s audit log, credited to both the rep and the Claude connector. So a manager can always see what changed and who asked for it.

For the full list of capabilities and limits, see what can Claude actually do inside HubSpot?

Which sales jobs should you hand to Claude first?

The ones that are repetitive, internal and easy to check. Here are five, in the order we’d usually build them.

Job What Claude does Who checks it Risk
1. Deal review Reads open deals, flags stalled ones, missing next steps and close dates in the past Sales manager Low, internal only
2. Call prep Pulls the company record, deal history, last notes and recent news into a one-page brief The rep, before the call Low
3. Post-call admin Turns the rep’s notes into a HubSpot note, next-step task and updated deal stage The rep Low to medium, writes to the CRM
4. Dormant quote follow-up Finds quotes nobody chased and drafts a follow-up for each The rep, before sending Medium, customer-facing
5. First-touch prospecting Researches a target account and drafts a personalised first email The rep, before sending Medium, customer-facing

Numbers 1 to 3 never touch a customer. That’s why they come first. Your team learns how Claude behaves before anything leaves the building.

1. Deal review

Ask Claude for every open deal with no activity in 14 days, no next step, or a close date that’s already passed. It comes back with a list and a reason for each.

Tell it what “stalled” means for your team (14 days, 21 days, no meeting booked). Otherwise it’ll pick a rule for you, and it might not be yours.

Managers stop scrolling through pipeline boards on a Monday. The conversation starts with the deals that need it.

2. Call prep

A rep asks for a brief on the company they’re meeting at 2pm. Claude pulls the record, open deals, the last few notes and anything public worth knowing (that last part needs web search switched on in Claude).

One page to read, instead of six tabs to click through.

3. Post-call admin

The rep pastes rough notes. Claude writes a clean note on the deal, creates the follow-up task and suggests a stage change.

With write tools set to Needs Approval, the rep confirms each change before it lands. And HubSpot’s own rules still apply: if a stage needs a field filled in before a deal can move, Claude hits the same validation a rep would.

4. Dormant quote follow-up

Plenty of portals have quotes nobody chased. Claude can read your quotes, find the ones with no follow-up since they went out, read the deal context and draft a chase for each.

The rep edits and sends.

5. First-touch prospecting

Claude researches each contact from their website, news, LinkedIn and CRM history, then drafts an email that opens with something specific to them.

Keep the volume low at first and keep the rep in the loop. This is the job where a bad draft costs you a relationship.

A sales meeting with a laptop on the table

What happened when IXT put Claude in front of their team?

IXT is a global IoT and SIM connectivity operator. In April 2026 they had a marketing team of one and a Claude experiment from a year earlier that had gone nowhere.

We built them a Super Agent: Claude connected to HubSpot, with company skills signed off one at a time and a 45-prompt playbook. Five months later:

  • Deal review, call prep and a board summary run on demand.
  • 5 working processes run on it (prospecting, CRM hygiene, campaign build, content and reporting). None existed in April.
  • 4 departments use it: marketing live, the CEO and CFO using it, sales and development onboarding.
  • Ingunn, their CMO, built lead gen herself on it: a 22,000-row spreadsheet reduced to around 500 genuinely unique companies, scored against the ICP and handed over 10 a day with records, owners and draft emails. It was booking meetings inside three days.
  • 800 companies with no industry were fixed with 300+ approved corrections in an afternoon.

IXT has since bought the next phase.

“Now that it’s so connected to our HubSpot, it knows exactly what to do. It’s all factually correct. It’s kind of spot on.”

Ingunn Bjøru, CMO, IXT

The full story is in IXT Super Agent.

Where Breeze was the better fit

Here’s the bit worth catching. For high-volume first-touch outreach, IXT runs HubSpot’s Breeze prospecting agent, not Claude. It researches every contact and drafts a personalised email in each rep’s name and language. It never sends without approval.

Result (Breeze prospecting agent) Figure
Response rate 10.29%
Emails sent 324, around 108 per rep
Leads engaged per rep 9.5
Days to first outreach 3.6
Dormant quotes One rep’s 84 chased in a single afternoon of review

Reps who started sceptical asked to expand it into ABM. The full story is in the IXT prospecting agent case study.

I’d still pick Claude for the analysis and admin around a deal, and Breeze when the job lives entirely inside HubSpot’s own prospecting tools. The side-by-side is in Claude vs HubSpot Breeze.

What should a sales team not hand to Claude yet?

Anything that sends to a customer without a person in the loop. Claude drafts. A rep sends.

A few other limits to plan around:

  • Claude can’t delete records. Duplicate clean-up still needs a person in HubSpot.
  • It creates or updates up to 10 records at a time. Bigger data fixes need a different approach.
  • If Sensitive Data is on in your portal, Claude can’t read engagement data (calls, emails, meetings, notes and tasks). That rules out call-note summaries and anything built on past calls, emails or meetings.
  • Ask for a sequence or a workflow and you’ll get the steps and copy to build yourself. Claude doesn’t build HubSpot workflows.
  • Claude can schedule and publish HubSpot marketing emails if the marketing email scopes are switched on. Keep write tools on Needs Approval so nothing goes out without a click.
  • Forecast calls belong to managers. Claude can point at risk, but it shouldn’t own the number.

How do you roll this out to a sales team?

Small, then wider. This is the four-week shape we use.

  1. Week 1: approvals. A HubSpot Super Admin approves the connector. On Claude Team or Enterprise, an Owner enables it for the organisation. Write tools go on Needs Approval. Pick one manager and two reps.
  2. Week 2: deal review only. Run it every Monday and check it against what the manager already knows.
  3. Week 3: call prep and post-call admin for the same reps. Skim the audit log for anything odd.
  4. Week 4: decide. If the reviews are right and the reps are using it, add the next job and the rest of the team. If they’re not right, look at the data before you rewrite the prompt.

What has to be true in HubSpot first?

Clean deal stages, real owners and logged activity. Claude reads what’s there. If reps don’t log calls, Claude can’t tell you a deal’s gone quiet.

Run through the 10-point HubSpot AI readiness test before you start. If it flags gaps, how to prepare your HubSpot data for AI covers the fixes.

Want to see which sales jobs Claude could take on in your HubSpot? Free until 12 January, book a 30-minute Day One session. We look at your HubSpot live with Claude, then send you the three fixes worth making first, in writing, within 48 hours. Want it built for you? Our AI agent for HubSpot is live in four weeks, at a fixed price, with a person approving every customer-facing output.

Frequently asked questions

Can Claude update deals in HubSpot? Yes. Through HubSpot’s connector, Claude can create and update deals, tasks, notes and other records. It can’t delete them. Set write tools to Needs Approval so a rep confirms each change.

Can Claude send sales emails from HubSpot? Not one-to-one sales emails. It drafts them, and it can log an email to a record. Sending stays with the rep. It can schedule and publish HubSpot marketing emails, which is another reason to keep write tools on Needs Approval. In our builds, every customer-facing email waits in a review queue until a rep approves it.

Will each rep see the whole CRM? No. Claude sees what the connected HubSpot user can see. Rep permissions carry straight through.

Can managers see what Claude changed? Yes. Every create and update shows in HubSpot’s audit log, credited to the user and the Claude connector.

Which HubSpot plan do sales teams need? The connector works on any HubSpot subscription. Each rep needs a paid Claude plan and an active HubSpot user. A Super Admin approves the connector first, and on Claude Team or Enterprise an Owner enables it.

How is this different from HubSpot’s own AI? Breeze lives inside HubSpot. Claude works across HubSpot and your other tools. IXT uses both. We compare them in Claude vs HubSpot Breeze.

Keep reading