There is a quiet thing happening in RevOps circles. Every couple of weeks, someone posts about giving their AI assistant direct access to their HubSpot portal. “The instruction file that replaced my analyst.” “How we defined our revenue operations as a set of docs an AI reads from.” People are figuring out that if you give AI the right context, it stops being a chatbot and starts being a useful ops tool.

I have been running that setup for months. Here is what it looks like, why it works, and what you need to set it up.

The setup

Four things.

1. An AI assistant that supports MCP - Claude Desktop, Cursor, or any MCP-compatible tool. You connect it to external data sources through MCP servers, and it can read, reason, plan, and act.
2. Daeda AI - our HubSpot Marketplace app. Its Automation Suite connects your AI assistant to your portal data. Read queries in plain English, write actions through human-approved Write Plans, cross-object reasoning, multi-portal support.
3. A folder with your ops context in it. Not code - just documents. Your segmentation logic, your lifecycle definitions, your naming conventions, your pipeline rules, your workflow inventory. Written down once, so the AI starts every session already knowing how your team works.
4. An instruction file that tells the AI how your team thinks, which tools to prefer, and what “done” looks like for common ops tasks.

That is it. No coding. No custom integrations. No orchestration platform.

What it feels like to use

You open your AI assistant. You type “the MQL count dropped this week - find the twelve contacts behind the change and tell me which workflow dropped them.”

The AI reads your instruction file, sees you have Daeda AI connected, queries the synced data from your portal, finds the drop, cross-references workflow enrollments, and gives you an answer with the contact IDs. Not a summary. The actual records.

You follow up. “Build me a new workflow that catches this before it happens again. Enrollment criteria: lifecycle becomes MQL and no email engagement in fourteen days.”

The AI drafts a Write Plan. You read it. You tweak the criteria. You approve it inside Daeda AI in HubSpot. It executes.

The whole exchange is under five minutes. The equivalent in the HubSpot UI is a morning.

Why it works

Two reasons people miss.

First, the context is always loaded. When your segmentation logic and naming conventions are written in documents your AI reads at the start of every session, you stop re-explaining. The AI is not a stranger every time you open it. It already knows your lifecycle stages, your pipeline rules, and your team’s way of working.

Second, the data layer is always ready. Daeda AI’s Automation Suite syncs your portal data to a managed database. That means your AI can scan thousands of records in one query without hitting the HubSpot API mid-conversation. You can ask “every deal where the close date has been pushed more than twice” and actually get an answer - not a timeout or a surface-level summary.

This is what people mean when they talk about AI-powered RevOps. It is not about writing code. It is about giving AI the same depth of context about your operations that a senior team member would have.

What you need to start

• An AI assistant that supports MCP - Claude Desktop, Cursor, or similar
• Daeda AI installed on your HubSpot portal, with an MCP license key from Master Settings
• A folder with your ops context written down - lifecycle definitions, naming conventions, pipeline rules
• A willingness to document your playbook once, so you never have to re-explain it

That last one is the part people skip, and it is the part that makes the whole thing work.

The short version

The RevOps teams getting real value from AI are not waiting for HubSpot to build it all natively. They are connecting an AI assistant to their portal through Daeda AI, writing their ops context down once, and running actual operations through conversation.

If you want the HubSpot piece already built, that is Daeda AI. The context documents are yours to write - and they are the part that makes everything click.