One of the quickest ways to create resistance in a co-managed conversation is to lead with tools.
Most MSPs do this without realising.
They talk about:
Monitoring platforms
Security stacks
Automation tools
Their tech ecosystem
That works in B2B.
It doesn’t work here.
Why this creates friction
An IT director already knows those tools exist. They may already be using them.
So when you lead with tools, it signals something else:
That you’re thinking tactically, not structurally.
And that’s not what they’re evaluating.
They’re not asking:
“What tools do you use?”
They’re asking:
Who owns what?
How does this fit into our structure?
What changes for my team?
How is risk controlled?
What to lead with instead
In co-managed, trust is built through structure.
So lead with:
Responsibility agreements
Defined boundaries
Escalation pathways
Governance
How you work alongside internal IT
Tools support the model.
They are not the model.
The simple rule
If your first instinct is to explain your stack, stop.
Start with structure.
That’s what makes you feel like a safe partner, not just another supplier.