HubSpot's community team just published a breakdown of six things customers keep doing with the HubSpot connector for Claude. It's a great read and very helpful, but only if you are a HubSpot user deciding whether to turn the connector on. We sit on the other side of that decision - as a HubSpot Elite Partner and a member of Anthropic's Partner Network, we're usually the ones building the pipeline stages, lifecycle definitions, and custom properties that determine whether any of this actually works.
Claude reading your CRM is only as good as the CRM it's reading. Every one of the six use cases discussed depends on data that most portals don't have in the specific state Claude needs it to be effective.
Finding the revenue sitting in accounts nobody has time for. The long-tail problem is real - a minority of accounts get proper attention and the rest sit dormant, not because anyone decided that, but because coverage is a staffing problem nobody solves by hiring their way out of it. Claude reading engagement history against performance data can surface which of those accounts are worth a look and what to say. It only works if the engagement history is actually logged against the right record.
Seeing what's working across campaigns without an export. Campaign performance, landing pages, blog content - it's all sitting in HubSpot already. The shift isn't that Claude produces a report faster. It's that you can ask the follow-up question in the same conversation instead of waiting for someone in RevOps to pull it again.
Walking into a call already briefed. Two years of history on an account, and someone still has to piece it together from memory before a call starts in twenty minutes. This is the most consistently useful of the six, because it removes a task nobody enjoyed doing manually and nobody was doing well.
Logging the call properly, every time. CRM hygiene is the thing everyone agrees matters and almost nobody does consistently, because the gap between finishing a call and updating the record is wide enough that it just doesn't happen. Paste the notes, Claude finds the record, logs the engagement, moves the deal stage, creates the follow-up - with confirmation before anything writes. The output isn't a cleaner CRM for its own sake. It's a record accurate enough that the next person prepping for a call with that account gets something real to work from.
Knowing who's already a customer before you email them. Someone hands you a list - event attendees, an inbound batch, accounts a new hire brought with them - and every name on it gets treated the same by default. Checking each one against HubSpot first is the difference between a prioritised list and a generic one. Get it wrong and you're pitching a long-time customer like a stranger, or dropping a live deal into a cold sequence.
Seeing where the team's workload actually sits. Pipeline visibility and pipeline distribution aren't the same thing. Team memberships, seat assignments, deal counts and average deal age, cross-referenced in one conversation instead of pulled manually and stitched together - useful the moment velocity slows and you're not sure if it's the market or a coverage gap.
None of this is new capability from Claude. It's context that was always sitting in HubSpot, made reachable in a normal conversation instead of a report someone has to build. What determines whether it works is the same thing that determines whether any HubSpot implementation works: clean pipeline stages, a lifecycle definition everyone actually uses, properties named things a person would recognise. That's the accreditation work. Claude doesn't fix a messy portal - it just makes the mess easier to ask questions of, faster.
If your portal isn't in a state where these six things would return a straight answer, you’ve got yourself a data foundation problem. Worth running the Revenue System Audit before you spend time building prompts around a CRM that isn't ready to answer them.
If you want to have a go at seeing how to use Claude and HubSpot together, check out our Claude x HubSpot prompts guide.