A quick observation
- There’s a surge of social discussion (LinkedIn, Twitter mainly) about connecting Claude to HubSpot for tasks that HubSpot already handles natively, often more effectively.
Why doing it inside HubSpot is often better
- HubSpot Assistant (or is it Breeze Assistant?) can query across your portal, create properties, pages, and lists, and act on deals/lists directly.
- Keeping it in-product means you can verify and sanity-check results against the actual record (activity log, properties, deal context). Doing it externally in Claude removes that visibility.
- Claude’s knowledge of HubSpot’s current capabilities is often out of date, so it over-engineers solutions that native features already cover.
An adjacent real-world example
- A client wanted to track link clicks on their website. They turned to Claude. Claude confidently advised them and generated custom JavaScript, manual footer implementation, and logging logic. And completely missed that the whole thing is achievable with HubSpot’s built-in Data Management > Event Management. No code, no maintenance debt.
Why the confusion exists
- HubSpot’s relentless promotion of agentic AI and its positioning as an “AI-enabled CRM” seems to overshadow education about the basics.
- Some Partners and the discussion ecosystem follow suit, amplifying MCP, ChatGPT, and Claude connector content while rarely covering what HubSpot can do on its own.
The problem
- Regular customers who aren’t developers or implementers get sold an obfuscation layer: they believe they need Claude (or ChatGPT, or another Marketplace integration) and the complexity that comes with it, to accomplish things HubSpot already does out of the box.
To be clear
- There are many legitimate agentic and developer use cases for Marketplace, MCP and Claude integrations. My comment isn’t that those don’t exist, it’s that the balance is off. The discussion ecosystem is top-heavy with agentic content and seems thin on practical, in-product capability reminders.
(First noted here)
