Observed control coverage
One square per observed check · unavailable data is never scored as safe
Here's a mistake I made for years and watch other MSPs make daily: assuming clients care about security the way we care about security. We think in vulnerabilities, controls, attack surfaces. So we present in vulnerabilities, controls, and attack surfaces, and then wonder why the owner's eyes glaze before slide four.
Business owners don't lie awake thinking about CVEs. I've spent decades around SMB owners, sold to them, been one, and I can tell you what actually circles at 3AM. Am I wasting money I can't see? What happens if my key person quits? Could someone trick us into wiring money to a criminal? Am I going to get embarrassed in front of my customers? Will insurance actually pay if something happens? Is my data walking out the door? What did my people connect to our systems without asking? Would we survive a bad week?
Notice what those are. They're not technical categories. They're worries, in owner language, about money, people, embarrassment, and survival. One insight reorganized how I think about this entire business: every one of those worries can be answered from the same scan.
The data doesn't change. The lens does. One authenticated read of a tenant contains the spend-waste story, licenses assigned to nobody, premium tiers unused. It contains the key-person story, the concentration of admin roles and registered dependencies in one account. It contains the wire-fraud story, legacy auth, forwarding rules, unprotected finance mailboxes. The embarrassment story lives in email authentication, whether criminals can send as the company's own domain. The insurance story is the attestation map. The shadow-adoption story is the OAuth grant list. Same tenant, same consent, same collectors underneath. Eight different reports, because there are eight different anxieties reading them.
This changes how an MSP should open a relationship. Stop leading with your framework and start asking a genuinely better question: which of these keeps you up? Then hand the owner the report that answers their worry, not the report your tooling defaults to. The owner worried about waste gets the spend story first, and suddenly you're the vendor who found money. The owner who just watched a peer get hit with wire fraud gets the BEC exposure story, in plain language, with the fixes priced. You've met them where their anxiety actually lives, and everything after that meeting is easier, because they've experienced you as someone who listened before scanning.
The security-first framing was always backwards for this market. Security is our word. Worry is theirs. The scan was never really a security tool; it's an answer engine, and the skill is knowing which question you've been asked.
One scan. One consent. Eight worries, each with a factual answer. Start with the one written on your client's face.