Your HubSpot AI journeyStage 2 of 4

Your team uses AI. The answers still feel generic.

Most teams at this stage have ChatGPT, Claude or Breeze open every day. The problem isn't the tool. The AI doesn't know your customers, your tone or the way you sell, so everyone re-explains the business in every chat and gets a different answer.

Context before agentsOne version of the truthSkills your team signs off
Emma walking through a lead flow on the whiteboard
Quick self-check

This sounds like you if…

Tick what's true today. Nothing is sent anywhere. It's just a quick way to check you're reading the right page.

0 of 6 ticked
What's really going on

Everyone has AI. Nobody's AI knows the business.

When reps use personal accounts with no company context, the output is generic and the quality swings from person to person. Teams that set up one shared context see the difference straight away. We've watched the same prompt go from bland to genuinely useful once the context was in place. One sales leader called the difference night and day.

HubSpot now has a proper home for that context. Context home holds your business, customers and processes. Knowledge vaults hold the documents. Skills hold the way you like things done. Claude can read the CRM too, through HubSpot's own connector. The work is filling them with the right things, and keeping them right.

Wrong context is worse than none.

HubSpot at this stage

The context layer, in plain words.

Checked against HubSpot's knowledge base, November 2026.

Context home
What it doesYour business profile, products, brand kit, ideal customer profiles, personas and sales methodology, in one place every HubSpot agent reads.
PlansAll products and plans. Super Admins edit most sections.
CreditsNot on the credit-using list.
Our tip Filling it in properly takes about a day of focused work. Most portals we see are part done.
Knowledge vaults
What it doesPlaybooks, policies, pricing notes and guides attached to the agents that need them.
PlansBeta. Starter and above on most hubs, Smart CRM Professional and Enterprise.
CreditsNot on the credit-using list.
Our tip Put in what an agent should quote. Leave out anything you would not want a customer to read.
Breeze Assistant skills
What it doesYour processes written as instructions the assistant follows, like a deal review or a call prep, run with a slash command.
PlansAvailable with Breeze Assistant.
CreditsNot on the credit-using list.
Our tip Skills are plain text, not code, and the assistant only uses one when someone calls it. Name them so people remember.
HubSpot connector for Claude
What it doesClaude reads and updates your live CRM, under the permissions your admins set, with audit logs.
PlansAll plans.
CreditsNo HubSpot credits. Claude is licensed separately.
Our tip Set write tools to Needs Approval. The connector can't see Context home, so your context needs to live in Claude too.
From real portals

What this looks like in real teams.

From our own client work. Names left out on purpose.

Sales team

Same question, different answers.

Reps on their own AI accounts asked the same questions and got different answers, in different tones, with different next steps. Once one shared project held the ICP, the offer and the voice, the answers lined up.

The lesson Shared context beats better prompting.
Manufacturer

HubSpot's AI said no. HubSpot said yes.

A team was told by HubSpot's own assistant that their plan couldn't automate a form follow-up. It could. They'd nearly paid for an upgrade they didn't need.

The lesson Check plan and feature claims step by step against the knowledge base.
Services firm

Context home, three quarters done.

One team had started Context home and stopped about three quarters of the way through. Finishing it properly, with the ICP, products and sales process written the way the team actually talks, took a good day.

The lesson A day on context saves weeks of rewriting AI output. Then put a review date on it.
How we help

Four weeks, start to live.

This is the AI agent for HubSpot, fixed price.

Week 01
Discovery and definitions

Your ICP, voice, products and the words your team uses, agreed in one workshop. Access set up with the permissions you choose.

Week 02
Context and skills

Context home filled in. Knowledge vaults set up. Skills for tone, ICP, products and your CRM's own definitions, signed off one at a time.

Week 03
Connect and test

HubSpot connected to Claude and tested on your live deals until the output is something your team would have written.

Week 04
Train and hand over

Recorded training, a prompt playbook for each role, and a how-not-to-break-it guide. You own all of it.

What you leave with

Things you can point at, not a slide deck.

Everything is documented and owned by you. It keeps working whether or not we're still involved.

Context home filled in and reviewed, with a date on every source.
Five skills built around how your team actually works: tone of voice, ICP, products and services, definitions, and CRM structure.
HubSpot and Claude connected, with write actions set to need approval.
A tested starter playbook of prompts for each role.
A HubSpot health report, so you know what the AI is reading.
Your team trained, with recordings to onboard new starters.
Proof
45
tested prompts, five company skills, four departments using it

IXT started with a marketing team of one and an AI experiment that had gone nowhere. A 75/100 portal health check, five company skills signed off one at a time, and a 45-prompt playbook later, the CEO and CFO use it daily.

Read the case study →

Rikki and Mark working across two laptops
Where to start

The services that fit stage 2.

Published prices. Fixed before we start.

Ready for building momentum?

Ready to move on when
Your team gets consistent answers from AI.
Context home and your skills are filled in and owned by someone.
You can name one repeating job you would hand to an agent.
Not yet if
People still re-explain the business in every chat.
Nobody knows what's in the documents AI can see.
Your CRM data still needs the stage 1 fixes.
Common questions

Stage 2, answered straight.

Should we use Breeze or Claude?

Both, for different jobs. Breeze knows HubSpot inside out and runs HubSpot's agents. Claude goes deeper on analysis and writing, and works across email, calls, Slack and finance as well. HubSpot holds the context they share.

Can Claude see what we put in Context home?

Not today. HubSpot's connector gives Claude your CRM records, not the AI context. So we keep the same context in a Claude project as well, from one source, so they never disagree.

Can Claude change or delete our HubSpot data?

It can create and update records if you let it, with the same permissions as the person connected. It can't delete. We set write tools to Needs Approval, so nothing changes until a person says yes.

How long does it take to fill in the context?

About a day of focused work for Context home if your positioning is clear. Longer if it isn't, which is worth knowing too. Skills take a week or two, because your team should sign each one off.

Who keeps it up to date?

You do, with a named owner and a review date on every source. We train them. If you'd rather we did it, that's part of the Growth Partnership.

Make AI sound like your business.

Bring the prompts your team uses most. We'll show you what the same prompt returns once it knows your customers, your offer and your voice.

Book a 30 minute callNo sales team, no gatekeeper.
Rikki Lear
Rikki LearCommercial Director