Service · capability
AI Enablement
Four weeks teaching the person who owns your HubSpot portal to do the admin work AI can genuinely help with — and to verify it before it writes. We leave the capability with your team instead of the dependency with us.
The method
Describe, plan, check and approve, verify
Four steps your admin applies to every piece of portal work. The third one is what separates this from prompt training, and it’s the one everyone else leaves out.
Describe
State the outcome in business terms before touching anything. Most bad CRM work starts as a vague instruction, not a bad execution.
Plan
Get the proposed change written out in full — the properties, the records affected, the order of operations — before anything runs.
Check and approve
A human reads the plan and approves it. The model is often confidently wrong about your pipeline, and this is the step that catches it. Nothing writes to the portal without passing through here.
Verify
Confirm the change did what it said on a sample of real records. Not “it ran without an error” — did it produce the outcome you described in step one.
Scope
Portal admin work, not customer-facing AI
HubSpot’s Breeze agents handle the customer-facing side, and they do it well. We work on the part they don’t: building, cleaning and restructuring the portal itself.
In scope
The admin gap
Property architecture, workflow builds and rebuilds, list logic, data cleanup and normalisation, pipeline and lifecycle structure, reporting setup, bulk changes done safely.
Out of scope
Anything Breeze already does
Prospecting agents, customer agents, content agents. If HubSpot ships it, use HubSpot’s version — we’re not going to sell you a worse copy of something included in your licence.
How it runs
Four weeks, six hours a week, on your real backlog
Deliberately spread rather than compressed. The learning happens in the gaps between sessions, working on your own portal, not in a workshop room.
- Week one — the method on one real taskWe pick something from your actual backlog and run the four steps together, slowly, with the reasoning said out loud.
- Week two — they lead, we watchYour admin runs the next task. We interrupt only at the approval step, which is where it usually goes wrong first.
- Week three — harder work, and the failure modesBulk operations, anything touching records at volume, and a deliberate look at what a confidently wrong plan looks like before it runs.
- Week four — their own checklistThey write the approval checklist in their own words, for your portal. That document is the deliverable that outlasts us.
Fair warning
This only works if there’s a person
- You need a named someone who owns the portal and has roughly a day a week for it. Capability without time doesn’t stick.
- If the portal is orphaned, or belongs to a sales manager on Fridays, don’t buy this. Ask us to do the work instead.
- If your findings are one-off cleanup — four thousand duplicates to merge — that’s a job, not a capability gap.
- We’ll want to meet the person being trained before you buy. If we haven’t met them, we’ll say no.
“CogniOps provided hands-on training and left the team with instructional step-by-step videos that were helpful as each seller moved through execution.”Ben FursmanHead of Sales · Excite Cyber · Cybersecurity
Start by finding out what’s actually wrong
Most Enablement engagements follow a Leak Report, because the findings tell us what your admin should learn first. Start with the free Check.