If you're a marketing agency, founder, or RevOps engineer trying to implement AI inside HubSpot, you’ve probably felt this already:
AI sounds powerful… but the results? Meh.
Workflows break. Data gets messy. Outputs feel generic. And suddenly, AI feels like more work instead of less.
We recently sat down with Trisha Merriam, a marketing expert who has worked extensively with HubSpot and AI integrations, to unpack where things go wrong — and more importantly, how to fix them.
Most teams think they are ready for AI because their CRM is “clean.”
They’ve got:
But according to Trisha Merriam from SWOPtimize, that’s only scratching the surface.
AI doesn’t just need clean data. It needs context.
That means documenting:
If this isn’t documented, AI simply doesn’t have enough information to work with.
And when AI lacks context, it doesn’t fail loudly, it fails quietly with mediocre results.
You’ve probably heard this before:
“We tried AI… it didn’t really work.”
In most cases, the problem isn’t AI.
The problem is missing inputs.
As Trisha explained, when teams don’t provide enough context, AI outputs feel generic, irrelevant, or just plain wrong.
So instead of fixing the inputs, teams abandon the tool. That’s like blaming Google Maps… without entering a destination.
One of the most interesting moments in our conversation was when Trisha shared a real-world example. She used AI (Claude) to clean up a messy contact list before importing it into a CRM. Sounds smart, right?
Until this happened:
Yes. AI literally changed people’s names. Why? Because there were no guardrails defined.
Once she added a simple rule:
“Never change first name, last name, job title, or email”
The issue was fixed in seconds.
Lesson: AI is powerful, but without constraints, it can confidently do the wrong thing.
Most teams jump straight to tools.
But the real order should be:
If you skip the first three, the tool won’t save you.
Some simple guardrails to start with:
Here’s something most people don’t talk about:
AI is a skill, not a switch.
According to Trisha, the teams that succeed are the ones that:
Because honestly?
A lot of things don’t work at first.
But over time, you start understanding:
One of the most practical insights from this conversation:
Don’t learn AI alone. Trisha recommends creating small “learning cohorts,” groups of people at the same stage in their AI journey.
Why this works:
Think of it as shared experimentation.
Let’s address the big question.
Should you use HubSpot Breeze or external AI tools?
Why?
For example, Breeze can:
That said… it’s not perfect.
It’s improving fast, but still a bit of a “mixed bag.”
Best use case: Understanding your data
Not ideal for: Complex workflows or advanced automation
Once you:
Then tools like ChatGPT or Claude become incredibly powerful.
But jumping to them too early?
That’s where most teams go wrong.
If we had to simplify everything into a process, it would look like this:
Most likely because your data and processes are not properly documented. AI needs context, not just clean fields.
It’s a great starting point. Especially for data insights and quick wins. But you may need third-party tools for advanced use cases.
Provide better inputs: clear documentation, structured prompts, and defined constraints.
AI in HubSpot isn’t magic. It’s leverage. And like any leverage, it only works when the foundation is strong. If your processes are messy, AI will amplify the mess. But if your foundation is solid?
AI becomes a force multiplier for your entire revenue engine.
Big thanks to Trisha Merriam for sharing her real-world insights and experiences.