Someone in the leadership meeting asks a simple question: how many active customers do we have? You know the answer is in HubSpot. You also know three different properties might hold it, two are half-filled, and one was created by an admin who left in 2022. So you say "let me get back to you" and spend the afternoon in exports.
That's the quiet tax of a portal nobody can see all at once. Every object, custom property and association was added for a good reason by someone, at some point. Nobody ever stepped back to look at the whole map. And now you're being asked to put AI on top of it.
If you're responsible for revenue clarity, that's an uncomfortable place to sit. You're supposed to have the answers. You're just not sure the system underneath you can give them.
Portals don't break all at once. They drift. A rep needs a field, so someone creates one. Marketing launches a campaign, so a new lifecycle workaround appears. An integration syncs in properties nobody asked for. A few years and a few admins later, you have hundreds of properties and objects that don't connect the way revenue actually moves.
Nobody did anything wrong. Each decision made sense on the day it was made. But disconnected systems and dirty data don't announce themselves. They show up as a forecast you have to caveat and dashboards that tell three different stories.
Good leaders make bad decisions when their data can't be trusted. That's a systems problem, not a people problem. And you can't fix a system you can't see.
Until now, seeing your whole portal meant a consultant clicking through settings for days, or someone exporting property lists into a spreadsheet. The HubSpot Agent CLI changes that. It's a command-line tool that lets an AI agent, such as Claude or ChatGPT Codex, connect to your HubSpot account and read its structure directly.
HubSpot's Ecosystem Mentorship Program built a hands-on workshop around it. The design choice I like most is the first rule: read-only. The agent doesn't create, edit, delete or import anything. It looks, it reports, and you decide.
That distinction matters. AI won't fix operational chaos; it accelerates it. Point an agent at your CRM and tell it to "clean things up," and you get confident, automated wrong answers, faster. Point it at your CRM and ask it to show you what's there, and you get something different. That isn't AI running your foundation. It's AI helping you finally see it.
The order matters more than the effort. Here's how to sequence it.
A starter prompt for step 1:
Using the HubSpot Agent CLI, build a read-only map of my HubSpot account. List every standard and custom object, its properties, record counts, and associations. Do not create, edit, delete or import anything. Save the result as hubspot-account-map.html.
If this order sounds familiar, it's the same one we follow with clients across 100+ HubSpot CRM implementations: understand the reality behind the CRM, stabilize the foundation, then operationalize growth and AI. The agent just makes the first step faster.
hubspot auth login) and let it handle access.api.hubapi.com. HubSpot's setup and IT requirements cover the details.Skip this step, and the portal keeps drifting. Your team keeps building spreadsheets on the side. And when AI gets layered on top, it scales whatever definitions and data you already have. Bad data doesn't get smarter. It gets faster.
Run it, and the next leadership meeting looks different. You know what's in the portal, which three things to fix first, and why. You're not defending the pipeline or reconciling three dashboards. You're the one with the map, and you can spend your time improving revenue instead of explaining reports.
Not ready to install a CLI? Start with the RevOps Foundation Scorecard. It takes five minutes and shows you where your foundation stands across all three steps, so you know where to start. Take the Scorecard →
Already ran the map and want a second set of eyes on what it found? Schedule a Call. We'll help you separate the cosmetic findings from the ones holding your revenue back.
AI Ready. Foundation First.