I was talking to the CEO of an MSP this week. Sharp guy. He tells me, “Yeah, I’m going to Galactic Universe. So’s my sales guy.”

I nodded… and waited.

“And your service manager?” I asked.

Silence.

“No, just us.”

I just about spit out my coffee.

Are You Kidding Me?

You’re about to spend two days learning how to communicate cyber liability like a pro. You’re going to be surrounded by conversations about security, lawsuits, insurance landmines, and how to build a defensible stack.

You’re going to learn how to sell it.

Position it.

Price it.

But who’s going to operationalize it?

Are you going to come home with a notepad full of security strategies and try to play a game of telephone with your engineer? “Hey man, so there was this session about how we’re all one lawsuit away from extinction and also we need DLP and a documented IR plan by next quarter—cool?”

Yeah. That’s going to land well.

Let’s Get Real for a Minute

You know who’s going to have to:

  • Build the program?
  • Deploy the stack?
  • Defend the framework when the client pushes back?
  • Be on the call when the data exfil alert goes off?
  • Keep your tail out of court with a trail of evidence?

Not you.

Not your sales guy.

Your engineer.

And if they don’t understand why you’re shifting your entire service model, if they don’t know what cyber liability even means, you’re setting them—and yourself—up to fail.

“But It’s Last Minute…”

Yeah. And?

So was the call that took down that 16-person firm. So was the zero-day that slid right past your EDR. So was the breach that landed an MSP with a $925,000 liability bill. Do you really think you’re going to win the liability game with half your team informed?

The CEO I talked to? I pushed him. Hard.

“Buy the ticket. Get your engineer to Universe.”

And guess what?

He’s doing it.

Today.

So What’s Your Plan?

Are you going to walk into Universe, get everything you need to fix your business, and then try to pass that knowledge down secondhand?

Or are you going to bring the person who actually has to implement it?

Let me put it another way:

If you don’t bring your engineer to Universe, you’ll spend the next 6 months translating the message—poorly—while trying to rebuild your services from memory and sticky notes.

Here’s the Move

If you’ve already committed to Galactic Universe, awesome.

Now bring your engineer.

Scramble. Shift. Do what you need to do.

Because if they’re not with you,

you’re not just missing a seat—you’re missing the win.

And if you haven’t grabbed your tickets yet?

Fix that now. 

You can’t build a defensible MSP without your service delivery lead understanding what they’re defending.