It’s here. Today’s the day.
Standardized is officially out in the wild, and if you’re reading this—I’m asking for a favor: go grab your copy, take it for a spin, and hit the session. I want your feedback. I want your truth. I want your war stories.
But also…I’m terrified.
Let me tell you a story.
A few weeks ago, one of the first CEOs to get an advance copy of Standardized texted me. “Hey man, I just finished it. Got some thoughts.”
Now, this guy runs a top-tier MSP. He’s built a security program that could teach a few three-letter agencies a thing or two. His opinion carries weight. Like—boardroom-or-firing-squad kind of weight.
And in that moment, staring at that text, my brain started doing what any rational security expert would do:
- Considered throwing my phone in a lake.
- Checked the calendar for an “unexpected malware outbreak” I could use as an excuse.
- Ran through every worst-case scenario like I was scanning an L1 pen test report written by a drunk AI.
He finally called. And I kid you not—I stood up, walked out my house, and paced in the driveway like a guy waiting for the results of a CISSP exam (IYKYK)
Because here’s the truth:
Writing this book meant taking everything I’ve learned helping MSPs escape disaster zones, packaging it into something useful, and then sending it off for judgment. Not exactly a relaxing experience.
The Good News? That CEO called me back and said this: “This book? It’s what I wish I had five years ago. It’s not easy. It’s not safe. It’s a punch to the gut—with a blueprint taped to the glove.” I exhaled for the first time in 24 hours. And then I realized—this wasn’t about me. This was about you.
Why You Need to Read It (Or At Least Steal This One Thing)
Here’s a taste:
Compliance Moves Slow—Hackers Move Fast (And Lawyers Move Even Faster)
You already know that compliance lags behind reality. Regulators don’t move quickly. They don’t push out new security standards the moment a new threat appears. They’re playing catch-up.
Hackers, on the other hand? They don’t wait for government approvals. They don’t hold committee meetings. They don’t draft policies, debate them, then revise them six months later. They just attack.
And while you’re waiting for compliance rules to update, while your clients are debating whether they really need to take security seriously, cybercriminals are already inside their network, selling their data, draining their accounts, and locking them out of their own systems. This is why MSPs who treat compliance like a shield—as if being compliant somehow means being secure—are walking directly into a lawsuit.
Because when something happens, compliance isn’t what protects you.
Evidence does.”
Sound familiar? It should. You’ve probably got half-built policy libraries. An IRP you started during the SolarWinds mess. A compliance roadmap sitting in Notepad++ like it’s a good luck charm.
This book is a call to arms for every MSP who’s done the 3AM-freakout wondering if that one missed patch is going to cost them a client (or a lawsuit). It’s not just theory. It’s field-tested, client-scarred, engineering-approved, no-BS guidance to build a standardized, scalable security program—without burning your techs alive or going broke trying.
What I’m Asking from You
If you’re reading this, you’re probably one of the MSPs we wrote this for. You’ve been in the war zone. You’ve seen what happens when compliance is a spreadsheet and security is “just run the scan, we’ll fix it later.”
I’d be honored if you’d do three things:
- Get the book (or just hit the session if that’s more your jam).
- Read one chapter. Just one. I dare you to stop there.
- Tell me what you think. The good, the bad, the “this feels like it was written by someone in a panic room with only coffee and trauma.”
Because this isn’t just my story. It’s ours.
This industry doesn’t need another vendor pitch, another “framework-as-a-service,” or another motivational poster with a firewall quote. It needs standardization that actually works—and a community of people willing to share what’s broken so we can fix it.
Let’s build it together.
Let’s standardize.
Let’s stop pretending this isn’t mission-critical.
Go grab the book. Get Started. Get Standardized.
