Every few weeks someone in r/hubspot posts the same question. “Is anyone actually using Breeze AI for ops, or is this just a glorified email drafter?” The replies are always the same - a couple of people say they love the assistant for simple how-do-I questions, a couple more say they turned it off, and nobody seems to have pushed it past the edges of drafting copy.

I have been waiting for someone to write the honest answer, so here it is.

What Breeze is genuinely good at

Breeze is a copilot for HubSpot’s UI. If you want a workflow drafted from a prompt, or a report sketched from a sentence, or an email rewritten in your brand voice, it is a real improvement over clicking through the builder cold. The Breeze Assistant sidebar in particular is good at telling you where a setting lives when you cannot remember which of the nine settings screens it hides on.

That is not nothing. It is a better front door to HubSpot than the search bar used to be.

What Breeze cannot do

The minute you need ops work - the real stuff, not the drafting stuff - Breeze taps out. Here is what I mean by “real stuff”:

• “Why did the MQL count drop this week? Show me the twelve contacts behind the change.”
• “Which open deals are stuck because the phone number field is empty?”
• “Build me a pipeline with these six stages, these enter/exit criteria, and these three workflows hanging off stage transitions - and execute it.”
• “Find every contact with a duplicate email across two portals and write me a merge plan.”

These are not exotic requests. They are the questions ops teams answer every day. And Breeze cannot touch them, because Breeze was not built to read your rows - it was built to draw charts, generate copy, and nudge you toward the buttons that already exist in the UI.

That is a product decision. It is not a bug Breeze is going to fix in a point release.

What ops teams are reaching for instead

The pattern I see consistently is that the operators who want more than drafting help are wiring their AI assistant into HubSpot through MCP. They have given it direct read access to their portal. They ask questions in plain English and get back actual records - not summaries of dashboards. They draft changes in a conversation, and hand them off to execute.

This is the cyborg workflow I have written about before. And it is why we built Daeda AI.

The short version

If you only want to draft emails and ask “where is this setting”, Breeze is fine. If you want an AI that can read your actual CRM rows, reason across objects, and execute changes, you are going to need more than Breeze.

That is the gap Daeda AI fills. Take a look.